What Is a Group Audit and How Does It Work?

A group audit is the coordinated audit of consolidated financial statements that combine a parent company with its subsidiaries, divisions, and branches into a single economic entity. One audit team, led by a group engagement partner, plans the whole engagement, decides how much testing each business unit needs, directs local auditors who perform much of that testing, and issues a single opinion covering everything. The partner who signs that opinion is fully accountable for the entire engagement, even when dozens of separate firms across different countries performed the underlying work.

The point of the exercise is to give investors and lenders one audited number for a business that may operate in twenty jurisdictions under a dozen local accounting regimes. No single local audit would catch a misstatement that only shows up once every subsidiary is rolled up. The group audit is how that gap gets closed.

Who Does What

The group is the whole structure being audited: parent plus every subsidiary, division, or branch whose numbers flow into the consolidated statements. Each of those units is a component. A component can be a foreign subsidiary, a joint venture, a standalone division, or a shared service center that handles accounting for several units at once.

At the top sits the group engagement team, usually based at the parent’s headquarters. It plans the overall audit, decides which components need what level of testing, and issues the opinion on the consolidated financials. The group engagement partner leads that team and signs the report. That signature carries full accountability for the quality of the entire engagement, including work performed by others.

A component auditor performs procedures on the financial information of an individual component. Component auditors may belong to the same international firm network as the group team, or they may be entirely separate local firms. When the component auditor is an unaffiliated firm, the group team’s oversight obligations intensify. It has to verify the component auditor’s independence, confirm familiarity with the group’s reporting framework, and set up clear communication protocols before fieldwork begins.

The Standards That Govern the Process

Two standard-setters shape how group audits work in practice, and which one applies depends on where the company reports.

ISA 600 (Revised) for International Audits

The International Auditing and Assurance Standards Board’s ISA 600 (Revised) is effective for audits of periods beginning on or after December 15, 2023. It sets four core objectives for the group auditor: decide at the outset whether enough evidence can reasonably be obtained; identify and assess risks of material misstatement in the group financials; stay sufficiently involved in component auditors’ work throughout the engagement; and evaluate whether the evidence gathered supports the final opinion. The revised standard puts particular weight on two-way communication with component auditors and tightens documentation requirements.

The most consequential change in the revision is the removal of the old “significant component” classification. The previous version sorted components largely by financial size, and teams sometimes under-audited a small subsidiary in a high-risk jurisdiction because it fell below a size threshold. The revised standard replaces that approach with a risk-based model that evaluates each component on the specific risks it poses to the group financial statements, regardless of size.

PCAOB Standards for U.S. Public Companies

For companies registered with the SEC, Public Company Accounting Oversight Board standards apply. AS 1201 establishes that the engagement partner “is responsible for the engagement and its performance,” including supervision of all team members, even those outside the partner’s firm. Delegating supervisory tasks does not reduce the partner’s own responsibility. AS 1201 requires the partner to review enough documentation to confirm that the engagement was performed as planned, that significant judgments were appropriate, that conclusions are supported by sufficient evidence, and that required communications have been made.

When the group engagement partner wants to divide responsibility with another firm rather than assume full responsibility for its work, AS 1206 sets the conditions. The referred-to auditor must provide written confirmation of its independence under PCAOB and SEC rules, confirm it holds the proper license, and represent that it performed its audit in accordance with PCAOB standards. If the referred-to auditor played a substantial role in preparing the lead auditor’s report, it must also be registered with the PCAOB.

Scoping Components and Setting Materiality

Not every component gets the same level of attention. The group engagement team evaluates each one and assigns a scope of work based on the risk it poses to the consolidated financials.

Components representing a large share of the group’s revenue, assets, or other key metrics typically receive a full-scope audit using an assigned component materiality. Many teams aim for their fully audited components to cover roughly 80 percent or more of a key group metric such as total assets or revenue. That figure is a widely followed practice benchmark rather than a number mandated by any auditing standard, and the actual coverage target depends on the group’s risk profile.

A component can also warrant full-scope or targeted testing because of its risk characteristics rather than its size. A small subsidiary operating in a country with weak rule of law, a newly acquired business unit still being integrated, or a component involved in complex related-party transactions can all pose outsized risks to the consolidated financials. Under the revised ISA 600 framework, this risk-based lens is the primary driver of scoping decisions.

Components that fall outside a full-scope audit may still receive targeted procedures on specific balances or transaction classes, particularly intercompany balances, unusual revenue streams, or accounts where the group team has flagged elevated risk. The remaining components, those with low individual risk and minimal contribution to the group’s numbers, may only need analytical procedures at the group level.

Materiality is the threshold below which a misstatement is unlikely to influence an investor’s decision. The group team sets group materiality by applying a percentage to a financial benchmark from the consolidated statements. No standard prescribes a single formula, so the choice is judgmental. Common benchmarks include pre-tax income (often around 3 to 10 percent, with listed companies typically at the lower end of that range), total revenue, total assets, and total equity. The team picks whichever metric best reflects what users of the financial statements care about most.

