
The supplier statement shows a different balance from your accounts payable ledger. Matching invoice numbers is a useful start. It still leaves a question: which entries explain the difference, and who must resolve them?
A July 2026 r/AskAccounting post describes manually comparing hundreds of statement lines in Excel. It is a public problem report, not an independently verified business result. The workflow below is a proposed method for preparing a reviewable reconciliation.
Freeze the comparison period
Choose the supplier account, legal entity, currency and statement cutoff. Export the relevant ledger with its extraction time. Keep both source files. Comparing a statement ending on Friday with a live ledger updated on Monday can create apparent gaps caused by timing.
Record opening balance, invoices, credit notes, payments and closing balance where available. If the source omits opening items or a payment allocation, flag that absence. Do not silently infer missing transactions from the closing total.
Match with evidence and visible rules
Retain the original reference and a normalized comparison reference. Normalization may remove harmless spaces, but it must not merge genuinely different invoice numbers. Match within the supplier, entity and currency context.
An exact reference and compatible amount can propose a match. Repeated references, amount differences and partial allocations need separate review. A fuzzy resemblance should remain a suggested candidate, with the rule and source lines displayed.
OCR can help prepare rows from a PDF statement. It cannot establish that a credit exists in the ledger or that a payment reached the supplier. Those conclusions need the relevant accounting record and supporting evidence.
Give unmatched items meaningful states
Use distinct reasons: statement only, ledger only, amount difference, credit awaiting allocation, payment awaiting allocation, cutoff difference and reference ambiguity. An unmatched statement invoice is not automatically an unrecorded liability. It might be a timing issue, reference variation or a document already under dispute.
Each item needs an owner, next action, evidence link and review date. “Ask supplier for invoice copy” and “finance to check payment allocation” are different tasks. Resolve the source issue before any authorized accounting correction.
A fictional balance bridge
Suppose the statement closes at 12,000 and the ledger at 10,800 in the same currency. A 1,000 invoice appears only on the statement; a 200 credit appears only in the ledger. Those two items could explain the 1,200 difference under the stated signs and cutoff.
That arithmetic is a hypothesis to verify, not an instruction to post 1,200. The reviewer must establish the invoice status, the credit status and whether both belong in the chosen period. Keep the balance bridge linked to the actual source lines.
Choose a proportionate workflow
For recurring clean exports, a controlled spreadsheet or the reconciliation feature in your accounting system may be enough. Preserve the raw exports and document the matching rules. Add automation when statement layouts, volume or exception routing exceed what the team can maintain reliably.
Kaliits can scope document extraction, proposed matching and a review queue around the approved accounting process. Ledger edits and payment decisions remain with the authorized finance team.
Test closure rather than a green total
Use duplicate references, an unapplied credit, a payment near cutoff and a genuinely missing document. Check that the workflow explains the balance difference and leaves unresolved entries visible.
Measure unresolved-item age, reviewer corrections and time to prepare a supported reconciliation. A matching closing balance alone does not prove every entry is right. Review the document-control scope through Kaliits workflow services.
