Supplier statements: the 15-minute check that stops duplicate payments

Most duplicate payments are not fraud. They are the same invoice arriving twice, once by email and once through a supplier portal, or a paper copy landing on a desk after the emailed version was already entered. The supplier gets paid twice, the error surfaces months later at year end, and recovering the money takes far longer than preventing it would have done.

A monthly supplier statement reconciliation stops most of this. It is a short, regular habit: take the statement the supplier sends, tick it against your own purchase ledger, and query anything that does not match. For most suppliers this takes about fifteen minutes.

Start with one entry point for invoices

Duplicates begin at the point of entry. If invoices can arrive by email, through a portal, by post, and by a photo in a messaging app, the same invoice will eventually be entered twice by two different people, or by the same person on two different days.

Pick one channel and make it the rule. Every supplier invoice goes into one inbox or one upload folder, and nothing is entered from a personal inbox or a forwarded photo. When a supplier sends the same invoice twice, the second copy is easy to spot because it lands in the same place as the first.

Invoice numbers matter here. Enter the supplier's invoice number exactly as printed, every time. A system that lets staff invent their own references, or leave the reference blank, makes duplicate checking nearly impossible, because the same invoice can sit in the ledger under two different numbers.

Match before you pay, not after

The second control is matching. Before any invoice is paid, it should be matched to something that proves the spend was authorised and the goods or service were received. Where there is a purchase order, match the invoice to the order and to the delivery record. Where there is no order, match it to an approved spend, a contract, or a named approver.

The matching check should include three fields: supplier, invoice number, and amount. Checking only the amount is not enough, because two different invoices from the same supplier can easily be for the same amount. A simple rule works for small businesses without a formal approval workflow: no invoice is paid unless one named person has approved it and the approver is not the person who entered it.

The monthly statement routine

Even with good entry and matching, duplicates still slip through. That is what the statement reconciliation is for. Once a month, for each regular supplier, take the supplier statement and tick every line against your purchase ledger. There are only four possible outcomes for each line, and each one has a clear action.

First, the line matches an invoice in your ledger and a payment you have made. Tick it and move on. Second, the line is an invoice in your ledger that you have not yet paid. That is normal, and it confirms your outstanding balance. Third, the line is on the statement but not in your ledger. That is either an invoice you never received, which needs chasing and entering, or a duplicate the supplier has raised in error, which needs querying. Fourth, a payment in your ledger does not appear on the statement. That is either a timing difference, a payment allocated to the wrong account, or a payment the supplier has not processed, and it needs a query before the next payment run.

Do the reconciliation in the first week of the month, not at year end, and query every unmatched item in the same week. An unmatched item left for three months becomes a dispute. An unmatched item queried within a week is usually a simple correction.

Keep an exceptions list, and review it before paying

Every reconciliation produces a short list of exceptions: disputed invoices, missing credit notes, payments the supplier has not allocated, and invoices that arrived after the statement date. That list should be written down, owned by one person, and reviewed before the next payment run.

The rule that makes the list work is simple: nothing on the exceptions list is paid again until the exception is resolved. A disputed invoice is not paid a second time while the dispute is open. A credit note that has not been posted is chased, not ignored. A payment the supplier has not allocated is queried, not re-sent. Most duplicate payments happen because nobody remembered that the item was already in dispute.

When to hand the purchase ledger over

If supplier statements are piling up unreconciled, if duplicate payments have already happened, or if the purchase ledger depends on one person who is also approving the payments, the routine is telling you something. The control is failing because nobody owns it, and that is a staffing and process problem, not a software problem.

An outsourced accounts payable routine brings the entry, matching, and reconciliation steps as a single monthly process, with separation between entry and approval built in. See our guides on accounting outsourcing services and accounts payable outsourcing services for what that monthly routine looks like in practice.

Duplicate payments are rarely dramatic. They are quiet, small, and repeated, and they add up to real money over a year. One entry point, matching before payment, a monthly statement check, and an exceptions list reviewed before every payment run.