- ClassificationCategoryCompliance / Assurance StandardDomainFinancial Services RegulationFramework FamilyOther
- Regulatory ContextTypeStandardLegal InstrumentStandardSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionNorth AmericaRegion DetailUnited StatesPublisherPublic Company Accounting Oversight Board (PCAOB)
- VersioningVersionAS 2201 (adopted 2007 as Auditing Standard No. 5; amendments effective December 15, 2026)Effective DateNovember 15, 2007 (fiscal years ending on or after); conforming amendments effective December 15, 2026Issue DateJune 12, 2007 (PCAOB Release No. 2007-005A)
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
AS 2201 is published free of charge on the PCAOB website.
Framework text is licensed by its publisher and is included only where stated above.
- PCAOB AS 2201 governs how an auditor examines and reports on a public company's internal control over financial reporting.
- The PCAOB adopted it in 2007 as Auditing Standard No. 5 and later renumbered it AS 2201.
- It binds registered public accounting firms auditing issuers subject to Section 404(b) of the Sarbanes-Oxley Act.
- Auditors use a top-down, risk-based approach, test control design and operating effectiveness, and evaluate deficiencies up to material weaknesses.
- Amendments to paragraph .09 and a new paragraph .99 are effective December 15, 2026.
Overview
PCAOB AS 2201, An Audit of Internal Control Over Financial Reporting That Is Integrated with An Audit of Financial Statements, is the standard that governs how an auditor examines and reports on a public company's internal control over financial reporting (ICFR). It establishes the requirements for planning the audit, using a top-down approach to select controls, testing their design and operating effectiveness, evaluating deficiencies, and forming an opinion on whether ICFR was effective as of the company's year end.
The Public Company Accounting Oversight Board (PCAOB) adopted the standard in 2007 as Auditing Standard No. 5 through PCAOB Release No. 2007-005A, approved by the U.S. Securities and Exchange Commission, and later renumbered it AS 2201. It binds the registered public accounting firms that audit issuers subject to Section 404(b) of the Sarbanes-Oxley Act. The PCAOB has since adopted amendments to the standard, to paragraph .09 and a new paragraph .99, that are effective on December 15, 2026 (PCAOB Release No. 2024-005, approved by the SEC in Release No. 34-100968 of August 28, 2025).
Auditors apply AS 2201 by identifying the risks of material misstatement at the financial statement and assertion level, selecting entity-level controls and the controls that address those risks, testing them, and evaluating any deficiencies as control deficiencies, significant deficiencies, or material weaknesses. Companies prepare for the audit by documenting their ICFR, typically against the COSO Internal Control framework, testing their own controls, and maintaining the evidence auditors will examine.
Why does it matter?
An integrated audit under AS 2201 is the independent test behind every public company's assertion that its financial reporting controls work. A material weakness reported under the standard is disclosed to investors, so the way controls are scoped, tested, and evidenced determines both the audit outcome and management's own Section 404(a) assessment.
Key benefits include:
- One audit, two opinions
The integrated audit achieves the objectives of the financial statement audit and the ICFR audit together, so evidence gathered for one supports the other.
- Top-down, risk-based scoping
The auditor begins at the financial statement level with the overall risks to ICFR and works down to entity-level controls and the significant accounts, disclosures, and assertions that matter, rather than testing every control.
- A shared definition of material weakness
The standard defines material weakness and significant deficiency, giving management, auditors, and audit committees the same terms for evaluating control failures.
- Clear expectations for entity-level controls
Controls over management override, the control environment, and the period-end financial reporting process are singled out as the ones that shape the rest of the audit.
- Predictable reporting
Paragraphs .85 onward set out what the auditor's report must say, including when a material weakness exists, so companies know how findings will be communicated.
How does it work?
AS 2201 is organized in numbered paragraphs. Planning the audit begins at paragraph .09 and covers the role of risk assessment, scaling the audit to the company, fraud risk, and using the work of others; the top-down approach begins at .21 and covers entity-level controls, significant accounts and disclosures and their relevant assertions, likely sources of misstatement, and the selection of controls to test; testing controls begins at .42 and covers the evidence needed to test design and operating effectiveness, the timing of tests, and the use of prior-year evidence; evaluating identified deficiencies begins at .62; wrapping up begins at .71 and covers management's written representations and communicating matters to management and the audit committee; and reporting on ICFR begins at .85. Appendix A defines the terms, Appendix B addresses special topics such as multiple locations and benchmarking automated controls, and Appendix C covers special reporting situations.
In practice the auditor obtains an understanding of the company's ICFR, identifies significant accounts and disclosures and their relevant assertions, walks through transactions to identify the points at which a misstatement could occur, and selects the controls that sufficiently address the assessed risk of misstatement for each assertion. The auditor tests the design and operating effectiveness of those controls with inquiry, observation, inspection, and reperformance, evaluates each deficiency for its severity, and issues an opinion. Management's own assessment, the work of internal audit, and the company's control documentation are inputs the auditor may use, subject to the standard's requirements on competence and objectivity.
Key Elements
- Integrated audit objective
The auditor plans and performs the ICFR audit and the financial statement audit together so that evidence and conclusions from each inform the other.
- Top-down approach
Scoping starts at the financial statement level and the overall risks to ICFR, moves to entity-level controls, and then to significant accounts, disclosures, and relevant assertions.
- Entity-level controls
Controls related to the control environment, management override, and the period-end financial reporting process are evaluated because they affect the extent of testing elsewhere.
- Testing design and operating effectiveness
Selected controls are tested to determine whether they are designed to prevent or detect material misstatements and whether they operated as designed during the period.
- Evaluation of deficiencies
Each deficiency is assessed for severity, individually and in combination, to determine whether it is a material weakness.
- Material weakness definition
A material weakness is a deficiency, or a combination of deficiencies, such that there is a reasonable possibility that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis (Appendix A, paragraph .A7).
- Reporting on ICFR
The auditor's report expresses an opinion on the effectiveness of ICFR as of the year end and describes any material weakness identified.
What does it cover?
AS 2201 applies to audits of internal control over financial reporting performed by PCAOB-registered firms for issuers whose auditors must attest to ICFR under Section 404(b) of the Sarbanes-Oxley Act. It governs the auditor's work, not management's; management's assessment is addressed by SEC rules, though companies use the standard's definitions and top-down approach to organize their own testing. Smaller reporting companies and emerging growth companies exempt from Section 404(b) are outside its reach unless they obtain an ICFR audit voluntarily.
What are its objectives?
The standard exists so that an auditor can form and report an opinion on the effectiveness of a company's internal control over financial reporting.
Integrate the audit of internal control with the audit of the financial statements so that each supports the other.
Focus audit effort on the controls that address the risk of material misstatement through a top-down, risk-based approach.
Obtain sufficient evidence about the design and operating effectiveness of selected controls.
Evaluate identified deficiencies consistently against the definitions of significant deficiency and material weakness.
Communicate deficiencies to management and the audit committee and obtain management's written representations.
Report clearly to investors on whether ICFR was effective as of the year end.
Framework in Context
AS 2201 operates within the Sarbanes-Oxley Act's Section 404 regime, in which management assesses ICFR and the auditor attests to it, and it relies on a suitable control framework such as the COSO Internal Control – Integrated Framework (2013) as the criteria for that assessment. It connects to other PCAOB standards including AS 1000 on the auditor's general responsibilities, AS 2110 on identifying and assessing risks of material misstatement, AS 2605 on using the work of internal auditors, AS 2801 on subsequent events, AS 2805 on management representations, AS 2905 on subsequent discovery of facts, and AS 4105 on reviews of interim financial information; AS 6115 governs the separate engagement of reporting on whether a previously reported material weakness continues to exist. Service organization reports under SOC 1 and ISAE 3402 supply evidence about outsourced controls, and COBIT 2019 is often used to structure the IT general controls the audit examines.
Common Framework Mappings
AS 2201 is commonly mapped to the law that requires the ICFR audit, the control framework used as its criteria, and the assurance standards that supply evidence about outsourced and IT controls.
Mapped frameworks include:
SOX
COSO IC 2013
COSO ERM 2017
SOC 1
ISAE 3402
ISAE 3000
COBIT 2019
How SmartSuite Supports PCAOB AS 2201
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
For PCAOB AS 2201, SmartSuite organizes the ICFR control library by significant account and assertion, records design and operating-effectiveness tests with evidence, and evaluates and tracks deficiencies so management's assessment and the auditor's requests draw on one record.
ICFR Control Library
Hold entity-level, process, and IT general controls with their linked accounts, assertions, and risks in one risk and control matrix.
Ownership, Cadence, and Accountability
Assign control owners and testing cycles, and route sign-offs and management representations through approval workflows.
Evidence Collection and Audit Trail
Attach walkthroughs, samples, screenshots, and reperformance results to each test with timestamps and reviewers for the external auditor.
Control Testing and Operating Effectiveness
Plan design and operating tests, record exceptions, and roll results forward across interim and year-end periods.
Risk and Third-Party Alignment
Link controls to fraud risks, SOC 1 reports from service organizations, and complementary user entity controls.
Deficiency and Audit Committee Reporting
Evaluate deficiencies individually and in aggregate, track remediation, and report status to management and the audit committee.
Related frameworks

