From 18 to 9 working days: what a six-entity FRS 102 close transformation actually involves

If you run group reporting for a mid-cap multi-entity group, the close is probably running longer than it should, intercompany positions are not reconciling cleanly, FX retranslation runs twice each cycle because late entries force it, the partner audit firm asks the same questions every year, and the team rolling out of close has no headroom for the IFRS 18 transition that sits on next year's agenda. The fix is not working harder. The fix is a different close. This article walks through what the different close actually contains, with the numbers from a programme that has already been through it.

Atlas Verum has delivered a group reporting close transformation that took a six-entity FRS 102 consolidation from 18 working days to 9 working days end-to-end, with the audit cycle compressing in parallel from the partner audit firm's side. The work is replicable across mid-cap groups of similar complexity. This article walks through what the engagement actually contained, broken down by phase, with the design decisions made explicit.

The headline number, halving the close, masks the operational reality. A close that runs in 9 working days rather than 18 is not the same close finished faster. It is a different close, with different cut-off rules, different reconciliation cadence, different consolidation logic, and a different relationship to the audit cycle that follows it. The transformation produced a faster close because the design changed, not because the team worked harder.

What a 9-day close means at the right level of abstraction

The 9 working days are not 9 days of overtime. They are 9 working days of disciplined sequence: day 1 to 3 covers transactional cut-off and entity-level close, day 4 to 5 covers intercompany and FX, day 6 to 7 covers consolidation and elimination, day 8 covers analytical review and board pack assembly, day 9 covers the management commentary and the partner audit firm's preliminary walkthrough. The 18-day starting position used the same calendar shape but with two of every step rather than one, with rework in the middle.

The compression came from removing the rework, not from compressing the steps. Rework removal is the discipline that distinguishes transformation from optimisation. Optimisation makes a step faster. Transformation makes a step unnecessary or moves it earlier in the chain so it never blocks the path forward.

The starting position

The group ran six entities consolidating under FRS 102, with one principal trading entity, two service companies, two dormant holding companies, and one international subsidiary translated under IAS 21. The close took 18 working days from period-end to signed-off board pack. The audit cycle that followed took 14 working weeks from close completion to signed audit opinion. The combined cycle, close plus audit, sat at roughly 12 calendar weeks from period-end to filed accounts.

The pain points reported at the start of the engagement were five. First, intercompany positions did not reconcile cleanly at the entity level, with reconciliation chases extending into the audit cycle. Second, FX translation re-ran multiple times as late journal entries on the international subsidiary forced re-translation. Third, manual consolidation eliminations were tracked on a spreadsheet that no single owner controlled, with version-control breakdowns mid-close. Fourth, the audit firm asked the same set of questions every year because the prior-year audit file did not flow into the current-year close documentation. Fifth, the board pack assembly was a manual exercise of copying numbers from the consolidation file into a presentation, with the manual step producing rework when late adjustments came in.

Each of these five pain points represented a design failure, not an effort failure. The team was capable. The team was experienced. The team was working through a design that produced rework regardless of how hard they worked.

The four-stage critical-analysis protocol applied to the close

Atlas Verum's standard delivery methodology, the four-stage critical-analysis protocol, applied directly to the close transformation. Stage one, critical analysis, walked the close end-to-end with the group reporting team across a full quarter. Stage two, gap surfacing, identified where each of the five pain points originated. Stage three, bridging, designed the fix. Stage four, documentation, captured the redesign at inspection standard so the partner audit firm could consume it as the entry point to a re-scoped audit cycle.

The bridging-stage decisions are where the transformation lives. Some examples follow.

Intercompany reconciliation was redesigned from a month-end reconciliation exercise to a daily auto-match running off the ERP intercompany flag, with break investigation triggered at break crystallisation rather than at month-end. The month-end reconciliation became a confirmation that the daily auto-match had cleared rather than a reconciliation event in its own right.

FX translation was redesigned to lock the translation at day 3 with a controlled re-translation gate for late entries, rather than letting any entity-level adjustment force a re-run. The gate requires sign-off by the group reporting controller, which means late entries that do not justify re-translation flow into the next period rather than disrupting the current one.

Consolidation eliminations were moved out of the manual spreadsheet into a controlled file held on the group reporting platform, with a single owner, version control, and a documented method statement. The method statement is the deliverable the partner audit firm consumes during the audit cycle, which means the audit walkthrough is preserved across years and the audit firm does not re-ask the same questions.

The board pack was redesigned around an automated assembly process that pulls the final consolidation outputs directly into the pack, with the management commentary added as the only manual layer. Late adjustments now flow through the automation rather than requiring a manual re-key.

The prior-year audit file was integrated into the current-year close documentation through a structured handover document that captures the audit firm's previous-cycle questions, management responses, and resolution. The current year close addresses each item proactively, which means the audit firm starts its current-year fieldwork with the previous-year items already closed out.

What the redesign produced

