Group Audits: Which Entities in Your Structure Get Tested

Table of Contents

What Makes an Audit a Group Audit

Group audit requirements apply to any audit of financial statements that include more than one entity or business unit through a consolidation process. That is the whole test. There’s no size gate, no entity count gate, and no requirement that a second firm be involved. A parent with one wholly owned subsidiary is already a group, and indinero’s CPA-led team usually has that conversation with a controller long before the auditor does.

SAS No. 149, Special Considerations, Audits of Group Financial Statements (Including the Work of Component Auditors and Audits of Referred-to Auditors), defines the consolidation process broadly. It reaches past consolidated statements prepared under the applicable financial reporting framework to cover combined financial statements and the aggregation of financial information of entities or business units such as branches or divisions. The AICPA publishes the full standard for anyone who wants the source text.

The Journal of Accountancy made the practical point in a piece titled “The scoop on group audits: You may have them, even though you think you don’t,” noting that the standard applies even with a single engagement team, and that the same personnel often function as both the group engagement team and a component audit team. One firm doing all the work is still a group audit. The scoping memo and the component materiality mechanics still apply.

Structures that are already group audits and routinely surprise the finance team:

  • A parent with exactly one subsidiary, including a single-member LLC.
  • A holdco over an opco, even when the holdco has no operations of its own.
  • Combined statements of commonly controlled entities, where there is no parent at all.
  • Divisions, branches, or geographic locations that keep their own ledgers and report separately.
  • Equity method investments and joint ventures, which AICPA group audit guidance names as components.
  • A dental or veterinary support organization over practice entities. The DSO structure is a group audit from the first practice acquisition.
  • A real estate owner running one LLC per property.

What is not a component: certificates of deposit and other cash held at financial institutions, inventory, and an employee stock ownership plan’s shares. A single legal entity running departments on one general ledger isn’t a group either. For the structural mechanics underneath, start with the multi-entity accounting guide.

What Counts as a Component Under SAS 149

Under the extant standard, a component was tied to the entities that group or component management prepares financial information for. Under SAS No. 149, a component is an entity, business unit, function, or business activity, or some combination of those, determined by the group auditor for the purpose of planning and performing audit procedures.

The subject of that sentence changed, and that’s worth reading twice. The auditor now decides what the components are, and a component doesn’t have to be a separate legal entity. A revenue process run centrally across five entities can be one component. A shared services function can be another. Your legal entity list is an input to that decision, not the answer to it.

One clarification saves a lot of wasted anxiety. SAS No. 149 is an auditing standard from the AICPA Auditing Standards Board, effective for audits of group financial statements for periods ending on or after December 15, 2026. It supersedes SAS No. 122, as amended, section 600, and carries the AU-C section 600 designation. It does not change GAAP and it does not change which entities consolidate. ASC 810 still governs that, under the voting interest model or the primary beneficiary analysis for a variable interest entity.

How the Auditor Decides Where to Do the Work

Entity size no longer drives scope. Under SAS 149 group audits, the group engagement partner scopes audit work to the assessed risks of material misstatement affecting the group financial statements.

The Journal of Accountancy described it as a standard that shifts the auditor’s approach to determining where to perform audit work away from identifying significant components and toward professional judgment based on assessed risk. That’s a change in outcome, not a relabeling. Under the old model, a controller could predict scope from a materiality table. Under the new one, a $3 million subsidiary holding the group’s only foreign currency exposure, or all of the capitalized software, or a newly acquired opening balance sheet, can be in scope while a $40 million distribution entity on the same centralized system as the parent is not.

Timing matters more than most groups expect. A group with a December 31, 2026 year end is in the first year under SAS No. 149, and that audit gets fieldworked in early 2027. A June 30, 2026 year end is not, because the period ended before December 15, 2026. Some firms are applying the standard ahead of the effective date, so ask yours directly.

What to expect at planning: a scoping memo, a named list of in-scope components, component performance materiality figures, and requests for entity-level detail on entities your team had written off as immaterial.

Component Materiality and Aggregation Risk

Component performance materiality is set below group performance materiality, and that’s deliberate. SAS No. 149 recognizes aggregation risk, the probability that uncorrected and undetected misstatements in aggregate exceed materiality for the group financial statements as a whole. The auditor isn’t saying your subsidiary is riskier than the group. The auditor is saying five separately immaterial errors across five entities add up to one material error at the top.

The Journal of Accountancy’s guidance on allocating materiality to components names the factors that push component materiality down: diverse product lines, decentralized systems, differing jurisdictions, dissimilar risks across components, and overall group complexity. Centralized systems used uniformly and similar risks across subsidiaries push it back up. Component materiality doesn’t have to be an arithmetic allocation of group materiality either, so the sum of the component figures can legitimately exceed the group number. That surprises controllers in planning meetings. It isn’t an error.

