Nothing to reconcile against

“Nothing to reconcile against” is a reconciliation outcome meaning that no document allows the payment to be checked: the provider sent no statement, none for that currency, or an incomplete one. It is not a loss and not a match. It is a named volume of money that cannot be verified yet.

How it works

“Nothing to reconcile against” is assigned when the merchant log holds a payment but no provider statement can confirm or deny it. The cause is recorded with the outcome. Illustrative, synthetic example:

  • PAY-5E1B · Provider K · CUR-3 — no statement received for the day.
  • PAY-5E1C · Provider L · CUR-4 — statement received, but only for CUR-1.
  • PAY-5E1D · Provider M — statement received, but it is an incomplete statement.

Each payment keeps its log record. Nothing is marked as matched or as a debt.

Why it matters

“Nothing to reconcile against” is not an error and not a zero. Folding these payments into “matched” hides risk. Folding them into “missing” produces false claims. On one anonymised merchant day, 10.1% of turnover in scope had nothing to reconcile against. 26 providers sent no statement at all.

How to spot it

  • List providers and currencies with traffic in the log.
  • Tick off those with a statement for the same period and currency.
  • Any provider or currency left unticked has nothing to reconcile against.
  • Compare statement line counts with log counts to catch partial statements.

Related terms

Statement coverage · Incomplete statement · Provider statement · No final status · Reconciliation

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