Month-End Close Calendar Template: Day-by-Day Schedule

A month-end close calendar template is a day-by-day schedule that assigns every close task to a named owner, sets a due date, and defines the output required to call that task done. It runs from Day 0 (the last day of the period) through final sign-off — typically Day 8 to Day 10 of the following month. The calendar is distinct from a checklist: a checklist tells you what to do; a calendar tells you who does what, by when, and in what order.

Key Takeaways

• Most teams close in 5–10 business days; best-in-class targets 3–6 days with disciplined pre-close controls.
• A reliable close is less about speed and more about sequencing dependencies correctly: subledgers → reconciliations → review → reporting.
• Every day in the calendar needs a defined deliverable and a named owner — not just a task category.
• According to Ledge data cited by Vena, 94% of teams still use Excel to drive their close, and 50% cite it as a key reason their close is slow.
• According to Ventana Research cited by FloQast, 88% of companies that apply substantial automation to their close finish within six business days, vs. 40% that apply little or none.

What Is a Month-End Close Calendar (and How Is It Different From a Checklist)?

A month-end close calendar maps tasks to real calendar dates and named owners. A close checklist is a task inventory — it tells you what needs to happen. The calendar answers the harder question: who does it, by which day, and what does "done" look like?

In practice, teams that rely only on a checklist often finish late because nobody managed the sequencing. Reconciliations can't start until subledgers are closed. Review can't start until reconciliations are complete. If those handoffs aren't scheduled, they slip.

The calendar enforces the dependency chain. It also creates accountability: when Day 3 passes and bank reconciliations aren't complete, the calendar makes the delay visible immediately — not on Day 9 when the controller is waiting on financials.

The difference at a glance:

Use all three together. The calendar is the backbone.

How Long Should Month-End Close Take?

Most finance teams target a 5–10 business day close, but the timeline depends on transaction volume, team size, and how much work is still manual. A PwC Finance Benchmarking Report notes a median of 6.4 days. Research from Ledge shows only 18% of teams finish in 3 days or less, and half take longer than 5 business days.

According to Xenett, the benchmarks break down like this:

• 3-day close: highly standardized, often enabled by automation, clean subledger feeds, and few late adjustments.
• 5-day close: the common optimized target for scaling teams. Requires pre-close work, clear cutoffs, and consistent review standards.
• 7–10 day close: common when reconciliations and review happen late, or when dependencies stay open too long.

For most service businesses — agencies, consultancies, software studios — a 10-business-day target is realistic and defensible. Getting to 5–7 days requires pre-close controls that happen during the month, not after it ends.

Day-by-Day Month-End Close Calendar

This calendar runs Day 0 through Day 10. Day 0 is the last day of the accounting period. Days 1–10 are business days in the following month.

As Xenett notes, a 5-day close works when you pre-close during the month and account-level review happens early — not at the end. The calendar below reflects that logic: the heaviest data work lands in Days 1–3, review in Days 4–6, and reporting in Days 7–10.

Day 0 — Period End (Last Day of the Month)

Owner: Bookkeeper / Controller
Deliverable: All transactions through period end are entered or queued; cutoff memo sent to department heads.

• Confirm all invoices issued through month-end are recorded
• Send cutoff reminder to department heads: no backdated entries after this point without approval
• Confirm payroll for the period is posted or accrued
• Flag any known late items (vendor invoices, expense reports) for Day 1 follow-up
• Lock the prior period in your accounting system if your workflow supports it

Dependency: Nothing starts cleanly on Day 1 if cutoff isn't enforced on Day 0.

Day 1 — Subledger Close and Data Pull

Owner: Bookkeeper
Deliverable: All subledgers closed; bank and credit card feeds confirmed current.

• Close accounts payable subledger — no new entries for the prior period
• Close accounts receivable subledger — confirm all invoices are posted
• Pull bank and credit card feeds; confirm data is current through Day 0
• Collect outstanding expense reports from team members
• Confirm payroll data is fully posted in the general ledger
• Flag any missing or uncleared transactions for same-day resolution

Dependency: Reconciliations on Day 2 cannot start until subledgers are closed and feeds are current.

Day 2 — Bank and Credit Card Reconciliation

Owner: Bookkeeper
Deliverable: All bank and credit card accounts reconciled; unreconciled items documented with explanations.

