Reading a reconciliation break before it becomes a finding

A break on a daily processor reconciliation can be ordinary: timing differences, weekend settlement lag, a refund still in flight. The question for a fintech audit is whether someone owns the item, whether it ages past a stated threshold, and whether the explanation still makes sense when a third party re-reads it months later.

Teams that clear breaks verbally in chat leave thin evidence. When supervisors or investors ask later, the story evaporates. A short note in the reconciliation pack—reference, amount, expected clear date, owner—often separates a tidy operation from a reportable gap.

Aging is the quiet signal. A cluster of items older than your stated policy suggests the control design is fine on paper while the practice has slipped. That pattern shows up frequently in wallet firms after a processor migration, when temporary workarounds become the unofficial close routine.

Before an engagement starts, pull a break aging report for the last two month-ends. If you cannot produce one quickly, that itself is useful information about how your close is run.