Month-End Close Optimisation: Diagnose and Cut Close Days

Month-end close optimisation: where the days goMonth-end close optimisation starts with measurement, not redesign: log the actual start and finish of each step for two cycles, with its blocking input. In most groups the delay concentrates in three places — sub-ledger cut-off discipline, late manual journals, and intercompany differences surfacing at consolidation. Fixing those three typically recovers two to four days without changing systems.Close acceleration projects usually begin with a target — 'five days' — and a tool. They should begin with a measurement, because the days are rarely lost where the team thinks they are.The pattern we see repeatedly: a step nominally starts on its calendar date, but its input is not final, so the work is performed twice. The second pass is invisible in the calendar and completely visible in the overtime.Diagnose before you change anything

Log per step: planned start, actual start, actual finish, who performed it, and what it was waiting for

Run the log for two full cycles — one cycle is anecdote

Separate rework from work: how much of each step was redone because an input changed

Count manual journals by day, and identify which arrive after downstream steps have started

Measure the intercompany residual at submission versus at consolidation; a gap means differences are being found too late

Ask each preparer what they wait for. The answer is usually more precise than the calendar

The interventions that payOrdered by return per unit of effort, based on what typically moves the needle in multi-entity groups.

Move work before period end: accruals prepared from known data, recurring journals scheduled, fixed asset and depreciation runs pre-validated, reconciliations of stable accounts performed at day -5

Enforce cut-offs: intercompany invoicing, AP, AR and payroll cut-offs that are dates, not aspirations, with a documented exception route

Materiality-tier the reconciliations: full monthly reconciliation for material and volatile accounts, quarterly for the rest, documented as policy

Kill the second pass: no downstream step starts until its entry condition is met — this feels slower and finishes earlier

Automate the mechanical parts first: bank matching, sub-ledger to GL agreement, recurring journals, validation of submissions on entry

Move intercompany matching to submission, not consolidation, with categorised differences and named owners

What not to do

Do not shorten the calendar without removing work — the deadline moves, the quality drops, and post-close adjustments rise

Do not cut reconciliation scope without a documented materiality policy; that is a control weakening, and the auditor will treat it as one

Do not keep the period open 'just in case'; a soft close means nothing downstream can be relied on

Do not buy a close-management tool before the calendar has owners and entry conditions — the tool will encode the current chaos

Do not treat management reporting and statutory reporting as separate builds; the reconciliation between them is pure waste

Sequencing a realistic programme

Cycle 1: measure only. No changes, full logging

Cycle 2: cut-off discipline and pre-close work. Usually the largest single gain

Cycle 3: reconciliation tiering and the reviewer sign-off trail

Cycle 4: intercompany matching moved to submission, with tolerance and taxonomy applied

Cycle 5: automate the mechanical steps now that the process is stable

Cycle 6: reset the calendar to the achieved timing and hold it

Metrics that prove it

Days to close, split local versus group

Post-close adjustments in number and value — the strongest single quality indicator

Manual journals after day +2, in number and value

Percentage of reconciliations signed off by the calendar date

Rework hours per cycle, from the step log

Intercompany residual after elimination, and its ageing

Close optimisation checklist

Two cycles of step-level timing logged, including blocking inputs

Rework identified and quantified per step

Entry condition defined per step, alongside the date

Named owner and backup per step

Cut-offs documented for intercompany, AP, AR and payroll, with an exception route

Pre-close work moved to before period end where the data allows

Reconciliation materiality tiering approved as policy

Intercompany matching performed at submission, not consolidation

Hard close enforced, with logged approval for any reopening

Management and statutory reporting sourced from the same consolidated data

Close metrics reported monthly to the CFO

Automation applied only after the process is stable

How we would approach this

We measure the actual close before proposing changes, because the calendar on paper is rarely the calendar in practice.

We attack cut-off discipline and rework first — those are free, and they usually deliver most of the improvement.

We only automate once the process is stable, so the tooling encodes the target state rather than the current one.

How do you shorten a month-end close?Sequence tasks by dependency rather than department, move reconciliations to a continuous basis, set materiality thresholds for investigation, and remove manual re-keying between source systems and the consolidation.Does a faster close reduce quality?Not when the acceleration comes from earlier evidence rather than fewer checks. Closes degrade when review steps are dropped; they improve when reconciliation happens before the cut-off instead of after it.Primary sources

IAS 1 — Presentation of Financial Statements — https://www.ifrs.org/issued-standards/list-of-standards/ias-1-presentation-of-financial-statements/

IAS 34 — Interim Financial Reporting — https://www.ifrs.org/issued-standards/list-of-standards/ias-34-interim-financial-reporting/