Year-End Financial Close Checklist for CFOs: Automation, Reconciliation & Reporting

Year-End Financial Close Checklist for CFOs: Automation, Reconciliation & Reporting

Year-end financial close has a way of exposing problems that remained manageable throughout the rest of the year.

An unreconciled account that was carried forward month after month. An intercompany balance that does not match the counterparty. Supplier invoices still waiting for approval.

Customer payments sitting unapplied. Spreadsheet reports that depend on one person. Data that has not moved correctly between operational and accounting systems.

Individually, these issues may appear small.

At year-end, they converge.

For CFOs and controllers, the objective is therefore not simply to complete a longer version of the month-end close.

The objective is to reach a point where the organization can demonstrate that:

• Material balances are supported
• Transactions are recorded in the appropriate period
• Reconciliations are complete
• Intercompany differences have been investigated
• Adjustments are documented and approved
• Exceptions are visible
• Management reporting agrees with the underlying financial data
• The final period can be closed with confidence

That requires more than a checklist of accounting tasks.

A strong year-end financial close needs clear ownership, reliable data, reconciliation discipline, exception management, review controls, and the right use of automation.

This checklist provides a practical framework CFOs, controllers, and finance leaders can use to organize the process.

What Makes Year-End Close Different From a Normal Month-End Close?

Month-end and year-end close share many of the same activities.

Both may require:

• Bank reconciliation
• Accounts payable review
• Accounts receivable review
• Journal entries
• Balance-sheet reconciliation
• Variance analysis
• Financial reporting

But year-end normally introduces an additional level of completeness and scrutiny.

Finance teams may also need to address:

• Full-year balance validation
• Older unreconciled items
• Inventory and fixed asset reviews
• Intercompany differences
• Annual accruals and adjustments
• Supporting documentation
• Audit preparation
• Management sign-offs
• Consolidated reporting
• Period locking
• Carry-forward issues for the next financial year

A useful way to think about the distinction is:

Month-end confirms the period. Year-end also needs to prove the year.

That makes preparation before the closing date particularly important.

Before You Start: Build a Year-End Close Control Sheet

One of the simplest ways to improve year-end close management is to stop treating the checklist as a list of accounting activities and start treating it as a controlled workflow.

Every important close activity should answer:

What needs to be completed?
Who owns it?
Who reviews it?
When is it due?
What evidence proves completion?
What exception remains open?

A close control sheet could look like this:

The exact format is less important than the discipline behind it.

Every material close activity should have:

Task → Owner → Deadline → Evidence → Review → Exception

When those six elements are visible, CFOs can manage the close by exception rather than repeatedly asking teams whether individual tasks are finished.

Year-End Financial Close Checklist

1. Confirm Close Ownership, Deadlines and Dependencies

Before the accounting work begins, establish the close calendar.

Do not assume everyone knows what they own because the same task was completed last month.

Year-end frequently involves additional reviews, approvals, and dependencies.

Confirm:

• Close start date
• Financial cut-off date
• Task owners
• Reviewers
• Due dates
• Task dependencies
• Escalation path
• Final CFO or controller approval
• Reporting deadline
• Period-lock date

Dependencies matter particularly at year-end.

The consolidated financial statements, for example, cannot be finalized if one entity has not completed its intercompany reconciliation.

Similarly, management reporting may depend on completing inventory adjustments first.

CFO question

Which unfinished activity can delay everything behind it?

Those tasks should receive the highest visibility.

Automation opportunity

Workflow tools can support:

• Task assignment
• Deadline reminders
• Dependency tracking
• Escalation of overdue items
• Review notifications
• Close-status dashboards

Automation does not replace task ownership.

It makes ownership easier to monitor.

2. Complete Accounts Payable Cut-Off and Accrual Review

Year-end accounts payable should reflect obligations belonging to the closing period, based on the organization’s applicable accounting policies.

Review:

• Outstanding supplier invoices
• Invoices received but not yet entered
• Pending approvals
• Supplier credit notes
• Old unmatched purchase orders
• Duplicate invoices
• Supplier statement differences
• Accrual requirements
• Expenses recorded in the wrong period

One recurring year-end problem is that the finance team knows an expense relates to the closing year, but the invoice has not yet reached accounting.

That creates a dependency on AP, procurement, department heads, or suppliers.

The sooner these items are identified, the less likely they are to become last-minute adjustments.

For finance teams where invoice capture, matching, and approval follow-ups regularly delay the close, accounts payable automation can reduce repetitive processing while keeping exceptions and accounting decisions under finance review