• Reconcile all bank accounts to statement balances
• Reconcile all credit card accounts
• Investigate and document any unreconciled items — do not leave unexplained variances
• Confirm clearing accounts are reviewed (not used as a catch-all)
• Post any missing transactions identified during reconciliation

Dependency: Balance sheet reconciliations on Day 3 depend on clean bank recs.

In practice, clearing accounts are a common failure point. If nobody reviews them until Day 5, they become a junk drawer — as Xenett notes — and reconciliation takes twice as long.

Day 3 — Accounts Receivable, Accounts Payable, and Accruals

Owner: Bookkeeper / Controller
Deliverable: AR and AP reconciled; accruals posted; deferred revenue updated.

• Reconcile accounts receivable — flag invoices overdue by 30+ days
• Reconcile accounts payable — confirm all vendor bills are entered
• Post accruals for expenses incurred but not yet invoiced (e.g., contractor work, subscriptions)
• Update deferred revenue schedule if applicable (common for retainer-based businesses)
• Record prepaid expense amortization
• Confirm intercompany transactions are eliminated if applicable

Dependency: The trial balance review on Day 4 requires all accruals and subledger reconciliations to be complete.

Day 4 — Trial Balance Review and Adjusting Entries

Owner: Controller / Senior Accountant
Deliverable: Trial balance reviewed; all adjusting journal entries posted; no unexplained variances.

• Run trial balance and review for anomalies — look for accounts with unexpected balances or large swings
• Post all adjusting journal entries
• Confirm depreciation and amortization are recorded
• Review fixed asset additions or disposals for the period
• Confirm loan balances and interest accruals match amortization schedules
• Document the rationale for any material adjusting entries

Dependency: Financial statements on Day 5 cannot be finalized until the trial balance is clean.

Day 5 — Financial Statement Preparation

Owner: Controller
Deliverable: Draft P&L, balance sheet, and cash flow statement prepared and internally consistent.

• Generate draft profit and loss statement
• Generate draft balance sheet — confirm it balances
• Generate draft cash flow statement (or confirm cash movement ties to bank recs)
• Confirm revenue recognition is correct for the period — no premature or deferred revenue errors
• Run a flux analysis: compare current month to prior month and prior year; flag variances above a defined threshold (e.g., hypothetically, any line item moving more than 10% month-over-month)
• Prepare a summary of key movements for the review memo

Day 6 — First Review Pass

Owner: Controller / Engagement Lead
Deliverable: Review notes documented; open items list created with owners and due dates.

• Review draft financials against flux analysis — challenge any unexplained variances
• Confirm all balance sheet accounts are supported by a reconciliation
• Review AR aging — confirm bad debt reserve is appropriate
• Confirm payroll expense ties to payroll reports
• Document all open items with a named owner and a same-day or next-day deadline
• Send open items list to relevant team members

Dependency: Day 7 resolution depends on open items being clearly assigned on Day 6.

Day 7 — Open Item Resolution

Owner: Bookkeeper / Controller (shared)
Deliverable: All Day 6 open items resolved or escalated; financials updated.

• Resolve all open items from Day 6 review
• Post any final adjusting entries
• Re-run trial balance to confirm clean
• Escalate any unresolvable items to the engagement lead or client — do not let them sit
• Update financial statements to reflect all final entries

Day 8 — Final Review and Sign-Off Preparation

Owner: Controller / Partner
Deliverable: Final financials reviewed and approved; commentary drafted.

• Conduct final review of P&L, balance sheet, and cash flow
• Confirm all reconciliations are complete and filed
• Draft monthly financial commentary: what changed, why it changed, and what it means
• Confirm tax accruals are appropriate (estimated quarterly payments, sales tax if applicable)
• Prepare the reporting package for delivery

Day 9–10 — Reporting Delivery and Close Sign-Off

Owner: Controller / Engagement Lead
Deliverable: Reporting package delivered; close formally signed off; post-close notes filed.

• Deliver financial reporting package to stakeholders (founder, board, investors)
• Obtain formal close sign-off from the responsible party
• File all reconciliations and supporting workpapers
• Document any recurring issues for process improvement
• Set up the pre-close checklist for next month — confirm cutoff dates, payroll schedule, and any known timing items

Owner and Dependency Map

A calendar without clear ownership is just a wish list. Every task needs one named owner — not a team, not a role category, but a specific person. Dependencies need to be explicit so that when one task slips, the downstream impact is immediately visible.