The close itself dropped from 18 to 9 working days through the bridging-stage decisions above. The audit cycle that followed dropped from 14 weeks to 9 weeks because the audit firm received a documentation pack that already addressed the previous-cycle questions, the elimination method statement, and the FX translation gate. The audit firm did not ask for things it had already received.

The combined close-plus-audit cycle moved from roughly 12 calendar weeks to roughly 7 calendar weeks from period-end to filed accounts. The implications for the group were operational, not just process. The reduced cycle freed group reporting capacity for the second half of the calendar, allowing the team to take on the IFRS 18 transition work scoped for the following year without expanding headcount.

The transformation paid for itself within the first cycle in two ways. First, the partner audit firm's audit fee compressed because the audit work compressed. Second, the freed group reporting capacity displaced a budgeted contractor cost for the IFRS 18 transition. Combined, the in-period saving exceeded the transformation engagement cost.

What the documentation looks like

The transformation produced documentation at inspection standard from day one. The deliverable pack included a process map for each of the six entities and the consolidation, a method statement for intercompany auto-match, an FX translation gate procedure, an elimination method statement, a board pack assembly specification, and a prior-year audit handover template. Each document carried a control-owner, a frequency, a deficiency-classification protocol, and a documented method.

The partner audit firm consumed this documentation as the entry point to the redesigned audit cycle. The audit firm's substantive testing approach changed in response. Substantive testing of intercompany positions moved from a sample-based monthly test to a quarterly check of the auto-match controls, freeing audit hours for higher-risk areas. Substantive testing of FX translation moved from a re-performance of the translation to a controls-based test of the translation gate. The audit firm's testing approach compressed because the controls being tested were better designed.

For the partner audit firm to consume the documentation cleanly, three conditions had to hold. First, the documentation had to be complete enough that the audit firm could re-perform the close steps independently. Second, the documentation had to be specific enough that the audit firm could trace any consolidation adjustment back to the underlying entity-level transaction. Third, the documentation had to address the partner audit firm's previous-cycle questions proactively. All three conditions were met across the close-and-audit cycle.

What this means for similar groups

The 18-to-9 transformation is replicable for mid-cap multi-entity groups with similar complexity. The criteria for similar complexity are: between four and twelve entities consolidating, single primary ERP environment, FRS 102 or IFRS reporting framework, single functional currency for the principal trading entity, and at least one foreign currency subsidiary requiring translation.

Below this complexity, a 9-day close may already be achievable through optimisation rather than transformation. Above this complexity, the bridging-stage decisions still apply but the calendar compression may stop at the 11 or 12-day mark rather than 9 days, because the additional entities introduce additional reconciliation events that do not compress to zero.

The criteria for whether transformation is worth the engagement cost are three. First, is the close cycle producing rework in the middle of the close, rather than running as a clean sequence? Second, is the audit cycle following the close asking the same questions every year? Third, is the group reporting team running at capacity that leaves no headroom for new transitions like IFRS 18 or Provision 29? If two of these three conditions hold, transformation is justified. If all three hold, transformation is the highest-leverage finance investment the group can make in the period.

What Atlas Verum produces for a group reporting transformation

Atlas Verum delivers group reporting transformation as a programme under Module 3 (Group Reporting & Consolidation). The standard scope:

A process map for each in-scope entity and the consolidation. Intercompany auto-match design and method statement. FX translation gate procedure. Elimination method statement and ownership model. Board pack assembly specification. Prior-year audit handover integration template. Method statements for each substantive control point. Partner audit firm handoff pack for the next audit cycle.

Engagement structures are typically full programmes scoped to the entity count, ERP complexity and audit cycle alignment. Duration and commercials are shared after a discovery call.

The audit cycle compression that follows the transformation is delivered by the entity's partner audit firm under the standard audit engagement letter. Atlas Verum coordinates the handover and supports the audit cycle from the client side. Two contracts, two scopes, aligned outcome.

What comes next

Article 4 in this series will cover the IFRS 18 transition, effective 1 January 2027, with 2026 comparatives required. The same four-stage protocol applies to a transition that touches the chart of accounts, the income statement presentation, the MPM disclosure framework, and the cash flow classification. Article 5 will cover the AuditEngine architecture and how 34 specialised agents produce 47 audit-ready workpaper templates with 82% prep reduction at deliverable quality.

For now, the takeaway. The 18-to-9 close transformation is a verified output of a disciplined design programme. The compression came from removing rework, not from working harder. The bridging-stage decisions are what produced the compression, and the documentation produced at inspection standard is what allowed the audit cycle to compress in parallel. Groups of similar complexity have 18 months of operating cycles in which to land a similar transformation cleanly, with the same critical-analysis protocol available as a starting point.

Atlas Verum Limited · Company No. 17203202 · 71–75 Shelton Street, Covent Garden, London WC2H 9JQ · DK@AtlasVerum.co.uk · AtlasVerum.co.uk

Field Notes · Atlas Verum thought-leadership programme · Audit opinions delivered by Atlas Verum's trusted UK partner audit firm network.