Module 3: Missing on each side

Find what is missing on the statement vs in the ERP — after ruling out timing. · ~40 min

Progress this module: 0/4 required labs passed

On the statement but not in ERP → often a missing bill (or wrong vendor / wrong extract).

In ERP but not on the statement → dispute, vendor lag, or report-flavour / timing.

Always check report flavour and timing before emailing the vendor.
Aged open payables that omit a paid invoice do not mean “missing from ERP.”
Duplicate candidates split into two subtypes: pre-payment (same invoice entered twice, neither paid — void it) vs. post-disbursement (both entries paid — now a recovery). APQC benchmarks put duplicate payments alone at 0.8%-2% of total spend without automated duplicate-detection controls, which is why catching the pre-payment subtype matters.

Lab 3.1 — Missing hunt

Match what you can. Two statement lines are missing from AP. Two AP lines are extras — classify carefully (one may be timing).

Click a statement line, then click an AP line to pair. Click a pair badge to unlink. Archetypes: S1 × L1.

Norwood Timber Supplies

8 Millwright St, Norwood SA 5067

Statement date: 2026-05-13

Vendor statement(S1 — open-item statement)

AP / ERP extract

Lab 3.2 — Story cards

Read each scenario, click it, then click the correct bucket. Watch for the aged-open false alarm.

Select a card, then click a bucket. Timing and report-flavour mistakes that look like “missing” are critical fails.

Lab 3.3 — Duplicate candidate clinic

Classify each scenario. DUP_CAND has two subtypes: caught before either entry is paid (freeze and void) vs. caught after both have been paid (recovery). Watch for lookalikes that are not actually duplicates.

Select a card, then click a bucket. Timing and report-flavour mistakes that look like “missing” are critical fails.

M3 — The invoice that isn't on your ledger

Rank ALL five actions from best (1) to worst (5). There is no single 'correct' answer to pick — every option must be weighed against the others, and the ranking is scored against an expert-consensus order, not a single best answer.

Consensus ranking: authored, provisional — not yet scored against a real multi-rater expert panel.

You're reconciling a vendor statement. One line on the statement — Invoice #INV-40218, $2,140.00 — has no matching line anywhere in the ledger export you pulled from the ERP. Before you do anything else, decide what order you'd tackle these five possible next actions in.

1.Check whether the ledger report you pulled is a paid-invoices-only view or the full transaction history (report flavour) before assuming the invoice is genuinely missing.
2.Mark the line MISS_ERP in your workpaper with a note, and continue reconciling the rest of the statement.
3.Email the vendor right away asking them to resend a copy of the invoice.
4.Escalate to your manager before doing anything else on this line.
5.Assume the amount is a duplicate of an already-matched line and ignore it without checking further.

Previous module Next module

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