Introduction to reconciliation
What vendor statement reconciliation is, the three documents, and how the software categorises every line. Covers the 'open amount' concept and the 20 action categories, out of 21 the engine produces.
Vendor statement reconciliation is matching what a supplier says you owe against what your accounting system shows — then explaining every item that does not match.
You work with three documents: the vendor statement (usually a PDF), your accounting system report (from your ERP), and (when available) a prior reconciliation.
The software compares each line on the statement against the invoices in your accounting system. It places every item into one of 21 categories, 20 of which produce an action — the 21st, reconciled_activity, is suppressed noise the software does not ask you to act on. This course teaches the 20 action categories: what each means, how the software decides, and what you need to do in your accounting system to fix each one.
Important: the software only reads from your accounting system. It does not write to it. The fix steps you learn in this course are done by you, in your accounting system — not by the software.
- The 'open amount' is the amount still unpaid on an invoice. This is what the software compares against the statement. If an invoice is fully paid, the open amount is $0.00.
- Some accounting systems (like Xero or NetSuite) show both the original amount and the remaining amount. Others (like Vista or QuickBooks) show only the open amount.
- When in doubt, prefer timing over 'missing'. A payment you made that the supplier has not processed yet is not a missing invoice — it is a timing difference.
- This course does not teach Excel. It teaches judgment and understanding — the part a spreadsheet cannot do for you.
- Aside — you already know this pattern from bank reconciliation: outstanding cheques and deposits-in-transit are the bank-rec equivalent of status_conflict_timing; genuine bank errors or book errors are the equivalent of amount_variance or fuzzy_ref. Same judgment, different pair of documents.
- Aside — three-way match / GR-IR is a different process from vendor statement reconciliation. Three-way match checks a purchase order, a goods receipt, and a vendor invoice agree before payment. Vendor statement reconciliation checks the vendor's statement against your AP ledger after the fact. Knowing both names stops you confusing the two.
- Aside — regional terminology: Aged Creditors (UK/AU) = Aged Payables (US) — same report, different name. PLCA (Purchase Ledger Control Account, UK/AU) = the AP subledger in US terms.
Internal aside (devs & marketers)
Statement Zen automates the same 20 action categories, out of 21 the engine emits: deterministic matches first, then an exception report. The software proposes; arithmetic proves. Never claim 'AI decides the balance.'
Module 1 calibration (SCT)
For each situation, rate how the new fact changes the hypothesis on a 5-point scale, from much less likely to much more likely. There is no single 'correct' answer — you are scored against the most-defensible, panel-backed reading.
Answer key: authored, provisional — not yet scored against a real multi-rater expert panel.
1. You are told vendor statement reconciliation is worth doing because it 'catches problems.'
Hypothesis: Reconciliation's primary value is catching invoices the vendor's books show that you never entered into your own AP.
New fact: In your last three reconciliations, every real exception found was a vendor-side invoice missing from your AP, caught weeks before it became a dispute.
2. A colleague claims reconciliation only ever needs the bank feed.
Hypothesis: The three documents that matter are the vendor statement, your AP/ERP extract, and (when available) a prior reconciliation.
New fact: You are handed a bank feed export and told it's everything you need to reconcile a vendor statement.
3. A statement line appears open on your vendor's list but you can't immediately find it in your AP.
Hypothesis: When in doubt between timing and a genuinely missing invoice, you should prefer timing and rule it out before treating it as missing.
New fact: The invoice in question was paid four days ago, but your AP extract is an aged-open-only report that stops showing paid items.
4. A learner asks whether this course will teach them Excel VLOOKUP techniques for reconciliation.
Hypothesis: This course teaches Excel mechanics (VLOOKUP, formulas) as its primary skill.
New fact: The course's labs are dual-pane click-to-pair exercises and exception-classification judgment calls, with no spreadsheet screen anywhere.
5. An aged open payables report doesn't show a specific invoice a vendor says is outstanding.
Hypothesis: The invoice is definitely missing from the ERP and must be chased immediately.
New fact: The invoice was paid last week — it simply isn't 'open' anymore, so the aged-open report never lists it.
Statement Zen Academy Team — Built from Statement Zen's own vendor statement reconciliation engineering and casework — pending Michael's named byline commitment (spec.md section 7). · Last updated