Three references you can check without doing the reconciliation yourself: what each symptom usually means, how manual and automated approaches compare, and what the same control is called in the UK, US, and Australia.
Every exception bucket in the taxonomy — symptom, how to confirm it, how to fix it.
| Code | Symptom | How to confirm | How to fix |
|---|---|---|---|
| MATCH_EXACT | Ref, amount, and date all agree on both sides. | Line up ref + amount (+ date) — all three tie out with no gap. | Nothing to fix. Tick as matched and move on. |
| MATCH_PARTIAL | Two of three fields agree (ref/amount/date); one is open. | Open the bill and statement line side by side to see which single field disagrees. | Confirm the open field against a PO, receiving record, or the vendor, then tick as matched or reclassify as amount/reference mismatch. |
| MISS_ERP | The vendor's statement lists an invoice you can't find in your AP extract at all. | Search your AP by amount and approximate date, not just the exact reference, in case it was entered under a different ref or vendor code. | Request a PDF copy of the invoice from the vendor, then enter the bill in AP against the correct vendor and entity. |
| MISS_STMT | Your AP extract shows an open invoice the vendor's statement doesn't list. | Confirm the statement period and entity match, then check for disputes, holds, or debit notes on the AP bill. | Email the vendor with the invoice reference and ask whether it was omitted in error, disputed, or simply falls outside their statement cutoff. |
| TIMING_PAY | A payment you've recorded as sent (or received) hasn't been applied on the other side yet. | Check the payment date against the statement's cutoff date — a payment made close to the cutoff often hasn't posted on the vendor's side yet. | Hold the line and recheck on the next statement cycle. Do not treat it as a missing invoice or re-pay it. |
| TIMING_INV | An invoice appears on one side of the cutoff date but not the other. | Compare the invoice date to both systems' period-close dates — a lag of a few days across a month-end is the usual explanation. | Hold the line for the next cycle, or accrue it per your close policy if the amount is material. |
| CREDIT_UNAPP | A credit memo is on the statement but not reflected (or not fully applied) in your AP balance. | Search your AP for the credit memo reference; if absent, ask the vendor for a copy. | Obtain the credit memo and apply it against the correct invoice(s) in AP. |
| DUP_CAND | The same invoice reference and amount appear twice, on either side. | Compare invoice numbers, dates, and amounts closely — a genuine duplicate has identical (or near-identical) values, not just a similar reference. | Investigate before paying a second time; void or reverse the duplicate entry once confirmed. |
| AMT_MISMATCH | Same invoice reference on both sides, but the amounts differ. | Check for tax, freight, FX rate, or short-pay adjustments that would explain the delta. | Resolve the pricing/tax/FX difference with the vendor and correct whichever side is wrong. |
| REF_MISMATCH | Same amount and date on both sides, but the reference numbers differ. | Fuzzy-match on amount + date + rough reference similarity before concluding it's the same invoice. | Confirm with the vendor which reference is correct, then correct your AP record and tick the pair as matched. |
| OB_SCOPE | The statement's opening balance includes older history your AP extract doesn't cover. | Check whether a prior-period reconciliation exists that already cleared that opening balance. | Carry forward the prior reconciliation's closing figure, or request a fuller extract. Never invent historical invoice lines to force a tie-out. |
| OB_NEWVENDOR | This is the first statement from a new vendor and it shows a nonzero opening balance. | Confirm with AP or the vendor that this is genuinely the first statement for this relationship. | Treat any nonzero opening balance on a first statement as a report-flavour or scope issue — request a corrected statement rather than accepting it as a real carry-forward balance. |
| REPORT_FLAVOUR | Multiple invoices look 'missing' but they were actually already paid. | Check whether the statement is an aged-open-items report (excludes anything paid) rather than a full-activity report. | Re-pull the correct report type (full activity / transaction list) from the vendor before chasing any 'missing' invoices. |
| DISPUTE | You already know there's a disagreement with the vendor over this line. | Check the dispute or hold flag already recorded against the AP bill or vendor file. | Document the dispute on the exception log and leave it open — do not clear it as a match just to close the reconciliation. |
| VENDOR_DATA | The statement is for the wrong legal entity, wrong currency, or has an implausible statement date. | Check the vendor/entity name, currency symbol, and statement date against what you expected to receive. | Stop reconciling this statement and request the correct one from the vendor before doing any further matching. |
| Dimension | Manual (Excel) | Generic automated tool | StatementZen |
|---|---|---|---|
| Matching exact + partial lines | Line-by-line eyeballing in Excel; slow and error-prone at volume. | Rule-based exact matching; partial matches often still dumped to a manual review queue. | Exact and partial matching with confidence-scored candidates, so partials are pre-ranked, not a blind pile. |
| Classifying leftovers | Analyst judgment call each time, inconsistent between people and between periods. | Usually stops at 'unmatched' with no further breakdown of why. | Structured exception taxonomy (missing/timing/credit/duplicate/mismatch/report-flavour/opening-balance) applied consistently. |
| Report-flavour traps (aged-open vs full activity) | Frequently missed — a paid invoice on an aged-open report reads as 'missing'. | Rarely modelled; most tools assume one canonical report shape. | Report type is explicitly detected and factored in before anything is flagged as missing. |
| Exception documentation | Sticky notes, email threads, or a highlighted spreadsheet cell — hard to defend at audit. | A matched/unmatched flag with little narrative context. | A defensible exception log: bucket, evidence, and stated next action per line. |
| Time per vendor per period | 30-90+ minutes for a moderately active vendor. | Faster matching, but manual triage of the unmatched pile often eats the time savings back. | Minutes, with the remaining human time spent on genuine judgment calls, not re-deriving what's already known. |
Same control, different regional name — useful when reading ERP docs or job postings written for a different region.
| Concept | UK | US | AU |
|---|---|---|---|
| Vendor/supplier statement matching against your ledger | Supplier statement reconciliation | Vendor statement reconciliation | Supplier statement reconciliation |
| Report of amounts currently owed, aged by how overdue | Aged Creditors | Aged Payables | Aged Creditors |
| The detailed vendor-by-vendor subledger behind the AP control account | PLCA (Purchase Ledger Control Account) | AP subledger / AP subsidiary ledger | PLCA (Purchase Ledger Control Account) |
| Matching a PO, goods receipt, and invoice at entry | Three-way match / GRNI | Three-way match / GR/IR | Three-way match / GRNI |
StatementZen Academy Team — Built from StatementZen's own vendor statement reconciliation engineering and casework — pending Michael's named byline commitment (spec.md section 7). · Last updated