Vendor statement reconciliation — done properly

What you'll learn

• Match statements to AP extracts

  Exact and partial matches across invoice ref, amount, and date — without forcing leftovers into fake pairs.

• Classify every leftover

  Missing each side, timing, credits, duplicates, amount/ref mismatches, opening-balance scope, and report flavour.

• Know what to do next in your books

  For each exception: request invoices, hold payment, re-pull the right report, apply a credit — not just label it.

• Avoid false “missing” traps

  Payment timing and aged-open extracts look like missing bills until you check the right signals.

• Leave a defensible exception log

  Controllers get evidence, not “we think it’s fine.” Capstone proves you can finish a messy vendor week.

Syllabus

Full module list — open any module without logging in.

Free reconciliation template

A working spreadsheet with the same reconciliation columns and exception codes taught in this course, plus a step-by-step checklist — free, no sign-up.

The Google Sheets link opens Google's own "Make a copy" prompt, so you get your own editable copy — no sign-up on our side, nothing shared back to us.

FAQ

Do I need to sign in to see the course?

No. The syllabus, module lessons, labs, and cheat sheet are public. Sign-in is only required to claim the certificate.

Is the course free?

Yes. No course fee. Optional free StatementZen account if you want the shareable certificate.

How long does it take?

About 3.5–5 hours self-paced, including the capstone.

Do I need Excel or a specific ERP?

No Excel module. Works with any AP/ERP extract you can put next to a vendor statement.

What does the certificate prove?

StatementZen Vendor Statement Reconciliation Professional proves you passed the required labs and capstone — judgment on matching and exceptions, not that you used StatementZen product automation.

What is vendor statement reconciliation?

It's the process of comparing a vendor's (or supplier's) statement of account against your own accounts payable ledger to confirm the two agree, then investigating and classifying every line that doesn't — missing on one side, timing, credit, duplicate, amount mismatch, or opening-balance scope — before deciding a next action in your AP system. It is not the same as three-way match (PO/receipt/invoice matching at entry) or an internal-only AP subledger tie-out — vendor statement reconciliation always cross-checks against the vendor's own, external document.

Why doesn't my vendor statement match my AP ledger?

The most common causes are timing (a payment or invoice posted after the statement was cut), report flavour (the vendor sent an aged-open-items view that excludes anything already paid, so a paid invoice looks 'missing'), credits or duplicate entries on one side, and a large undocumented opening balance on a balance-forward statement. A genuine mismatch — where neither side explains it — is the minority case, not the default assumption.

How do you reconcile a supplier statement in Excel?

List both sides — vendor statement lines and your AP extract lines — by reference, date, and amount, then match on reference first (most reliable), amount second, and date last (dates drift with posting timing). Anything that doesn't match becomes an exception row: classify it (missing, timing, credit, duplicate, amount/ref mismatch, opening-balance scope) and record the next action, not just a highlighted cell. This course teaches the judgment behind that classification step — the part a spreadsheet can't do for you.

What's the difference between vendor statement reconciliation and AP reconciliation?

AP reconciliation (or AP subledger reconciliation) is typically an internal, single-side check: does the AP subledger detail add up to the general ledger control account total? Vendor statement reconciliation is external and vendor-by-vendor: it cross-checks your books against each supplier's own independent statement, which is why it catches things an internal-only reconciliation can miss — like an invoice the vendor issued that never made it into your ERP at all.

What causes discrepancies between vendor statements and the AP ledger?

In order of frequency: timing differences (invoice or payment recorded on one side but not yet the other), the vendor's statement being an aged-open-items report rather than full activity (so paid items look absent), credits or debit notes applied on only one side, duplicate invoice entries, genuine amount or reference mismatches, and unexplained opening-balance carry-forward on balance-forward statements. Most 'discrepancies' resolve to timing or report-flavour once you pull the full-activity ledger instead of an aged-open snapshot.

Is vendor statement reconciliation required for audit?

It isn't a single universal audit requirement in the way a bank reconciliation often is, but auditors commonly test accounts payable completeness and existence, and a documented vendor statement reconciliation — with a defensible exception log, not just a tie-out total — is one of the strongest pieces of evidence a controller can hand an auditor for that testing. Many audit programs specifically request supplier statement reconciliations for a sample of significant vendors.

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 21 July 2026