← All templates

Accounting

Month-End Close Checklist

A bookkeeper with a dozen clients runs the same twelve steps twelve times and remembers eleven of them for at least one client. This workflow issues the close checklist per client on the same working day each month, chases the missing paperwork with a named list rather than a general plea, and gives the client a short summary that makes the fee visible.

7 stepsRequires Zapier Starter or higher25 minMedium
Google SheetsTrelloGmailSlackSchedule by ZapierDelay by Zapier

What you get

Every client gets the same close sequence on the same day each month.
Missing receipts are chased as a named list, which is what actually gets them sent.
The client sees what was done, so the monthly fee stops feeling invisible.

Workflow blueprint

SC
When this happens
Schedule by ZapierEvery Month
1GS
Google SheetsLookup Spreadsheet Row
2TR
TrelloCreate Card
3GM
GmailSend Email
4DE
Delay by ZapierDelay For
5GM
GmailSend Email
6SL
SlackSend Direct Message

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 7 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Run on the first working day

Configure this step using the field mapping in the blueprint.

2
Read the client list

Configure this step using the field mapping in the blueprint.

3
Create the close checklist card

Configure this step using the field mapping in the blueprint.

4
Send the document request

Configure this step using the field mapping in the blueprint.

5
Wait five days

Configure this step using the field mapping in the blueprint.

6
Chase what is still missing

Configure this step using the field mapping in the blueprint.

Implementation notes

  • Stagger close days across the month. Twelve clients all closing on the first is a week you will dread every month for as long as you have those clients.
  • Chase a named list, never a general reminder. "Seven receipts outstanding" gets ignored; "Bauhaus 14/03 €412, Circle K 19/03 €88" gets photographed that evening.
  • Suspense to nil is the hard gate. Everything else can slip a day; a carried-forward suspense balance compounds into a reconciliation you will spend a weekend on.
  • Send the management pack even to clients who never open it. It is the visible artefact of the fee, and it is what you point to when the fee is questioned.