CFO question

Are year-end liabilities complete, or are we waiting for information that nobody owns?

Automation opportunity

Potential automation areas include:

• Invoice capture
• Data extraction
• PO/invoice matching
• Approval routing
• Duplicate detection
• Missing-invoice alerts
• Accrual-support workflows
• AP exception dashboards

Accounting judgments around cut-off and accruals should remain subject to the organization’s policies and appropriate professional review.

3. Review Accounts Receivable and Revenue Completeness

Year-end AR should provide a clear picture of what customers owe and why.

Review:

• Open customer invoices
• Unapplied receipts
• Customer credits
• Old balances
• Disputed invoices
• Write-offs awaiting approval
• Bad-debt considerations
• Revenue completeness
• Deferred or unearned amounts where applicable
• Receipts received after period-end that relate to open balances

Pay particular attention to old receivables.

An invoice that has remained open for several months may represent:

• A genuine outstanding balance
• An unapplied payment
• A billing dispute
• A credit that was not processed
• Incorrect customer mapping
• An accounting error

The aging report alone does not answer that question.

CFO question

Does the AR aging represent genuine customer debt, or does it contain balances nobody can explain?

Automation opportunity

Potential areas include:

• Payment matching
• Aging alerts
• Customer-account reconciliation
• Unapplied-receipt detection
• Collection workflow triggers
• Exception reporting

The purpose is not to automate decisions about collectability.

It is to make the exceptions requiring finance judgment easier to identify.

4. Reconcile Bank, Credit Card and Cash Accounts

Cash reconciliation should be completed before unresolved differences become part of the new year.

For each relevant account, compare:

External Statement ↔ General Ledger

Review:

• Bank accounts
• Credit cards
• Payment processor balances
• Cash clearing accounts
• Transfers between accounts
• Deposits in transit
• Outstanding payments
• Unidentified receipts
• Duplicate transactions
• Old reconciling items

Do not focus only on whether the reconciliation mathematically balances.

Review the age and nature of outstanding items.

A reconciling item carried forward repeatedly may indicate an underlying process issue rather than a timing difference.

Key principle

Do not carry unexplained cash differences into the next financial year simply because the reconciliation technically balances.

Automation opportunity

Reconciliation automation can assist with:

• Transaction matching
• Amount/date/reference matching
• Tolerance rules
• Duplicate detection
• Unmatched-transaction queues
• Exception categorization
• Reconciliation status reporting

The finance team should then spend more time investigating exceptions and less time manually matching obvious transactions.

More broadly, accounting automation can support bank and ledger reconciliation by matching routine transactions automatically and directing finance teams toward the exceptions that require investigation.

5. Reconcile Material Balance-Sheet Accounts

Year-end reconciliation should extend beyond bank accounts.

Every material balance-sheet account should have reasonable support.

Depending on the organization, this may include:

• Accounts receivable
• Accounts payable
• Inventory
• Prepaid expenses
• Accrued expenses
• Fixed assets
• Loans
• Payroll liabilities
• Tax accounts
• Deposits
• Clearing accounts
• Suspense accounts
• Other material assets or liabilities

For each account, ask:

What does this balance represent?

What external or supporting evidence exists?

What reconciling items remain?

How old are those items?

Who reviewed the reconciliation?

CFO question

Can every material balance-sheet number be explained and supported?

This is one of the strongest indicators of close quality.

A P&L may look reasonable while unresolved balance-sheet items continue accumulating underneath it.

Automation opportunity

Potential improvements include:

• Automated balance import
• Reconciliation templates
• Rule-based matching
• Supporting-document links
• Aging of reconciling items
• Reviewer workflows
• Exception dashboards

6. Resolve Intercompany Balances Before Consolidation

For multi-entity groups, intercompany differences can become one of the biggest year-end bottlenecks.

If Entity A records an intercompany receivable of $200,000, Entity B should normally have the corresponding payable reflected according to the group’s accounting policies.

But differences may arise because of:

• Timing
• Currency
• Different posting dates
• Missing transactions
• Incorrect counterparties
• Different account mappings
• One-sided entries
• FX adjustments
• Manual posting errors

A useful reconciliation structure is:

Entity A Receivable

↕

Entity B Payable

Then compare:

• Counterparty
• Amount
• Currency
• Period
• Transaction reference
• Account
• Supporting documentation

Importantly, three activities should not be treated as the same thing:

