Any chatClose

Build a month-end close checklist for your business

Get a close checklist written for one business: steps in dependency order, each with a day, an owner slot and a definition of done.

For Controller · Fractional CFO · Updated

What this skill does

When there's no checklist, or the one you have is a template from somewhere else. A generic template lists every step any company might need. A useful checklist lists the steps this business needs, in the order its data arrives, with a name against each.

The assistant drafts from what you tell it about the business. It doesn't know your systems' quirks or who is good at what, so it leaves owners blank and asks about anything it would otherwise have to guess. If you already have a checklist and want it reviewed, use Find the gaps in a month-end close checklist instead.

What it needs

Works in Claude, ChatGPT, Copilot or any AI assistant. No setup.

Use it

01Point your assistant at it

Paste this line into a chat with any assistant that can read a web page. It reads the skill and follows it.

Read https://harbinger.finance/skills/month-end-close-checklist/SKILL.md and follow it.

02Download the skill file

Add it to your assistant as a skill, or attach it to a chat. It is plain markdown, so you can read every word first.

Download SKILL.md

03Or fill it in and paste the prompt

Fill in what you know and the prompt below updates. Anything you leave blank stays in [brackets] for you to replace in the chat. What you type stays in your browser.

5 blanks left in [brackets]
Write a month-end close checklist for this business.

The business: [industry, cash or accrual basis, rough annual revenue].
Systems: [accounting, payroll, billing and bank systems].
Who works on the close: [roles on the close].
Target: closed by business day [number].
What makes it different: [inventory, deferred revenue, loans, multiple entities, or none]

1. List the steps this business needs, in the order they can actually be done. A step that depends on another comes after it. Say what each step depends on.
2. For each step give: the business day, the role that would normally own it, and what "done" means in one line that a reviewer could check.
3. Mark each step as "always" or "because of" something I told you, so I can see why it's there.
4. Leave out steps that don't apply to a business like this. Don't pad the list.
5. Put review and sign-off steps in as their own lines, with a different role from the one that did the work.
6. End with the questions you'd need answered to finish it, instead of guessing.

Use the roles I gave you. Don't invent names, account numbers or policies.

What you provide

  • -The business: industry, cash or accrual basis, rough size.
  • -The systems: accounting, payroll, billing, banking, anything that feeds the books.
  • -Who works on the close, by role.
  • -The day you want to be closed by.
  • -Anything that makes this business different: inventory, deferred revenue, loans, more than one entity.

What a good answer looks like

Day 1

  1. Bank and card feeds caught up through month-end. Staff accountant. Always. Done: no uncategorized lines dated in the month.
  2. Stripe payouts matched to deposits. Staff accountant. Because of Stripe. Depends on 1. Done: clearing account is zero or every item is listed.

Day 2 3. Bank reconciliations, all accounts. Staff accountant. Always. Depends on 1. Done: reconciled balance ties to the statement, unreconciled items listed. 4. Payroll journal tied to the Gusto register. Staff accountant. Because of Gusto. Done: wages and liabilities agree to the register.

Day 3 5. Deferred revenue roll-forward. Controller. Because of annual contracts. Depends on 2. Done: ending balance ties to the contract list. 6. Loan interest and principal split. Controller. Because of the loan. Depends on 3. Done: balance ties to the lender statement.

Day 4 7. Flux review of the income statement and balance sheet. Controller. Always. Done: every line over the threshold has an explanation.

Day 5 8. Owner review and sign-off. Owner. Always. Depends on 7.

Questions

  • Is revenue recognized monthly from the contract dates, or from the invoice dates?
  • Who approves journal entries the controller prepares?

Check before you use it

  1. 01Walk the order against how your data actually arrives. The assistant is reasoning from typical dependencies.
  2. 02Put a named person on every step. A role is not an owner.
  3. 03Answer the questions at the end before you adopt it. They mark where it guessed least.
  4. 04Run it for one close and cut any step nobody needed.

The assistant drafts. The person whose name is on the work approves it.

The skill file

