Supplier Statement Reconciliation Automation

The process nobody has time to finish

Supplier statement reconciliation is the clearest example in finance of a task that is unambiguously worth doing and almost never done completely. The method is simple: take the statement, take your ledger, and find the differences. The obstacle is that doing it properly for every supplier, every month, is more hours than the team has.

So it gets rationed. The biggest twenty accounts, or the ones where something went wrong last time. Everything else is reconciled when a supplier complains, which means the credit note you were owed eighteen months ago is now a credit note you will never claim.

What replaces it

Statements collected from wherever they arrive — email, portal, post-scan — and normalised into a common shape regardless of the supplier’s layout.
Matched to the purchase ledger on invoice reference, value and date, with fallbacks for suppliers who reference nothing usefully.
Differences classified by cause rather than listed: not received, not posted, not paid, not applied by them, disputed, or timing.
Duplicate payment candidates raised before the payment run, which is the only point at which raising them is cheap.
Credits you are owed but have not taken surfaced as a working list rather than discovered by accident.
Every account reconciled every cycle, because the marginal cost of the twenty-first supplier is no longer a person’s afternoon.

The control question

This reconciliation is the completeness check on your purchase ledger. If it is only performed on a sample, then the assertion that your creditors are complete rests on a sample too — which is a reasonable thing for an auditor to ask about and an uncomfortable one to answer honestly.

Automating it does not just save the hours. It converts a partial, informal control into a complete and evidenced one, with a record of what was reconciled, when, and what was outstanding at the time.

The unglamorous case for doing this first. Of the processes on this site, statement reconciliation is the one most likely to find money that is already yours — unclaimed credits, duplicate payments, invoices billed twice. It is rarely anyone’s favourite candidate, and it is frequently the one with the shortest payback.

Common questions

Our suppliers send statements as PDFs, and some as images.

That is the normal case and it is workable. The harder problem is not reading the document, it is that no two suppliers lay one out the same way, reference invoices differently, or agree on what a credit looks like. Handling that variation is most of the build.

We only reconcile our largest suppliers. Is that not enough?

It is a reasonable manual compromise, and it is exactly the compromise automation removes. The reason smaller accounts get skipped is cost per account, not risk per account — and duplicate payments do not preferentially occur on large suppliers.

What do we do with the differences it finds?

Each one is categorised by cause — invoice we never received, invoice we have but have not posted, payment they have not applied, credit note in dispute, timing. The category determines who acts, which is what turns a list of differences into work anybody can pick up.

See it against your own process

The quickest way to know whether this is worth doing is to walk one of your own processes through it. That is what the Finance Automation Review is —one week, ending in a ranked build plan.

A first call needs nothing prepared and no system access. We reply within one working day.