8 Month End Close Checklist Tasks for 2026

A reliable month-end close checklist sequences eight tasks by dependency: readiness, reconciliation, revenue and AP cutoffs, journal entry approval, intercompany consolidation, fixed assets, and tax provision. Each task needs an owner, an approval gate, and retained evidence.

The best finance teams treat close as a controlled operating workflow, not a list of reminders. Yet 50% of finance teams take six or more business days to complete month-end close, and most automate less than 40% of the process, according to 2025 month-end close benchmarks from Ledge. A six-day close is therefore a practical baseline, not an exception.

A strong operating calendar starts five business days before close, reaches a defined period-end cutoff, executes core postings during close days one through three, and ends with final sign-off. Controllers coordinate the process. Accounting owners perform reconciliations and postings. AP, revenue, tax, payroll, FP&A, and entity controllers supply inputs and approvals.

Loopfour, the deterministic finance workflow automation platform, connects existing systems while preserving execution evidence. Deterministic workflows execute predefined rules. AI Copilot can interpret documents or unusual descriptions, but it should use confidence thresholds and human fallback. That boundary matters when approval actions carry financial risk.

This article was prepared by Jordan Ellis, a finance systems writer focused on controllership, audit controls, and workflow engineering.

Table of Contents

• 1. Account Reconciliation and Balance Verification
• 2. Revenue Recognition and Contract-to-Cash Synchronization
• 3. Accounts Payable and Expense Accrual
• 4. Journal Entry Review and GL Posting Approval
• 5. Intercompany Transaction and Consolidation Reconciliation
  • What the evidence should show
• 6. Fixed Asset Capitalization and Depreciation
• 7. Tax Provision and Deferred Tax Calculation
  • The right automation boundary
• 8. Close Readiness and Cycle-Time Management
• Month-End Close: 8-Point Checklist Comparison
• Turn the Checklist Into a Controlled Close
  • Frequently asked questions

1. Account Reconciliation and Balance Verification

Account reconciliation confirms that general ledger balances agree with source systems and external statements. The accounting owner should complete high-risk accounts before the period-end cutoff, while the controller reviews exceptions and signs off before reporting is finalized.

Bank accounts, credit cards, accounts receivable, accounts payable, payroll liabilities, fixed assets, and intercompany balances belong on the reconciliation schedule. Suspense accounts need explicit review. ProcessReel’s month-end close guidance identifies these accounts as core control points and calls for sign-off on each reconciliation.

Practical rule: A “reconciled” status is not evidence. The retained record should show which source transactions matched, which items remained open, who resolved each exception, and when approval occurred.

The automation boundary should be deterministic. A workflow can pull balances from the ERP, bank feeds, and subsidiary ledgers. It can apply predefined matching rules, tolerance thresholds, and exception routing. Human reviewers should decide whether an unusual item reflects timing, a missing posting, a duplicate, or a genuine error.

Start with cash, AR, revenue, and accrued expenses. These accounts typically combine volume with material reporting risk. Schedule recurring runs before close rather than waiting for a manual review queue to form. The control gate should block final reporting when a material exception lacks an owner, explanation, or approval.

A mid-market SaaS business might connect Salesforce revenue data, Stripe payments, and NetSuite balances. The useful design principle is not the vendor combination. It’s the evidence model. A reviewer should be able to open the run, inspect the matching logic, and trace every adjustment back to its source.

Teams evaluating account reconciliation automation should ask whether the system preserves transaction-level matching details, versioned rules, exception history, and approval records. A dashboard that only changes status from “open” to “complete” doesn’t remove audit risk.

2. Revenue Recognition and Contract-to-Cash Synchronization

Revenue recognition must connect signed contract terms, billing activity, service dates, and general ledger postings. The revenue owner performs the pre-close review five business days before month end. The controller approves policy exceptions and unresolved contract interpretations.

ASC 606 and IFRS 15 make contract terms operational inputs. Subscription revenue, professional services, usage charges, renewals, credits, and deferred revenue can require different posting logic. The workflow should map each revenue type to its approved GL account and recognition rule.