Why the dependency map matters more than the calendar

The calendar gives you dates. The dependency map tells you which tasks are on the critical path. If bank reconciliations slip from Day 2 to Day 4, everything downstream — trial balance, financial statements, review — compresses into Days 4–8. That's where late closes come from: not from any single task being slow, but from a dependency chain that nobody managed.

As Xenett notes, a reliable close timeline is less about speed and more about sequencing dependencies correctly.

How Do You Compress the Close to Under Ten Days?

The fastest safe path to a shorter close is pre-close work — tasks you complete during the month rather than after it ends. According to Xenett, a 5-day close works when you pre-close during the month and account-level review happens early, not at the end.

Pre-close tasks to run during the month:

• Reconcile bank accounts weekly, not monthly — so Day 2 is a confirmation, not a discovery
• Review and code transactions on a rolling basis (weekly or bi-weekly)
• Collect and approve expense reports before month-end, not after
• Confirm payroll is correctly coded each pay period
• Flag any unusual transactions as they occur — don't save investigation for the close

Structural changes that compress the close:

• Define output standards for every task. As Xenett notes, evidence standards prevent 80% of rework — people stop arguing about "complete" when you define what the output looks like.
• Assign one owner per task. Shared ownership means no ownership.
• Set hard cutoffs. Late entries after Day 0 require explicit approval — no exceptions.
• According to Ventana Research cited by FloQast, 88% of companies that apply substantial automation to their close finish within six business days, compared to 40% that apply little or none.

For a deeper look at the reconciliation work that underpins a fast close, see the balance sheet reconciliation checklist and account reconciliation best practices for service businesses.

What's the Difference Between a Close Calendar and a Close Checklist?

A close checklist is a task inventory — it ensures completeness. A close calendar is a scheduling and accountability tool — it ensures tasks happen in the right order, by the right person, by the right date.

As Jetpack Workflow describes, the five steps of using a checklist template are: assign each task to a team member, set deadlines for every stage, track progress using status updates, review all completed tasks, and finalize and close the accounting period. The calendar is what makes steps one and two real — it translates "assign" and "set deadlines" into specific dates and names.

Use both. The checklist ensures nothing is missed. The calendar ensures nothing is late.

How to Adapt This Template to Your Business

The calendar above is a starting point. Adapt it based on:

Transaction volume. Higher volume businesses may need to split Day 1 into two days — one for AP subledger close, one for AR and payroll. Lower volume businesses may be able to combine Days 2 and 3.

Revenue model. Retainer-based businesses (agencies, MSPs, consultancies) need to update deferred revenue schedules on Day 3. Project-based businesses need to confirm milestone billing and WIP on the same day. For more on how this applies to software and web studios, see outsourced accounting for software and web studios.

Team size. Solo bookkeepers own every task. Larger teams split ownership across bookkeeper, controller, and engagement lead — which makes the dependency map more important, not less.

Reporting requirements. If you report to a board or investors, the Day 9–10 package needs to be more formal. See startup board reporting metrics for what investors typically expect.

Name your close tracker clearly — something like "[Company] Close Tracker – [Month] 2026" — and attach a short one-pager outlining escalation paths, backup approvers, and final sign-off roles. As Vena recommends, it's a small step that saves time and reduces confusion under pressure.

Frequently Asked Questions

What should be done on Day 0 of month-end close?

Day 0 is the last day of the accounting period. The primary tasks are enforcing the transaction cutoff, sending reminders to department heads about pending expenses, confirming payroll is posted or accrued, and flagging any known late items. Nothing on Day 1 starts cleanly without a firm Day 0 cutoff.

What's the fastest safe way to shorten the close?

The fastest safe path is pre-close work done during the month — weekly bank reconciliations, rolling transaction coding, and expense report collection before month-end. Xenett notes that a 5-day close works when pre-close happens consistently and account-level review starts early rather than at the end.

How is a close calendar different from a close timeline?

A close timeline defines the total duration and sequence of close phases. A close calendar maps those phases to real dates with named owners and defined outputs. The timeline tells you the shape of the close; the calendar makes it operational and accountable.

This content is provided for informational purposes only and does not constitute accounting, tax, or legal advice. Please consult your own advisors before making changes to your financial processes.

To see what a completed, reviewed close package looks like in practice, view a sample close — or book an intro to talk through how Laya runs the close for service businesses.