Yes. AI can help draft a supplier statement reconciliation without changing the ledger. Give the workflow a supplier statement and a fixed ledger export, then have it produce proposed matches, unresolved differences and supporting evidence in a review workbook. Keep posting, allocation and payment actions outside its scope.
The useful output is a reconciliation that a finance person can check row by row. A matching closing balance alone is insufficient: unrelated errors can cancel each other out. This proposed accounting automation workflow should explain both the balance difference and the individual transactions behind it.
Fix the comparison boundary before matching
Start with one supplier account, one currency and one statement cut-off. Record the statement period, ledger export time and whether the export includes all movements or only outstanding items. These are different comparisons: an outstanding-items statement cannot be treated as a complete transaction history.
Include opening balances, invoices, credit notes, payments and adjustments where relevant to the chosen statement format. If the opening balance is unexplained, carry it as an unresolved item rather than forcing current-period transactions to absorb it.
Ask finance to define the signs. For this proposed workbook, invoices increase the amount owed; payments and credit notes decrease it. Retain the original debit and credit columns alongside that interpretation. Otherwise, a supplier’s presentation could reverse the apparent difference.
Also distinguish document date from posting date. An invoice dated before the cut-off but posted afterwards may explain a timing difference. A ledger exported later must still represent the agreed cut-off; today’s outstanding amount may have changed since then.
Extract statement rows without inventing missing details
For each row, capture supplier account, document type, reference, date, currency, amount and any displayed balance. Preserve the statement filename, page and row location. Keep unreadable values blank and flag them for inspection.
Microsoft documents text, table and structure extraction through Azure Document Intelligence, including its Layout model. That establishes an extraction capability; it does not establish that a particular supplier statement will be interpreted correctly. Select and check the extraction approach against the actual layout. Source: Azure Document Intelligence overview
Normalisation should create an additional comparison value, leaving the original intact. Trimming spaces may be reasonable; removing leading zeros or every punctuation mark could merge distinct invoice references. Finance should approve the rules for the supplier’s reference format.
Check extracted row counts, signs and totals against the document before matching. A carried-forward balance should not become another invoice. Repeated table headings and overlapping pages should remain identifiable so they can be excluded with a recorded reason.
Use explicit rules to propose matches
Begin with the strongest available evidence: supplier identity, currency, document type, reference and amount. A proposed exact-match rule should require a unique candidate, with date differences displayed for review. Equal amounts alone are weak evidence when a supplier issues recurring charges.
Use separate categories for exact candidates, reference variations, amount differences, statement-only items, ledger-only items, timing differences and suspected duplicates. Treat these as proposed review categories rather than accounting conclusions.
A payment covering several invoices needs an allocation trail. Do not let AI choose a convenient combination merely because the amounts add up. Request remittance or allocation evidence, and show every member of any proposed grouped match.
Calculate differences and totals with spreadsheet formulas or other deterministic rules. AI can draft an explanation from those results. Schema-constrained output can enforce required fields and permitted categories, but correct structure still needs factual validation against the inputs. Source: OpenAI Structured Outputs
The distinction in AI agents versus automation matters here: fixed rules handle arithmetic and candidate selection; interpretation helps explain exceptions.
Copy this review workbook specification
Use the following specification as a handover brief. The workbook should preserve imported evidence and keep proposed matches separate from reviewer decisions.
Purpose: Compare one supplier statement with a ledger snapshot and prepare evidence for finance review. No ledger writes or payment instructions.
| Sheet | Required contents | Review rule |
|---|---|---|
| Scope | Supplier/account ID, currency, statement period, cut-off, export time, export coverage, sign convention, preparer | Confirm comparable scope before matching. |
| Statement rows | Row ID, original reference/date/type, normalised reference, signed amount, displayed balance, filename/page/row, extraction issue | Preserve originals; leave unknown values blank. |
| Ledger rows | Unique transaction ID, supplier ID, reference, document and posting dates, type, currency, signed amount, status, export row | Include relevant movements and opening evidence; explain exclusions. |
| Match groups | Group ID, statement row IDs, ledger transaction IDs, rule used, totals on each side, difference, evidence location | Use each source row once; show all grouped members. |
| Exceptions | Exception ID, affected rows, category, observed evidence, missing evidence, proposed next step, owner, review status | Record uncertainty; never infer approval from a suggested match. |
| Balance bridge | Statement closing balance, ledger closing balance, initial difference, signed reconciling items, supporting exception IDs, residual difference | Initial difference = statement closing balance − ledger closing balance. Residual = initial difference − sum(signed reconciling items). |
| Review log | Reviewer, date, decision, supporting document, unresolved reason, workbook version | Keep later corrections and payments outside this workbook. |
Reconciling signs: Record each item’s contribution to statement balance minus ledger balance. A statement-only invoice is positive; a statement-only payment or credit is negative. Reverse these signs for ledger-only items. Count each difference once.
Suggested statuses: Unreviewed, evidence requested, accepted explanation, rejected match, unresolved.
Completion checklist: Confirm source completeness; validate extraction totals; account for every source row; resolve reused-row warnings; explain opening differences; check both balance-bridge formulas; distinguish evidenced explanations from provisional items; name an owner for every unresolved exception; retain the reviewed workbook with its source snapshots.
Work through ordinary, missing and duplicate cases
All figures and references in this example are hypothetical. A supplier statement closes at R12,400, while the comparable ledger balance is R11,900. The initial difference, using statement minus ledger, is R500.
An ordinary invoice, INV-104, appears for R4,600 in both sources with the same currency and a unique reference. The workflow proposes an exact match. The reviewer checks the source row and ledger transaction, then accepts that match. Acceptance records agreement between the sources; it does not approve payment.
The statement also contains invoice INV-108 for R1,200, absent from the export. Record a statement-only exception. Finance requests the invoice and checks whether it was received, posted after cut-off or recorded under another reference. Until evidence arrives, call it missing from the supplied ledger data, rather than definitively unrecorded.
A R700 payment appears in the statement but not in the ledger snapshot. The invoice contributes positive R1,200 to the bridge; the payment contributes negative R700. Their net contribution is R500. The residual is therefore (R12,400 − R11,900) − (R1,200 − R700) = R0. Finance still needs invoice and payment evidence: this provisional bridge adds up without proving either explanation.
Separately, suppose a R2,300 statement invoice could match either of two ledger invoices with similar references. Keep both candidates and mark the match ambiguous. The reviewer checks the invoices and supplier account details. Selecting the first candidate would hide the uncertainty.
Finally, suppose INV-104 appears twice in extracted statement rows. Compare page locations and the original statement. An overlapping scan may justify excluding one extraction row; two genuine statement entries require a supplier query. Retain both original rows and the reviewer’s reason. Do not delete a ledger invoice based on a suspected duplicate.
Keep the ledger unchanged through review and handover
An export-based pilot provides a clear boundary: the workflow receives copies and produces a workbook. It needs no posting connection. If later connected directly, check current account, plan and region eligibility, available fields and permissions before deployment.
Xero’s official API definition distinguishes retrieval operations from operations that create or update accounting records. Do not assume that access to accounting data automatically prevents writes; select and verify the permitted operations for the integration. Source: Xero official Accounting API definition
A custom AI agent specification should restrict this task to reading approved inputs and preparing review evidence. For broader implementation choices, see custom AI agent workflows.
At handover, finance should receive the snapshots, match rules, workbook and unresolved evidence requests. Any correction belongs in the organisation’s existing accounting process, with a fresh reconciliation afterwards where necessary.
FAQ: supplier statement reconciliation
Can we reconcile using only an aged payables report?
Only if it provides enough detail for the chosen comparison. Check its date basis and coverage. If it omits settled movements, payment allocations or opening evidence, supplement it or explicitly limit the draft to outstanding items.
What should happen when the statement has no invoice reference?
Leave the reference blank. Use other evidence to present candidates, clearly labelled as uncertain. Finance should request the underlying invoice or supplier clarification before accepting a match; a plausible description is insufficient.
Does a zero residual mean the supplier can be paid?
No. It means the initial balance difference equals the sum of the signed reconciling items. Those items may still be provisional. Missing documents, disputed charges or incorrect allocations can remain, so finance must assess them through its payment approval process.
If your business needs a repeatable statement review, start with one supplier and compare the draft with a manual reconciliation. For help defining the inputs, matching rules and review workbook within an AI automation project, get in touch.