Before the close window opens, revenue operations owns contract completeness. Accounting owns recognition treatment. Systems such as Salesforce or Ironclad, billing platforms such as Stripe or Zuora, and the ERP should exchange the records needed for deterministic checks. Those checks can flag missing contracts, inconsistent service dates, duplicate billing references, and deferred revenue movements that disagree with the underlying schedule.

Routine schedules can run automatically. Ambiguous terms remain with accounting. That boundary accelerates standard processing without removing human approval.

The control gate combines completeness and policy review. Revenue operations resolves missing terms, while accounting approves exceptions. Retained evidence should include the contract reference, extracted terms, applicable policy version, billing record, posting result, and every human override.

A B2B SaaS company might run a contract-to-cash check before the close window opens. The workflow routes exceptions to sales operations or revenue accounting while standard schedules continue. The close team then addresses contract gaps before the GL is finalized, rather than discovering them during final review.

The workflow definition should contain the organization’s approved revenue policy. This keeps the policy version visible during control testing and reduces dependence on personal spreadsheets that can drift as contracts and systems change.

Teams implementing ASC 606 revenue recognition automation should keep AI Copilot focused on document interpretation, such as extracting dates or payment terms. Posting should follow deterministic, predefined rules. A human approver should review low-confidence results and contracts outside standard patterns.

The illustration and video below show how automated schedules handle standard amortization while human judgment applies to non-standard terms.

3. Accounts Payable and Expense Accrual

AP close work records invoices and unbilled obligations in the correct accounting period. The AP lead owns invoice completeness and three-way matching. The accounting manager approves material accruals before the cutoff, while procurement resolves vendor and receipt exceptions.

The workflow should distinguish matched invoices from PO-less invoices and blanket-PO invoices. Those populations carry different evidence requirements and should not share one routing path. A matched invoice can follow a predefined posting path. An unmatched item should route to procurement or the relevant budget owner.

The retained evidence should separate the invoice-to-GL posting date from the accrual booking date. Auditors may need to understand whether an expense was booked from an invoice, an estimate, or a subsequent reversal. A single final balance rarely explains that chronology.

Useful control gates include:

• Three-way match: Compare purchase order, receipt, and invoice before routine posting.
• Accrual approval: Require supporting evidence for services received but not yet invoiced.
• Materiality routing: Send high-value or unusual items to an approver instead of automatic posting.
• Tax validation: Apply the ERP’s approved tax code logic before the accrual reaches the GL.

A services company may use Slack or Microsoft Teams to collect department confirmations for unbilled work. The channel is only useful if the workflow captures the decision, source document, approver, timestamp, and resulting journal entry. Conversation alone is not a durable control record.

The automation boundary should cover invoice ingestion, matching, cutoff checks, aging analysis, recurring accrual logic, and exception routing. Human owners should approve estimates, unusual vendors, policy exceptions, and incomplete support.

The most common failure is treating every AP exception as an accounting problem. Procurement often owns the missing receipt. A department owner may own the unapproved service confirmation. A role-aware workflow sends the issue to the person who can resolve it, rather than leaving accounting to chase every dependency manually.

4. Journal Entry Review and GL Posting Approval

Journal entry approval confirms that manual and automated postings are accurate, authorized, supported, and properly coded. Preparers create entries. Subject-matter owners review the business rationale. Controllers approve entries that meet the organization’s materiality and segregation-of-duties policy.

Journal entries should be categorized before routing. Accruals, revenue adjustments, FX, reclassifications, depreciation, tax, and consolidation entries often require different reviewers. A generic approval inbox creates delay and weakens accountability because the reviewer may understand the arithmetic but not the underlying business event.

The control gate should require:

• A documented rationale: The preparer explains why the entry is needed.
• Supporting evidence: Contracts, schedules, invoices, calculations, or other source records are attached.
• Independent review: The approver checks coding, period, amount, and business purpose.
• Reversal logic: Temporary accruals include a defined reversal date and retained reversal evidence.

