What are reconciliation exceptions?

‍

Reconciliation exceptions are transactions or balances that cannot be automatically matched during a reconciliation process — items that appear in one data source but not another, or items where the amounts, dates, or references do not agree within defined tolerances. They are the output of automated matching that requires human investigation and resolution.

‍

Exceptions are not errors by definition — many are legitimate timing differences or system behaviour. But each one needs to be investigated, explained, and either cleared or corrected before reconciliation can be certified.

‍

What causes reconciliation exceptions

‍

Timing differences. A payment issued by the company has not yet cleared the bank. An invoice posted in the ERP has not yet been matched by the supplier's system.

‍

Amount discrepancies. A supplier invoice amount differs from the purchase order by more than the matching tolerance. A gateway fee has been deducted differently than expected.

‍

Missing references. A bank credit cannot be matched because the remittance information is absent.

‍

Duplicate postings. The same transaction has been entered twice in one system and once in the other.

‍

Data format differences. The same transaction is described differently in two systems — different date formats, different reference conventions — preventing automatic matching.

‍

Why exception management determines close speed

‍

In organisations with high exception volumes and slow resolution workflows, the close sprint is largely an exception-clearing sprint. Finance teams spend the first week of close investigating items that should have been resolved during the month. The volume of open exceptions at period-end — and the average time to resolve each one — is the single biggest determinant of close duration.

‍

Related: Exception management · Account reconciliation · Continuous close · Straight-through processing (STP)