Invoice Reconciliation

Overview

Context and purpose

It determines whether each obligation is unpaid, partially paid, exactly paid, overpaid, reversed, refunded, or otherwise resolved. Material operational risks include unbalanced postings, wrong accounts, stale exchange rates, duplicate events, missing fees, cutoff mismatches, unexplained suspense, manual changes without evidence, and reconciliation that forces totals to match without finding the cause. The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence. Invoice Reconciliation should remain distinct from Reconciliation and Reconciliation Exception , because each can represent a different stage, record, control, or financial outcome. Important failure modes include missing records, duplicate matches, timing differences, hidden fees, currency mismatches, stale files, and adjustments that force balances to agree without explaining the cause. Controls should keep original source records immutable, use stable match keys, explain many-to-one or one-to-many relationships, and route unresolved differences to an aged exception queue.

How it works

Invoice reconciliation matches what the invoice requested with verified incoming payment evidence and the merchant’s order and accounting records. Differences can involve short payment, excess payment, wrong asset, duplicates or timing.

Practical checks and failure points

Preserve transaction identifiers, amounts in exact base units, confirmation state, fees and exception decisions.

Related concepts

Invoice Generation · Invoice Metadata