A journal entry should explain the business event, not merely balance the debits and credits.

A multi-entity organization can route revenue accruals to revenue accounting, FX entries to treasury, and consolidation entries to technical accounting. The workflow can enforce account combinations, entity permissions, required attachments, and approval thresholds. The human approver still owns the accounting judgment.

Email approval is weak when it lacks version control. A reviewer may approve an attachment that later changes. A governed workflow links the approval to the exact entry version, supporting files, and system write. That connection matters when auditors test whether the approved entry matches the posted entry.

Known month-end accruals should generate predefined reversal instructions. The next month’s run should confirm whether the reversal posted successfully. If the reversal fails, the workflow should create an exception instead of allowing the issue to disappear into the next close.

5. Intercompany Transaction and Consolidation Reconciliation

Intercompany reconciliation confirms that both sides of an entity-to-entity transaction agree before consolidation. Entity controllers own their balances and resolve source differences. The group controller sets matching policy, approves elimination logic, and signs off the consolidated result.

Set up a shared intercompany account structure before the pre-close window. Each transaction needs a consistent counterparty tag, entity identifier, currency, transaction type, and relevant pricing reference. Missing fields force spreadsheet matching and make local naming differences a control risk.

During pre-close, the workflow should match intercompany receivables with payables, compare amounts and currencies, validate required fields, and route exceptions to the responsible entity controllers. Large or unusual variances should escalate before the final consolidation run. The system can automate deterministic matching, while controllers retain judgment over disputed transactions.

The control gate should block manual elimination entries where an approved rule already applies. The workflow creates the elimination, links the source transactions, preserves the rule version, and routes approval to the group controller. Retain the matched pair, counterparty confirmation, variance explanation, approval history, currency treatment, and elimination posting.

A holding company with several legal entities may find that one entity posted an invoice while its counterparty posted a different amount. Each entity controller should correct the source posting, document the variance, and approve the revised result. A group-level plug can conceal a pricing error or missing counterparty posting and create reporting problems later.

What the evidence should show

The archive should preserve the consolidation run, including rejected and rerun versions. It should also connect the approved elimination to the exact source transactions and posted result.

Speed without accuracy is worse than slowness. Deterministic matching makes routine work faster, but human review remains accountable for exceptions, pricing interpretation, and policy decisions.

6. Fixed Asset Capitalization and Depreciation

Fixed asset close work separates capital purchases from operating expenses, updates the asset register, and posts depreciation under approved policy. The fixed asset accountant owns classification and register integrity. The controller approves policy exceptions and reviews the asset-to-GL reconciliation.

Before close, accounting should apply documented rules by asset class. Buildings, equipment, vehicles, software, lease-related assets, and internally developed items can require different useful lives, depreciation methods, and approval paths. Personal spreadsheets create version risk and weaken review evidence, so automation should handle repeatable calculations while accounting retains approval of classifications.

The capitalization policy forms the first control gate. The workflow routes items meeting approved criteria for review and sends items below the policy boundary through the expense path. Systems should enforce documented capitalization rules, not infer acceptable behavior from past postings. Retain the policy version, reviewer decision, and supporting approval.

During the monthly close run, the system calculates depreciation and prepares the entry after the asset register and GL inputs are complete. The fixed asset accountant owns the run. The controller releases posting only after reconciliation identifies additions, disposals, transfers, impairments, and accumulated depreciation differences.

Treat the asset register as a subledger. Its balance must agree with the GL, and its history must explain every material change.

A construction services company may purchase equipment through procurement, place it in service through operations, and record it in the ERP through accounting. The workflow should connect those handoffs. Retained evidence can include the invoice, approval, asset class, in-service date, depreciation calculation, and posting result.

Disposals require a separate control path. The workflow calculates the gain or loss, confirms proceeds, removes the asset and accumulated depreciation, and routes the offset account for review. The evidence package should trace the full asset lifecycle from purchase through disposal.

7. Tax Provision and Deferred Tax Calculation

