Skills / Foundational — run before the rest, Reconciliation and close

Month-end close checklist

What it does

Builds a close checklist from the trial balance rather than from a template. Every account with movement generates a task, with an owner, a status, and the procedure assigned from what the account actually is — a cash account gets a bank reconciliation, a fixed asset account gets a rollforward — and the task names the skill in this repository that performs it.

Every generic close checklist has the same problem: it is a list of tasks somebody else's business needed. It tells you to reconcile the bank and review accruals, which you knew, and says nothing about the seven accounts on your trial balance that had activity this month and nobody has looked at.

Accounts you deliberately do not reconcile get waived with a reason, on the record. The close is not complete until every account is in one of those states — which is a completeness test, not a to-do list.

What it proves

The usual close failure is not a forgotten task. It is an account nobody ever considered, because it was not on the template. So an account absent from the checklist entirely is reported as not considered rather than silently defaulted to open. Five conditions before the close is reportable as complete:

  • Every account with activity is accounted for — reconciled + waived + open must equal the population of accounts with movement, in count and in dollars.
  • Nothing above materiality is waived without a reason. A waiver is a professional judgement and is recorded as one. A blank reason is not a waiver, it is an omission.
  • Every open item has an owner and a due date. An open item with no owner does not close.
  • Every reconciled account names its support — which workpaper, statement, or schedule. "Reconciled" with no reference is an assertion, not a reconciliation.
  • The trial balance balances. If debits do not equal credits, the close has not started — run trial-balance-integrity first.

What you get

Seven tabs:

  1. Close Status — the gate, counts and dollars by status, days against target, the accounts driving lateness, and the escalations. The page a controller reads each morning.
  2. Checklist — every account with movement: balance, movement, status, procedure required, skill to run, support reference, owner, due date, notes. The working document.
  3. Open Items — sorted by materiality then age, with owners.
  4. Waivers — every waived account with its reason and how many consecutive periods it has been waived.
  5. Coverage Proof — reconciled + waived + open + blocked equals the population of accounts with movement, in count and in dollars.
  6. Recurring Issues — items open or waived across consecutive periods.
  7. Next Period Carry-Forward — a pre-populated checklist for the following period with owners retained, so the next close starts from evidence rather than a blank template.

Where it stops

It does not perform the procedures. It identifies which one each account needs and names the skill that does it.

An account with movement and no owner, a suspense or clearing account with a balance at close, the same account open at three consecutive closes, an account waived above materiality or waived repeatedly, a reconciliation marked complete with no support reference, journal entries posted after the close was declared complete: each is escalated.

A close completed while items remain open means the financial statements were issued on an incomplete basis. Whether that is acceptable is a judgement for the controller — the point is that it should be a decision rather than an accident.