Discrepancy queue

A discrepancy queue is the work list of payments that did not reconcile, each with a named reason and evidence from every source. It is a list to clear, not a report to read: an operator approves, defers or bundles each item into a claim, and every action is recorded.

How it works

A discrepancy queue holds one row per payment that did not reconcile, with its reason. Operators filter by reason, provider or currency. An illustrative slice:

PAY-2B3C  Provider H  CUR-1  amount differs            log 1500 / statement 1000
PAY-4D5E  Provider K  CUR-3  in the statement, not in the log
PAY-6F7A  Provider H  CUR-1  missing from the statement

Each row opens the evidence: the provider’s message, the merchant’s record and the statement line, each with its row address. Rows with the same provider and reason can be bundled into a claim candidate.

Why it matters

A discrepancy without an owner, a reason and an age is rarely closed. On one anonymised merchant day Reconora’s queue held 809 discrepancies, each with a named reason. The engine grouped them into 11 claim candidates covering 128 payments.

How to spot it

Look at how your team handles differences today. If they sit in spreadsheet tabs without a reason column, an owner or a date found, you have a report, not a queue. A queue tells you what is open, why, and for how long.

Related terms

Claim candidate · Reversed outcome · Statement-only payment · Tamper-evident audit trail · Discrepancies and claims

Try it on one day of your data

One day of your data, reconciled, and the report stays with you whether or not you continue.

Updated