Written in September 2026 against the UK Corporate Governance Code 2024 and FRC guidance, with Provision 29 applying to financial years beginning on or after 1 January 2026. Check the current Code and guidance before acting on it.
Most preparation for Provision 29 focuses on entity-level controls. The consolidated numbers the board actually signs off are produced in the group layer - and that is where the evidence trail is thinnest. This piece sets out what group-layer controls look like and what documentation a board can point to at 31 December 2026.
What Provision 29 asks and when it applies
Provision 29 of the UK Corporate Governance Code 2024 requires the board of a company subject to the Code to make an annual declaration on the effectiveness of the group's material controls. The obligation applies to financial years beginning on or after 1 January 2026. For a standard calendar-year group, the first declaration sits in the annual report covering the year ended 31 December 2026 - published in early 2027, but the controls it describes are assessed as at 31 December 2026 itself.
The FRC and ICAEW have published guidance on what material controls means and how a board should approach the declaration. Readers should confirm the precise scope, definitions and expectations directly against the FRC's Code and that guidance rather than relying on any single commentary, including this one. What is clear is that the declaration is a board responsibility, grounded in evidence the board has seen and assessed. The FRC does not present it as a UK version of Sarbanes-Oxley, and it is best described in the FRC's own terms.
This piece was written in September 2026 against the UK Corporate Governance Code 2024 and FRC guidance current at that date.
Why the group layer is where evidence gets hard
Entity-level controls - account reconciliations, analytical review, journal authorisation at subsidiary level - attract most of the attention, and rightly so. Finance teams have been running those controls for years and they tend to leave reasonable documentation.
The problem is that the numbers the board actually approves are not the entity numbers. They are the consolidated numbers, produced in the group layer after a set of adjustments that no individual subsidiary sees in full: intercompany eliminations, consolidation journals, FX translation, structural changes from acquisitions or disposals, and whatever top-side adjustments the group team makes. Each of those steps changes the numbers. Each is therefore a point at which a material error can enter, and each needs a control that leaves evidence.
For the financial reporting controls within the declaration, the numbers that matter are the consolidated ones. The evidence base therefore has to cover the group layer as completely as it covers the entity layer.
Five group-layer controls and the evidence each one must leave
| Control area | What the control does | Evidence required |
|---|---|---|
| Intercompany matching and sign-off | Confirms that intercompany balances and transactions agree across entities before the cut-off date, with differences resolved or formally explained | Signed-off matching schedule dated before cut-off; log of differences with resolution notes; evidence that unresolved items were reviewed and approved at the appropriate level |
| Consolidation and top-side journals | Captures every journal posted in the group consolidation layer with preparer, reviewer, reason and link to source documentation | Journal register with preparer and reviewer fields completed; source documents attached or referenced; evidence of independent review separate from preparation |
| FX rates governance | Ensures that closing and average rates are sourced from an approved reference, held in one controlled location and applied consistently across all entities | Rate table with source, approval date and approver; version history showing no unauthorised changes; evidence that entities used the same approved table |
| Ownership and structure change approval | Ensures that acquisitions, disposals and restructuring steps are reflected in the consolidation only after formal approval, so the structure the consolidation uses matches the legal and accounting position approved by the board | Approved group structure document dated before the consolidation run; sign-off showing who authorised any in-year changes; reconciliation of opening to closing structure |
| Close calendar with recorded status | Tracks each step in the group close against a planned timeline and records completion or escalation in real time as the close runs | Timestamped status log for each close milestone; record of any steps completed late or overridden; evidence of escalation where required |
Taken together, these five areas cover the main points at which a group-layer error can enter without leaving a footprint at entity level. A board seeking to make a credible declaration needs to be able to show that each area has an operating control and that the control left contemporaneous evidence during the period under review.
What a spreadsheet consolidation struggles to evidence
Some groups still consolidate in spreadsheets, either because the group is structurally straightforward or because investment in a dedicated tool has not been prioritised. For Provision 29 purposes, that approach creates specific evidential problems that are worth naming plainly.
- Version control - a spreadsheet file does not natively record which version of the model produced the final numbers, or whether the file opened during an audit review is identical to the file that produced the signed-off output.
- Formula and rate changes - if someone changes an FX rate or a consolidation formula mid-close, the change is typically invisible unless the file is under external version control. There is no audit log of who changed what and when.
- Reviewer sign-off tied to the numbers - an approval email records that a reviewer saw a file at a point in time. If the spreadsheet changes after the approval email, there is no automatic link between the sign-off and the final figure.
- Completeness of intercompany eliminations - in a manually maintained model, demonstrating that every intercompany relationship has been captured and eliminated requires a separate reconciliation step, which itself needs to be controlled and evidenced.
- Close status tracking - a spreadsheet consolidation does not record the time at which each step was completed. Reconstructing a close timeline after the event is difficult and typically relies on email trails rather than system logs.
None of these problems is insurmountable with compensating controls - rigorous file-naming conventions, external version control, separate sign-off registers and manually maintained close logs can all help. The point is that each compensation adds process overhead and introduces further points at which the evidence chain can break. Groups using spreadsheet consolidations should map these gaps explicitly and decide which compensating controls are sufficient before the December 2026 close.
A practical checklist for the 31 December 2026 close
With one quarter remaining before the first declaration date, a group financial controller can use the following checklist to assess readiness. The questions are framed around evidence - because a control that operates but leaves no trace will not support a board declaration.
- Intercompany: is there a formal matching and sign-off process with a documented cut-off date, and does it produce a record that can be retrieved after the close?
- Consolidation journals: does every journal posted at the group layer have a named preparer, a named reviewer and a link to source documentation - or is the journal register maintained informally?
- FX rates: is there a single approved rate table, a record of who approved it and when, and evidence that all entities used it without local adjustment?
- Group structure: is the consolidation structure document formally approved before each close run, and is there a sign-off trail for any acquisitions, disposals or restructuring steps taken during the year?
- Close calendar: does the calendar record actual completion times and escalations, or does it only show planned dates?
- Spreadsheet risk: if the consolidation runs in spreadsheets, have compensating controls been documented and tested, and is someone responsible for maintaining the evidence trail they require?
- Board reporting: can the group finance team produce a summary of control operation across all five areas in a form the board can review and challenge - or does the evidence exist only in working files that the board has never seen?
Where to focus between now and year end
The group close is a sequence of dependent steps. The intercompany position has to be settled before eliminations can be run; the structure has to be agreed before the ownership percentage is applied; the rate table has to be locked before translation begins. That dependency chain means that a weakness early in the sequence compounds through every step that follows.
The most productive use of the remaining quarter is to run a dry-run close - or to review the September interim close - specifically looking at whether each of the five control areas produced contemporaneous evidence. Gaps identified now can be addressed in the October or November reporting cycle before the December close that matters.
AIS has covered the individual components of the group close - intercompany matching, FX governance and audit trail design - in separate pieces in this series. The underlying principle across all of them is the same: evidence has to be created at the time the control operates, because it cannot reliably be reconstructed after the board needs to sign off on it.