All insights
Reconciliation

Timing Differences in Reconciliation: What They Are and When They're Not

Timing differences are reconciliation variances caused by transactions recorded in different periods across two systems. This guide covers common scenarios, how to distinguish timing from real breaks, ageing rules, and escalation.

Aetherix Research Published 8 min read

Timing differences are reconciliation variances caused by transactions being recorded in different periods across two systems. The transaction is correct in both systems — it simply hasn't landed in both places at the same point in time. Timing differences are the most common reconciliation break type and the most frequently misclassified.

Why timing differences exist

Every financial system has a recording lag. A payment initiated on Day 1 may clear the bank on Day 3. An invoice posted on the last day of the month may not appear on the vendor statement until the following month. A trade executed at 4:55 PM may settle T+1 or T+2. These lags are normal — but they create variances when two systems are compared at the same point in time.

Common timing difference scenarios

ScenarioSystem A showsSystem B showsResolution
Payment in transitPayment recorded (AP ledger)Not yet cleared (bank statement)Clears next day — auto-resolves
Deposit in transitCash received (AR ledger)Not yet credited (bank statement)Clears within settlement window
Month-end cut-offInvoice posted 31 Jan (buyer's AP)Invoice dated 1 Feb (vendor's AR)Resolves on next period's reconciliation
Trade settlementTrade booked T+0 (portfolio system)Cash/securities move T+1 or T+2 (custodian)Resolves on settlement date
Batch processing lagTransaction entered real-time (ERP)Batch posted overnight (bank/custodian)Resolves next business day
Cross-timezoneTransaction posted 11 PM EST (US entity)Received next business day (APAC counterparty)Resolves within 24 hours

Why timing differences matter

Timing differences are benign — they resolve themselves. But they matter because:

  • They consume investigation time when misclassified as real breaks
  • They inflate exception counts, making it harder to find genuine errors
  • They can mask real issues — a genuine missing payment looks like a timing difference until it ages
  • They complicate period-end close when items straddle the cut-off date

Distinguishing timing from real breaks

The critical question is: will this variance resolve itself in the next cycle? Indicators that a variance is a timing difference:

  • The transaction exists in one system with a recent date (within settlement window)
  • The same type of variance resolved automatically in prior periods
  • The counterparty has confirmed the transaction (e.g., payment confirmation received)
  • The amount matches a known pending item (outstanding cheque, unsettled trade)

Indicators that a variance is NOT a timing difference:

  • The item has been outstanding for longer than the expected settlement window
  • No matching pending item exists in either system
  • The amount doesn't correspond to any known transaction
  • The item appeared as a timing difference last period and still hasn't resolved

Ageing and escalation

Best practice is to classify timing differences by age and escalate when they exceed expected settlement windows:

AgeStatusAction
0-2 daysNormal settlement windowMonitor — expect auto-resolution
3-5 daysExtended but plausibleFlag for review if not resolved by next cycle
6-14 daysOverdueReclassify as potential break, investigate
15+ daysStaleEscalate — this is not a timing difference

How AI agents handle timing differences

The agent maintains a rolling register of expected timing differences — items that should resolve within a known window. On each reconciliation cycle:

  1. New variances are checked against the expected timing register
  2. Items that match a known pending transaction are classified as timing and monitored
  3. Items from prior cycles are checked for resolution — if resolved, they're cleared automatically
  4. Items that exceed their expected window are reclassified and escalated
  5. The agent learns settlement patterns per counterparty and adjusts expected windows

Related

Frequently asked questions

What are timing differences in reconciliation?

Timing differences occur when a transaction is recorded in one system but hasn't yet appeared in another — such as a payment sent but not yet cleared by the bank. They resolve themselves within the normal settlement window and don't represent errors.

How do you distinguish timing differences from real breaks?

Timing differences have a matching pending item, fall within the expected settlement window, and have resolved automatically in prior periods. Real breaks have no matching item, exceed the settlement window, or have been outstanding for multiple cycles without resolution.

Related guides

Reconciliation

Position Reconciliation: What It Is, Why It Breaks, and How to Fix It

Position reconciliation is the process of comparing securities positions held at a custodian against the positions recorded in an investment book of record. This guide covers the full process, common break causes, and resolution approaches.

Reconciliation

Trade Reconciliation: The Complete Process Guide

Trade reconciliation is the process of matching executed trades against confirmations from brokers and custodians to ensure every transaction is accurately recorded. This guide covers the end-to-end process, common failure points, and resolution workflows.

Reconciliation

Investment Reconciliation: What It Covers and How It Works

Investment reconciliation is the umbrella process of verifying that all investment-related records — positions, trades, cash, and corporate actions — agree across custodians, administrators, and internal systems. This guide explains the full scope and common approaches.

Need help with reconciliation?

Our agents handle the exception queue — investigating breaks, determining root causes, and resolving discrepancies with a full audit trail.