Most group finance teams trying to shorten the path to a board pack focus on the pack itself - templates, automation, commentary workflows. By the time the pack is being assembled, most of the days have already been spent. They were lost in the subsidiary ledgers, in unreconciled intercompany balances, in FX rates that kept changing, and in top-side journals posted after the numbers were called final. Fix the sequence upstream and the pack has stable numbers to start from.
Where the days actually go
Suppose your group close runs to ten working days and the board pack lands on day ten. Trace back through the last three or four cycles and you will often find the same pattern: consolidation did not lock until day seven or eight, commentary was written against figures that then moved, and a round of re-reviews followed. The pack was not the problem. Consolidation was not entirely the problem either. The problem was that consolidation could not lock because intercompany was still being argued, because one or two subsidiaries had submitted late or had re-opened their ledgers, and because the group FX rates were applied entity by entity rather than centrally. Each of those is a dependency. Dependencies that are unmanaged compound - a two-day delay in submissions can become a four-day delay by the time it has worked through intercompany matching and consolidation review.
Remove the first dependency first: late subsidiary submissions
The most important dependency to address is subsidiary submission timing, for a straightforward reason: every other dependency sits downstream of it. You cannot match intercompany until both sides have submitted. You cannot run a meaningful consolidation until submissions are in. A published submission calendar with hard entity cut-offs is therefore the starting point. Hard means the consolidation run happens at the cut-off regardless. Entities that miss it are carried forward at prior-month figures with a flag, or they submit an agreed estimate and true up in the following period. The group controller does not wait. This is a governance decision as much as a process one, and it typically needs CFO backing to hold the first time a significant subsidiary is the late one.
The calendar should show each entity's cut-off, the intercompany agreement deadline, the group consolidation run, the lock point, and the pack completion date. Once it is published and enforced for two or three cycles, the incentive changes: subsidiary teams know the run happens on the published day whether or not they have submitted.
Publish group FX rates before submissions are due
Group FX rates that are not locked before the submission window opens create a quiet but persistent source of rework. An entity submits in local currency on day two. The group applies rates on day four. The rates move. The entity resubmits or the group adjusts. Consolidation has to be re-run. Commentary written on day four is now wrong. The fix is simple in principle: publish one table of group closing and average rates as soon as period-end rates are available, before the submission window opens, and translate centrally at consolidation using that table only. AIS has covered the mechanics in the FX part of its Close and Consolidate series. The point here is sequencing: the rate table is an input to the submission process, so it needs to be fixed before that process starts.
Agree intercompany before the submission cut-off
Intercompany disputes found at consolidation are a consolidation problem only in the sense that consolidation is where they are discovered. They are actually a pre-submission problem. If intercompany balances are not agreed between entities before the submission cut-off, consolidation will surface the mismatch and someone will have to resolve it - often the group team, under time pressure, by posting a top-side that someone then questions the following month. The fix is to run an intercompany agreement process in the final days of the accounting period, before books close, so that both sides of each material balance are confirmed before either entity submits. The intercompany part of the Close and Consolidate series sets out the workflow. The practical implication for the timetable is that the intercompany agreement deadline sits one day before the submission cut-off, giving entities a narrow window to correct postings in their own ledgers rather than relying on the group to absorb the difference.
Establish a consolidation lock point and enforce it
Once consolidation has run on clean submissions with agreed intercompany and locked FX rates, there needs to be a defined lock point after which the consolidated numbers do not move for the current period. Any adjustment identified after the lock goes to next month or requires explicit sign-off from the group controller with a documented rationale. Without a lock point, the consolidation remains a working document, commentary cannot start from stable figures, and the pack is always written against numbers that might change. Top-side journals are the main reason lock points fail. Journals posted after the lock - to tidy up a presentation line, to move a balance between entities, to correct a classification - are often individually reasonable and collectively destructive. A short sign-off process for post-lock adjustments, with a named approver and a same-day turnaround expectation, is usually enough to discourage the habit without blocking genuine corrections.
Build the pack directly off the locked consolidation
Commentary should start on the same day the consolidation locks, against numbers that will not change. If the pack template is connected directly to the consolidation output - whether through a reporting layer or a structured extract - the financial tables populate without manual re-keying. The commentary writer is working from final figures on day six rather than provisional figures on day eight. That difference is where the time saving actually comes from. The pack gets faster because the numbers it reports on became stable earlier.
An illustrative ten-day timetable
The table below is an example of how the sequence can be structured for a UK multi-entity group. It is illustrative only - the right numbers for any group depend on entity count, ledger complexity, and the current state of intercompany discipline. Use it as a conversation starter with your subsidiary controllers.
| Working day | Activity | Owner | Gate condition |
|---|---|---|---|
| Day -2 to -1 (before period end) | Intercompany agreement process runs between entities | Subsidiary controllers | Material balances confirmed on both sides |
| Day 1 (morning) | Group closing and average FX rates published | Group finance | One rate table, published before submissions are due |
| Day 1 | Subsidiary ledgers close; any remaining intercompany differences corrected in entity ledgers | Subsidiary controllers | Intercompany agreed before submission |
| Day 2 | Subsidiary trial balances submitted to group | Subsidiary controllers | Hard cut-off; late entities flagged |
| Day 3 | Group consolidation run; intercompany eliminations applied; translation at locked rates | Group consolidation team | All submissions received or prior-month estimates applied |
| Day 4 | Consolidation review; non-controlling interests, goodwill, acquisition adjustments reviewed | Group controller | No new submissions accepted |
| Day 5 | Consolidation locked; any post-lock adjustment requires sign-off | Group controller | Lock confirmed in writing |
| Day 6 | Commentary drafting begins against locked numbers; pack template populated from consolidation output | Group FP&A | Numbers stable |
| Day 7 | First draft pack reviewed by group controller; variance commentary challenged | Group controller | No changes to underlying numbers |
| Day 8 | CFO review; narrative revised; cover page and executive summary drafted | CFO / group finance | Commentary finalised |
| Day 9 | Final pack formatted and quality-checked; supporting schedules confirmed | Group finance | Sign-off from group controller |
| Day 10 | Board pack distributed | Group finance | Distribution list confirmed in advance |
The order matters as much as the actions
None of the individual steps above is unfamiliar to an experienced group controller. The point of setting them out in sequence is that the order is not arbitrary. Fixing intercompany discipline before fixing the submission calendar wastes effort because late submissions mean intercompany cannot be agreed in time regardless. Automating the pack before locking the consolidation means automation is applied to moving figures. The dependency chain runs from intercompany agreement and the rate table, through submission timeliness and consolidation integrity, to the lock point, and only then to the pack. Work backwards along that chain, identify where it breaks in your current cycle, and start there. For most groups the first break is the submission cut-off. Fix that first, hold it for two or three cycles, and the rest of the chain tightens around it.
AIS is running a 30-minute LinkedIn Live working lunch, From Financial Close to Board Pack in 10 Days, on Thursday 29 October 2026 at 1pm GMT. Registration is listed under upcoming events on the Insights page.