How to reconcile supplier statements with an AI agent

Supplier statement reconciliation finds what the supplier thinks you owe that your ledger does not show, and the reverse. The agent matches each statement line to the payables ledger, classifies the differences, requests copies of missing invoices and drafts entries for errors. An AP person approves every entry. Statements are never posted as invoices, and their bank details are ignored.

What is supplier statement reconciliation, and who owns it?

Suppliers send statements listing invoices, credit notes and payments on your account. Comparing them with your payables ledger catches invoices you never received, payments the supplier has not applied, credit notes you are owed and duplicates you might pay. It also catches fraud: an invoice on your ledger that the supplier has never heard of is a serious finding.

The AP lead owns the process, usually for the largest suppliers monthly and others periodically. Many teams struggle to keep up, because each statement arrives in a different format and the work is manual. That is what makes it suitable for an agent. Whether an agent can reconcile supplier statements at all depends mainly on reading those formats reliably.

What does the agent prepare?

1. Agent, depth 1: classifies and reads the statement. From the AP inbox or supplier portal. It is a statement, not an invoice, and is routed only to reconciliation.
2. Agent, depth 1: matches lines. Each statement line against the supplier's account in the payables ledger by invoice number, amount and date, allowing for format differences in invoice numbers.
3. Agent, depth 2: classifies differences. Invoice on statement, not on ledger (not received, received and held, or posted to another supplier); payment on ledger, not on statement (in transit, or applied to another account by the supplier); credit note missing; amount differences; items on the ledger the supplier does not show.
4. Agent, depth 2: drafts supplier requests. Copy invoices, credit notes, or confirmation of payments applied. Standard requests can be sent at depth 3 once certified, to the contact on the supplier record.
5. Agent, depth 2: drafts entries. For clear errors, such as an invoice posted to the wrong supplier. Parked.
6. Person, AP clerk: reviews and approves. Entries, and any invoice copies received, which then go through normal invoice processing and approval.
7. Person, AP lead: investigates ledger items the supplier does not recognise.

What does a named person approve, and why?

The AP clerk approves every entry. A missing invoice found on a statement is not posted from the statement: the agent requests a copy, and the copy goes through the normal invoice route with matching and budget holder approval. A statement is the supplier's summary, an external claim, not evidence that you owe the amount.

The AP lead decides what to do about ledger items the supplier does not recognise. These may be errors in your ledger, or invoices from a fictitious supplier using a real name. Either way, nothing is paid until they are explained.

Which controls matter, and what evidence do they leave?

Statements never become invoices. Evidence: classification on each document and no invoices with a statement as source.

Bank details on statements ignored. A statement that shows new bank details is flagged to master data, which follows the supplier bank detail change verification checklist. Evidence: flags raised and outcomes.

Requests to the contact on record. Not to an address on the statement. Evidence: recipient on each request.

Entries approved. Evidence: approver identity.

Coverage. A list of suppliers reconciled per period against the target list. Evidence: the coverage report.

What does one statement look like in practice?

Take an illustrative supplier statement showing 14 open invoices totalling 86,000. The ledger shows 11 of them, 64,000, plus a payment of 20,000 the statement does not show. The agent finds that two of the missing invoices were received and are on hold awaiting a receipt, and one was posted to a sister company of the supplier. The 20,000 payment was made three days before the statement date and is in transit. It drafts a reclassification entry for the misposted invoice, a request for confirmation of the payment, and notes the two held invoices for the budget holder.

What should you measure?

• Statement differences by type and value, per supplier.
• Missing invoices found before they became late payment disputes.
• Credit notes recovered.
• Unrecognised ledger items, which must be zero after investigation.
• Coverage of suppliers against the target.

Where does it usually go wrong?

Paying from the statement. A supplier chases an amount; someone pays the statement total. Duplicates follow. Payments come only from approved invoices.

Invoice number formats. "INV-00123" on the statement, "123" in the ledger. Matching must normalise numbers, or every line looks missing.

Payments on account. Your payment was applied to the wrong invoice by the supplier. The difference is theirs to fix, but the agent should explain it so the request is specific.

Unread statements. Statements arrive and nobody opens them. Classifying the inbox, as with payment processor settlements, routes each document to the right reconciliation.

Where Pryme fits

In Pryme, matching statements and drafting requests are separate capabilities, certified on your own past statements. Statements arrive as external claims and the ledger as sealed, so the agent cannot post or pay from a statement. Entries are held for an AP person and every match is filed. The finance bounds are in AI agents for finance.