Month-end close

A close calendar should show when a task can start, who prepares it, and what must happen before it counts as finished.

Hear it in practice.

What’s holding up the close?

Listen to a browser-narrated example or read the transcript. The speakers are fictional.

Read transcript

Host We close at a different time every month. Where do we start?

Guest List the tasks that must happen before you can review the numbers. Identify the inputs each task depends on and give each one an owner.

Host What would that look like for cash?

Guest The preparer needs a complete bank statement and the ledger. The reviewer needs the reconciliation and an explanation of any outstanding items.

Host What if the bank statement is late?

Guest Flag the blocker early, tell the reviewer what it affects, and update the expected date. Keep the task open until the reconciliation is actually reviewed.

Practice what you heard ↘

Put dependencies on the calendar.

A close calendar should show when a task can start, who prepares it, and what must happen before it counts as finished.

Build a close calendar

Step 1 of 3

Put dependencies on the calendar

Sequence Put required inputs and dependencies next to each task.
Assign Name a preparer and a reviewer.
Escalate Flag late inputs with an owner and a revised date.

This demo records sample completion in this session. It carries no CPA continuing education credit.

Take it to the meeting.

Sequence recurring close tasks and track the preparer, reviewer, and inputs each one needs.

Month-end close calendar

Sequence recurring close tasks and track the preparer, reviewer, and inputs each one needs.

Download worksheet ↓

Browse the resource store ↗