Reconciliation → Elimination → Consolidation

First confirm that the entity-level balances agree.

Then apply the appropriate elimination process.

Then produce the consolidated financial view.

For a deeper look at transaction matching, due-to/due-from balances, FX differences, exceptions, and the handoff from reconciliation to consolidation, see our intercompany reconciliation software guide.

CFO question

Which intercompany differences remain unresolved, who owns them, and can they delay consolidation?

Automation opportunity

Intercompany workflows can support:

• Counterparty matching
• Reference-based matching
• Currency-aware comparison
• Variance thresholds
• Exception identification
• Aging
• Entity ownership
• Reconciliation status dashboards

This allows finance teams to concentrate on differences that actually require investigation.

7. Review Inventory, Fixed Assets and Relevant Subledgers

Year-end close often requires confirming that key subledgers agree with the general ledger.

Inventory

Review:

• Physical count differences
• Inventory adjustments
• Goods in transit where relevant
• Obsolete or slow-moving inventory
• Warehouse transfers
• Inventory valuation inputs
• COGS alignment
• Inventory-to-GL reconciliation

Fixed assets

Review:

• Asset additions
• Disposals
• Depreciation
• Asset transfers
• Supporting documentation
• Fixed asset register-to-GL reconciliation

Other subledgers

Depending on the business, also review:

• Payroll
• Employee expenses
• Leases
• Loans
• Subscription billing
• Payment processors
• Other operational systems feeding accounting

The CFO-level objective is not to reproduce every detailed accounting calculation.

It is to make sure that subledger activity agrees with the general ledger and material differences have owners.

8. Post and Review Year-End Adjusting Entries

Once reconciliations are substantially complete, finance may identify adjusting entries required under the organization’s accounting policies.

Typical categories can include:

• Accruals
• Prepayments
• Depreciation
• Amortization
• Reclassifications
• Corrections
• Approved year-end adjustments

Avoid situations where journal entries appear in the ledger without sufficient explanation several months later.

Review:

• Who prepared the entry?
• Why was it required?
• What supporting evidence exists?
• Which accounts were affected?
• Has somebody independent reviewed it?
• Is reversal required in the next period?

Automation opportunity

Potential improvements include:

• Recurring journal templates
• Approval workflows
• Supporting-document attachment
• Automated recurring journals where appropriate
• Journal status tracking
• Reviewer notifications

Material judgment and final approval should remain under appropriate finance control.

9. Validate Data Completeness Across Connected Systems

This is an increasingly important year-end close check.

Accounting rarely operates in isolation.

Financial data may originate from:

• ERP systems
• CRM platforms
• Payroll
• Expense management
• Banking systems
• eCommerce platforms
• Inventory systems
• Payment gateways
• Billing applications
• Custom operational software

Before finalizing the year, ask:

Did every transaction that should have reached accounting actually arrive?

When financial information originates across ERP, CRM, payroll, banking, eCommerce, inventory, and other applications, connected business systems can reduce manual data handoffs and provide a more controlled path into the accounting platform.

Review:

• Failed integrations
• Missing batches
• Duplicate transactions
• Delayed synchronization
• Unresolved exception queues
• Failed API jobs
• Manual CSV imports
• Transactions waiting for mapping
• Systems with processing backlogs

An integration can technically remain online while some transactions are still missing or waiting to process.

CFO question

Do we have evidence that the ledger is complete, or are we assuming every connected system worked correctly?

Automation opportunity

Useful controls include:

• API health monitoring
• Transaction-count reconciliation
• Missing-record alerts
• Duplicate detection
• Sync exception queues
• Processing-latency monitoring
• Source-to-ledger completeness checks

This connects technical integration health directly to financial control.

10. Complete Variance and Management Review

A reconciled account is not automatically a reasonable account.

Once transaction-level and balance-level controls are substantially complete, management should step back and review the financial results.

Compare:

Current Year vs Prior Year

Actual vs Budget

Actual vs Forecast

Entity vs Group

Month vs Historical Trend

Investigate material movements in:

• Revenue
• Gross margin
• Operating expenses
• Payroll
• Cash
• Working capital
• Receivables
• Payables
• Inventory
• Entity-level profitability
• Other key KPIs

The purpose is to detect something that may be technically posted correctly but economically unusual.

Key principle

Reconciled does not automatically mean reasonable.

This is where stronger FP&A and financial visibility becomes important, giving CFOs a clearer way to compare actual performance against budgets, forecasts, historical trends, and operational drivers

