- Documentation completeness before cut-off is the strongest predictor of close duration.
- Every step needs an owner and a dependency, not just a description.
- Reconcile weekly so the month-end version is a formality.
- Accruals require judgement and should follow a written cut-off rule.
- Distribute with commentary, not just numbers.
Before close: the work that decides everything
Most of the variance in close duration is determined before the period even ends. If receipt completeness is above ninety-five per cent and review queues are clear on the last day, close runs to schedule.
That means the highest-leverage close activity happens continuously during the month, not in the first week of the next one.
- Automatic receipt capture running for all cardholders.
- Coding rules applied to recurring merchants.
- Review queue cleared weekly rather than at month-end.
- Bank and card feeds confirmed working, with gaps investigated immediately.
The close sequence
Working days after period end. Adjust the number of days to your own complexity, but keep the order.
| Day | Step | Owner | Depends on |
|---|---|---|---|
| 1 | Enforce cut-off; confirm all feeds complete | Finance operations | Feed connectivity |
| 1–2 | Chase outstanding documentation | Finance operations | Exception list |
| 2 | Clear the review queue | Cost centre owners | Documentation |
| 2–3 | Reconcile bank and card accounts | Finance operations | Complete feeds |
| 3 | Post accruals and prepayment releases | Accountant | Reconciliations |
| 3–4 | Review payables and unbilled receivables | Accountant | Accruals |
| 4 | Prepare management pack and commentary | Controller | Ledger closed |
| 5 | Review, approve and distribute | Finance lead | Pack complete |
Accruals and cut-off
Accruals record costs incurred but not yet invoiced, so the period reflects what actually happened. This is judgement, not data entry, and it needs a written rule to be applied consistently between months and between people.
Define the rule once — which date determines the period, what materiality threshold applies, and how recurring accruals are reversed — and document exceptions.
- Fix the rule that determines which period a cost falls into.
- Set a materiality threshold so trivial items do not consume time.
- Reverse recurring accruals automatically to avoid double counting.
- Document any judgement call at the time, not at audit.
What usually causes delay
In practice, close is rarely delayed by accounting complexity. It is delayed by inputs arriving late, and the same three inputs are responsible almost every time.
- Receipts arriving after cut-off, requiring rework of already-coded transactions.
- A review queue nobody cleared, discovered on day two.
- A feed that silently stopped, discovered during reconciliation.
Evidence to retain
Retain the reconciliations, the approval records, the accrual workings and the version of the pack that was distributed. Auditors ask for evidence that the process operated, and reconstructing it later is far more work than saving it at the time.
Frequently asked questions
It depends on complexity, but predictability matters more than the number. Reducing variance is usually easier and more valuable than shaving a day off the average.
No. Data collection, coding and reconciliation can be heavily automated; accruals, judgement and commentary cannot. Automation moves the effort, it does not remove it.
Documentation completeness before cut-off. It is the input that delays everything downstream and the one most improved by configuration rather than effort.
Keep reading
Sources and further reading
Every factual statement on this page is checked against primary documentation. Terms change frequently, so confirm details with the provider before acting on them.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.
- IRS Publication 463 — travel, gift and car expenses Used for statements about expense substantiation and record keeping in the United States.
- Nacha — ACH Network rules and resources Used for statements about ACH timing and payment rails.