Group materiality then cascades down to individual components as component materiality, which must be set lower than the group-level figure. If every component could tolerate misstatements up to the full group threshold, combined errors could easily blow past the group limit. Component materiality does not have to be a simple arithmetic slice, and the sum of all component materiality amounts is allowed to exceed group materiality. The group team uses professional judgment, often aided by probabilistic models, to set each component’s threshold at a level that keeps the overall risk of the consolidated statements being materially misstated acceptably low.

The Instruction Package and Component Fieldwork

Once scoping is settled, the group engagement team sends each component auditor a formal instruction package. This document is the operational backbone of the engagement. It spells out the component materiality threshold, reporting deadlines, the financial reporting framework the component must follow (such as US GAAP or IFRS), and the format for reporting findings back to the group team.

The instructions also communicate the component auditor’s responsibilities and applicable ethical requirements, flag specific risks the group team has identified, describe related-party relationships relevant to the component, and note any conditions that could raise doubt about the group’s ability to continue as a going concern. The group team requests written confirmation that the component auditor will cooperate throughout the engagement and communicate promptly when issues arise. Where the component’s local statements use a different reporting framework than the group’s consolidated statements, the instruction package clarifies who audits the conversion adjustments.

The component auditor then performs risk assessment, tests controls, and substantively tests account balances in line with the assigned scope and component materiality. Depth of work ranges from a full financial statement audit down to targeted procedures on specific accounts.

Every misstatement the component auditor identifies, even one below component materiality, gets documented and communicated upward. A misstatement that looks trivial at the local level can combine with similar errors at other components to breach the group threshold. The component auditor also reports anything that could affect the consolidated statements more broadly: noncompliance with local laws, fraud indicators, or going-concern issues at the component.

The final deliverable is a formal reporting package transmitted by the deadline. It includes a summary of work performed, a schedule of all identified misstatements (corrected and uncorrected), and an assessment of the component’s internal controls.

Assuming Responsibility vs. Making Reference

When another firm audits a component, the group engagement partner faces a choice that directly affects the final report: assume responsibility for that firm’s work, or make reference to it.

Assuming responsibility means the partner treats the component auditor’s work as if the group team had performed it. The final report makes no mention of another auditor. To take this position, the partner must be satisfied with the other firm’s independence, professional reputation, and audit quality. The partner typically reviews the component auditor’s key working papers, discusses significant findings, and performs whatever additional procedures are needed to gain comfort. Most large multinational audits follow this model, especially when the component auditor belongs to the same international firm network.

Making reference means the group engagement partner’s report explicitly states that part of the audit was performed by another firm and indicates the portion of the financial statements that firm covered. Under PCAOB standards, this is not a qualification of the opinion; it is a disclosure of divided responsibility. The referred-to auditor must confirm independence, proper licensing, and compliance with PCAOB standards, and must be PCAOB-registered if it played a substantial role.

If the group engagement partner can neither assume responsibility nor satisfy the conditions for making reference, the only options are a qualified opinion or a disclaimer of opinion on the consolidated financial statements.

Pulling It Together Into One Opinion

Once the component reporting packages arrive, the group engagement team reviews each one for quality and compliance with the original instructions. It aggregates every reported misstatement from every component, corrected and uncorrected, and compares the total against group materiality. If the combined uncorrected misstatements exceed the group threshold or come close, the team must decide whether to push for corrections or modify the opinion.

The team also performs its own procedures on the consolidation process itself. That means testing whether intercompany transactions and balances have been properly eliminated, verifying that consolidation adjustments are accurate, and confirming the statements present the group as a single economic entity. Intercompany discrepancies that survive elimination can distort the consolidated numbers enough to trigger a modified opinion.

The group engagement partner then forms and issues the final opinion, covering the group team’s own work, every component auditor’s work, and the consolidation process. If access restrictions prevented the team from obtaining sufficient evidence about a component, that gap does not disappear. The partner must consider whether it constitutes a scope limitation that would produce a qualified opinion or a disclaimer. Restrictions on access do not eliminate the requirement to obtain sufficient appropriate audit evidence.

When Something Breaks at a Component

The group engagement partner’s accountability means component-level problems cascade upward. If a component auditor discovers fraud, the group team has to evaluate whether the fraud could affect other components or the consolidated statements. If a jurisdiction restricts the team’s access to audit documentation, workarounds like remote reviews, on-site visits, or detailed memoranda from the component auditor may bridge the gap. When they don’t, the result is a potential scope limitation on the group audit.

If a component auditor’s work turns out to be substandard after the package arrives, the group team cannot accept it and move on. AS 1201 requires the engagement partner to determine that the work supports the conclusions reached. If it doesn’t, the team must either perform additional procedures itself or direct the component auditor to redo the work. The partner’s signature on the final report vouches for the entire engagement, and no amount of delegation changes that.