What a defensible close cycle actually looks like across multiple entities

The close is a control, not a deadline

Most finance teams measure the close in days. That measurement is useful, but it hides the question auditors and boards actually ask: can you demonstrate that the numbers were produced through a controlled process, consistently, every cycle?

In a multi-entity group, the failure mode is rarely a single missed reconciliation. It is drift, each entity closing slightly differently, each controller applying slightly different judgement, until the consolidated position becomes difficult to defend.

Three structural decisions

First, a single close calendar with entity-level ownership. Not a shared spreadsheet, but a tracked calendar where each task has a named owner, a due day relative to close, and an escalation path.

Second, standardised reconciliation thresholds. Materiality applied consistently across entities removes the argument about what needs supporting evidence.

Third, evidence collected as work happens. Audit packs assembled after the fact are always incomplete. Evidence captured inside the workflow is always available.

What good looks like

A group operating this way can answer, at any point in the cycle, which entities are on track, which tasks are at risk, and what the consolidated position looks like on a preliminary basis. Leadership stops asking when the numbers will be ready and starts asking what the numbers mean.