The accountant who reconciles cash is out on day two of close. Her backup finds the checklist, opens the task, and sees “Bank rec: done” from last month. Nothing says which statement was used, why one transfer stayed open, or who signs off. The backup spends the morning in someone else’s inbox.
A close checklist is only as good as what it lets a stranger do. Before you automate any part of the close, make the checklist carry enough detail that a backup could run it, then use one real close to find the delays worth fixing.
Start with the task that held up sign-off
Take your last close and work backward from the controller’s final sign-off. What was the last thing it waited for? Then what was that task waiting for? Keep going until you reach an input: a bank statement, a receiving cutoff, an intercompany confirmation, an accrual schedule from operations.
You will usually find one of three kinds of delay:
| Kind of delay | What it looks like | What fixes it |
|---|---|---|
| Waiting for an input | Reconciliation can’t start because the statement or report isn’t in | An owner and a deadline for the input; automation won’t help |
| Preparation effort | Hours of matching, ticking, or copying between reports | A tool on that specific task |
| Waiting for review | Work is done but sits until the reviewer gets to it | Review scheduling, or smaller review batches |
Track these three separately. If a reconciliation waited two days for a bank file and took three hours to prepare, faster matching saves at most the three hours. The two days remain.
Give each task enough detail to hand off
Every task on the checklist should answer six questions without anyone being in the room.
| Field | What to write down |
|---|---|
| Owner and backup | Who prepares the work and who can take it over |
| Predecessor | Which earlier task or report must finish first |
| Source | System, account, cutoff, and report filters |
| Evidence | The reconciliation, supporting records, and explanations for open items |
| Reviewer | Who checks the result and what they must verify |
| Unresolved items | Exact difference, current owner, next action |
The predecessor field matters because finishing one task is what lets another start. Oracle’s Financial Close Management guide describes tasks waiting on predecessors and submitted work passing to an approver (Oracle Financial Close Management user’s guide). Use the same distinction: a preparer can be finished while review is still open, and the next task may depend on either.
Microsoft documents that Dynamics 365 Finance supports task dependencies in financial close templates, applies those templates to specific periods through schedules, and retains completed task history (Microsoft’s financial close workspace documentation). If you run the close in a spreadsheet or another ERP, keep the same link between each task and its prerequisites in a column.
Replace the checkbox with a completion check. For a reconciliation, “complete” means an approved worksheet plus a list of unresolved items with owners. A tick tells the reviewer nothing about what changed.
An example close sequence
The order matters more than the day numbers, which depend on your calendar and staffing. Here is a typical dependency chain for a mid-sized AP/AR operation. Treat it as a template to adjust.
| Step | Task | Waits for | Evidence at completion |
|---|---|---|---|
| 1 | AP cutoff: last bills entered for the period | Receiving cutoff, invoice inbox cleared | List of late invoices held for accrual review |
| 2 | Receipt accrual review | Step 1; receiving report | Unmatched receipts with owners; accrual schedule |
| 3 | Bank reconciliations | Statements; step 1 for payment runs | Statement balance, book balance, outstanding items |
| 4 | AR cutoff and cash application | Bank activity through period end | Unapplied cash list with reasons |
| 5 | Recurring and accrual journals | Steps 2 and 4 | Source schedules and approved entries |
| 6 | Subledger to GL tie-outs | Steps 1, 4, and 5 | AP and AR aging vs. control accounts, differences explained |
| 7 | Intercompany tie-out | Each entity through step 6 | Paired balances, timing items, approved corrections |
| 8 | Flux review and controller sign-off | Steps 3, 6, and 7 | Reviewed balances, open exceptions, reviewer name |
| 9 | Period lock | Step 8 | Authorized close decision |
Steps 2 and 5 are where late changes tend to land. A bill that arrives after the accrual review either gets accrued, gets posted, or occasionally gets both. The receipt accrual guide covers step 2 in detail, and journal entries, accruals, and prepaids covers step 5.
Verify before you lock
A checklist can show every task complete while a late bill is still waiting to post. Before closing the period, confirm the ledger still reflects what the reviewers approved.
| Stage | Evidence to review |
|---|---|
| Cutoff | Transaction dates, invoices received late, owner for exceptions |
| Reconciliation | Bank, AP, and AR tie-outs using the same period and entity as the ledger |
| Adjustments | Approved journals, source schedules, required reversals |
| Review | Reconciliations signed off, unresolved differences listed, reports refreshed |
| Period close | Authorized close decision and a record of any reopening |
Use the posting controls your ERP has. Oracle documents that NetSuite’s Period Close Checklist includes locking tasks for AP and AR before the period is closed, and describes preliminary locks that limit posting while review finishes (Oracle’s accounting period close documentation). Check which tasks appear in your configuration and who is authorized to perform them.
Tie each approval to the balance the reviewer saw
The controller is ready to review AP. The reconciliation was signed off, then someone posted another bill to the period. The sign-off now covers a balance that no longer exists.
Illustrative example: a late bill after sign-off
- AP control account reviewed and signed off at $412,300.
- On day four, a $6,800 maintenance bill dated in the period is posted. The control account is now $412,300 + $6,800 = $419,100.
- The receipt accrual review on day two had already accrued that same $6,800 because the work was received but not billed.
Unless the accrual is reversed against the bill, period expense is overstated by $6,800 and the accrued liability carries a balance with nothing behind it. The fix is one reversing entry, but only if someone sees the change. Three things should happen automatically when a posting lands after sign-off:
- The owner of the affected reconciliation is told which balance changed and by how much.
- The earlier evidence is kept, and the new review links to it rather than overwriting it.
- Any related task (here, the accrual schedule) is flagged for a second look.
If a closed period must be reopened, record the reason, the approved entry, and the rerun reports before closing it again.
Where automation helps, and where it should stop
Good targets are the preparation-heavy tasks with clear inputs: bank matching, subledger tie-outs, recurring journals, gathering support for flux explanations.
Take a bank account that is off by the amount of one transfer: the outgoing leg posted before cutoff, and the receiving bank credited it the next day. A tool can draft that explanation and save a lookup. A journal entry would be premature, because the reviewer still needs to check both statements and the ledger. Have the draft show what it relied on:
| Close item | What the draft should show |
|---|---|
| Transfer across cutoff | Both bank accounts, ledger entries, actual clearance dates |
| Unbilled receipt | Receipt and order lines, billed amount, what the ledger already recorded |
| Intercompany difference | Both entity records, currency basis, the unmatched entry |
| Proposed adjustment | Source evidence, accounting period, amounts for review |
Keep arithmetic in the reconciliation schedule so the reviewer can recalculate it, and keep a proposed journal separate from a posted one. Oracle’s NetSuite documentation distinguishes saving a journal as a draft from submitting it through approval and posting (Oracle’s guide to creating a journal entry). Check how your setup enforces that step and who can act at each point.
Test whether automation actually speeds the close
A task that finishes sooner but reopens after sign-off creates rework. Measure both.
- Pick a completed period. Save the source records, the signed result, and the exceptions.
- Run the tool on the same inputs. Include an ambiguous match and an item with no supporting record.
- Have the reviewer compare the output with the approved result. Record each correction and how long it took.
- In the next live close, log when the task was ready, when work started, and when it was approved. Check whether the next task could start sooner.
Then rehearse a handoff. Give a backup last month’s cash reconciliation with one outstanding transfer and ask them to reproduce the report, identify what remains open, and check the transfer against the next statement. If they need an email or a desktop file, add that evidence to the task. Expand only once someone outside the pilot can reconstruct the result from saved records.
What usually goes wrong
| Symptom | Likely cause |
|---|---|
| Checklist is 100% complete but numbers move after sign-off | No posting restriction, or no alert when a reviewed balance changes |
| Faster reconciliations, same close date | The constraint was an input, not preparation |
| Backup can’t finish a task | Evidence lives in the preparer’s inbox, not with the task |
| Same reconciling items every month | Items carried without an owner or a next action |
| Expense double-counted | Accrual and late bill both posted without a reversal |
First changes for next month’s close
- Trace last month’s sign-off back to its slowest input and give that input an owner and a deadline
- Add predecessor, evidence, and backup columns to the checklist
- Decide who is notified when a reviewed balance changes after sign-off
- Pick one preparation-heavy task for a pilot and log ready, start, and approval times
Related: bank reconciliation automation, intercompany and GL reconciliation, and audit trails for automated AP and AR.