Timing difference

A timing difference is a gap between the merchant log and the provider statement caused only by when a payment was recorded, not by what happened to it. A payment made just before midnight may appear on the next day’s statement. It is not lost, and it should resolve without a claim.

How it works

A timing difference appears when two sources cut the day at different moments. The merchant may close the day at midnight UTC. The provider may close it at midnight in its own time zone, or settle a day later. An illustrative case:

merchant log:  PAY-3C4D  23:58:41 UTC  success
Provider D:    cut-off 00:00 local (UTC+3)
statement:     PAY-3C4D appears in the next day's file

Viewed one day at a time, the payment looks missing. Viewed across two days, it reconciles.

Why it matters

Treating a timing difference as a discrepancy wastes analyst time and produces claims that providers rightly reject. On one anonymised merchant day, 464 reconciliation lines sat on the day edge. Reconora marks such payments as awaiting, not as discrepancies, and checks them again when the next statement arrives.

How to spot it

Look at the payment time first. If it falls within an hour of a cut-off, check the provider’s time zone and settlement lag. Then open the next day’s statement before raising anything. A real gap survives that check; a timing difference does not.

Related terms

Day edge · No final status · Settlement · Provider statement · Methodology

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