Guides
Why part of the day is always awaiting a statement
Part of every reconciled day is awaiting a statement because provider statements arrive after the payments and cover their own periods and time zones. Those payments are neither discrepancies nor matched. They wait for the statement that covers their hour, and the awaiting share shrinks as the next statements arrive.
What “awaiting a statement” means
“Awaiting a statement” means the provider’s statement does not cover that payment’s hour yet. The payment exists in the merchant log. Notifications may already report it. The statement that would confirm it has not arrived, or it covers a period that ends before the payment happened. Nothing is wrong with the payment, and nothing has been confirmed either. On one anonymised merchant day reconciled by Reconora, 12.6% of turnover in the reconciliation scope was awaiting a statement. That figure describes one day only. It is not an industry benchmark, and your own day will differ. It is also not a discrepancy. The share is large enough that the way it is reported changes how the whole day reads. This guide explains where it comes from, why it is reported on its own, and how it shrinks.
Statements arrive later and cut the day their own way
A provider statement is a file for a period, and the period is the provider’s choice. Payments happen in real time. Statements arrive later: often the next morning, sometimes after several days. Each provider also closes its day at its own moment. One closes at midnight in its own time zone. Another closes at a fixed hour. A third issues a file per settlement batch rather than per calendar day. The merchant, meanwhile, closes its own day in its own time zone. When the merchant reconciles its day, some statements have arrived and some have not. Of those that have arrived, some end before the merchant’s day ends. Every payment that falls outside the statements received so far is awaiting a statement. This is a timing difference, not a gap in the money.
Payments near midnight wait for the neighbouring day
The day edge is the window around midnight where the merchant’s day and the provider’s day disagree. A payment made a few minutes before the merchant’s midnight may be booked by the provider a few minutes after its own. It then appears in the provider’s statement for the next day. Reconciled one day at a time, that payment looks missing from day one. On day two it matches. On one anonymised merchant day, 464 reconciliation lines sat on the day edge. A careful reconciliation holds those lines as awaiting the neighbouring day’s statement. It also looks back: a payment from the previous evening may be found in today’s file. The rule is simple. Before a day-edge payment is called missing, both neighbouring statements must have been checked.
Why counting them as discrepancies would be wrong
A discrepancy is a claim that two sources disagree. A payment awaiting a statement has nothing to disagree with yet. Counting it as a discrepancy turns every late file into a list of false problems. Analysts spend the morning closing them by hand. Worse, some reach the provider as claims, and the provider rightly rejects them when its statement arrives. Each rejected claim weakens the next real one. The discrepancy queue also loses its meaning. If a large part of it is simply early, nobody can tell which lines need action. A reconciliation should reserve the word “discrepancy” for disagreements it can show: an amount that differs, or a fact that differs, such as an outcome or a missing line, with the source rows behind it.
Why counting them as matched would hide risk
Counting awaiting payments as matched is the opposite mistake, and it is quieter. The payment has not been confirmed by the provider. If the statement never arrives, or arrives without that line, the money was never verified. A report that folds awaiting payments into “matched” shows a high rate today and has no way to correct itself tomorrow. It also hides the providers that are slow to send statements. Those providers deserve attention, because a statement that arrives late is a statement nobody checks in time. Keeping awaiting payments apart keeps the risk visible: this much turnover is not yet confirmed, and here is the provider and hour it belongs to.
How the awaiting share shrinks
The awaiting share is not fixed. It falls as statements arrive. When the next statement from a provider is received, every payment in the hours it covers is reconciled again. Each one leaves “awaiting” and lands in a real outcome: matched, differs in money, differs in facts, or nothing to reconcile against if the statement turns out not to cover it after all. Day-edge payments move when the neighbouring day’s file arrives. A payment that stays awaiting long after its provider normally reports is itself a signal. Either the statement is late, or it is incomplete, and both are questions for the provider. Watching the share over the following days tells you more than the figure on the first morning.
How to report it
A useful report shows “awaiting a statement” next to the four outcomes, not inside any of them. The four outcomes are matched, differs in money, differs in facts and nothing to reconcile against. Awaiting sits beside them as a separate line, stated as a share of turnover in the same scope. Each awaiting payment should carry its provider, its hour and the statement period it is waiting for. Grouped by provider, the report then shows which statements are outstanding and when they are due. A reader can see at once that the day is partly unconfirmed, and why. Reconora’s reconciliation results show “awaiting a statement” next to the four outcomes, as a share of turnover in scope: it is not a discrepancy, because the provider’s statement does not cover that hour yet.
Not the same as no final status, or nothing to reconcile against
“Awaiting a statement” is easily confused with two other states, and each needs its own handling. No final status is about the provider’s word on the payment itself: no message has yet said whether it succeeded or failed. It is a separate count, not part of the awaiting share. On one anonymised merchant day, 14,191 of 114,065 transactions in scope had no final status from the provider. “Nothing to reconcile against” is an outcome, not a wait: no statement exists that could confirm the payment, for example because the provider sends none for that currency. Awaiting payments are expected to resolve when a known statement arrives. Payments with nothing to reconcile against are not. The methodology page explains how each of these figures is scoped.
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.
By Reconora Research · Updated