Component Auditor vs Referred-to Auditor

This distinction is new terminology in SAS No. 149, and it determines who signs what.

A component auditor is part of the engagement team for the group audit. The group engagement partner directs, supervises, and reviews that work, and the group auditor assumes responsibility for it. The group financial statements get one opinion from one firm.

A referred-to auditor audits a component’s financial statements, and the group engagement partner decides to reference that audit in the report on the group financial statements. A referred-to auditor isn’t part of the engagement team and isn’t directed, supervised, or reviewed by the group engagement partner. The group auditor’s report references that audit instead of assuming responsibility for that portion. The group engagement partner still determines whether the referred-to auditor followed GAAS or PCAOB standards, and reads the component’s statements and report for significant matters.

In practice the trigger is relationship history or jurisdiction. A joint venture with its own long-standing auditor, a minority-held subsidiary whose other investors picked the firm, or a foreign subsidiary audited locally. One note for anyone who turns up PCAOB material while researching this. If the group includes an SEC issuer, PCAOB standards govern instead of GAAS. For a private group, SAS No. 149 does.

Access is a scoping question too. Before accepting a group audit, the group engagement partner determines whether sufficient appropriate audit evidence can reasonably be expected to be obtained. If your group can’t deliver access to a joint venture’s records or a local component auditor’s files, that conversation belongs before the engagement letter is signed.

When a Subsidiary Needs Its Own Audit

Does each subsidiary need its own audit? In the United States, no. There is no federal statute and no general state corporate statute that requires a private US company, parent or subsidiary, to obtain an audit because it crossed a revenue, asset, or headcount line.

That answer matters because the search results for this question are dominated by foreign law. The United Kingdom does work on thresholds. Under the Companies Act regime, for accounting periods beginning on or after 6 April 2025, a company can take audit exemption if it meets at least two of three tests on turnover, balance sheet total, and average employees, with separate aggregate tests for small groups. None of that applies to a US GAAS audit. A controller who finds a turnover threshold in a search result has found UK company law.

Five things actually force a separate US subsidiary audit, and none of them is the group auditor’s call.

  1. A credit agreement. The covenant names a borrower entity. If the borrower is the operating company rather than the holding company, the lender may require audited statements at the opco level regardless of what the group reports.
  2. An investor, shareholder, or LLC operating agreement. Subsidiary-level audit rights are common wherever a noncontrolling investor sits in that specific entity.
  3. A US regulator with its own threshold. Under 2 CFR 200.501, a non-federal entity that expends $1,000,000 or more in federal awards during its fiscal year must have a single audit. That threshold rose from $750,000 and applies to fiscal years beginning on or after October 1, 2024. A large employee benefit plan separately requires an audit attached to its Form 5500, and state charity, insurance, and banking regulators each set their own.
  4. A foreign jurisdiction where a subsidiary is incorporated. A UK, German, or Japanese subsidiary can carry a local statutory audit obligation with its own deadline, unrelated to the US group audit.
  5. A transaction. A buyer in diligence, an acquisition lender, or an SEC filing requirement for acquired-business financial statements.

Here’s the distinction that trips up almost every first group audit. When the group auditor scopes an entity in for group audit procedures, that entity does not get its own audit report. It gets tested as part of the group engagement. In scope for group procedures and needs a standalone opinion are different outcomes with different costs. The one exception is the referred-to auditor arrangement, where reference can only be made to an audit that actually exists under GAAS or PCAOB standards. Whether your group needs an audit at all, rather than a review or a compilation, is covered in audit vs review vs compilation.

What the Group Auditor Asks the Group to Produce

