Timing Difference
A timing difference is a temporary discrepancy between two sets of financial records caused by transactions being recorded in different periods across systems. In reconciliation, timing differences arise when a payment is initiated in one system but not yet reflected in another — for example, a wire sent on Friday that settles on Monday. Unlike true errors, timing differences are expected and self-resolving, but they must be tracked to prevent false exception flags and to maintain accurate real-time balances.
Key Details
- Common causes include bank processing delays (T+1 to T+3 settlement), batch posting schedules, and cut-off time mismatches between systems
- Timing differences account for 40-60% of unmatched items in typical reconciliation runs, making them the largest category of exceptions
- Automated reconciliation engines use configurable date tolerance windows (e.g., +/- 3 business days) to match across timing gaps
- Persistent timing differences that exceed expected settlement windows should trigger alerts — they may indicate failed transactions or system errors
- Multi-currency timing differences compound with FX rate fluctuations, requiring date-specific rate lookups for accurate matching
- Tracking timing differences separately from true exceptions improves match rates and reduces false positives for operations teams
- Best practice: maintain a timing difference register that ages items and auto-escalates when expected clearing dates are missed