Reconciliation Exception

Overview

How it works

The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence. For Reconciliation Exception, this point supports the definition’s focus on reconciliation exception is an item or difference that the normal matching process cannot resolve within defined rules.

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. For Reconciliation Exception, this point supports the definition’s focus on reconciliation exception is an item or difference that the normal matching process cannot resolve within defined rules.

What matters in practice

An exception is a discrepancy that automated matching cannot safely resolve: missing payout evidence, duplicate credits, currency mismatch, late payment or a fee difference beyond tolerance. Each exception should record affected records, observed values, expected values, severity, owner and resolution evidence. Avoid 'clearing' exceptions merely by changing a dashboard status; corrections must flow to the ledger and relevant customer records. Thresholds and aging reports prevent small discrepancies from accumulating. Reconciliation should allow multiple transaction legs and conversions rather than assuming one invoice matches one chain transfer.

Exceptions should age through a managed queue with a reason code, owner, priority and expected resolution date. A missing provider record may be temporary; a token-decimal mismatch may require a ledger correction; an unsupported deposit can need customer verification. Measures such as oldest unresolved exception, total outstanding value and repeat causes are more actionable than a simple count of mismatches. Document manual decisions before closing the case.

Related glossary concepts

Reconciliation; Payment Exception