2 tables ยท 10 columns
Workflow process map template
One row per handoff: who does it, what goes in and out, the system, touch time and wait time.
This month-end close checklist template is a master inventory of every close task, with preparer, reviewer, due working day, dependencies, evidence and automation fit. It is for controllers and finance managers. List each task once, then sort by due day to build your close calendar. Our close checklist post has the day-by-day version.
Typical tasks are listed by area for you to confirm or delete. This is the master list. For the day-by-day sequence and what to automate, read our month-end close checklist.
Month-end close task inventory template
Free to copy. No email and no download.
Confirm or delete the typical tasks, then add your own in the blank rows. Due is a working day after period end, written WD1, WD2 and so on.
| TaskVerb and object. | PreparerRole. | ReviewerA different person. | DueWD1, WD2. | Depends onTask or report that must come first. | SourceSystem or report. | Evidence savedWhere the proof is kept. | Reviewer checksWhat sign-off means. | FitRules, Model or Person. |
|---|---|---|---|---|---|---|---|---|
| Cash and bank | ||||||||
| Reconcile each bank account | ||||||||
| Clear or explain old reconciling items | ||||||||
| Post bank fees and interest | ||||||||
| Receivables | ||||||||
| Apply cash receipts to open invoices | ||||||||
| Review the aging report and unapplied credits | ||||||||
| Update the bad debt reserve | ||||||||
| Payables and accruals | ||||||||
| Post remaining supplier invoices and credit notes | ||||||||
| Reconcile the AP subledger to the general ledger | ||||||||
| Accrue goods and services received but not invoiced | ||||||||
| Review unmatched receipts and open purchase orders | ||||||||
| Fixed assets and leases | ||||||||
| Capitalize new assets and post depreciation | ||||||||
| Record disposals and write-offs | ||||||||
| Post lease schedule entries | ||||||||
| Payroll and benefits | ||||||||
| Post the payroll journal and reconcile it to the payroll report | ||||||||
| Accrue unpaid wages, bonuses and leave | ||||||||
| Intercompany and equity | ||||||||
| Match and reconcile intercompany balances | ||||||||
| Revalue foreign currency balances | ||||||||
| Post eliminations for consolidation | ||||||||
| Reporting and review | ||||||||
| Run the trial balance and check unusual balances | ||||||||
| Review variances to budget and prior month | ||||||||
| Lock the period and archive the close package | ||||||||
Scroll sideways to see every column.
6 steps, in the order that saves rework.
Ask each preparer to list the tasks they did in the last close, including the ones that live in a personal spreadsheet. The inventory should be longer than the checklist you have today.
One name each. If the same person prepares and reviews, write that down as a control gap and fix it later. Do not hide it.
A task cannot be due before the thing it depends on. Fill the Depends on column honestly, because the longest chain of dependent tasks sets the length of your close.
Write the report or system the figures come from and the folder or tool where the reconciliation is saved. Auditors will ask for it, and so will the next person on leave cover.
Be specific: reconciling items older than a month are explained, accruals tie to receipts. A review that is only a signature is not a control.
Rules means fixed logic such as a scheduled entry, Model means reading or drafting from documents, and Person means judgment such as an estimate. Sort by due day for the calendar, and by fit to see what to automate first.
A made-up case, so you can see what a filled-in version looks like. None of the numbers are real.
Illustrative. Roles, days and checks are made up to show the level of detail.
| Task | Preparer | Reviewer | Due | Evidence saved | Reviewer checks | Fit |
|---|---|---|---|---|---|---|
| Reconcile the operating bank account | Staff accountant | Controller | WD2 | Statement and ledger report in the Cash folder | Items older than a month are explained | Rules |
| Accrue goods received but not invoiced | AP lead | Controller | WD3 | Open receipts report, budget owner replies | Estimates tie to receipts, reversal date is set | Model drafts, Person approves |
| Post lease schedule entries | Staff accountant | Controller | WD3 | Lease schedule, journal reference | Totals tie to the schedule | Rules |
| Review variances to budget | FP&A analyst | CFO | WD5 | Variance report with comments | Lines over the threshold have an explanation | Person |
Scroll sideways to see every column.
How to read it. The schedule-driven tasks are Rules and are the easiest to automate. The accrual needs a draft from documents and a person's estimate. The variance review stays a Person task, because the explanation is the work.
The inventory is the master list: every recurring close task, who prepares and reviews it, what it depends on and how it is evidenced. A checklist is one period's run through that list, in order, by working day. Build the inventory once and generate each month's checklist from it.
Yes. Use Copy for Sheets, click cell A1 and paste. It lands in cells in both Excel and Google Sheets. Copy as CSV is for saving a .csv file or importing. The group names become a Section column, so you can filter by area.
As many as people actually do. List the tasks from the last close, including the ones kept in personal spreadsheets, and expect the result to be longer than your current checklist. We do not quote a standard number, because it varies with systems and entities.
It tags the kind of work the task needs. Rules is fixed logic, Model is reading or drafting from documents, and Person is judgment or approval. It shows where automation helps and where a person must stay.
Sort by due day and follow the Depends on column. The longest chain of dependent tasks sets the length of the close. Shorten that chain first, for example by moving an approval chase before the period ends.
2 tables ยท 10 columns
One row per handoff: who does it, what goes in and out, the system, touch time and wait time.
3 tables ยท 12 columns
Score each candidate workflow on five criteria, weigh it against hours spent, and pick the first pilot.
3 tables ยท 8 columns
Questions, gold answers, sources and expected behavior, plus a run log for every release.
40 questions ยท 7 columns
Forty neutral questions to ask any AI vendor, on data, models, approvals, logging, testing and exit.
1 table ยท 35 items
What to settle before signing: outcome, workflow, data, test thresholds, security, delivery and support.
A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.
What happens next
Strategy call
We learn how the workflow runs today and what a good outcome would be.
Workflow audit
We map the process and measure where a system would save the most time.
Proposal
A written scope, timeline and fixed price for your first system. No obligation to build.
Scenox Studios AI assistant