AbenAudit / Group internal audit across several legal entities
Topic · Group audits
Group internal audit across several legal entities
One plan per company, local approvals before the group, findings that belong to one company, and a report version for each company, with records kept apart between entities.
A group's internal audit function works across several legal entities at once. Each company needs its own plan, approvals and report, and the group needs one view across all of them. Records also have to stay inside the company they belong to. AbenAudit is built around that structure.
What makes group audit different
A single-entity audit tool assumes one plan, one approval chain and one audience for each report. In a group that breaks down quickly:
- Each subsidiary approves its own annual plan before any group body sees it.
- An engagement may cover several companies. Each finding belongs to one of them.
- Each company receives a report about itself, while the group report holds the overall conclusion.
- A subsidiary's people must not see another subsidiary's records, not even that they exist.
- Group audit leadership and the audit committee need the whole picture: coverage, open findings and overdue actions per company.
Legal entities and who reaches what
In AbenAudit, staff roles are given per legal entity. Roles come from Microsoft Entra ID app roles at each sign-in. There is no separate role administration screen to keep in sync.
| Role | Reach |
|---|---|
| Audit director | Every entity, read and write |
| Supervisory body member | Every entity, reads; records approvals |
| Audit manager, lead auditor, auditor | Their own entity |
| Consolidator | Every entity, read-only: for group reporting and exports |
| Auditee | Only the records that name them |
| Administrator | Runs the deployment; reads no audit content |
Separation you can demonstrate. When someone opens another entity's record, by link or by typing its address, they get exactly the same answer as for a record that does not exist. Lists, counts and exports leave such records out. A built-in Assurance page shows this side by side: it asks for a foreign record and a non-existent one and compares the two responses byte for byte.
Planning across the group
- One planning cycle per legal entity, provisioned from the group's structure.
- Level of execution on each engagement: Group, Local, Local-aligned (parallel in several entities) or One-man show. Each level has a default hour budget, and the defaults are configurable.
- Need against capacity per entity and per level. Resource pools can belong to one entity or to the whole group, for example a pool of group experts.
- Local approval first. The plan goes to local review, then the operating company records its own decision and date. After that it routes to the group committee or an alternate governance body, then to the supervisory body, whose members each record their approval.
- The approved plan is frozen. It shows who approved it and when, with a SHA-256 fingerprint of the approved list. Engagements opened, changed or removed after approval are listed separately.
Fieldwork and findings on a group engagement
- Team members can come from other entities of the group.
- Each finding records which company it is about. Its criteria, condition, cause and effect are separate fields, and its residual risk comes from the risk matrix in force.
- Evidence sheets gather the findings of one problem for one company and risk type. Each sheet is reviewed and approved as a unit, and its findings are frozen while it is in review.
Reporting: one engagement, a version per company
When an engagement covers more than one company, the live report can be read for a single company. A local version is prepared for each company and approved by a named local approver, normally that company's audit manager. It leaves out the group conclusion and the other companies' findings, and it is filed under the engagement's report versions.
Follow-up and group oversight
- Actions are tracked per finding with a responsible owner. The original deadline is written once. Extensions need an approver and a reason, and reminders and escalation run on a working-day calendar.
- A monthly evaluation and closing cycle is built in, and the closing note can differ per entity.
- The coverage overlay shows, across the group's location and process trees, the last concluded audit, open findings, overdue actions and the worst residual risk for each node. It also shows the areas nobody has audited yet. The trees download as CSV or Excel.
- Every step, approval and refused access is written to a hash-chained ledger that the director and the supervisory body can verify and export.
Not there yet
We would rather you hear this from us than find it in a pilot. The following group-audit items are on the roadmap:
| Item | Status |
|---|---|
| One programme view that groups parallel (local-aligned) engagements | Planned |
| An accountable audit manager seat, required on group engagements | Planned |
| Mapping of managerial levels between subsidiaries and the group | Planned |
| Each company's auditee comments only on their part of the 1st draft | Planned |
| Per-country report and mail templates; screen language choice (the interface is English today) | Planned |
| Audit universe with scoring and ranking (today: coverage across the group's structure) | Planned |
| Company-specific executive summary and branding on the local report version | Partly available |
Source: AbenAudit user manual, verified against the product in November 2026. Demo deployment, fictional companies, synthetic data.
AbenAudit
See it
running.
A demo on a laptop, without touching your systems. Demo deployment, fictional companies, synthetic data.