A large unexplained margin shift, for example, may indicate a legitimate operational change.

Or it may reveal:

• Incorrect mapping
• Missing costs
• Duplicate revenue
• Incorrect period allocation
• Inventory differences

Automation opportunity

Automation and analytics can assist with:

• Variance detection
• Threshold alerts
• Trend comparison
• Anomaly identification
• Dashboard refreshes
• Exception prioritization

Interpretation still belongs to finance leadership.

11. Finalize Financial Statements and Management Reporting

Once balances and adjustments are complete, finance can move from closing the ledger to communicating the result.

Depending on the organization, reporting may include:

• Profit and loss statement
• Balance sheet
• Cash flow statement
• Entity-level reporting
• Consolidated reporting
• Department reporting
• Budget vs actual
• Forecast comparison
• KPI dashboards
• Working-capital reporting
• Variance commentary
• Board or management reporting

The reporting process should not require finance to rebuild the same spreadsheet model every year if the required information already exists across accounting systems.

For multi-entity organizations, our guide to consolidated financial reporting explains this process in more detail, including financial data collection, chart-of-accounts standardization, intercompany reconciliation, consolidation adjustments, and group-level reporting.

CFO question

How much of our reporting process involves analyzing financial performance, and how much involves gathering and rebuilding data?

That distinction often reveals significant automation opportunities.

12. Lock the Period, Preserve Evidence and Run a Post-Close Review

The close should not end when the CFO receives the final reporting pack.

Once appropriate approvals are complete:

• Complete required sign-offs
• Apply period-lock controls
• Preserve reconciliation evidence
• Retain journal support
• Archive final reports
• Document unresolved carry-forward items
• Restrict unauthorized changes to the closed period

Then run a short post-close review.

Ask:

What delayed the close?

Which tasks missed deadlines?

What created the most manual work?

Was finance repeatedly gathering information from other teams?

What produced the most exceptions?

Bank matching? Intercompany? AR? Integrations?

Which problems repeated from previous closes?

Recurring issues should become improvement priorities.

Which processes should be automated before the next close?

Focus on recurring activities rather than one-off year-end events.

A year-end close should therefore produce two outputs:

1. Final financial reporting

and

2. A better process for the next close

CFO Year-End Close Scorecard

Use this scorecard to track high-level readiness.

The goal is not merely to turn every line green.

CFOs should pay particular attention to open exceptions.

A task can technically be complete while still containing an unresolved issue.

An Illustrative Year-End Close Timeline

Every organization should adapt its timeline according to reporting requirements, team size, systems, and complexity.

A practical framework might look like this:

30 Days Before Year-End

Focus on cleanup and ownership.

• Review old reconciliations
• Identify long-outstanding AR/AP items
• Confirm close owners
• Review intercompany differences
• Identify system and integration issues
• Confirm inventory-count requirements
• Review recurring close bottlenecks

15 Days Before Year-End

Focus on dependencies.

• Confirm accrual inputs
• Review pending supplier invoices
• Validate intercompany balances
• Review inventory and fixed asset changes
• Resolve open integration exceptions
• Confirm close reporting requirements

5 Days Before Year-End

Focus on unresolved exceptions.

• Escalate outstanding approvals
• Review unreconciled cash items
• Resolve known mapping issues
• Confirm entity readiness
• Validate supporting documentation

Year-End Date

Focus on cut-off.

• Capture required period transactions
• Apply relevant operational cut-offs
• Confirm feeds and integrations
• Record known year-end information according to policy

Days 1–3 After Year-End

Focus on reconciliation.

• Bank reconciliation
• AP/AR review
• Balance-sheet reconciliation
• Intercompany reconciliation
• Adjusting entries
• Integration completeness checks

Days 4–5

Focus on management review.

• Variance analysis
• Entity review
• Consolidation
• Management adjustments
• Final exception resolution

Days 5–7

Focus on reporting and control.

• Final financial statements
• Management reporting
• CFO review
• Sign-off
• Period lock
• Evidence retention

This is an illustrative framework, not a universal close deadline.

What Should Be Automated in the Financial Close?

The strongest finance automation strategies do not attempt to automate every accounting decision.

Instead, they separate repetitive process work from activities that require professional judgment.

A practical rule is:

Automate repetitive evidence gathering, matching, monitoring and reporting. Keep judgment, material review and approval under human control.

Deciding what to automate should also be based on measurable business value. Satva's finance automation ROI framework helps CFOs compare automation opportunities using processing time, errors, rework, close-cycle improvement, exception volume, and team capacity.

