Audit Readiness for EU Corporate Groups

Audit readiness for EU corporate groupsAudit readiness means the evidence behind every reported number can be produced on request, in the same form, without rebuilding it. For an EU group that comes down to four things: a documented path from source system to consolidated figure, controls that leave a trace, reconciliations that are already closed, and a single owner per data area.Statutory audits of EU groups are governed by the Audit Directive and Audit Regulation, implemented locally — in the Netherlands through the Wta and the NV COS standards the auditor works to. The auditor's request list is therefore predictable. What varies is how long it takes a finance team to answer it.Groups that struggle at year-end rarely lack controls. They lack a retrievable, consistent evidence trail: the reconciliation exists in someone's spreadsheet, the journal rationale lives in an email, the mapping from local GAAP to group policy is undocumented. Readiness is an architecture problem before it is an accounting problem.What the auditor actually asks forAcross the request lists we see at multi-entity groups, the substance clusters into six areas. Each has a predictable evidence form.

Consolidation: the entity scope, ownership percentages, and the trail from each local trial balance to the group figure

Journal entries: complete population for the period, with the ability to filter on manual, post-close, and unusual accounts

Reconciliations: balance sheet accounts reconciled to a supporting source, with ageing and cleared differences

Intercompany: matched positions per counterparty pair, with the elimination and the residual explained

Estimates and judgements: provisions, impairment, revenue cut-off — the inputs, the model, and who approved it

IT and controls: access rights, segregation of duties, change management on the systems that produce the numbers

The four failure patterns

Evidence rebuilt on request. If a reconciliation is produced only because the auditor asked, it is not a control — it is a reconstruction, and it invites more testing.

Broken lineage. A consolidated number that cannot be walked back to a source system entry forces the auditor into substantive testing at transaction level.

Unowned data areas. Where no single person owns a balance, questions bounce between entities and the request stays open for weeks.

Late scope changes. Acquisitions, liquidations and dormant entities that surface during fieldwork rather than during planning.

What continuous readiness looks likeThe target state is that year-end is a hand-over of evidence that already exists. Practically: reconciliations closed monthly with reviewer sign-off captured in the system; journal population extractable from the ledger without manual assembly; entity scope maintained as data, not as a memo; and a lineage map that lets anyone trace a group figure to its sources in a few steps.That also shortens the interim audit, which is where a well-prepared group buys the most time back.Evidence checklist by area

Entity scope list with ownership, consolidation method, and changes in the period

Trial balance per entity, in group chart of accounts, with the mapping documented

Full journal entry listing for the period, exportable with user, date, and source flag

Balance sheet reconciliations for all material accounts, signed off, with ageing of open items

Intercompany matrix per counterparty pair with differences explained above a stated threshold

Provision and estimate files: inputs, calculation, approval, and comparison to prior period

Revenue cut-off testing evidence around period end

FX rate sources and the translation method applied per entity

Access rights and segregation-of-duties report for ERP and consolidation tooling

Change log for reporting logic, mappings, and consolidation rules

Data lineage map: source system to consolidated line item

Named owner per data area, with a backup

How we would approach this

We start from the prior-year request list and management letter — they are the cheapest available diagnosis of where evidence broke down.

We map lineage for the highest-risk reporting lines first, then close the gaps where evidence is assembled manually.

We move reconciliations and sign-off into the monthly close so the year-end file is a by-product, not a project.

What does audit readiness mean for an EU corporate group?It means the evidence behind every reported figure can be produced on request, in the same form, without rebuilding it: a documented path from source system to consolidated figure, controls that leave a trace, reconciliations already closed, and a named owner per data area.When should an EU group start preparing for the statutory audit?Readiness is a continuous state rather than a year-end project. Groups that hand over cleanly maintain the reconciliation, journal and intercompany evidence monthly, so the auditor's request list is answered from existing records instead of a reconstruction exercise.Which rules govern the statutory audit of a Dutch group?The EU Audit Directive (2006/43/EC) and Audit Regulation (537/2014), implemented in the Netherlands through the Wet toezicht accountantsorganisaties (Wta), with the auditor working to the NV COS standards.Primary sources

EU Audit Regulation 537/2014 — https://eur-lex.europa.eu/eli/reg/2014/537/oj

EU Audit Directive 2006/43/EC — https://eur-lex.europa.eu/eli/dir/2006/43/oj

NBA — Dutch auditing standards (NV COS) — https://www.nba.nl/