Tax provision close work reconciles book income with tax obligations and records current and deferred tax under approved policy. The tax lead owns the calculation. Accounting posts approved entries. The controller reviews the provision, effective tax rate analysis, and unresolved policy questions.

The calculation may combine book-to-tax differences, jurisdictional rules, NOL usage, valuation allowance analysis, and deferred tax balances. Spreadsheets are not risky by nature. Ungoverned copies that change without version history or an approval trail create that risk. The tax lead should retain one controlled workpaper and restrict edits after review begins.

Before close, the workflow should encode policy definitions for NOLs, valuation allowance triggers, GILTI where relevant, effective tax rate assumptions, and jurisdictional mappings. Attach the policy version to the calculation and resulting GL entries. A preliminary provision five business days before close gives the tax team time to investigate large movements. The final run uses locked period data and approved accounting entries. Every change from preliminary to final requires a visible variance and explanation.

The right automation boundary

Deterministic workflow logic can reconcile book to tax, apply approved mappings, calculate recurring components, and prepare postings. AI Copilot can classify supporting documents or help interpret tax materials when confidence thresholds are met. The tax professional retains judgment over ambiguous treatment and approval of exceptions.

A multi-state SaaS organization might connect ERP income data, tax schedules, and jurisdictional workpapers. The control gate verifies support for every material adjustment and confirms that the final provision agrees with the approved calculation. The controller releases the entry only after that check.

The archive should retain the policy version, input snapshot, calculation steps, reviewer comments, approvals, journal entry, and subsequent adjustments. This evidence supports repeatable review while keeping tax judgment with the accountable owner. It also shows which steps were automated, which exceptions required human action, and which calculation was ultimately posted.

8. Close Readiness and Cycle-Time Management

Close readiness turns the seven accounting tasks into a controlled operating system. The controller sets the close calendar and approves its dependencies. Task owners update status and resolve assigned exceptions. The CFO receives escalations when a critical dependency threatens reporting delivery.

APQC data places the median monthly consolidated close at about 6.0 to 6.4 calendar days. Top performers finish in roughly 4.8 calendar days, while bottom performers need 10 days or more, as summarized in APQC close benchmarks. The gap makes bottleneck removal more valuable than tracking completion percentages alone.

Before period end, the controller assigns readiness work, cutoff dates, dependent postings, review windows, consolidation, reporting, and final sign-off. Each task needs a timing rule, accountable owner, automation boundary, control gate, and evidence requirement. AR aging may close before revenue accrual. AP accruals may precede consolidation. Tax provision may wait for approved pre-tax results. The workflow should show each dependency.

Automation can create tasks, schedule reminders, test dependencies, route exceptions, and capture evidence. It should not approve judgment-based exceptions. The controller decides whether a delay is acceptable, whether reporting can proceed with an open exception, and whether the period can be locked.

Use these operating rules:

• Parallelize independent work: Run reconciliations, AP collection, revenue preparation, and tax pre-work concurrently where dependencies do not exist.
• Escalate before cutoff: Alert the owner when a task is at risk, then route the issue to the controller or CFO under the escalation policy.
• Track root causes: Record missing data, failed integrations, late approvals, unclear ownership, or policy uncertainty.
• Review trends: Compare blockers across closes and prioritize deterministic fixes that reduce recurring manual intervention.

Independent close coverage reports that 50% of finance teams still take six or more business days, while 18% finish in one to three business days, according to CFO’s coverage of the Ledge benchmark. That gap supports a bottleneck-first operating model.

Loopfour’s month-end close automation can encode the calendar as governed workflow logic across ERP, CRM, billing, and document systems. A definitive close checklist for SaaS can define task coverage. The controller still owns approvals, control gates, exception decisions, and retained evidence.

Month-End Close: 8-Point Checklist Comparison

Turn the Checklist Into a Controlled Close

A month-end close checklist becomes useful when it controls execution. The checklist should assign a controller, accounting owner, AP owner, revenue owner, tax lead, and entity controller. It should define pre-close dates, period-end cutoffs, close-day deadlines, dependencies, and final sign-off.

