Finance & Back Office

A month-end close that tracks itself

The close as real tasks with owners, rebuilt each month, showing who is behind.

Time
15 minutes
You work in
Tasks
Connect first
Works out of the box

Before you start

  • Your current close steps, however rough

Month-end close is a process that exists mostly in the head of whoever does it, reconstructed each month from memory and last month's mistakes. It works fine until that person is away, and then it works badly and visibly.

Write down what actually happens

Including the order and the dependencies. Which steps cannot start until something else finishes, which need someone outside finance, and which one always gets missed.

That last category is worth being honest about. Every close has a step that is forgotten most months and caught late, and naming it is half of fixing it.

Build it as real tasks, not a document

A checklist in a document is a thing you tick privately. Tasks have owners and dates and are visible, which is the entire difference when someone is behind.

Prompt
On the first working day of each month, create the month-end close
checklist as tasks in the Close project.

One task per step, in our documented order, with the owner and the working
day it is due.

Where a step depends on another, say so in the description rather than
assuming the order is obvious.

Do not create the tasks for a step whose owner has left or is unset. List
those for me instead.

Then have it chase, gently

Prompt
Every working day during close, tell me which tasks are past their due day
and who owns them.

Say how far behind, not how late it is in the process overall. One line
each.

If everything is on track, say so in one line.

"How far behind, not how late overall" is a deliberate framing choice. A report saying the close is three days behind schedule reads as a failure of the group, which nobody can act on. A report saying two specific tasks are a day past due reads as two things to go and unblock, which somebody can.

Revise it the week after, not during

Every close reveals a step that was wrong, missing, or in the wrong order. Note it during and fix the document afterwards, while it is fresh and while nobody is under time pressure.

Changing the checklist mid-close is how you lose the thread of what has actually been done.

What good looks like

The close runs the same way whether or not the person who invented it is there, and being behind is visible on the day rather than at the end.

The measure is the step that always got missed. If it stops getting missed, the checklist is real. If it still does, it is a step nobody actually owns.