Supplier statement reconciliation, done before the supplier chases you
Supplier statement reconciliation compares what a supplier says you owe with what your accounts payable ledger says you owe, line by line, and explains every difference. An AI agent working inside your ERP or ledger can read each statement, match it to your records and sort the differences by cause, so your AP team spends its time on the ones that need a decision. The agent proposes and a person approves.
Many finance teams aim to do this monthly. Doing it for every supplier takes effort, because the work is tedious: statements arrive as PDFs, spreadsheets or portal downloads, in a different layout from every supplier, and each one has to be ticked against the ledger by hand.
This guide is for the finance leader, AP manager or financial controller at an organisation that buys from many suppliers across several sites, in construction, wholesale, facilities, manufacturing or health. It covers what the statement shows that your three-way match does not, the causes behind the differences, and how to prepare the reconciliation so it is finished before anyone rings you.
What a statement shows that your invoice queue does not
Your invoice process only knows about invoices that reached it. A supplier statement lists everything the supplier believes it has billed, credited and been paid. That makes it the only independent check that nothing is missing from your side.
The three-way match checks an invoice against a purchase order and a receipt. It cannot see an invoice that was emailed to a site manager and never forwarded. It cannot see a credit note the supplier issued and your team never received. The statement can, because the supplier produced it from their own ledger.
For that reason the reconciliation is a completeness control as well as a courtesy to suppliers. It finds liabilities missing from the ledger, which matters for accruals at month-end and year-end, and it finds money you are owed through credits that were never applied.
Six causes behind most statement differences
Each cause has a different owner and a different fix, which is why a single "differences" list is slow to clear.
Invoices that never reached AP
The supplier sent it to a branch, a project manager or a personal mailbox. It is on the statement and absent from your ledger. The fix is to obtain a copy, confirm it is valid and route it through the normal coding and approval path, not to post it straight from the statement.
Credit notes issued and not applied
Suppliers issue credits for returns, price corrections and rebates. If the credit note never reaches AP, your ledger still shows the original invoice as fully owing. Credit notes can go missing when they are sent to whoever raised the dispute instead of to the AP team.
Payments in transit
You paid on the 28th and the supplier posted the receipt on the 2nd. The statement shows the invoice open, your ledger shows it paid. This is a legitimate timing difference and should be recorded as a reconciling item with the payment reference, not chased as an error.
Invoices on hold in your own queue
The invoice reached you but is stuck on a mismatch or awaiting approval. The statement shows it as due. Your ledger may not show it at all, depending on whether held invoices are posted. This is the link between statement reconciliation and the exception queue, and it tells the supplier's collector exactly what you are waiting on.
Disputed or wrongly billed lines
A price that differs from the agreed rate, a delivery charged twice, a site billed for another site's goods. These need a person who knows the agreement, and they should be separated from the clerical differences so they do not sit hidden among them.
Posting differences on the supplier's side
The supplier applied your payment to a different invoice, or booked it on account. The totals agree and the lines do not. Matching by balance alone hides this, which is why the reconciliation has to work line by line.
| Typical cause | Who resolves it | Impact | |
|---|---|---|---|
| Invoice not in your ledger | Sent to a site or personal mailbox | AP obtains a copy and routes it for coding and approval | Missing liability found |
| Credit note not applied | Never reached AP | AP requests the credit note and applies it to the invoice | Overpayment avoided |
| Payment in transit | Posted on different dates | AP records the payment reference as a reconciling item | No chase needed |
| Invoice on hold | Stuck on a mismatch or approval | Buyer or site clears the hold | Supplier told the reason |
| Disputed line | Price or quantity disagrees | Procurement or the budget holder decides | Kept apart from clerical items |
| Supplier posting difference | Payment applied to another invoice | AP asks the supplier to reallocate | Lines agree, totals too |
Why the work does not get done every month
Reconciling a supplier statement by hand takes a person with ledger access and some patience. Consider an organisation with a few hundred active suppliers. Without automation, a team may only have time to reconcile its largest suppliers and check the rest when a supplier complains.
Three things make it slower than it looks. Statements have no standard format, so each supplier's layout needs its own handling. Reference numbers differ: your ledger might hold the supplier's invoice number with a prefix added at entry, or truncated, or with a site code. And the supplier's statement date rarely matches your period end, so the opening position is already disagreeing before the first line is read.
At a multi-site organisation there is a further problem. Different sites may buy from the same supplier under different account numbers, each with its own statement. One supplier can mean six statements, and nobody sees them together.
Differences sorted by cause before anyone opens the ledger
The pattern that suits an AI agent is the same one that works for invoice exceptions: do the investigation first, then hand the result to a person.
- Statement arrivesFrom the supplier's email, portal or a shared AP mailbox, in whatever format they use
- Lines readInvoice numbers, dates, amounts, credits and payments extracted from the PDF or spreadsheet
- Matched to ledgerEach line compared with your open items, held invoices and payments by supplier account
- Cause assignedEvery difference classified, with the evidence and a suggested next step
- AP approvesA person accepts, edits or rejects each proposal before any request goes out
- Ledger and supplier updatedCredits applied, missing invoices routed, payment references sent back
- Reconciliation filedStatement, matches and decisions stored for month-end and audit
The agent reads the statement lines, normalises the reference numbers, and looks each line up in your ledger across every supplier account that belongs to the same legal entity. It also looks in the places a clerk would forget: invoices on hold, invoices awaiting approval, payments run but not yet cleared at the bank.
What it hands back is a short list. Lines that agree are marked as matched and need no attention. Differences come with a stated cause, the evidence for it (the held invoice, the payment run, the missing credit note number) and a proposed action. Nothing is sent to a supplier and nothing is posted until a person approves it.
It does not decide disputes. A price disagreement is routed to the buyer with the purchase order and the invoice attached, because that is a commercial decision. Our view is that an agent earns trust on the routine causes first and leaves judgement calls to people.
Which suppliers to start with
Not every supplier is worth automating on day one. A short decision list keeps the first phase small.
Which suppliers carry the most risk if their statement is wrong?
- Suppliers who could put your account on stop and halt a siteStart here: reconcile monthly, every site account
- Suppliers with many invoices and frequent credit notesStart here: credits are where overpayment hides
- Suppliers billed by several sites under separate accountsSecond wave: link the accounts to one supplier first
- Low-volume suppliers with one or two invoices a quarterLeave with the team; check on supplier request
The first group is usually a short list. Many organisations can name the suppliers whose account hold would stop work within a day, and those are the ones where a clean statement matters most.
Accruals and the missing liability
The most expensive item on a statement is the invoice you have not recorded, because it is a liability the ledger does not show. If the goods or services arrived before the period end, the cost belongs in that period. Statement reconciliation is one of the few controls that finds these before the books close.
That is why the timing matters. Preparing the reconciliation in the last days of the month, or just after, gives the finance team the list of unrecorded invoices while the accrual journal is still open. A reconciliation that is finished three weeks later finds the same invoices after the numbers have gone to the board.
Our guide to month-end close for multi-entity groups covers where accruals sit in the close calendar. Statement reconciliation feeds that step: it gives the controller a dated list with evidence instead of a verbal estimate from AP.
Tax treatment of an invoice recorded late, including GST credits and the period in which they are claimed, is a matter for your tax adviser and the ATO's guidance. The agent flags the invoice date and the date it reached you. It does not decide the tax position.
Payment timing, e-invoicing and the statement
Two developments make a clean supplier ledger more useful than it was.
First, organisations that report under the Payment Times Reporting Scheme need accurate invoice and payment dates. An invoice that sat in a site manager's inbox for a month is a payment time problem as well as a reconciliation problem. We cover the reporting side in our post on payment times reporting.
Second, as more suppliers move to Peppol e-invoicing, fewer invoices will go astray in inboxes, because they arrive as structured data in a defined channel. That reduces the missing-invoice cause but does not remove credits, payments in transit or disputes. Suppliers who have not moved will still send PDFs, and the statement is still the check on both. See e-invoicing compliance in Australia for how to handle the PDFs that remain.
Shadow mode before the agent sends anything
The first phase runs the agent beside your AP team. Your team reconciles statements as they do today. The agent prepares the same reconciliations from the same statements, and nothing it produces reaches a supplier or the ledger.
Each week the two are compared. Where the agent matched a line your team matched, that is a hit. Where it missed a credit note or assigned the wrong cause, that is recorded and the matching rules or prompts are adjusted. The comparison is the evidence, and your finance leader sets the accuracy threshold at which the agent graduates to co-pilot mode, where it drafts and a person approves every action.
- Phase 1Discovery and baselineCount last quarter's differences by cause for the suppliers that matter most, and agree the accuracy threshold
- Phase 2Build and shadow modeThe agent prepares reconciliations beside your team; nothing is sent or posted
- Phase 3Co-pilot and handoverThe agent drafts, AP approves each action, and the build is handed to your IT team
Each phase is a fixed fee agreed before we start, with a decision point at the end where you can proceed, pause or stop and keep what was delivered.
Where the data stays
Supplier statements contain your pricing, volumes and bank details. Where the work runs matters to your security lead.
We build inside your own cloud environment, in an Australian region, using the ERP, ledger and mailboxes you already run. Whether that is Business Central, NetSuite, SAP Business One, MYOB or Xero, the agent reaches the data through the system's own interfaces and an account with permissions you set. Your data is not used to train a model, and the code and credentials are yours at handover.
Bank detail changes deserve their own rule. A statement or email that asks you to change where a supplier is paid should be verified by phone on a number already held on file, and the agent should flag it instead of acting on it.
For how the invoice side is captured and coded in the first place, see our guide to automating invoice processing. If you are weighing capture tools against a custom build, the honest guide to invoice automation sets out the trade-offs.
What to measure
Agree these in Phase 1, measured from your own ledger, so the later comparison is not a matter of opinion.
- Suppliers reconciled each monthCount from your records
- Differences found per statement, by causeCount from last quarter
- Days from period end to reconciliation finishedMeasure today
- Unrecorded invoices found after closeCount from last year
The measure to watch is the last one. If statement reconciliation is working, invoices discovered after the books close fall. Everything else is a means to that.
How Solve8 can help
If your AP team reconciles statements for a handful of suppliers and hopes for the best with the rest, a short review will show which suppliers carry the most risk and how much of the work is routine enough for an agent. You leave with last quarter's differences counted by cause and a straight answer on whether a pilot is worth running.
We build inside the ERP and finance systems you already run, as part of our process automation work, with the connections to mailboxes, portals and supplier data handled through system integration. Where an off-the-shelf tool cannot follow your rules, we scope custom AI development in your own environment. Our wholesale and distribution work covers the multi-site buying patterns that make statements hard to track. Our principal consultant spent 18 years on projects for BHP, Rio Tinto and Senex Energy, delivered while working with previous consulting employers. These companies are not Solve8 clients. More about how we work is on our about page, and our guide to choosing an AI advisory partner sets out what to ask.
Book a free 30-minute review and bring your five largest supplier statements. We will tell you which causes we would start with and which we would leave with your team.
Related reading:
- Three-Way Match Exceptions: Clear the AP Queue: why invoices stop matching and how routine exceptions are cleared.
- Automate Invoice Processing with AI in Australia: Xero and MYOB: capture, coding and approval before the statement check.
- Month-End Close Automation for Multi-Entity Groups: where accruals and reconciliations sit in the close calendar.
- E-Invoicing Compliance in Australia: Peppol Without Rekeying: moving suppliers to Peppol and checking the PDFs that remain.
