Close calendar

Publish the calendar before the month starts. Changing it mid-close is how trust dies.

A close calendar is the operating system for month end. Without it, the work is whoever remembered. With it, every control has an owner, a due date, and a reviewer who is not the same person who prepared the work. This playbook is the Tarient standard for a five-business-day close. Adapt the hours to your systems, not the ownership model. If a task has no owner on the calendar, it does not exist.

• Each task: preparer, reviewer, due business day, system of record.
• Each anomaly: severity (block vs note), owner, evidence link, resolution date.
• Each judgment: policy reference, amount, who approved.

Pre-close days matter as much as BD1–BD5. By BD−2 the cutoff memo is out, AP is soft-closed, and payroll timing for month end is confirmed. Surprises that appear on BD1 that could have been known on BD−2 are process failures, not bad luck. The calendar makes that distinction visible to everyone who depends on the pack.

1. BD1 — Cash and feeds. Reconcile every material bank and processor account. Confirm the prior month’s ending cash ties to this month’s opening. Flag missing statements the same day, not on BD4. Day one belongs to cash; flux before cash invents a story you later walk back.

2. BD2 — Subledgers. Tie AR and AP aging to the general ledger. Post payroll and benefits. Draft revenue rollforward against the billing export. Queue anomalies with screenshots or system IDs attached so the reviewer is not hunting folklore.

3. BD3 — Accruals and judgments. Book known accruals with support. Park unknown items with a named decision owner. Draft flux for P&L and balance sheet lines above the materiality threshold. Debate revenue policy before month end, not inside the anomaly queue.

4. BD4 — Review. CFO reviews the pack and the anomaly queue. Founder briefing draft written. Certify-blockers either resolve or explicitly defer with impact noted. Silence is not approval.

5. BD5 — Certify and freeze. Pack certified. Access frozen for prior-period edits without a documented post-close adjustment. Forecast rebased to closed numbers so Tuesday’s cash view does not lean on last month’s guesses.

Ownership rules that keep the calendar honest

The preparer never reviews their own material reconciliations. The founder is not the backup accountant. If a system export is late, the owner of that system is on the critical path, not the analyst who is waiting. Escalations happen on the calendar’s clock, not when someone finally feels awkward. Companies that close by the fifth treat the calendar as product. Companies that close “when we can” treat it as optional paperwork.

Holiday weeks and short months need a published exception, not improvisation. If BD5 falls on a company shutdown, the calendar either pulls work forward or states the revised certify date before the month begins. Silent slips teach the organization that dates are optional. System outages happen too. The calendar should name the escalation path: who calls the payroll vendor, who owns the billing export, who can approve a soft-close label if a feed is dark. Escalation written down is faster than escalation invented under stress.

A late surprise that could have been a BD−2 note is a calendar failure, not a heroic save.

New entities, new payment processors, and new revenue products must be added to the calendar when they go live—not when someone notices a hole on BD2. A lightweight systems-change checklist sits beside the close calendar for that reason. Training a backup preparer is part of the calendar’s health. If only one analyst can reconcile a processor, vacation becomes a close risk. Cross-training is scheduled work, not a hope squeezed into leftover hours after certification.

• On-time task rate by business day
• Count of certify-blockers opened and cleared
• Hours from freeze to founder briefing
• Post-close adjustments that should have been known earlier

Those metrics belong in Oversight. Improving the close is impossible if the close is not measured. Tarient engagements use this calendar inside Oversight so status is visible without status meetings. The pair does not wait for a perfect month; they close the month that happened, document what is imperfect, and improve the next cycle. Ambiguity is what turns a five-day close into a fifteen-day ordeal. Lanes are assigned before the month starts and kept stable. When a lane is empty, the delay is visible the day it happens—not discovered in a board preview.

When a month contains a financing, a major outage, or a system migration, label the risk on BD−3. The fifth can still hold if the team pre-agrees which analyses move to a supplement. Surprise scope is what breaks the date. External bookkeepers and prior firms can be part of a transition. Tarient will take a handoff with a document trail. What we will not do is leave two conflicting closes in flight without naming which pack is authoritative. After the fifth becomes routine, protect it. The easiest way to lose a published calendar is to treat the first busy month as a free pass.

Related reading: close by the fifth and the monthly close service. To put the calendar on retainer with a stable pair, contact Tarient.