Supplier statement reconciliation: what an agent can match

The statement arrives and somebody has to tie it up

A heating and plumbing firm we talk to runs trade accounts at three merchants. On the fourth of the month the statements land, two by email and one still on paper. One of them says the account stands at £14,206.80. The purchase ledger says £11,930.55.

Nobody has done anything wrong. Somebody now has to prove that, line by line, before the account goes on stop.

That job is supplier statement reconciliation: taking the statement of account a supplier sends and tying every line on it back to what your own books say you owe. It is dull, it is a genuine financial control, and in a business with five to fifty staff it usually lands on a bookkeeper who comes in two days a week, or on an office manager doing it between other things.

It is also the job most often left half done. Not out of carelessness. A statement with sixty lines on it takes an hour to tick off by hand, the difference is almost always innocent, and there is a customer on the phone. So the big accounts get reconciled, the small ones get a glance, and the one duplicate payment of the year sits in a supplier's cash for eleven months.

This is a guide, not accounting or legal advice. Check anything that matters to your business with your accountant.

Why does my supplier statement never match my purchase ledger?

Because the two documents are written on different days from different sides of the same trade. Your ledger records an invoice when you post it; the supplier records it when they raise it. Payments in transit, credit notes not yet issued and pro forma invoices all sit in the gap. A matching balance is the exception.

Once you have seen a few hundred of these, the differences sort themselves into a small set. Timing, on both sides. Credit notes the supplier has agreed on the phone and not yet put on the account. Carriage charged on the statement and never invoiced separately. A payment allocated to the wrong invoice number because someone typed 1 for I. Transpositions: £1,450 posted for £1,540.

None of that is interesting. All of it has to be looked at anyway, because the two or three lines that do matter are hiding inside sixty that do not. That is the shape of the job, and it is exactly the shape a machine is good at.

Which differences clear themselves?

Most of them, if you wait a fortnight. A payment in transit lands. A credit note gets issued. The next statement opens on a balance that agrees. The risk is not that these differences exist. It is that nobody separates them from the ones that will not clear, so the real problem ages quietly.

That is how a whole statement ends up filed under 'probably fine'.

Can an AI agent reconcile supplier statements on its own?

It can do the matching on its own. It should not do the deciding on its own. An agent reads the statement, pulls the supplier's account from your accounting system, matches on invoice number and amount, and produces a reconciliation with the agreed lines cleared and the rest set out with a reason. A person approves what happens next.

That division is not a limitation to be engineered away. It is the point. Matching is arithmetic against a reference, which machines do faster and more consistently than any of us at four in the afternoon. Deciding what a difference means is judgement about a commercial relationship, and it has consequences that are hard to reverse.

In practice the agent works on your own systems rather than a copy of them. It reads the statement out of the mailbox it was sent to, including the scanned one, and works against the live purchase ledger in Xero, QuickBooks or Sage, so the reconciliation reflects what the books say this morning rather than at the last export. Everything it does is logged: what it matched, on what basis, and how confident it was.

How would I know it got it right?

You watch it before you trust it. Every agent we build runs in shadow mode first: for several days it reconciles every statement that arrives and hands the result to whoever does the books, who compares it against their own tick-off. If the two agree for a week, you have evidence rather than a demo.

If they do not, you have found out cheaply, before it went anywhere near a payment run.

The three differences worth the whole exercise

An invoice on the statement that is not in your ledger. Either it never arrived, or it arrived and was never posted, or it is not yours. All three need a person, and the third is the one to take seriously. An invoice from a supplier you do not recognise, or a familiar supplier's invoice carrying bank details that have changed, is how invoice fraud reaches a business.

UK Finance's Annual Fraud Report 2026 puts invoice and mandate scam losses at £41.3 million in 2025, the lowest since 2020, and notes that 68 per cent of that, £28 million, fell on business rather than personal accounts. Their own explanation is the uncomfortable one: businesses make genuine high-value payments often enough that a fraudulent one does not stand out. Slightly under half of those losses, 48 per cent, were returned to the victim.

A payment you have made that the supplier has not applied. Your money is sitting on their account unallocated while an invoice shows as overdue and your account edges towards being stopped. This one is worth catching the same week, and it is a phone call, not an accounting entry.

The same invoice paid twice. It happens when a supplier sends a copy, when a statement gets paid alongside the invoices that make it up, or when two people pay the same email on the same day. Nobody notices, because a payment going out twice does not break anything. It shows up as a credit balance sitting on the supplier's account, and it stays there until someone asks for it back.

That third one is the argument for reconciling the small accounts as well as the big ones. Weighting by spend is sound advice for an accounts payable team rationing its hours. If the hours are no longer the constraint, the reason to skip an account goes with them.

What the agent is not allowed to do

Four things, and they are the same four we hold to across every agent we build, set out in what an agent should never do without asking. They are not settings. They are how we build custom automations at all.

It does not pay. A reconciliation can propose a payment run; releasing money is a person's decision with a person's name against it.

It does not write off a difference. A £4.80 gap is almost certainly carriage, and 'almost certainly' is not a standard to apply to someone else's ledger without telling them.

It does not agree the statement with the supplier. Confirming a balance is a commercial act. The agent prepares the reconciliation and says what it would confirm; a person sends it.

It does not open a dispute. If a line looks wrong, the agent drafts the query with the evidence attached and leaves it for someone to read before it goes. Suppliers are relationships, and the first message about a disputed invoice sets the tone of the conversation that follows.

Do I need every invoice, or is the statement enough for VAT?

Usually you need the invoices, and there is a narrow exception. HMRC's record-keeping notice for VAT, Notice 700/21, allows you to record the totals from a supplier statement rather than the individual invoices, on two conditions: every supply on the statement falls in the same VAT return, and the statement shows the total VAT charged at each rate.

Read that again from the agent's point of view. Where a business relies on that exception, the statement stops being a cross-check on the ledger and becomes the accounting record itself. A line matched wrongly is then a wrong VAT return rather than an untidy account. HMRC also expects business records to be kept for at least six years, which means the reconciliation the agent produces is not a working paper to be thrown away at month end. It is part of what you would hand over if anyone ever asked.

That is also where this job stops and another one starts. Matching a statement to a ledger is not the same as deciding how a transaction should be treated, which is the argument in AI bookkeeping: coding versus judgement. An agent can tell you the line on the statement is your invoice. It cannot tell you what rate belongs on it.

Where the spreadsheet is still the right answer

Be fair to the free template. If you have four suppliers and forty lines a month, the Excel sheet you can download in ten seconds will do this job properly, and building anything is a poor use of your money. The honest test is volume and spread: how many accounts, how many lines, and how many of them get skipped in a normal month.

The same goes for a good bookkeeper. Nobody who already reconciles every statement every month needs an agent to do it for them. What they sometimes want is the hour back, and that is a different conversation with a different answer. Working out which of those you are is most of what our AI roadmap fortnight does, and it regularly ends with us saying the job is not worth automating yet.

What to do next

Pull the last three statements from your largest supplier and find the closing balance on each. Then find the same three dates in your purchase ledger. If all three agree, this is not your problem and you can stop reading. If they do not, write down what the difference was made of each time. Ten minutes of that tells you whether you have a timing pattern, which is fine, or a matching pattern, which is not.

Then do the same for the smallest account you have. That is usually where the twice-paid invoice is.