Free certification · no login required to learn
Vendor statement reconciliation — done properly
Learn to match statements to AP extracts, classify every leftover, and know what to do next in your accounting system. No Excel module. No course fee. Earn a LinkedIn-shareable certificate when you pass.
About 3.5–5 hours · self-paced · syllabus and labs public without signing in
Free reference material
- Decision treePrintable flowchart: follow the branches to classify any item.
- PracticeClassify statement and ledger lines with instant feedback. No login required.
- Exception taxonomyEvery leftover bucket and the AP action that clears it.
- GlossaryThe reconciliation vocabulary, defined plainly.
- Root causes & comparisonsWhy statements and ledgers drift apart in the first place.
- Worked examplesThree reconciliations worked line by line, every figure shown.
- Why extraction quality mattersWhat a bad read costs you further down the process.
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.” The Final Challenge proves you can finish a messy vendor week.
Skills you'll practice
How to start
You do not need an account to open the syllabus or practice. Sign up only when you want to claim the certificate.
- 1
Browse the syllabus (no account needed)
Read every module overview and the exception taxonomy. Labs work in your browser with local progress.
- 2
Start Module 1
Orientation takes about 15 minutes. Practice packs save progress on this device until you sign in.
- 3
Create a free account when you want the certificate
Sign up is free. After you pass the required labs and Final Challenge, sign in to claim your LinkedIn-shareable certificate.
Syllabus
Full module list — open any module without logging in.
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.
Perfect and near-perfect matches
When invoice number, amount, and date all agree (clean_match), or amount and date agree without a reference (date_corroborated), or the reference is formatted differently (fuzzy_ref). Tick and move on.
Date and amount differences
When two of three fields agree but one differs: date_mismatch, amount_variance, part_paid, and ambiguous_match. Investigate without inventing a match.
Items on one side only
Items that appear on the statement but not in your ledger (statement_only, not_open_maybe_paid, out_of_period) or in your ledger but not on the statement (ledger_only, ledger_out_of_period). Rule out timing before chasing.
Statement layout fluency
Read debit/credit, original vs outstanding, and rolling-balance layouts. Learn to prove statement math without a spreadsheet. Includes duplicate detection (duplicate_statement, duplicate_ledger) and consolidation matching (many_to_one, one_to_many).
Payments, credits, timing, and opening balances
Your ledger says paid but they still show it open (status_conflict, status_conflict_timing), unallocated credits (credit_on_account), and the brought-forward balance check (bbf_anchor). Includes the practical reality that most statements do not have a brought-forward line, and the paid-invoices (L3) report-flavour trap where an extract that only lists paid items makes every genuinely open invoice look missing.
Exception log workflow and course-only concepts
Classify every leftover and sign off with a defensible log. Includes course-only concepts the software does not detect: new_vendor_opening, document_type_mismatch, dispute_on_hold, and vendor_data_issue. Learn what to do in your accounting system for each category.
Messy vendor week
Full dual-pane recon + exception classification. Pass to claim Statement Zen Vendor Statement Reconciliation Professional.
Free reconciliation template
A real reconciliation workbook, not an exception log: 26 cause codes, five dispositions (including a dedicated "never chase" for the residuals that only look like debts), a formula-driven balance bridge, and ten checks that withhold sign-off until the reconciliation actually proves itself.
How you earn the certificate
- Pass required labs in Modules 0–6 (practice in-browser; no login).
- Final Challenge: match + classify a messy week; timing/opening-balance mistakes are critical fails.
- Sign in with a free account and claim Statement Zen Vendor Statement Reconciliation Professional — public verify page + LinkedIn add link.
Exception → next action (preview)
Classification is not the finish line — you learn what to do in AP next.
| Bucket | Typical next action |
|---|---|
| Brought-forward check | If balances agree — nothing to do. If they differ — investigate which prior-period items explain the gap. |
| Your ledger says paid — still open on their statement | Confirm the payment cleared your bank and was applied on the supplier's side. Do not pay again. |
| On their statement — missing from your ledger | Request a copy of the invoice from the supplier, then enter it in your accounting system. Or query the charge if you believe it is wrong. |
| Amount doesn't match | Check for tax, freight, FX, or short-payment differences. Adjust the bill or arrange a credit with the supplier. |
| Part-paid — billed in full, partly settled | Confirm the partial payment cleared. Verify the remaining balance is correct. |
| Charged twice on the statement | Query the duplicate with the supplier. Pay only once. Do not enter a second bill. |
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 Statement Zen account if you want the shareable certificate.
- How long does it take?
- About 3.5–5 hours self-paced, including the Final Challenge.
- 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?
- Statement Zen Vendor Statement Reconciliation Professional proves you passed the required labs and Final Challenge — judgment on matching and exceptions, not that you used Statement Zen 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.
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