That creates a more controlled close rather than simply a more automated one.

Where Is Your Financial Close Actually Losing Time?

If the close repeatedly misses its target, the underlying problem is not always accounting complexity.

Often, the delay comes from process design.

This diagnostic exercise is important because different bottlenecks require different solutions.

If these problems recur throughout the year, our analysis of where finance teams lose time explores manual data collection, spreadsheet reporting, reconciliation, approval delays, disconnected systems, and other recurring finance bottlenecks in greater detail.

A reporting problem should not automatically be treated as a reconciliation problem.

A reconciliation problem should not automatically be treated as an accounting-system problem.

And an automation project should not begin until the underlying workflow is understood.

Final Year-End Close Checklist for CFOs

Before the period is locked, confirm that:

• Close owners and deadlines are documented
• AP cut-off and accrual review is complete
• AR and revenue completeness have been reviewed
• Bank and credit card accounts are reconciled
• Material balance-sheet accounts are supported
• Intercompany balances are reconciled
• Inventory and fixed asset subledgers have been reviewed
• Year-end adjusting entries are supported and approved
• Connected-system data completeness has been validated
• Material variances have been investigated
• Financial statements and management reporting are complete
• Required approvals have been obtained
• The period has been locked appropriately
• Supporting evidence has been retained
• Carry-forward exceptions have been documented
• Post-close improvement actions have owners

The last item is easy to overlook.

Do not wait until next December to remember what made this close difficult.

Record the lessons while the problems are still fresh.

A Better Year-End Close Creates a Better Next Close

The year-end close is often viewed as the final accounting exercise of the financial year.

It should also be treated as a diagnostic opportunity.

It shows finance leaders:

• Which reconciliations consume the most time
• Which systems remain disconnected
• Where data quality breaks down
• Which approvals create delays
• Which exceptions repeat
• Which reports still depend on spreadsheets
• Which activities require judgment
• Which activities are simply repetitive

The strongest close process is therefore not the one with the longest checklist.

It is the one where finance knows:

What needs to happen.

Who owns it.

What proves completion.

Which exceptions remain.

Where automation can help.

And when the numbers are ready to trust.

Frequently Asked Questions

What is included in a year-end financial close checklist?

A year-end financial close checklist typically includes close ownership, accounts payable and receivable review, bank reconciliation, balance-sheet reconciliation, intercompany reconciliation, inventory and fixed asset review, adjusting entries, system-data completeness, variance analysis, financial reporting, approvals, evidence retention, and period locking.

The exact checklist will depend on the organization’s accounting policies, systems, industry, entity structure, and reporting requirements.

How is year-end close different from month-end close?

Year-end usually requires broader validation of full-year balances, additional adjusting entries, more extensive supporting documentation, inventory and fixed asset reviews, intercompany cleanup, management sign-off, final annual reporting, and preparation for audit or other annual reporting requirements.

Month-end confirms the financial activity of a shorter period, while year-end typically requires a more comprehensive review of the financial year.

When should finance teams start preparing for year-end close?

Preparation should begin before the final accounting period ends.

Many organizations benefit from reviewing old reconciliations, open AR/AP items, intercompany differences, system issues, task ownership, and reporting requirements several weeks before year-end.

The exact timing depends on the organization’s close calendar and complexity.

Which year-end close activities can be automated?

Common automation opportunities include data collection, transaction matching, repetitive reconciliations, task reminders, exception monitoring, system-to-system data transfer, report refreshes, and status tracking.

Accounting judgments, significant adjustments, policy decisions, material estimates, and final approvals should remain under appropriate human control.

How can CFOs reduce delays in financial close?

Start by identifying where the close actually loses time.

Common bottlenecks include manual reconciliations, late intercompany differences, approval delays, disconnected systems, repeated spreadsheet consolidation, unresolved exceptions, and unclear task ownership.

Once the bottleneck is identified, finance can determine whether the right solution is process redesign, earlier preparation, better monitoring, system integration, or automation.

How should multi-entity businesses handle intercompany reconciliation at year-end?

Each entity should compare its intercompany receivables, payables, revenue, expenses, and other relevant balances with the corresponding counterparty records.

Differences should be investigated before consolidation.

Finance teams should distinguish between reconciliation, elimination, and consolidation rather than treating them as one process.

Matching rules, variance thresholds, ownership workflows, and exception tracking can help reduce the amount of manual comparison required.