The Sarbanes-Oxley Act of 2002 (Public Law 107-204) requires SEC-reporting companies to certify reports, assess internal control over financial reporting and use PCAOB-registered auditors.

COSO Internal Control (2013) defines five components and 17 principles of internal control. Public companies commonly use it as the ICFR framework for SOX section 404.

COSO ERM (2017) sets five components and 20 principles for integrating risk management with strategy and performance. It is voluntary guidance from COSO, not a regulation.

SOC 1 is the AICPA examination, under AT-C section 320, of a service organization's controls relevant to user entities' internal control over financial reporting, reported for user auditors.

ISAE 3402 is the IAASB standard for service auditors' reports on a service organization's controls relevant to user entities' financial reporting, from periods ending June 15, 2011.
Frequently Asked Questions For PCAOB AS 2201
AS 2201 binds PCAOB-registered public accounting firms that audit issuers whose internal control over financial reporting (ICFR) must be attested under Section 404(b) of the Sarbanes-Oxley Act. It governs the auditor's work in an audit of ICFR that is integrated with the audit of the financial statements: planning (from paragraph .09), the top-down approach (.21), testing controls (.42), evaluating deficiencies (.62), wrapping up (.71) and reporting (.85). Companies are not directly bound, but their control documentation, testing and evidence are what the auditor examines.
Under the top-down approach, which begins at paragraph .21, the auditor starts at the financial statement level with the overall risks to ICFR, evaluates entity-level controls, identifies significant accounts and disclosures and their relevant assertions, works out the likely sources of misstatement, and then selects for testing the controls that sufficiently address the assessed risk of misstatement for each assertion. Controls over the control environment, management override and the period-end financial reporting process shape the extent of testing elsewhere.
Appendix A, paragraph .A7, defines a material weakness as a deficiency, or a combination of deficiencies, in internal control over financial reporting such that there is a reasonable possibility that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis. Each deficiency identified is evaluated for severity, individually and in combination (from paragraph .62), and the auditor's report describes any material weakness that exists as of the year end (from paragraph .85).
The PCAOB adopted the standard in 2007 as Auditing Standard No. 5 through PCAOB Release No. 2007-005A, approved by the SEC, and later renumbered it AS 2201. Amendments to paragraph .09 and a new paragraph .99, adopted in PCAOB Release No. 2024-005 and approved by the SEC in Release No. 34-100968 (File No. PCAOB-2025-01, August 28, 2025), are effective on December 15, 2026; the PCAOB publishes the version effective December 15, 2025 and the version effective December 15, 2026 side by side.
No. AS 2201 governs the auditor's work; management's assessment under Section 404(a) is addressed by SEC rules, although companies use the standard's definitions and top-down approach to organize their own testing. The assessment and the audit rely on a suitable, recognized control framework as criteria, which in the United States is almost always the COSO Internal Control Integrated Framework (2013). Smaller reporting companies and emerging growth companies exempt from Section 404(b) are outside AS 2201 unless they obtain an ICFR audit voluntarily.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