An audit of consolidated financial statements adds a group layer of requests on top of the single-entity list your team already knows. The single-entity audit readiness checklist covers the baseline. Everything below sits on top of it, and it’s what determines whether a first group audit runs on schedule.

  1. The entity register. Legal name, EIN, jurisdiction of formation, fiscal year end, ownership percentage, the control basis under ASC 810, the date control was obtained or lost, and the resulting treatment. Consolidate, equity method, cost, or combine under common control. Expect the auditor to reconcile this register against the cap table, the org chart, the consolidated tax return group, and counsel’s legal entity list. Entities that appear in one of those four and not the others are where findings come from. FASB’s consolidation amendments are the reference behind the variable interest column.
  2. Entity-level trial balances that tie to the consolidation. One per reporting entity, as of the same date, mapped into the group chart of accounts, with a documented mapping file wherever a local chart differs. The classic failure is arithmetic. The sum of the entity trial balances doesn’t equal the pre-elimination consolidated column, and nobody can say why.
  3. An intercompany matrix agreed by both sides. Every intercompany receivable, payable, loan, interest accrual, management fee, royalty, and cost allocation, with both entities agreeing the balance before the schedule reaches the auditor. Out-of-balance intercompany is the most common group audit finding and the easiest to prevent. The mechanics are in intercompany eliminations explained.
  4. Elimination entries with support attached. Each entry nets to zero across the affected entities, traces back to the agreed intercompany balance, sits in the correct period, and hits the correct consolidated line. Separate the recurring eliminations from the one-off ones and name the preparer and reviewer on each.
  5. A consolidation schedule a second person can re-perform. A column per entity, an elimination column, a consolidated column, every figure traceable to a source, formulas intact, no hardcoded plugs. If one person is the only human who can reproduce the file, expect a control deficiency conversation on top of the scoping one. The sequence itself lives in the multi-entity consolidation process.
  6. Consistent accounting policies across every entity. Revenue recognition, capitalization thresholds, depreciation lives, lease policy under ASC 842, stock compensation under ASC 718, allowance methodology. Where an entity applies something different, the group needs a documented conforming adjustment, not a verbal explanation during fieldwork.
  7. The related party inventory. AU-C 550 requires the auditor to test the completeness and accuracy of the related party relationships and transactions the entity identified. In a group, that population is wider than the consolidation group. It includes commonly controlled entities that don’t consolidate, owner-affiliated entities, leases with an owner-owned real estate LLC, and management companies. See related party transactions disclosure.
  8. Group-level balances no single entity owns. The noncontrolling interest rollforward, foreign currency translation adjustment support, the consolidated equity rollforward, goodwill and acquired intangibles, and a consolidated cash flow statement built from consolidated movements rather than summed entity cash flows.
  9. Component auditor logistics, where they apply. Independence confirmations, the group instruction package, component reporting deadlines set ahead of the group report date, and a plan for subsequent events between a component report date and the group report date.

What slips, in order of frequency: intercompany agreement between entities, entity-level trial balances that don’t tie, opening balances for an entity formed or acquired mid-year, and component auditor turnaround. Scoping starts before year end. Intercompany gets locked inside the normal close window, not reconstructed in March.

Common Pitfalls

Most group audit damage happens in planning, months before anyone opens a workpaper. These are the ones that cost real money.

  1. Reading “we only use one audit firm” as “we don’t have a group audit.” The standard applies to the financial statements, not to the number of firms engaged.
  2. Predicting scope from entity size. Assessed risk drives it now, so a small entity carrying a risky balance can be in scope while a larger low-risk one isn’t.
  3. Confusing in scope for group procedures with needs its own opinion. Different outcomes, different costs, and the confusion usually surfaces after the budget is set.
  4. Importing UK or international rules found in a search. Companies Act thresholds and ISA 600 material are not US GAAS.
  5. Letting intercompany drift all year, then reconciling once at year end, from the parent’s side only.
  6. A consolidation spreadsheet with hardcoded plugs, broken links, and a single owner who happens to be on vacation during fieldwork.
  7. An incomplete related party inventory, especially owner-affiliated entities sitting entirely outside the consolidation group.
  8. A dormant or newly formed entity nobody mapped. Shells created for a state registration or an acquisition show up in the legal entity list and nowhere in the ledger. They still need a line on the entity register with an explanation.
  9. Discovering a timing problem after planning closes. A component year end that doesn’t match the group’s, or a joint venture auditor who turns out to be a referred-to auditor, both land too late to fix cheaply.
  10. Telling the auditor about a mid-year acquisition at fieldwork. Opening balance sheets, purchase accounting, and a new entity’s control basis belong in the planning conversation. The work behind that is post-acquisition accounting integration.

Nearly all of these are bookkeeping-discipline failures wearing an audit costume. Indinero’s accounting team is CPA-led and GAAP-first, which is the difference between a consolidation an auditor can test and a due-to/from balance nobody in the building can explain.

How Indinero Prepares a Group for Audit

Indinero prepares the group and works alongside the auditor. We don’t issue the opinion, and no outsourced accounting provider should. That independence boundary is worth stating plainly before anything else.

Multi-entity consolidation is in scope for the same engagement as the bookkeeping, the tax work, and the CFO advisory. What the engagement builds before the auditor arrives:

  • An entity register with the ASC 810 control basis documented per entity, kept current as entities are formed, acquired, or dissolved rather than reconstructed from counsel’s files in February.
  • Entity-level trial balances on one group chart of accounts, so consolidation is an assembly step instead of a reconstruction.
  • A standing intercompany agreement step inside the monthly close, with both sides signing off, so year-end intercompany is already agreed.
  • Elimination entries with support attached when they’re posted, not retrofitted when the request list arrives.
  • A consolidation workpaper a second person can re-perform, with preparer and reviewer evidence on the file.
  • One written group accounting policy every entity follows, with conforming adjustments documented where an entity can’t.
  • A maintained related party inventory that includes commonly controlled entities outside the consolidation.