The operating calendar should also define materiality thresholds. Routine transactions can follow predefined posting paths. Unusual or material items should require human approval. Every posting needs supporting evidence before release. Every exception needs an owner, due date, resolution, and approval. Every reversal needs a traceable link to the original entry.

The control record should retain:

• Approvals: Who reviewed the item and which version they approved.
• Exceptions: What failed, why it failed, and how the owner resolved it.
• Matching details: Which source transactions matched the GL balance.
• Reversals: Which temporary entries reversed and when.
• System writes: What the workflow changed in the ERP, billing platform, or other system.
• Version history: Which policy and workflow definition governed the run.

Process evidence guidance treats the checklist as an evidence system, not merely a task list. That distinction matters when auditors test whether controls operated consistently.

Loopfour Studio can implement predefined, deterministic workflows across the existing finance stack. The platform can connect systems such as NetSuite, Workday, Sage Intacct, QuickBooks, Salesforce, Stripe, Slack, Microsoft Teams, Box, Dropbox, DocuSign, Ironclad, Google Sheets, and Excel. Secure browser automation can support legacy tools without APIs, while run logs, execution trees, permissions, change history, and evidence capture preserve governance.

AI Copilot should remain scoped to interpretation tasks. It can help parse documents or classify unusual descriptions, but confidence thresholds and human fallback should control what happens next. Deterministic code should execute the approved workflow. Human approvers should make accounting judgments.

Frequently asked questions

What is a month-end close checklist?

A month-end close checklist is a controlled schedule of accounting tasks used to verify completeness, record adjustments, reconcile balances, review results, and approve final reporting. The checklist should identify owners, dependencies, control gates, supporting evidence, and escalation rules.

How long should a month-end close take?

An efficient close commonly targets three to five business days, according to Rippling’s month-end close checklist guidance. APQC benchmarking places the median consolidated close at about 6.0 to 6.4 calendar days, so finance leaders should compare both cycle time and control quality.

Which accounts should be reconciled during month end close?

The close should include bank accounts, credit cards, accounts receivable, accounts payable, payroll liabilities, fixed assets, intercompany balances, and suspense accounts. Each reconciliation should include matching support, exception handling, and sign-off before final reporting.

What should auditors see in a month-end close checklist?

Auditors should be able to see task ownership, supporting documents, approval history, exception records, matching details, reversal evidence, and system write logs. HighRadius’s month-end close process guidance emphasizes documentation and sign-off as the close becomes more distributed across systems and entities.

How can finance teams automate month-end close without removing human approval?

Finance teams can automate deterministic tasks such as data pulls, matching, recurring calculations, dependency checks, reminders, and exception routing. Human reviewers should approve material entries, unusual reconciliations, policy exceptions, and final reporting. This approach replaces repetitive execution without delegating accounting judgment to a black box.

What is the first bottleneck to address in a slow close?

The controller should identify the task that repeatedly blocks downstream work. Bank reconciliation is often a high-friction area. Recent benchmarking commentary identifies bank reconciliation as the most time-consuming close activity for 71% of mid-size organizations and a cause of missed target close dates for 43%, as reported in CFO’s benchmark coverage. The practical response is to inspect matching rules, data quality, exception ownership, and approval latency before buying another reporting tool.

How does Loopfour support a governed month-end close?

Loopfour encodes close tasks as versioned, deterministic workflows that run across existing finance systems. Loopfour Studio supports implementation, exception routing, human approvals, observability, governance, and retained evidence. AI Copilot remains limited to interpretation with confidence thresholds and human fallback.

Loopfour can turn a month-end close checklist into deterministic workflows for reconciliations, accruals, journal approvals, consolidation, and final sign-off. Finance leaders can connect the existing ERP, CRM, billing, and document stack while preserving execution evidence for every action and exception. Visit Loopfour to discuss a governed close workflow built around the team’s systems and control requirements.