Blog ·

Month end close checklist: the steps, day by day

A month end close checklist is the ordered list of everything a finance team does to finish one month's books: stop new transactions at a cut-off, reconcile every balance sheet account, post accruals and adjustments, review the numbers, and issue the statements. The checklist below is grouped by working day after month end, because the order matters as much as the steps: a reconciliation done before the last invoices are posted has to be done twice. The second half of this guide covers the part most checklists skip, which is making sure the close actually starts on time every month without somebody remembering to copy last month's list.

Treat it as a starting point. Every company adds its own lines for payroll, inventory, intercompany or revenue recognition, and your auditor may expect some steps to be signed off by a second person.

Month end close checklist by working day #

Most small and mid-sized teams spread the close over the first five to ten working days of the new month. The table shows a common shape. Your days will differ, but the dependencies between the rows rarely do.

Working day Phase What gets done Depends on
Last day of the month Prepare Send cut-off reminders, chase expense claims, confirm the payroll run Nothing
Day 1 Cut-off Post the last sales invoices and supplier bills, lock the prior period for everyone except finance Cut-off reminders went out
Day 1 to 2 Cash Reconcile every bank and card account to its statement Statements downloaded
Day 2 to 3 Receivables and payables Reconcile the AR and AP ledgers to the control accounts, review the aging reports Cut-off posted
Day 3 Accruals Book accrued expenses, prepaid amortisation, deferred revenue, depreciation Ledgers reconciled
Day 3 to 4 Balance sheet Reconcile the remaining balance sheet accounts, clear suspense and clearing accounts Accruals booked
Day 4 Review Trial balance review, flux analysis against last month and budget, a second reviewer signs off All reconciliations done
Day 5 Report Produce the P&L, balance sheet and cash flow, write the commentary, send the pack Review signed off
Day 5 Close Lock the period, file the support, note what slowed this close down Pack sent

The column people skip is the last one. A checklist without dependencies turns into a race to tick boxes, and the boxes that get ticked first are the easy ones, not the ones that unblock the rest.

The steps in detail #

Before month end: prepare #

The close is faster when the mess is cleared before the month is over.

Day 1: cut-off #

Cut-off means deciding which transactions belong in the month being closed and posting all of them.

Days 1 to 3: reconcile cash, receivables and payables #

Reconciliation is matching what the books say to an independent source.

  1. Bank and card accounts. Match the ledger balance to the statement balance, and explain every difference. Outstanding cheques and deposits in transit are normal; an unexplained difference is not.
  2. Accounts receivable. The total of the customer ledger should equal the receivables control account. Review the aging report and decide whether any balance needs a provision.
  3. Accounts payable. Same test for the supplier ledger. Look for duplicate bills and bills posted to the wrong supplier.

Day 3: accruals and adjustments #

These entries move income and expense into the month they belong to, whatever the date on the invoice.

Each journal should carry a short reason and a link to its support, because the reviewer on day 4 will ask.

Days 3 to 4: the rest of the balance sheet #

Work through every balance sheet account that was not reconciled already: fixed assets, loans, payroll liabilities, tax accounts, intercompany balances. A suspense or clearing account should end the month at zero, or with a list of what is in it and why.

Day 4: review #

Day 5: report and lock #

Where a month end close checklist breaks down #

The steps are well known. What goes wrong is rarely the accounting. It is usually one of these:

A task tracker fixes the first three if the close is a set of tickets with owners and due dates. The fourth needs a schedule that knows your working days.

Running the close checklist in Jira #

If your finance team already works in Jira, the close fits naturally as one parent issue per month with a subtask for each phase. Our Jira for finance guide covers setting up the project itself; this section is about the checklist.

A workable structure:

Issue Type Owner Due
Month end close: September 2026 Task Controller Day 5
Cut-off and lock prior period Subtask AP lead Day 1
Bank and card reconciliations Subtask Accountant Day 2
AR and AP reconciliations Subtask Accountant Day 3
Accruals and adjustments Subtask Senior accountant Day 3
Balance sheet reconciliations Subtask Senior accountant Day 4
Review and sign-off Subtask Controller Day 4
Reporting pack Subtask Controller Day 5

Doing this by hand means cloning last month's issue and its subtasks, renaming them, and resetting the dates. It works, and it brings back the spreadsheet problem: somebody has to remember. Our Jira subtask template guide compares the ways to get the same subtasks every time.

Have the close create itself every month #

Recurring Work Items for Jira creates the close issue and its subtasks on a schedule you write once. As of October 2026, this is how a close rule is set up in it:

  1. Repeats: Every month, on a date, day 1. To have the preparation ticket arrive before month end instead, choose day 31 and, under In months without that day, choose Use the last day of that month.
  2. If it falls on a non-working day: Move it to the next working day for a rule on the 1st, so a close that would start on a Saturday arrives on Monday. Move it to the previous working day suits the month-end preparation rule, which has to be done before the period ends. The working days and holidays are the project's setting, covered in our Jira holidays guide.
  3. Summary: Month end close: {{now.minusMonths(1).monthName}} {{now.minusMonths(1).year}}. A rule running on 1 October titles the issue for September, and the one on 1 January names December of the right year. The full list is on the tokens page.
  4. Due date: 1 week after, or an expression of your own such as {{now.plusDays(6).date}}. If the run moved off a weekend, the due date is counted from where it landed.
  5. Subtasks: one per phase from the table above, each with its own assignee. A rule creates up to 10 subtasks per run, in the order you list them.
  6. If the previous issue is still open: Create nothing until the previous issue is closed stops an unfinished close from being buried under the next one. The skipped run appears in the rule's history, naming the issue that held it up.

One limit to know before you rely on it. Subtasks share the parent issue's due date. The app has no "third working day" option either. If you want each phase due on its own working day, split the close into two or three rules: one for cut-off and cash on the first working day, and one for review and reporting a few days later, each with its own due date.

Everything the app does is scoped to the one Jira project you turn it on for, so the close calendar lives with the finance team and nowhere else. It runs on Jira Cloud only.

Jira Automation can also create a ticket on a schedule. Our Jira recurring tasks guide compares it with cloning and with scheduling apps, and is worth reading if you already have automation rules in place.

When a manual checklist is enough #

You do not need a scheduler, or Jira at all, when:

In those cases a well-kept spreadsheet or a pinned document is honest and cheap. The case for tickets grows with the number of people involved and the cost of starting late.

Frequently asked questions #

How long should a month end close take? It depends on the size of the business and how many entities and systems feed the books. Plan for a number of working days you can hit every month, then shorten it one step at a time by fixing whatever slowed the last close down.

What is the difference between a close checklist and a close calendar? The checklist says what to do and in what order. The calendar says on which day each step is due. You need both: a checklist without dates drifts, and dates without a checklist get missed steps.

Should the checklist be the same every month? The core should be. Quarter end and year end add steps, such as tax provisions or an audit pack. A separate rule that runs every three months, or once a year, is simpler than editing the monthly one each time.