The bundled structure matters here in a specific way. You’re not just preparing books for an auditor. The entity register that drives the consolidation is the same list that drives the state nexus footprint, the partnership and corporate return group, and the management fee documentation. One team working one entity list produces an audit package and a tax package that agree, which is the first reconciliation an auditor asks for. When the accounting firm and the tax firm are different firms, that list quietly forks. For the systems side, see multi-entity accounting software.

Continuous operations since 2009. SOC 2 compliant (2026). Prior-year books maintained by the same team that closed them, which is what audit defensibility looks like in practice.

A first group audit isn’t harder than a single-entity audit. It’s a different question, asked of a list most finance teams have never had to defend. If your entity register lives in three places and agrees in none of them, it might be time for a different approach. Reach out for a free consultation through our accounting services team. We’d love to learn how your entities are structured.

Frequently asked questions

These are the questions controllers and VPs of Finance ask most often heading into a first consolidated audit. Scope, cost drivers, foreign subsidiaries, and what SAS 149 actually changes for the company being audited. Short answers, with the standard named where one applies.

Can two different firms audit different entities in the same group?

Yes, different firms can audit different entities in a group, and SAS No. 149 sorts those firms into component auditors and referred-to auditors. A component auditor works inside the group engagement team, directed, supervised, and reviewed by the group engagement partner, who assumes responsibility for that work. A referred-to auditor stays outside the engagement team, and the group auditor’s report references that audit instead of assuming responsibility for it. Access to the other firm’s files is a planning-stage question, not a fieldwork one.

Does a foreign subsidiary’s local statutory audit count toward the group audit?

Not automatically, because the group engagement partner decides whether a foreign subsidiary’s local statutory audit can be used and under what supervision. A local audit run under another jurisdiction’s standards is not work performed under GAAS for the group. If the local firm joins the engagement team, it becomes a component auditor and the group partner directs and reviews that work. If the group auditor instead references the local audit in the group report, that firm is a referred-to auditor.

How much more does a group audit cost than a single-entity audit?

There’s no reliable multiplier, because group audit fees track the number of in-scope components and how much work sits outside the parent’s ledger. The drivers your auditor prices against are the count of components scoped in, whether separate component auditors are involved, travel, the quality of your consolidation workpapers, and whether this is a first-year or a recurring engagement. Clean entity-level trial balances and agreed intercompany balances move the number more than entity count does, which is where indinero’s CPA-led team spends the year.

What changes for a company being audited under SAS 149?

Your auditor’s scoping changes, not your accounting, because SAS No. 149 is an auditing standard rather than a change to GAAP. The standard is effective for audits of group financial statements for periods ending on or after December 15, 2026, and it supersedes SAS No. 122 section 600. The significant component model is gone, replaced by scoping driven by assessed risks of material misstatement. Expect a scoping memo, a named component list, and component performance materiality figures at planning.

Can an entity we report under the equity method be part of the audit scope?

Yes, equity method investments and joint ventures can sit in group audit scope, because AICPA group audit guidance names them as components. Being in scope for group procedures is not the same as the investee getting its own audit report. Access is the practical problem. Before accepting the engagement, the group engagement partner determines whether sufficient appropriate audit evidence can reasonably be obtained, so raise a joint venture you can’t get records from during planning rather than during fieldwork.

Do lenders ever ask for audited statements on one entity instead of the group?

Yes, and it’s common, because a credit agreement names a specific borrower entity that may be the operating company rather than the holding company. No US statute forces a private subsidiary audit on size alone. The real triggers are contractual or regulatory: a credit agreement, an investor or LLC operating agreement, a single audit under 2 CFR 200.501 once federal awards reach $1,000,000, a large employee benefit plan’s Form 5500 audit, or a foreign statutory requirement.

How early should a group start preparing for its first consolidated audit?

Start preparing for a first consolidated audit before year end, while the books are still open and the entity register can still be fixed. What slips, in order, is intercompany agreement between entities, entity-level trial balances that don’t tie to the consolidation, opening balances for an entity formed or acquired mid-year, and component auditor turnaround. Intercompany belongs inside the monthly close with both sides signing off, not reconstructed in March. Indinero’s CPA-led team keeps that register and those workpapers current year-round.

Group audit requirements apply whenever financial statements consolidate more than one entity, so a parent with a single subsidiary already has a group audit. Under SAS No. 149, effective for audits of group financial statements for periods ending on or after December 15, 2026, the group engagement partner scopes work by assessed risk rather than entity size. Indinero’s CPA-led team prepares the entity register, intercompany matrix, and consolidation workpapers the auditor tests.

Talk to an Expert

First audit with more than one entity in the group?

Indinero’s CPA-led team runs entity-level close, the eliminations, and the consolidation schedule a group auditor tests, so fieldwork starts on books that are already ready.

Talk to an Expert