← Academy

Module 0: Orientation

Why statement matching matters, the three documents, and when not to chase. · ~15 min

Progress this module: 0/1 required labs passed

Vendor statement reconciliation is matching what a supplier says you owe against what your accounting system shows — then explaining every leftover.

You work with three documents: the vendor statement, your AP/ERP extract, and (when available) a prior reconciliation.

  • Catch invoices on the vendor’s books you never entered — before they age into disputes.
  • Catch credits you are entitled to before you overpay.
  • Stop duplicate payments with evidence, not gut feel.
  • Give controllers a defensible close: an exception log beats “we think it’s fine.”
  • When in doubt, prefer timing over “missing.” Aged-open silence is not proof an invoice was never entered.
  • This course does not teach Excel. Judgment and dual-pane matching only.
  • Aside — you already know this pattern from bank reconciliation: outstanding cheques and deposits-in-transit are the bank-rec equivalent of TIMING_PAY/TIMING_INV; genuine bank errors or book errors are the equivalent of AMT_MISMATCH or REF_MISMATCH. Same judgment, different pair of documents.
  • Aside — three-way match / GR-IR disambiguation: in ERP screens you may see this process called a three-way match, GR/IR, or GRNI (goods-receipt/invoice-receipt). That is invoice-entry matching, a different process from vendor statement reconciliation — this course does not teach it, but knowing the name stops you confusing the two in an interview or on the job.
  • Aside — terminology gloss (UK/US/AU): Aged Creditors (UK/AU) = Aged Payables (US) — same report, different regional name. PLCA (Purchase Ledger Control Account, UK/AU usage) = the AP subledger / AP subsidiary ledger in US terms — same control account, different label.
  • Aside — AU GST compliance trap: a vendor's Statement of Account is NOT a valid tax invoice. It cannot substantiate a GST credit claim — you need the underlying tax invoice for that, not the statement. This is a domain-knowledge trap distinct from visual pattern-matching.
Internal aside (devs & marketers)

StatementZen automates the same buckets: deterministic matches first, then an exception report. Models may propose; arithmetic proves. Never claim “AI decides the balance.”

Module 0 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. 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. 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. 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. 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. 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.

StatementZen Academy TeamBuilt from StatementZen's own vendor statement reconciliation engineering and casework — pending Michael's named byline commitment (spec.md section 7). · Last updated