.avif)
Blog Summary / Key Takeaways
- A single universal checklist either misses risk on complex clients or wastes review time on simple ones.
- The four-stage close model (pre-close, production, review, reporting and lock) stays constant; what should change by client tier is how deep each stage goes.
- Tier 1, Tier 2, and Tier 3 clients need meaningfully different reconciliation depth, documentation, and review standards.
- Tag every checklist line by the tier it applies to, and re-tier clients whenever their structure changes.
Introduction
Most month-end close checklists assume every client looks the same. They don't. A checklist built for a single-entity, cash-basis client run against a multi-entity client with inventory and revenue recognition either misses critical steps or wastes review time double-checking things that don't need it.
Instead of giving you one more universal checklist (we cover the full task-level checklist and the four-stage close structure in our month-end close process guide), this guide is about customizing your checklist to the client sitting in front of you: what changes at each complexity tier, why, and how to build your own tier-based version.
Why One Checklist Doesn't Fit Every Client
A checklist is only as useful as its fit to the work. Run a Tier 3 client's checklist depth against a Tier 1 client and you'll burn review hours on reconciliations that don't carry real risk. Run a Tier 1 checklist against a Tier 3 client and you'll miss the intercompany eliminations, revenue recognition judgment calls, and rollforward schedules that actually matter.
The fix isn't a better universal checklist. It's recognizing that "month-end close checklist" should mean something different depending on which client you're closing.
The Four-Stage Close Model (Your Foundation)
Before tiering anything, every checklist, regardless of client complexity, should be organized around the same four stages. The tiers change what happens inside each stage, not the stages themselves.
| Stage | Goal | What changes by tier |
|---|---|---|
| 1. Pre-close | Confirm cutoffs and inputs before reconciling anything | Number of source systems and approval layers to confirm |
| 2. Production | Reconcile accounts and post adjusting entries | Which accounts are in scope and how much rollforward documentation is required |
| 3. Review | Verify the work against a defined standard | Variance threshold tightness and whether judgment memos are required |
| 4. Reporting and lock | Publish, lock, and log open items | Consolidation and elimination steps, if applicable |
Stage 1 is done when no source system has a pending batch and every prior open item has a written answer, at every tier. What differs is how many source systems and how many open items there typically are.
Close Complexity by Client Tier
Assign every client a tier once, in writing, and build the checklist depth around that tier rather than negotiating it fresh each month.
| Client tier | Typical profile | Realistic close target | Review depth |
|---|---|---|---|
| Tier 1 | Cash basis, low transaction volume, simple structure | 5 business days | Light flux review, key reconciliations only |
| Tier 2 | Accrual basis, moderate volume, standard payroll and AP/AR | 7 business days | Full balance sheet reconciliation set |
| Tier 3 | Multi-entity, inventory, deferred revenue, or revenue recognition complexity | 10 business days | Deeper flux analysis, rollforward schedules, written memos on judgment calls |
What Actually Changes at Each Tier
Tier 1: Simple Single-Entity Client
The checklist stays short on purpose. Bank and credit card reconciliations, a basic AR/AP tie-out, and a light P&L reasonableness check cover most of the risk. Adding rollforward schedules or judgment memos here is wasted review time; there's rarely enough complexity to justify it.
What to keep: cash and card reconciliations, AR/AP tie-out, basic flux check against a loose threshold.
What to skip: rollforward workpapers for accounts that never carry a material balance, multi-step judgment documentation, consolidation steps.
Tier 2: Standard Multi-Function Client
This is where most firms' "default" checklist actually belongs. Payroll liabilities, prepaid amortization, and fixed asset depreciation all enter the picture, and each needs its own reconciliation line rather than being folded into a general review.
What to add versus Tier 1: full balance sheet reconciliation (not just cash and AR/AP), payroll liability tie-out, fixed asset rollforward, a moderate flux threshold with written explanations required.
What to still skip: intercompany eliminations, revenue recognition memos, unless a specific transaction requires it that month.
Tier 3: Multi-Entity, Inventory, or Audit-Facing Client
Here the checklist needs to do more than confirm balances. It needs to document judgment. Every material accrual, every revenue recognition call, and every intercompany elimination needs a written explanation that would hold up under audit or lender scrutiny, not just a reconciling number that ties out.
What to add versus Tier 2: rollforward schedules for deferred revenue, inventory, and intercompany accounts; a documented policy for revenue recognition judgment calls, applied consistently rather than decided fresh each month; a tighter flux threshold with mandatory written memos on anything that trips it; an audit-readiness pass confirming supporting documentation is complete and traceable, not just that the number is correct.
An audit-facing client adds one more layer regardless of size: every adjusting entry needs support that a third-party auditor, not just your internal reviewer, could follow without asking a question.
Build Your Own Tier-Based Checklist: A Short Worksheet
Use this to translate the framework above into a checklist for your specific book of clients.
Step 1: Tier every client once
For each client, answer three questions: single entity or multiple, cash or accrual basis, and does revenue recognition or inventory require judgment calls. That's usually enough to place a client into Tier 1, 2, or 3 without debate.
Step 2: Set the review depth per tier, in writing
Decide, once, what "full reconciliation set" means for your Tier 2 clients and what "rollforward and memo" means for your Tier 3 clients. Write it down so it doesn't get renegotiated mid-close by whoever is reviewing that month.
Step 3: Mark which checklist lines apply at which tier
Take your existing task-level checklist and tag each line with the lowest tier it applies to. A line tagged "Tier 3 only" should not appear on a Tier 1 client's close, and a reviewer should be able to tell at a glance why it's missing.
Step 4: Re-tier clients when their profile changes
A client that adds a second entity, starts recognizing revenue over time, or brings on inventory has moved tiers, even if nothing else about the engagement changed. Revisit tiers at least annually, and immediately after any structural change to the client's business.
A Practical Example
A firm managing close across three tiers found that its Tier 1 clients were being reviewed with the same rollforward and memo requirements built for Tier 3 engagements, simply because the checklist had never been split apart. Review notes on simple clients were frequently about formatting, not substance, while a genuinely complex Tier 3 client's intercompany eliminations occasionally slipped through without a written explanation.
After tagging every checklist line by tier and rebuilding the Tier 1 version down to its essential reconciliations, review time on simple clients dropped noticeably, and the freed-up time went toward the judgment-heavy items on Tier 3 clients that actually needed it.
Frequently Asked Questions
Does a month-end close checklist need to be different for every client?
Not for every client individually, but it should differ by complexity tier. A single-entity cash-basis client and a multi-entity client with inventory should not run the same checklist depth, even if both use the same four-stage structure underneath.
What should a month-end close checklist include for a simple client?
For a Tier 1, single-entity client, the checklist should cover cash and card reconciliations, an AR/AP tie-out, and a light flux review. Rollforward schedules and judgment memos generally aren't warranted at this level of complexity.
What should a month-end close checklist include for an audit-facing client?
An audit-facing checklist needs rollforward schedules for material accounts, a documented and consistently applied revenue recognition policy, mandatory written memos on flagged variances, and support for every adjusting entry that a third-party auditor could follow independently.
How do I know which tier a client belongs on for my month-end close checklist?
Ask three questions: single entity or multiple, cash or accrual basis, and whether revenue recognition or inventory involves judgment calls. Most clients sort cleanly into Tier 1, 2, or 3 from those answers alone.
How often should I revisit a client's checklist tier?
At least annually, and immediately whenever a client's structure changes, such as adding a second entity, shifting to accrual accounting, or introducing inventory or deferred revenue.
Key Takeaways
Conclusion
A single month-end close checklist, applied the same way to every client, either misses risk on your complex clients or wastes review time on your simple ones. Tier your clients once, decide in writing what changes at each tier, and tag your checklist accordingly. The structure underneath, the four-stage model, stays the same. What should change is how deep each stage goes for the client in front of you.
For the full task-level checklist and documentation standards this tiering approach builds on, see our month-end close process guide. For the phase framework and close calendar that pairs with this structure, see our month-end close best practices guide. If you're evaluating how tiered checklists could fit an outsourced close model, talk to Etisson's team.
