← Academy
Root causes, manual vs automated, and regional terms
Use these tables to check what an exception may mean, how different approaches handle the work, and which regional term to look for in ERP guidance.
Root-cause matrix
Start with the symptom, confirm the cause, then take the next action shown.
| Code | Symptom | How to confirm | How to fix |
|---|---|---|---|
| clean_match | The reference, amount, and date agree on both sides. | Compare the statement line with the invoice and check all three fields. | No correction is needed. Mark the item as matched. |
| date_mismatch | The reference and amount match exactly, but the dates differ. | Compare the statement line with the invoice or source document to see which date is correct. | Correct the date only if your AP record is wrong. Otherwise, record the reason for the difference. |
| statement_only | The vendor's statement lists an invoice that you cannot find in your AP extract. | Search AP by amount and approximate date as well as by reference. The invoice may use a different reference or vendor code. | Request the invoice from the vendor, check it, and then enter the bill against the correct vendor and entity. |
| ledger_only | Your AP extract shows an open invoice that is not on the vendor's statement. | Check that the entity and statement period are correct, then review any disputes, holds, or debit notes on the bill. | Ask the vendor whether the invoice was omitted, disputed, or fell outside the statement cutoff. |
| status_conflict | Your ledger shows the invoice as paid, but the supplier still lists it as open, and the item is outside the timing window. | Confirm that the payment cleared your bank account. Check the payment date against the statement closing date; a gap of more than 7 days is treated as a settlement disagreement rather than timing. | Send the supplier the remittance advice and bank transaction reference, and ask them to apply the payment. Do not pay again. |
| status_conflict_timing | A payment or invoice recorded on one side has not yet been applied on the other side near the statement cutoff. | Compare the payment or invoice date with the statement cutoff date. A short gap across the cutoff may explain why the other side has not posted it yet. | Leave the item open for review on the next statement. Do not classify it as missing or pay it again. Follow your close policy if an accrual is required. |
| credit_on_account | A credit memo appears on the statement but is missing from, or not fully applied in, your AP balance. | Search AP for the credit memo reference. If you cannot find it, ask the vendor for a copy. | Obtain the credit memo and apply it to the correct invoice or invoices. |
| duplicate_statement | The same invoice reference and amount appear more than once on the statement. | Compare the invoice numbers, dates, and amounts. Similar references alone do not prove that the lines are duplicates. | Query the duplicate before paying. Pay only once and do not enter a second bill. |
| amount_variance | Same invoice reference on both sides, but the amounts differ. | Check tax, freight, the FX rate, and any short-payment adjustments that could explain the difference. | Resolve the price, tax, or FX difference with the vendor and correct the side that is wrong. |
| part_paid | The statement shows the full invoice amount, but your AP ledger shows a smaller remaining balance. | Review payment history for partial payments, short-pays, or credit memos applied to the invoice. | Confirm that the partial payment cleared and that the remaining balance is correct. Send remittance advice if the supplier has not applied the payment. |
| fuzzy_ref | The amount and date agree, but the reference numbers use different formatting. | Compare the amount, date, and core reference number to check whether both records refer to the same invoice. | Correct the reference in AP if needed. Contact the vendor only if you still cannot confirm the match. |
| bbf_anchor | The statement opening balance includes older items that are not covered by your AP extract. | Check for a prior-period reconciliation that explains the opening balance. | Carry forward the previous reconciliation's closing figure or request a fuller extract. Do not create historical invoice lines to force the balance to agree. |
| new_vendor_opening | This is the first statement from a new vendor and it shows a nonzero opening balance. | Confirm with AP or the vendor that this is the first statement for the relationship. | Treat the nonzero opening balance as a report-type or scope issue. Request a corrected statement rather than accepting it as a valid carry-forward balance. |
| document_type_mismatch | AP shows an invoice while the supplier statement shows a credit note for the same amount and date. | Compare the supplier document type and sign with the AP transaction. | Reverse the AP invoice, then record or apply the supplier credit note correctly. |
| not_open_maybe_paid | Invoices shown on the statement are absent from your open-payables report because they may already be paid. | Check whether your report is an aged-open-items view, which excludes paid invoices, rather than a full-activity report. | Check paid invoices or use a full-activity transaction list before treating any invoice as missing. |
| dispute_on_hold | The line is already disputed with the vendor. | Check the dispute or hold recorded against the AP bill or vendor file. | Record the dispute in the exception log and leave it open until it is resolved. Do not clear it as a match. |
| vendor_data_issue | The statement is for the wrong legal entity, wrong currency, or has an implausible statement date. | Compare the vendor and entity name, currency, and statement date with the statement you expected. | Stop the reconciliation and request the correct statement before doing any more matching. |
| date_corroborated | The reference is missing or different, but the amount and date agree within 7 days. | Compare the amount and date, then check the available documents for any supporting reference. | No correction is required. You can add the reference to help with future matching. |
| ambiguous_match | A statement line has the same amount and date as more than one invoice, with no reference to identify the correct one. | Check PO numbers and receiving records. Contact the supplier if the evidence still does not identify the invoice. | Do not match the line until you have confirmed the correct invoice. |
| duplicate_ledger | The same invoice number appears twice in your AP ledger. | Search AP for the invoice number and compare the entries to confirm whether it was posted twice. | Void or reverse the duplicate entry. Pay the invoice only once. |
| out_of_period | An item on the statement is dated outside the date range your accounting report covers. | Compare the item date with the start and end dates of your AP report. | No action is needed for this reconciliation. The item is outside the supplied period. |
| ledger_out_of_period | An item in your ledger is dated outside the report's range or after the statement's latest date. | Compare the item date with the statement period and the date range of your report. | No action is needed for this reconciliation. The item is outside the reconciliation window. |
| many_to_one | One statement line equals the sum of 2-4 of your invoices. | Add the 2-4 invoice amounts and compare the total with the statement line. | No correction is needed when the total agrees. The invoices are matched as a group. |
| one_to_many | One of your invoices equals the sum of 2-4 statement lines. | Add the 2-4 statement lines and compare the total with your invoice amount. | No correction is needed when the total agrees. The statement lines are matched to the invoice. |
Manual vs automated vs Statement Zen
| Dimension | Manual (Excel) | Generic automated tool | Statement Zen |
|---|---|---|---|
| Matching exact + partial lines | You compare each line in Excel and decide which possible pairs need review. | Rules can clear exact matches, while partial matches may still need manual review. | The software clears exact matches and ranks possible partial matches for review. |
| Classifying leftovers | You decide how to classify each remaining line and record the reason. | The output may identify a line only as unmatched, depending on the rules used. | Remaining lines are assigned categories for missing items, timing, credits, duplicates, mismatches, report type, and opening balances. |
| Report scope differences (open items vs full activity) | You need to identify whether the report shows open items or full activity before calling an invoice missing. | Results depend on whether the rules account for the report type. | The report type is considered before an item is classified as missing. |
| Exception documentation | You record the category, evidence, owner, and next action in your chosen working file. | Some systems provide only a matched or unmatched status. | The exception log records the category, evidence, and next action for each line. |
| Time per vendor per period | Time varies with the number of lines, statement layout, and quality of the references. | Exact matching can reduce line-by-line work, but unmatched items still need review. | Straightforward matches are cleared first so you can spend review time on the remaining items. |
UK / US / AU terminology
The same control may have a different name in the UK, US, or Australia. Use this table when reading ERP guidance from another region.
| Concept | UK | US | AU |
|---|---|---|---|
| Matching a vendor or supplier statement against your ledger | Supplier statement reconciliation | Vendor statement reconciliation | Supplier statement reconciliation |
| Report of amounts currently owed, grouped by age | Aged Creditors | Aged Payables | Aged Creditors |
| Detailed vendor-by-vendor ledger behind the AP control account | PLCA (Purchase Ledger Control Account) | AP subledger / AP subsidiary ledger | PLCA (Purchase Ledger Control Account) |
| Matching a PO, goods receipt, and invoice when the invoice is entered | Three-way match / GRNI | Three-way match / GR/IR | Three-way match / GRNI |
Statement Zen Academy Team — Practical guidance based on Statement Zen's vendor statement reconciliation work. · Last updated