Read the SKILL.md your assistant gets
---
name: month-end-close-checklist
description: "Use when the user needs a month-end close checklist written from scratch for a specific business, with steps in dependency order and a day, an owner and evidence of completion for each. Triggers: month end close checklist, close calendar, build a close process, first close for a new client, close template."
metadata:
  lane: use
  requires: "none"
  source: https://harbinger.finance/skills/month-end-close-checklist
  updated: "2026-11-18"
---

# Build a month-end close checklist for your business

Get a close checklist written for one business: steps in dependency order, each with a day, an owner slot and a definition of done.

## When to use it

When there's no checklist, or the one you have is a template from somewhere else. A generic template lists every step any company might need. A useful checklist lists the steps this business needs, in the order its data arrives, with a name against each.

The assistant drafts from what you tell it about the business. It doesn't know your systems' quirks or who is good at what, so it leaves owners blank and asks about anything it would otherwise have to guess. If you already have a checklist and want it reviewed, use [Find the gaps in a month-end close checklist](https://harbinger.finance/skills/close-checklist-gaps) instead.

**Where it works.** Any AI assistant. No setup.

## Ask the user for

- The business: industry, cash or accrual basis, rough size.
- The systems: accounting, payroll, billing, banking, anything that feeds the books.
- Who works on the close, by role.
- The day you want to be closed by.
- Anything that makes this business different: inventory, deferred revenue, loans, more than one entity.

Ask for anything missing before you start. Never invent a figure to fill a gap.

## Do this

Carry out the request below. Fill each [bracketed] item from what the user gave you.

Write a month-end close checklist for this business.

The business: [industry, cash or accrual basis, rough annual revenue].
Systems: [accounting, payroll, billing and bank systems].
Who works on the close: [roles on the close].
Target: closed by business day [number].
What makes it different: [inventory, deferred revenue, loans, multiple entities, or none]

1. List the steps this business needs, in the order they can actually be done. A step that depends on another comes after it. Say what each step depends on.
2. For each step give: the business day, the role that would normally own it, and what "done" means in one line that a reviewer could check.
3. Mark each step as "always" or "because of" something I told you, so I can see why it's there.
4. Leave out steps that don't apply to a business like this. Don't pad the list.
5. Put review and sign-off steps in as their own lines, with a different role from the one that did the work.
6. End with the questions you'd need answered to finish it, instead of guessing.

Use the roles I gave you. Don't invent names, account numbers or policies.

## Before you hand it over

Tell the user which of these checks they still need to make:

- Walk the order against how your data actually arrives. The assistant is reasoning from typical dependencies.
- Put a named person on every step. A role is not an owner.
- Answer the questions at the end before you adopt it. They mark where it guessed least.
- Run it for one close and cut any step nobody needed.

The assistant drafts. The person whose name is on the work approves it.

## What a good answer looks like

**Day 1**
1. *Bank and card feeds caught up through month-end.* Staff accountant. Always. Done: no uncategorized lines dated in the month.
2. *Stripe payouts matched to deposits.* Staff accountant. Because of Stripe. Depends on 1. Done: clearing account is zero or every item is listed.

**Day 2**
3. *Bank reconciliations, all accounts.* Staff accountant. Always. Depends on 1. Done: reconciled balance ties to the statement, unreconciled items listed.
4. *Payroll journal tied to the Gusto register.* Staff accountant. Because of Gusto. Done: wages and liabilities agree to the register.

**Day 3**
5. *Deferred revenue roll-forward.* Controller. Because of annual contracts. Depends on 2. Done: ending balance ties to the contract list.
6. *Loan interest and principal split.* Controller. Because of the loan. Depends on 3. Done: balance ties to the lender statement.

**Day 4**
7. *Flux review of the income statement and balance sheet.* Controller. Always. Done: every line over the threshold has an explanation.

**Day 5**
8. *Owner review and sign-off.* Owner. Always. Depends on 7.

**Questions**
- Is revenue recognized monthly from the contract dates, or from the invoice dates?
- Who approves journal entries the controller prepares?

---

From the Harbinger FinLab skill library: https://harbinger.finance/skills/month-end-close-checklist

Go deeper