AI agent · Finance & accounting · Match & reconcile
Supplier statement reconciliation
The software reads every supplier statement, matches it line by line to your payables ledger and explains each difference: an invoice you never received, a payment the supplier has not applied, a credit note still missing. Your team handles the disputes.
Typical volumes for this process, not a client figure.
Statements ticked off against the ledger by hand, for the largest suppliers only.
Every statement matched to the ledger; missing invoices and unapplied payments listed.
Where the time goes today
Suppliers send statements of account as PDFs by email, as downloads from their portals or as spreadsheets. Each lists the invoices, credit notes and payments the supplier has recorded, and the balance it believes you owe. An accounts payable clerk compares the statement with the supplier's account in your ledger and ticks the lines that agree. The supplier uses its own invoice numbers and dates; your ledger uses posting dates and the references your team keyed.
The differences fall into familiar groups. An invoice on the statement that never reached your ledger: lost, sent to the wrong address, stuck in approval. A credit note the supplier issued but you never received. A payment you made that the supplier has not applied, or applied to the wrong invoice. Payments in transit at the statement date. An invoice sent twice under slightly different numbers. An amount already on hold for a price dispute.
Because each supplier's format is different, teams reconcile the largest suppliers and leave the rest until a supplier chases. Missing invoices then surface as a stopped account or late-payment charges, and duplicates surface after they have been paid.
How the agent works
- Collect the statementsThe agent picks up statements from the payables inbox and supplier portals, and requests them from suppliers who do not send one, on the schedule you set. It identifies the supplier account and the statement date.
- Read every lineIt extracts document type, supplier reference, date, amount, currency and open balance for each line, plus the closing balance. It checks that the lines add up to the balance the supplier states.
- Match to the ledgerLines are matched on invoice number first, allowing for the usual differences in how references are keyed, then on amount and date within your tolerance. Payments are matched to your payment runs, and items dated after the statement date are set aside as timing.
- Explain each differenceEach unmatched line gets a reason: not in the ledger, payment not applied by the supplier, credit note missing, amount difference, possible duplicate. For invoices not in the ledger, the agent searches the inbox and approval workflow to see where they stopped.
- Act on the gapsIt requests copies of missing invoices, sends remittance details for payments the supplier has not applied and flags suspected duplicates so they are blocked from payment. The reconciliation is saved with every reconciling item listed.
What stays with a person
Your payables team decides disputed amounts, write-offs of old differences, whether to accept late-payment charges, and what to say to a supplier who claims more than your ledger shows when the evidence is unclear. Calls with key suppliers stay with the people who hold those relationships.
The agent does not post to the ledger. It proposes adjustments with the evidence; a person posts them. The ledger is the record your auditors rely on, and a person should own every change made to it for a reconciliation.
What it reads, what it produces
| It reads | It produces |
|---|---|
| Supplier statements in PDF, spreadsheet or portal format | A reconciliation per supplier, tying the statement balance to the ledger balance |
| The payables ledger and supplier master data | Requests to suppliers for missing invoice copies |
| Payment runs and bank remittances | Remittance details for payments the supplier has not applied |
| The payables inbox and invoice approval workflow | Suspected duplicate flags and an aged list of unresolved differences |
| Open disputes and invoices on hold |
Controls that come with it
- If the statement lines do not add up to the stated balance, the statement goes to a person before any matching.
- Amount and date tolerances are set by you; a line outside them is a difference, never a forced match.
- Supplier emails use templates you approve and only ask for documents or send remittances; they never agree a balance.
- Bank details printed on a statement are never used to update supplier records; any change goes through your supplier master control.
- Every match records the rule that made it, and proposed adjustments carry their evidence.
How you know it works
- Share of active suppliers reconciled each month
- Age and value of unresolved differences
- Missing invoices found before the supplier chased
- Duplicate invoices blocked before payment
- Clerk time per reconciliation
Is your process ready?
- Written rules: matching tolerances, the treatment of timing differences and who may write off a difference are documented.
- Systems: the payables ledger can be read through an interface or export, and statements arrive in a mailbox or portal the agent may access under the portal's terms.
- Cheap check: a reconciliation either ties both balances or it does not.
- Volume: hundreds of active suppliers repay the build; thirty suppliers can stay in a spreadsheet.
- Same description: payables teams in each entity treat timing differences and unapplied payments the same way.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Invoice numbers truncated or reformatted when keyed into your ledger; matching must learn your team's keying habits from past data.
- Statements that show only open items, rather than full activity, need different logic, and the agent must know which it has.
- The same supplier held under several accounts in the supplier master, so differences appear that are not real.
- Emailing suppliers too often for documents; set a frequency and a single contact per supplier.
Questions we get
How is this different from invoice matching?
Invoice matching checks each invoice against the order and the receipt before you pay it. Statement reconciliation works from the supplier's side: it shows what the supplier believes you owe and finds what never entered your process at all, such as invoices that went astray or credit notes you never received. The two catch different errors, so they complement each other rather than overlap.
What about suppliers who never send a statement?
The agent can request one on a schedule, by email or through the supplier's portal where you have access. Some suppliers will not respond. For those, it can still compare your ledger with their remittance acknowledgements and flag old open items, but without a statement you have no view of invoices the supplier issued that never reached you.
Will it change our ledger?
No. It reads the ledger, proposes adjustments with the supporting documents, and blocks suspected duplicates through your normal payment hold where you allow that. Postings are made by your team. This keeps a clear line between the reconciliation, which the agent prepares, and the accounting record, which a person owns.
What do we need to start?
A set of past statements with the reconciliations your team completed for them, including the reasons given for each difference. The agent is run against those first. Where its explanations differ from your team's, you review the cases and adjust tolerances or rules. The same set is re-run whenever a supplier changes its statement format or you change your rules.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.