Month-end close process: a day-by-day checklist and what to automate

The month-end close process is the set of tasks an accounting team completes after a period ends so the books are accurate and reportable: finishing transactions, reconciling accounts, booking adjusting entries, reviewing variances and locking the period. A good checklist gives every task an owner, a due day and a sign-off. Automation helps most with data gathering and reconciliation, and least with judgment calls.

#How long should month-end close take?

It depends on company size, number of entities, system quality and what your auditors and board expect. Published "average" close times come from surveys that define "closed" differently, so we don't quote one. Set your own target, count the working days you actually take, and track it monthly. A close that gets faster without more post-close adjustments is a real improvement.

The checklist below assumes a five-working-day close for a single-entity company on a cloud ERP. Treat the day numbers as a template. A multi-entity group will need more days and an intercompany step. A very small company may need fewer.

#Month-end closing procedures for accounting teams, by working day

"WD" means working day after period end. "Pre-close" tasks run before the month ends, so the close doesn't start with a backlog.

Every row needs a named person, not a team. You can't ask "Accounting" why the bank reconciliation is late.

#Four things that shorten a close

Most close problems start before the period ends.

1. Do more during the month. Reconcile bank accounts weekly, process invoices daily and chase approvals before cutoff. A close that starts with a short list of open items beats one that starts with a pile.
2. Make cutoff a rule. Agree a time after which transactions go to the next period, and enforce it in the system where you can.
3. Standardize recurring entries. Depreciation, prepaid amortization, rent and allocations should be scheduled journals, not entries retyped every month.
4. Review by exception. Reconcile in full only where differences appear. If a reconciliation matches 98% of lines automatically, the accountant spends their time on the other 2%.

#What to automate

The common thread: the data lives in systems, the logic can be written down, and a person can check a summary.

Data gathering and matching. Pull bank feeds, card transactions, payment processor payouts and subledger balances into one reconciliation view. Match bank lines to ledger entries by amount, date, reference and counterparty, then list the unmatched items with likely candidates. Chase missing documents, such as receipts for card spend, from whoever holds them.

Recurring entries. Scheduled journals cover depreciation, prepaid amortization, standard accruals and allocations. We usually prepare these as drafts that a person posts. Currency revaluation at period-end rates fits here too.

Close management. A live checklist tracks task status, shows who is blocking whom and nudges owners before a deadline. Sign-offs get timestamps automatically.

Variance analysis. An AI step can compare actuals to budget and to last month, then draft a plain-language explanation for each large movement using ledger detail, such as "Software expense up $12,400, mainly a new annual subscription booked on the 14th." A person checks it and adds context the data doesn't hold.

Our finance operations practice builds these as workflows that connect to your ERP and bank feeds, with review queues for anything uncertain. The month-end close blueprint shows how the pieces fit together.

#What stays human

Some tasks we usually don't automate, and we say so up front.

• Estimates and judgment. Reserves, impairment, provisions and anything with an assumption behind it. A system can gather inputs and draft a number, but a person owns it.
• Unusual transactions. One-off contracts, restructurings and acquisitions need accounting judgment under your reporting standard.
• Explaining variances to management. A draft saves time. The controller still has to know the business reason.
• Period lock and final sign-off. These are controls, so someone with authority should perform them.
• Posting entries with no review. AI can propose journal entries and attach the evidence. It shouldn't post them unsupervised.

Key point: Automate the preparation, keep the approval. Draft journals, matched reconciliations and variance commentary can all be generated, but a named person reviews and signs each one.

#Controls to keep in place

A faster close that is weaker on control isn't an improvement.

• Journal entries above a set amount, or manual entries to sensitive accounts, need a second person's approval.
• The person who prepares a reconciliation isn't the person who reviews it.
• Every automated journal records its source data, the logic that produced it and who posted it.
• Access to lock or reopen periods is restricted and logged.
• Changes to automation rules, such as allocation percentages, go through review like any other control change.

If you're audited, talk to your auditors before changing how reconciliations and journals are produced. They'll want to understand the evidence trail, and it's much easier to design it in at the start.

#Where to start

Don't try to automate the whole close at once. Pick the task that takes the most hours and has the clearest rules. For many teams that's bank and card reconciliation. For others it's recurring journals or chasing AP approvals. Our accounts payable automation guide covers the supplier-invoice side, which feeds the early days of the close.

A practical sequence:

1. Time your current close task by task for two cycles.
2. Pick the one or two tasks with the most hours and the most repetitive logic.
3. Automate the preparation step, with review gates.
4. Run it alongside the manual process for a cycle and compare results.
5. Move to the next task only once the first is stable.

If you want help sizing this, book a strategy call. Send us your close calendar, and we'll tell you where the hours sit and which tasks are worth automating.

#Frequently asked questions

#How do I perform month-end closing?

Cut off transactions for the period, post remaining invoices and receipts, reconcile bank and balance sheet accounts, book accruals and adjusting entries, review the trial balance and variances, then get sign-off and lock the period. Use a checklist with a named owner and due day for every task.

#How long should month-end close take?

It depends on your size, number of entities and systems, and there's no single right answer. Set a target based on what management needs, count your actual working days each month, and work on the slowest tasks. Faster is only better if post-close adjustments don't rise.

#What is the best software for creating a month-end close checklist?

A spreadsheet works for a small team. Dedicated close management tools add task dependencies, reminders, sign-offs and audit trails, and some ERPs include a basic version. Choose based on entity count, auditor expectations and whether you need to connect the checklist to reconciliation and journal workflows.

#What are the best practices for a month-end close checklist?

Assign every task to one named person with a due day. Do reconciliations and approvals during the month. Schedule recurring entries. Separate preparers and reviewers. Review the checklist after each close, and remove or reorder tasks that caused delays.

#Can month-end close be automated?

Parts of it can. Data gathering, bank matching, recurring journals, currency revaluation, reminders and variance drafts are good candidates. Estimates, unusual transactions, final review and period lock remain human decisions.

#Is it safe to let AI book journal entries?

We recommend that AI drafts entries and attaches the supporting evidence, and a person approves and posts them. That keeps accountability clear and gives auditors a trail showing who approved each entry and why.

#What is month-end reporting?

Month-end reporting is the pack produced after the books are locked: the income statement, balance sheet and cash flow, a variance commentary and whatever management or the board asks for, such as aging reports or departmental views. It depends on a clean monthly closing, because late adjustments change numbers people have already read. Drafting the pack and the variance notes can be automated, and the controller approves it before it goes out. Our reporting automation page covers that part, and month-end accounting steps are in the checklist above.