Journal · 12 June 2026
Aging buckets that auditors actually trust
Binary queues — open versus closed — look tidy in a dashboard and fall apart in an audit sample. Transaction reconciliation audits for fintech need aging that explains ownership, not just calendar days.
Five tags that change the conversation
We coach desks to tag every open exception with one primary cause: timing, amount, party, fee-path, or data quality. Secondary notes are fine; primary tags should be mutually exclusive so aging charts mean something.
Day thresholds with owners
Day 0–1 belongs to the matcher and ops analyst. Day 2–4 escalates to a rail owner. Past day 5 needs a named risk reviewer. Auditors care less about the exact numbers than about whether someone is accountable when the clock flips.
What not to do
Do not dump unexplained items into “other.” That bucket becomes the place where fee-path drift hides until an examiner picks the largest amount. In Ledger Break Investigation we force learners to retire miscellaneous codes before Module 3 ends.