P a y m e n t s   P r o c e s s i n g

ECS debit and credit, NEFT and NECS, direct debit and direct credit instructions, electronic bill presentment files, online payment settlements and physical cheque volumes. Where a client runs several of these against the same customer base, we prefer to take them together — the mandate validation and reconciliation logic is shared, and running them in one operation removes a whole class of cross-instrument mismatch.

The file does not go out. Control totals are checked before file generation precisely so that an unbalanced batch is caught inside our four walls, where it can be investigated, rather than at the clearing house, where it becomes your problem. The batch is held, the variance is traced to the instruction, and you are notified with the cause before the cut-off if the timing allows, and immediately after it if it does not.

They are worked, not filed. Each return is categorised by reason code, actioned according to rules you define — represent, suspend the mandate, refer to your team — and carried in a queue with a visible age. The reporting pack breaks returns down by reason so that a rising trend in one category is obvious well before it becomes a collections problem.

Yes, and for payments work it is often the better arrangement. Processing directly in your application over controlled access keeps the data in your environment and the audit trail in one place. Where that is not practical we process in ours and return output in your format, with the reconciliation performed on both sides. The choice is made at scoping and tested during the parallel run.

Volume and value presented, accepted and returned; returns by reason code; exceptions outstanding with their age; accuracy sampled by our independent quality team; and turnaround against the agreed cut-off. It arrives on your cycle, in the format you asked for, without you having to request it. If you need a cut we do not currently produce, we add it rather than explain why the standard pack is sufficient.