Planning Group Audits, Component Auditors, and Consolidations

Group audits require the auditor to plan from the consolidated financial statements back to the components that create them. A component may be a subsidiary, division, branch, joint venture, investment, or business unit whose financial information is included in the group financial statements. The group engagement team may use component auditors, but it does not delegate responsibility for the group audit opinion.

The exam focus is practical: identify significant components, decide the work to be performed, communicate clearly with component auditors, evaluate their evidence, and test the consolidation process with enough skepticism to catch misstatements that arise between component ledgers and the final group statements.

    flowchart LR
	    A["Group financial statements"] --> B["Identify components"]
	    B --> C["Assess significance and risk"]
	    C --> D["Set component materiality and scope"]
	    D --> E["Direct and review component work"]
	    E --> F["Evaluate consolidation evidence"]

Group Engagement Responsibility

The group engagement partner is responsible for the direction, supervision, performance, and review of the group audit. Component auditors can perform procedures at local components, but the group engagement team must be involved enough to conclude that sufficient appropriate audit evidence has been obtained for the group financial statements.

That responsibility affects planning in three ways:

The group team should also understand group management’s process for collecting component financial information. Weak reporting packages, late component submissions, inconsistent account mappings, and undocumented consolidation adjustments all increase audit risk.

Identifying Significant Components

Not every component receives the same audit response. The group engagement team evaluates quantitative and qualitative factors to determine which components need extensive work.

A small component can still be significant if it creates a group-level risk. For example, a small foreign subsidiary that records a complex derivative, holds restricted cash, or has weak local oversight may require more attention than its size alone suggests.

Component Materiality

Component materiality is the threshold used to plan and perform procedures at a component. It should be lower than group materiality because uncorrected misstatements from several components can aggregate into a material group misstatement.

When setting component materiality, the group team considers:

• The component’s size relative to the group.
• The assessed risk of material misstatement at the component.
• The expected number of components contributing audit evidence.
• The nature of account balances, transactions, and disclosures at the component.
• Whether component work will be performed by the group team or a component auditor.

Component auditors need clear instructions on component materiality, clearly trivial misstatement thresholds, reporting deadlines, identified risks, required procedures, documentation expectations, and how misstatements or control deficiencies should be reported back to the group team.

Using Component Auditors

Using a component auditor does not mean accepting the local audit file without review. The group engagement team evaluates whether the component auditor is competent, independent, and able to perform the assigned procedures under the applicable standards.

The group team’s instructions should be specific enough to prevent gaps:

After the component auditor completes the work, the group engagement team evaluates whether the work performed responds to the assigned risks. That may include reviewing selected workpapers, discussing findings with the component auditor, resolving inconsistent conclusions, and performing additional procedures when the evidence is not sufficient.

Consolidation Evidence

The consolidation process is a separate audit focus. A clean component audit does not automatically make the consolidated financial statements correct because errors can arise in mapping, eliminations, foreign currency translation, ownership accounting, and disclosure preparation.

Common consolidation risks include:

The group team should test consolidation entries, reconcile component submissions to the consolidation system, evaluate management’s review controls, and investigate late or unusual manual adjustments. Consolidation testing is especially important when the entity has many components, decentralized reporting, foreign operations, or recent acquisition activity.

Exam Traps

The AUD exam often tests whether you understand who remains responsible for the audit opinion. The group engagement team may use component auditors, but the group engagement partner still owns the group audit conclusion.

Watch for answer choices that overstate reliance. A component auditor’s report, management’s consolidation worksheet, or local statutory audit does not eliminate the group team’s need to evaluate relevance, sufficiency, independence, competence, and group-level implications.

Also separate component materiality from group materiality. Component materiality is not a duplicate of group materiality; it is normally lower and tailored to the component’s risk and size.

Quick Review

• The group engagement team remains responsible for the group audit opinion.
• Significant components are identified using both size and risk.
• Component materiality is set below group materiality to reduce aggregation risk.
• Component auditors must receive clear instructions and their work must be evaluated.
• Consolidation testing covers eliminations, translations, ownership accounting, mapping, adjustments, and disclosures.

Group Audits Knowledge Quiz