The annual close is not a bigger version of the monthly close. It is a fundamentally different operation, with its own legal deadlines, its own risks, and its own technical traps inside the ERP. Asset depreciation, tax provisions, audit file exports, and the irreversible fiscal year rollover — these are steps that do not exist in monthly routines and unfold over several months, not five days.
In September, finance teams enter the critical window. For companies on a calendar year, 90 days remain before 31 December. That is short if the schedule is not locked in now.
This guide provides an executable three-phase checklist (D-90, D-30, D-7) for CFOs, management controllers, and accounting leads running the year-end close in a cloud ERP (Sage X3, Business Central, Odoo, SAP Business One, Cegid XRP Flex).
Why the Year-End Close Is Different — and Riskier — Than the Monthly Close
Operations That Only Happen Annually
In the monthly close, the task list is well-known and repeated twelve times a year. The year-end close adds specific operations performed only once:
- Asset depreciation and impairment: calculating annual depreciation charges, updating the amortisation schedule in the Fixed Assets (FA) module, processing disposals and asset retirements for the year.
- Provisions for risks and liabilities: provisions for disputes, doubtful receivables, and obsolete inventory. These provisions result from a business judgement that the ERP cannot automate on its own.
- Annual cut-off entries: accrued expenses, prepaid expenses, accrued revenue, and deferred income. Monthly approximations are acceptable in routine closes; the year-end figures must be accurate for the audit.
- Corporate tax provision: the estimated income tax accrual has no equivalent in a standard monthly close.
- Statutory audit file export: most jurisdictions require an auditable accounting extract at year-end. In France this is the FEC (Fichier des Écritures Comptables, defined under Article L47 A of the Livre des Procédures Fiscales); equivalent formats include SAF-T in Norway and Austria, iXBRL in the UK, and SII in Spain. This file must cover the entire closed fiscal year and be available to tax authorities on request.
The Risk of Hidden Discrepancies After 12 Months of Transactions
A full year accumulates twelve months of journal entries, interface runs, manual corrections, and out-of-process postings. Discrepancies that went unnoticed through monthly closes surface during the annual reconciliation: uncleared suspense accounts, partially matched items across thousands of customer and supplier lines, FX translation differences on foreign-currency purchases. The higher the transaction volume, the larger the compounding effect.
D-90 — Preparing Your ERP for the Close
Ninety days out, the goal is to detect configuration and data problems before they turn into technical blockers in December.
Audit Your ERP Close Configuration
Start with a configuration review before touching any data:
- Fiscal year: confirm the current fiscal year is open with the correct start and end dates in the ERP’s accounting setup.
- VAT / tax codes: check active tax codes, applicable rates, and collection/deduction accounts. An incorrect rate introduced at D-90 will flow through every transaction until the close.
- Currency tables: verify exchange rate tables and the valuation method selected (spot rate, average rate, closing rate). In multi-currency environments, this setting drives all translation entries.
- Inter-module integration profiles: test that purchase-to-accounting, sales-to-accounting, and inventory-to-accounting flows are consistent. An integration anomaly discovered in December is unmanageable.
Launch the Fixed Assets Inventory
The Fixed Assets module is typically the first to generate discrepancies at year-end:
- List assets placed in service during the year and verify that each depreciation start date is correct.
- Identify assets disposed of or scrapped that must be written off in the ERP before close.
- Run a depreciation simulation to estimate the annual charge and compare it against the budget.
- Review lease and finance lease assets: their accounting treatment (IFRS 16 or local GAAP) must be correctly configured.
Reconcile Intercompany Accounts
If your ERP scope covers multiple entities, intercompany reconciliation is mandatory before any consolidation:
- List all intercompany transactions for the year (recharges, intergroup loans, treasury flows).
- Compare mirror balances across entities: a debit in one entity must match a credit in the other, net of FX effects.
- Resolve discrepancies immediately. The further from the original transaction date, the harder it is to trace its origin.
Review User Access Rights
The year-end close is the right moment to audit ERP profiles:
- Revoke access for employees who left the company during the year.
- Verify that posting rights for year-end entries are limited to authorised individuals.
- Document who can unlock a closed period — this right must be strictly controlled.
D-30 — The Reconciliation Phase
Thirty days from close, the slate must be clean. The objective of this phase is to eliminate all remaining anomalies and prepare the cut-off entries.
Match Open Items on Accounts Receivable and Payable
Matching is time-consuming but non-negotiable for the audit:
- Run an open-item report across all customer and supplier accounts.
- Prioritise accounts with abnormal balances (credit balances on receivables, debit balances on payables).
- For ongoing disputes, confirm that the corresponding provision is booked and documented.
Post Accrued Expenses (Uninvoiced Goods Receipts)
Uninvoiced goods receipts are one of the main sources of uncertainty in the year-end close. The process in the ERP:
- Extract the list of goods receipts or services received for which no supplier invoice has yet been posted.
- Estimate the accrual from purchase orders and goods receipts in the ERP.
- Post a cut-off journal entry at 31 December with a supporting note for the auditor.
In Odoo, this extract comes from the Purchase module (received orders without invoice). In Business Central, the “Uninvoiced Receipts” report provides the list directly.
Reconcile Annual VAT / Sales Tax
The annual VAT or sales tax balance must be reconciled against the periodic returns filed during the year:
- Extract the cumulative output and input tax balances from the ERP for the fiscal year.
- Compare line by line against the periodic returns submitted to your tax authority.
- Discrepancies must be justified (adjustments, credit notes, corrections) before the period is locked.
Lock Prior Accounting Periods
Before closing December, lock January through November to prevent late postings:
- Dynamics 365 Business Central: General Ledger > Setup > General Ledger Setup > Lock posting before the selected date.
- Odoo: Accounting > Configuration > Settings > Lock Date.
- Sage X3: Accounting > Parameters > Fiscal Years and Periods > Period Status.
A partial lock (read-only) is preferable to a hard lock in November: it still allows discrepancy investigation without creating new entries.
D-7 — Final Validation Before Period Freeze
The last week before close is for validation, not discovery. Any discrepancy found here must have a known resolution or a documented justification.
Run the Close Report
Most cloud ERPs include a year-end close wizard or report. Run it in simulation mode first:
- Verify that all journals for the year are balanced (debits = credits).
- Confirm there are no suspense or transit accounts with a non-zero balance.
- Validate the depreciation entries generated automatically by the FA module.
Export the General Ledger for the Auditor
At year-end, most jurisdictions require a complete, auditable accounting file that must be generated before the period freeze and retained securely:
- Odoo: Accounting > Reports > Audit > Export FEC (French entities) or the standard general ledger export.
- Sage X3: Accounting Extract > FEC format (French entities) or standard export.
- Business Central: “Audit File Export” extension > FEC format (French entities) or SAF-T for other jurisdictions.
- SAP Business One: Financial module > Accounting Data Export > FEC or SAF-T (via add-on depending on version and country).
Store the export file in a secure, unmodifiable location. An altered audit file can be used as evidence against the company during a tax inspection.
Validate Provisions and Final Adjustments
- Review the provisions posted at D-30 and confirm they reflect the latest business assessments.
- Post FX translation entries for foreign-currency balances at the closing rate.
- Book the estimated income tax provision using the amount from the external accountant or tax department.
- Document every manual journal entry outside the standard process with its justification and the approving signatory.
Full Backup Before Freeze
Before launching the irreversible year-end close procedure, take a full database backup:
- For cloud ERPs, confirm that your vendor offers an on-demand backup export (snapshot) before the rollover procedure.
- Keep the snapshot at minimum until the audit is complete.
- Test the year-end rollover procedure in your test environment (sandbox) before running it in production. The rollover is generally irreversible.
D0 — Year-End Posting and New Fiscal Year Opening
Rollover Procedure in the Main ERPs
| ERP | Menu | Key Points |
|---|---|---|
| SAP Business One | Administration > Utilities > Period-End Closing | Ensure all current-year periods are closed before launching |
| Dynamics 365 BC | General Ledger > Year-End Close > Create Closing Entries | Two-step process: close, then carry forward balances |
| Odoo | Accounting > Fiscal Year Closing | Balance carryforward is automatic if correctly configured |
| Sage X3 | Accounting > Year-End Processing | Verify the configuration of carryforward accounts |
| Cegid XRP Flex | Accounting > Year-End > Generate Opening Balances | Run the simulation before generating definitive opening balances |
Verify Opening Balances in the New Fiscal Year
After the rollover, immediately check the opening balances for the new year:
- The opening trial balance must match the closing trial balance of the prior year (excluding the appropriated profit).
- All balance sheet accounts must show an opening balance: a zero-balance sheet account at the start of the year indicates a carryforward error.
- Income statement accounts (P&L) must be zeroed out (carried to the income account, which is then transferred to equity).
The 5 Classic Year-End Close Mistakes
1) Starting checks too late. 1 December is not D-90, it is D-30. Teams that begin organising in November end up firefighting in December. The D-90 window (September) is the only one that leaves enough time to correct deep-seated anomalies.
2) Ignoring the audit file export until the last moment. The statutory accounting export must be generated and validated before the period freeze — not after. A file generated after post-close corrections does not reflect the state of the accounts at 31 December.
3) Running the year-end rollover without a prior test. Executing the rollover in production without a sandbox test exposes the business to configuration errors in the balance carryforward. Once the year is rolled over, reverting is nearly impossible without vendor intervention.
4) Forgetting suspense accounts. Transit and clearing accounts accumulate forgotten entries. A manually zeroed suspense account in late December with no supporting justification is an audit risk.
5) Underestimating the external auditor’s timeline. The external auditor works on their own schedule. If your general ledger is not ready by the agreed date, delays cascade to the sign-off on financial statements — and potentially to your shareholder meeting.
Typical Timeline for a 31 December Fiscal Year-End
| Date | Key Actions |
|---|---|
| End of September (D-90) | ERP configuration audit, launch fixed assets inventory |
| End of October (D-60) | Lock Jan–Sep periods, intercompany reconciliation |
| 30 November (D-30) | AR/AP matching, accrue uninvoiced receipts and prepayments, reconcile annual VAT |
| 15 December (D-15) | Run close report in simulation, validate provisions |
| 24 December (D-7) | Export audit file, hard-lock fiscal year, take snapshot backup |
| 2–5 January | Year-end rollover, verify opening balances |
For more on optimising your accounting cycle in the ERP, read our guide on ERP and real-time cash flow management and our article on management control and cost accounting in the ERP.
