Aged reconciling items: owner and escalation.
A framework for aging, assigning, escalating, and carrying forward open reconciling items so that open work stays visible instead of becoming routine.
An open item without an owner is not being managed.
Aging buckets are a forcing function, not a policy. Use them to make sure that items which stop moving are either resolved, escalated, or consciously carried forward with a named owner.
Illustrative aging buckets
Thresholds should follow your own materiality and audit expectations. The action column matters more than the day count.
| Bucket | Default expectation | Who is involved | If still open |
|---|---|---|---|
| Current (0-30 days) | Resolve in the current period | Preparer | Moves to the next bucket with a reason |
| 31-60 days | Resolve with a documented explanation | Preparer + reviewer | Escalated to the close owner |
| 61-90 days | Investigate the root cause | Close owner | Reported as a control issue |
| 91-180 days | Decide: correct, reclassify, or carry forward | Controller | Requires written approval to carry |
| Over 180 days | Treat as a process defect, not a task | Controller + leadership | Escalated with a proposed remediation |
The escalation ladder
Name an owner per item
Ownership sits with a person or role, never with a shared mailbox. An item with a team name and no name attached will age indefinitely.
Record the intended action and date
Each open item carries a next action and a review date. The review date is what makes aging visible without a separate report.
Escalate on schedule, not on frustration
Escalation should follow the published bucket thresholds. Deciding to escalate because something feels old makes the threshold meaningless.
Decide explicitly at the threshold
For items past the threshold, the choice is to correct, reclassify, or carry forward. Each is legitimate; leaving it undecided is not.
Correct, reclassify, or carry forward
Write-offs and reclassifications are accounting decisions with policy and, where relevant, auditor implications. Treat them as decisions that follow your own policy rather than as cleanup.
Correct
The difference was an error. Post the correcting entry with a reason, a reference to the investigation, and an approval. Correcting entries are normal; unexplained ones are not.
Reclassify
The item is not wrong, but it sits in the wrong account or the wrong period. Document why the reclassification is appropriate and whether it affects prior comparability.
Carry forward
The item is still open for a legitimate reason. Record the reason, the owner, the next review date, and the approval to carry it forward again.
Report the trend, not just the balance
A static list of open items hides the problem that matters: the same item reappearing every period.
- Track the count and value of items entering each bucket each cycle.
- Separate new items from items that carried forward, since they need different fixes.
- Flag any item that has been carried forward more than once for leadership review.
- Report a process fix for repeat categories, rather than only closing the individual item.
Make the clock visible to the owner.
Aging is not about blaming the preparer. It is about ensuring that an item which has stopped moving gets a decision from someone able to make it, before it becomes a write-off nobody can explain.
How old are your oldest reconciling items?
If the answer is 'we would have to check', that is worth a conversation.