The only document that checks your own books
Everything else in accounts payable is your view of your own records. A supplier statement is external: it lists the invoices, credit notes and payments the supplier has recorded against your account, and any difference between their list and yours is information you cannot get any other way.
That is why it catches things nothing else does — an invoice that never reached you, a credit note you were promised and never received, a payment allocated to the wrong invoice, or a duplicate charge sitting on their ledger.
The reason it gets skipped is purely mechanical. The statement is a PDF, your ledger is a system, and comparing them by eye across a few hundred lines is exactly the kind of work people quietly stop doing.
What a skipped reconciliation costs
Missing invoices are the expensive direction: a cost you never recorded understates what you owe, flatters this month's profit, and reappears later as an unexpected demand — often after a period has been closed.
Unapplied credit notes are the other direction and are simply money left on the table. A credit agreed after a dispute is worth nothing if nobody deducts it from a payment.
Then there is relationship damage: suppliers put accounts on hold for balances that were never actually outstanding, and the ensuing conversation costs more time than the reconciliation would have.
The two sides of the comparison
Side one is the supplier statement: their list of transactions on your account for a period, with a closing balance. It arrives as a PDF, sometimes as an email body, occasionally on paper.
Side two is your own record of the same account — the invoices you have posted, the credit notes you have applied and the payments you have made. If you run a ledger, export it. If you do not, an invoice register built from the invoices themselves is the equivalent.
Both need to be tables with the same key fields before anything can be compared: document reference, date, type and amount. Statement of account extraction handles the supplier's side without a template per supplier.
The reconciliation, step by step
Extract the statement
Their transactions become a table with reference, date, type and amount.
Export your side
The same account from your ledger or invoice register, same fields.
Agree the opening
Start from a point where both sides previously agreed, if one exists.
Match by reference
Invoice number first; amount and date only for the leftovers.
Classify every difference
Each unmatched item gets a type, not a shrug.
Act by type
Request missing documents, apply credits, chase misallocations.
Record the result
Keep the reconciliation, not just the conclusion.
What each difference usually means
Nearly every difference falls into one of seven types, and knowing the type tells you who to contact and what to ask for.
| On their statement | On yours | Usually means |
|---|---|---|
| Invoice present | Missing | Never received — request a copy |
| Invoice missing | Present | They have not raised or recorded it |
| Credit note present | Missing | Apply it before the next payment |
| Credit note missing | Present | Agreed but never issued — chase |
| Payment missing | Present | In transit, or allocated elsewhere |
| Different amount | Different amount | Partial payment, discount or dispute |
| Same invoice twice | Once | Duplicate on their ledger — flag it |
The differences that are not errors
Timing explains a large share of what looks alarming at first. A payment sent on the 30th appears on your side in that month and on theirs in the next. An invoice dated at the end of a period may not be posted by you until the following one.
The way to keep timing from consuming the exercise is to reconcile to a date rather than to a feeling — pick the statement date, treat everything after it as out of scope, and list in-transit items explicitly as a reconciling category rather than as unexplained differences.
It is also why reconciling monthly beats reconciling occasionally: fewer moving items, and the ones that move are recent enough to remember.
Why the statement is the hard document
Supplier statements are structurally awkward. Every supplier's layout differs, most carry a running balance that must not be mistaken for a transaction amount, credit notes are shown sometimes as negatives and sometimes in a separate column, and the tables frequently continue across pages with subtotals in between.
Extraction handles those specifically: amounts collapse into one signed value, running balances stay a separate column, wrapped descriptions rejoin, and page-break continuation is treated as one table rather than several.
Scans and photographs go through OCR first with low-confidence values flagged in an editable preview, which matters because posted statements are often scanned rather than emailed.
Which suppliers to reconcile, and how often
Reconciling every supplier every month is not a good use of anyone's time. Value concentrates sharply: the handful of accounts with the most transactions produce most of the differences.
A workable policy is monthly for your top suppliers by transaction count, quarterly for the middle, and annually or on demand for the rest. Add any supplier where a dispute is open, and any where the balance has moved oddly.
The exception worth making: reconcile before agreeing to a payment plan, before year end, and before any conversation about credit terms. Those are the moments when being wrong is expensive.
Chasing the invoices you never received
The most valuable output of the exercise is a specific list: invoice numbers, dates and amounts the supplier has recorded and you have not. That list is what turns a vague "can you send everything" into a request suppliers can actually fulfil.
Most arrive within a day. The ones that do not are usually the interesting cases — an invoice sent to a personal email, one billed to the wrong entity, or one that was never actually issued despite appearing on their ledger.
Post them in the right period where your accounting allows it, and where a period is closed, flag it for your accountant rather than backdating anything yourself.
The credits nobody applied
Credit notes go missing in both directions and are pure money. A credit sitting on the supplier's ledger that you have not applied means you are about to pay more than you owe; a credit you recorded that they have not issued means the deduction you are planning will be disputed.
Track them as a distinct category in the reconciliation rather than as generic differences, because they have a different owner: usually whoever negotiated the dispute rather than accounts payable.
Credit note extraction makes the paperwork side a table too, which matters when a supplier sends a batch after a long argument.
Payments they say they never received
When a supplier says a payment is missing, it is almost always allocated rather than absent — applied to the wrong invoice, sitting on account, or matched to a different entity of yours.
The evidence is your bank statement: date, amount and reference. Converting the relevant month gives you a line you can quote, and quoting the reference usually resolves it in one message. Statement conversion is the same extraction you use elsewhere.
If the payment genuinely never arrived, that is a bank-detail question and deserves the fraud check: verify the account through a known channel before re-sending anything.
Duplicates on their side and yours
Statements surface duplicates in both ledgers. The same invoice recorded twice by the supplier inflates what they think you owe; the same invoice posted twice by you risks paying it twice.
The reconciliation naturally exposes the first. The second is better caught by a check on your own data before a payment run — the same amount to the same payee within a short window — which is covered on duplicate payment detection.
Both are worth doing before the run rather than after: recovering an overpayment depends entirely on the supplier's goodwill and their cash position.
A worked example: one supplier, one afternoon
A construction business reconciles its largest materials supplier for the first time in a year. The statement runs to eleven pages and about 380 transactions.
Extraction turns it into a table in minutes. Matching against the purchase ledger by invoice number clears most of it and leaves 34 differences.
Classified, they are: nine invoices never received, six credit notes agreed after delivery disputes and never issued, four payments allocated to the wrong invoices, three timing items in transit, and two invoices duplicated on the supplier's ledger. The remaining ten are small price variances on delivery charges.
The six missing credit notes alone are worth more than the whole exercise. And the two duplicates, had a payment run happened first, would have been paid.
If you do not have a purchase ledger
Small businesses often have no ledger at all — invoices in a folder and payments in the bank. The reconciliation still works, with one substitution: build the register from the invoices themselves.
Extract every invoice from that supplier for the period into a table, add the payments from your bank statements, and compare that against their statement. It is the same three-column exercise.
It also produces something you did not have before: a supplier-level record you can reuse next quarter, which is the beginning of a purchase ledger without buying one.
What to keep afterwards
Keep the reconciliation itself, not just the corrected balance — the statement, your extract, and the classified list of differences with what was done about each.
That pack answers a question that reliably comes up later: why does this creditor balance differ from what the supplier claims. Auditors ask it directly, and so do suppliers during a dispute.
Note that an extraction tool is not an archive. FlowParse deletes the original document immediately after processing, so retaining the statements themselves stays your responsibility — the audit guide covers what a durable pack looks like.
Who this helps
AP teams
Monthly control on the accounts with the most transactions.
Bookkeepers
Finding missing purchase invoices before a period is closed.
Trades and construction
High-volume materials accounts with frequent credits.
Anyone in dispute
Turning "we disagree" into a specific, evidenced list.
Why extraction quality decides the result
A reconciliation built on a partially-extracted statement produces phantom differences, and hours get spent chasing items that were simply not read.
Two properties prevent it: the running balance must stay separate from transaction amounts, and a table continuing across a page break must be treated as one table. Both are ordinary in supplier statements and both are where naive extraction fails.
Where the document carries a closing balance, use it: your extracted transactions plus the opening figure should reproduce it exactly. See extraction accuracy for what such a check proves.
How documents are handled
TLS in transit, processing in EU data centres, the original document deleted immediately after extraction, extracted data encrypted at rest, and no model training on customer documents — see security.
How often to reconcile which accounts
Value concentrates, so the cadence should too. This is a defensible starting policy that most AP functions can actually sustain.
| Account type | Cadence | Why |
|---|---|---|
| Top 10 by transaction count | Monthly | Most differences arise here |
| Accounts with open disputes | Monthly | Positions change while unresolved |
| Mid-size suppliers | Quarterly | Enough to catch drift |
| Occasional suppliers | On demand | Reconcile before a large payment |
| Any account before year end | Once | Creditor balances get audited |
| Before agreeing a payment plan | Always | You are about to commit to a number |
Getting the statements in the first place
Many suppliers send statements automatically and many do not. Asking is usually enough — most accounts departments can generate one on request, and a standing request for a monthly statement is a normal thing to set up.
Ask for a PDF rather than a screenshot or an email body, because a PDF extracts cleanly and the other two do not. If a supplier only offers a portal, download from it monthly rather than relying on memory.
The suppliers who cannot produce a statement at all are worth noting: it usually means their own records are informal, which raises rather than lowers the value of reconciling what you can.
Reconciling around a period end
Year end is when creditor balances get scrutinised, and it is the moment an unreconciled account becomes expensive. An auditor asking why your balance differs from the supplier's statement is a question with only one good answer: here is the reconciliation.
Practically, that means reconciling the largest accounts as close to the period end as the statements allow, and keeping the working papers with the year-end file rather than in someone's downloads folder.
It also means resolving in-transit items deliberately rather than leaving them as a floating difference. A payment in transit at year end is a legitimate reconciling item; an unexplained difference of the same size is not.
Reconciling an account that is in dispute
An account in dispute is where reconciliation earns the most, because the argument is usually about a handful of specific documents inside a much larger balance, and neither side has separated them.
The move is to reconcile everything that is not disputed first. Agreeing 380 of 400 transactions turns the conversation from "your balance is wrong" into "we agree on everything except these six items", which is a solvable problem and a much calmer meeting.
Keep the disputed items as their own category with the reason and the amount, and pay the undisputed balance. Withholding an entire payment over one disputed line is how a supplier relationship deteriorates and how an account ends up on hold.
The boundary, stated plainly
FlowParse is a document-extraction engine, not an accounts-payable platform and not an ERP. It has no approval workflow, no purchase-order system, no vendor master, no payment execution and no ledger of its own. Nothing here approves, posts or pays anything.
What it does is turn the documents this work depends on — purchase orders, invoices, delivery and goods-received notes, supplier statements, remittance advice and bank statements — into structured, comparable data, with a completeness check on the statements so the numbers you compare are provably whole.
That is deliberately half the job. The other half — deciding what an exception means, approving a payment, posting a journal — belongs to your process and your people, and any tool claiming otherwise is describing something you would still have to supervise.
Start with your largest supplier
Take the most recent statement from the supplier you transact with most, extract it, and compare it against your own record for the same period. That single account usually contains more findings than the next ten combined.
If it produces nothing, your AP process is in better shape than most. If it produces a list, you have both a recovery and a reason to make this monthly.
One practical note on the first run: it will take longer than the ones that follow, because you are clearing an accumulated backlog rather than a month of movement. Budget an hour for a large account, expect most of it to be looking documents up rather than matching, and resist the temptation to stop at the first finding — the differences that matter are rarely the first ones you meet.
Turn a supplier statement into a comparison
Extract their statement and your invoices into matching tables, and get a classified list of every difference — missing invoices, unapplied credits, misallocated payments.