How to run month-end close as a checklist in monday.com

Month-end close has an unusual combination of properties. It is almost identical every month. It runs against a hard deadline. It involves several people whose steps depend on each other in a strict order. And months or years later, somebody may need to establish that it was done properly, by the right people, in the right sequence.

Most finance teams run it from a spreadsheet — a tab per month, columns for owner and status, copied forward and edited. That works until it does not. This guide covers modelling the close as a recurring checklist in monday.com: the phases, the dependencies that stop reconciliation starting before cut-off, how to get a preparer/reviewer split that actually holds, and what evidence you are left with when the auditor asks.

Why the close spreadsheet stops working

The close spreadsheet fails in slow, quiet ways rather than dramatic ones.

It drifts. Each month is a copy of the last, so a step someone quietly deleted in March is missing in April, May and every month after. Nobody notices, because the reference version is whichever tab was copied.

It has no order. Columns cannot express that revenue recognition cannot start until the sub-ledger is closed. The ordering lives in the head of whoever has run the close longest — a real problem the month that person is on leave.

It has no identity. A cell reading "done" was typed by someone; the spreadsheet does not know who or when, and it certainly does not distinguish the preparer from the reviewer.

And it is somewhere else, away from wherever the rest of the finance team's work is tracked, so status questions get answered in messages rather than by looking.

SOP & Compliance Checklists keeps the close on a monday.com item, with the sequence, the ownership and the history built into it rather than typed into it.

Model the close, phase by phase

Create an item for the period — "Close — August 2026" — and build the checklist as sections that follow the close itself:

1. Cut-off — stop the sub-ledgers, confirm the last transactions, freeze what needs freezing.
2. Reconciliations — bank, AR, AP, intercompany, payroll, fixed assets. One task per reconciliation, each with the person who prepares it as owner.
3. Accruals and adjustments — accruals, prepayments, depreciation, provisions, FX revaluation.
4. Review — variance analysis against budget and prior period, review of every reconciliation, resolution of open items.
5. Report and close — draft the pack, management review, post the final journals, lock the period, file the evidence.

Put a due date on the steps that carry the deadline — most closes are "day 3" or "day 5" processes, and those dates are what make it visible when a step is late rather than merely open. The earliest unfinished due date can mirror into a board Date column, which lets monday.com's own date automations send the reminders you would otherwise send by hand.

Use dependencies for the ordering the close genuinely requires: reconciliations depend on cut-off; the reporting pack depends on review; period lock depends on the final journals. The gating means a new team member cannot start something that is not yet startable, which is exactly the knowledge that otherwise lives with the longest-serving person on the team.

Make it recur instead of cloning it

The close is monthly, so do not clone it monthly. Set the checklist to recur: it resets its steps at the start of each cycle, keeping the structure and clearing the completions, and tracks a completion streak across cycles.

That single change removes the drift problem entirely. There is no "last month's tab" to copy, so there is no path by which a step disappears silently. The procedure is one object that resets, not a chain of copies each one edit away from the original.

If your close varies by entity or region, keep it as a template and apply it per entity item instead, or set it as the board default so every new close item starts complete. The recurring checklists guide covers cadence and streaks, and the templates guide covers defaults and bulk-apply.

Preparer, reviewer, sign-off

Segregation between whoever prepares a reconciliation and whoever reviews it is a basic control, and it is the one a spreadsheet cannot enforce at all.

Assign each reconciliation to its preparer and turn on Restrict completion, so only that person or an admin can mark it done. The tick becomes an assertion by a named person rather than an anonymous character in a cell.

For review, use approvals on the tasks that need a second pair of eyes, and Compliance sign-off for the close as a whole. A sign-off certifies the entire checklist and records the signer's role — Preparer, Reviewer, Approver — who they are, when they signed, and the completion at that moment. Sign-offs stack, so the controller can sign after the reviewer, and either they or an admin can revoke.

The header shows the state plainly: Sign off while pending, green Signed off once certified, and amber Modified after sign-off the moment anything changes afterwards. That amber state is the control that matters — it triggers on any change to the content, not merely on a different completion count, so a journal quietly amended after the controller signed does not pass unnoticed.

A cell that says "done" is a claim. A sign-off that records who, in what role, at what completion, and flags any later change is a control.

Evidence your auditor can use

Everything above produces an audit trail without anybody maintaining one: every status change, assignment, due date, approval and sign-off, with who and when, per task and across the board.

When the auditor asks, export the audit report (PDF) for the period's item. It contains a completion summary and sign-off status, the sign-off record with roles and timestamps, the full task table and the complete activity trail — plus a SHA-256 document fingerprint. The fingerprint is deterministic: the same data always produces the same hash, and any later change produces a different one, which is what makes the export tamper-evident rather than merely printed.

There is a practical benefit before any auditor is involved. Because completion mirrors into a board column and the board view aggregates every item, the controller can see on day 3 which entities are behind and which reconciliation is holding up review — without a status call. The analytics guide covers the trend and workload views that come from the same data.