An ICFR risk assessment determines which financial reporting risks matter most, which accounts and disclosures are susceptible to material misstatement, and which controls management should evaluate. For CFOs and controllers, it is the foundation of an efficient internal control over financial reporting (ICFR) program - not simply a spreadsheet exercise performed before an audit.
Poor scoping can create two costly outcomes: high-risk financial reporting areas receive insufficient attention, while teams spend time testing low-value or redundant controls. A risk-based approach helps management focus effort where an error or fraud could materially affect the financial statements, while documenting why selected controls are appropriate.
This guide explains how to scope ICFR using financial statement risks, COSO principles, account-level assertions, entity-level controls, IT dependencies, and a practical risk-control matrix (RCM). It also distinguishes management’s responsibilities from the independent auditor’s work under PCAOB AS 2201, and includes a downloadable-ready checklist format that finance teams can adapt.
What Is an ICFR Risk Assessment?
An ICFR risk assessment identifies the risks that could cause a material misstatement in external financial statements and connects those risks to controls designed to prevent or detect misstatements on a timely basis. It is typically performed using a top-down, risk-based approach, starting with the consolidated financial statements rather than an exhaustive inventory of every business process.
ICFR risk assessment vs. enterprise risk assessment
An enterprise risk assessment may cover cybersecurity, operations, strategy and legal exposure. ICFR scoping is narrower: it evaluates whether risks could materially affect financial statement recognition, measurement, presentation or disclosure. A cybersecurity incident becomes an ICFR matter, for example, when it threatens the integrity of systems or information used in financial reporting.
Who owns the assessment?
Management is responsible for establishing and evaluating ICFR. Finance leadership usually coordinates scoping with process owners, IT, internal audit and the audit committee. External auditors independently decide how to perform required financial statement or integrated-audit procedures; management should not delegate control ownership to the auditor.
For a broader overview of the ICFR framework and SOX responsibilities, read MBP Global’s Internal Control Over Financial Reporting (ICFR) Guide.
ICFR Risk Assessment Standards: SEC Guidance, COSO and PCAOB AS 2201
SEC guidance for management: top-down and risk-based
The SEC’s 2007 interpretive guidance permits management to evaluate ICFR using a top-down, risk-based approach, with the nature and extent of evidence tailored to risk. Management should identify financial reporting risks, determine whether appropriate controls address those risks, and evaluate evidence of their operation. The guidance does not require management to copy the external auditor’s testing plan.
COSO: the framework behind the assessment
The COSO Internal Control - Integrated Framework provides five connected components: control environment, risk assessment, control activities, information and communication, and monitoring. Using COSO helps management evaluate not only transaction controls but also governance, competence, information quality and oversight affecting reporting reliability.
PCAOB AS 2201: auditor scoping for integrated audits
For an auditor performing an integrated audit, PCAOB AS 2201 requires a top-down approach: identify entity-level controls; determine significant accounts, disclosures and relevant assertions; understand likely sources of misstatement; and select controls that sufficiently address the risks. The auditor need not test every control or redundant controls simply because they appear in a company inventory.
Effective-date note: The PCAOB identifies amendments to AS 2201 that become effective December 15, 2026. Engagement teams should confirm the version applicable to the audit period before finalizing procedures.
How to Scope Key Controls: A Seven-Step ICFR Risk Assessment Process
Step 1: Start with consolidated financial statements and materiality
Obtain the trial balance, consolidated financial statements, disclosures and prior-year audit findings. Establish a documented materiality reference consistent with the company’s circumstances, but do not use a single numerical threshold to exclude accounts automatically. A small balance may still be significant because of fraud risk, accounting complexity or qualitative disclosure considerations.
Consider balances and disclosures associated with revenue, receivables, debt, equity, cash flows, acquisitions, contingencies, related parties and significant estimates. Document the basis for including and excluding areas.
Step 2: Identify significant accounts and disclosures
Review both quantitative and qualitative risk factors: account size, transaction volume, susceptibility to fraud, changes since the prior period, judgment-intensive estimates, unusual arrangements, contingent liabilities and related-party activity. A revenue account with large recurring transactions may warrant a different control focus than a smaller balance involving highly complex valuation judgments.
Step 3: Map each account to relevant financial statement assertions
Relevant assertions commonly include existence or occurrence, completeness, valuation or allocation, rights and obligations, and presentation and disclosure. For each significant account, ask: “What could go wrong that would be material?” Assertions help convert broad concerns into specific prevent-or-detect control objectives.
Account / disclosure | Illustrative assertion | What could go wrong? |
Revenue | Occurrence / cut-off | Sales recorded before the related performance obligation is satisfied |
Accounts payable | Completeness | Unrecorded invoices or liabilities at period-end |
Inventory | Existence / valuation | Inventory quantities inaccurate or obsolete stock not written down |
Debt | Completeness / disclosure | Borrowings or covenants missing from financial statement disclosures |
Share-based compensation | Valuation / disclosure | Grant terms or fair-value inputs incorrectly applied |
Step 4: Understand transaction flows and key systems
Map how transactions originate, are authorized, processed, recorded, reconciled and disclosed. Identify locations where material misstatements could arise, including interfaces, spreadsheets, system-generated reports, consolidation entries and manual journal entries. Confirm whether information used by a review control is complete and accurate.
Step 5: Evaluate entity-level and fraud-related controls
Review board and audit committee oversight, ethics, reporting escalation, fraud-risk assessment, management override, journal entries and monitoring. Entity-level controls differ in precision: some only influence the control environment, while others may address a specific financial reporting assertion sufficiently to affect lower-level testing decisions.
Step 6: Select the controls that address the assessed risks
For each risk, identify controls with a clear objective, owner, frequency, procedure, evidence and follow-up mechanism. Focus on controls that together adequately address relevant assertions. Avoid over-scoping by selecting several redundant checks with no meaningful incremental risk coverage. Conversely, do not exclude necessary controls just to lower testing effort.
Step 7: Define testing, evidence and refresh triggers
Determine how management will evaluate design and operating effectiveness, using risk-appropriate inspection, reperformance, observation or inquiry corroborated by evidence. Establish refresh triggers such as new systems, acquisitions, turnover in control owners, significant accounting changes, unusual transactions and newly identified deficiencies.
How to Identify Key Controls vs. Non-Key Controls
A key control is a control selected because, individually or together with other controls, it adequately addresses a financial reporting risk that could lead to a material misstatement. “Key” is a practical scoping designation rather than a substitute for applying the relevant standards.
Selection question | In-scope implication | Example |
Does the control address a relevant assertion with material misstatement risk? | Strong reason to consider | Independent review of significant revenue estimates |
Does an entity-level control operate at sufficient precision? | May reduce need for overlapping detailed control | Detailed executive review with defined investigation thresholds |
Does the control rely on IT or a system report? | Scope relevant ITGCs and report reliability | Automated billing control using ERP permissions |
Is the control truly redundant? | Avoid testing duplication unless needed | Multiple approvals with no additional risk coverage |
Is the control limited to operational efficiency? | Usually outside ICFR unless it affects reporting | Office supply purchasing efficiency metric |
What makes a management review control precise?
A management review should specify the information reviewed, the level of disaggregation, criteria or thresholds for investigation, the reviewer’s competence, how exceptions are resolved and evidence retained. A broad monthly sign-off on financial statements may lack precision to detect a material misstatement in a particular assertion.
When should automated and IT-dependent controls be included?
Scope IT general controls when access, program changes or operations could affect relevant applications, automated controls or key reports. Also consider interfaces, end-user computing and third-party service organizations. An automated control is only as reliable as its configuration, access restrictions and data inputs.
ICFR Risk Control Matrix Template: Practical Example
A risk-control matrix documents why a financial reporting risk is in scope, which assertion it affects, which control addresses it, and how management will demonstrate operation. The following is an illustrative starter matrix; it is not a company-specific SOX compliance certification.
Process / risk | Assertion | Key control and owner | Evidence / frequency |
Revenue: premature recognition | Occurrence / cut-off | Controller reviews material contract terms and period-end revenue exceptions | Signed exception log; monthly |
Payables: unrecorded liabilities | Completeness | AP manager reviews subsequent disbursements and accrued liabilities | Review and accrual support; quarterly |
Financial close: unauthorized adjustment | Accuracy / presentation | Controller approves material manual journal entries and investigates unusual postings | Approval workflow and journal log; each event |
IT: unauthorized ERP changes | Multiple assertions | IT owner reviews privileged access and approved application changes | Access reports, tickets, approvals; scheduled |
Essential RCM columns
Process and sub-process; significant account or disclosure
Financial statement assertion and potential misstatement
Inherent risk rating and rationale
Control description, nature and type (manual / automated)
Control owner and reviewer; segregation of duties
Frequency and trigger; systems and reports relied upon
Evidence retained and location
Design assessment and operating test procedure
Deficiencies, remediation status and retest conclusion
Example: Scoping Revenue Recognition Controls for a SaaS Company
Assume a SaaS company sells annual subscriptions, usage-based contracts and professional services. Revenue is significant; contract modifications and variable consideration introduce complexity. The team identifies occurrence, completeness, accuracy and cut-off as relevant assertions. It then traces quote-to-cash workflows and determines where pricing overrides, activation dates and contract amendments could cause material reporting errors.
Potential key controls include a contract-review procedure for nonstandard terms, a monthly reconciliation between billing and the general ledger, and a review of deferred revenue and significant manual adjustments. The team also considers ITGCs for the billing platform and ERP, plus report completeness and accuracy. A generic sales-manager sign-off may not address the accounting assertions precisely enough.
The selected control set, inherent risks and test plan should be documented in the RCM. Whether a control can replace another depends on the actual level of risk coverage - not simply the existence of a review signature.
How Multiple Locations, Acquisitions and Service Providers Affect Scope
Multiple locations and business units
Start with consolidated financial statements and identify where significant risks arise. Consider whether operations, transaction systems and accounting policies vary by location. Centrally operated controls may address certain risks across the group, while unique location-level processes may require separate attention. PCAOB AS 2201 contains additional requirements for auditors evaluating multi-location operations.
New acquisitions and integrations
Assess the acquisition’s financial reporting significance, conversion entries, business combination accounting, access changes and controls at acquired entities. Some SEC transition relief may apply to management’s assessment in specified circumstances, but eligibility and disclosure requirements must be evaluated carefully rather than assumed.
Third-party systems and SOC reports
Where material processes rely on a service organization, identify relevant user-entity controls, available service-auditor reports and gaps in coverage. A SOC report does not automatically cover every reporting assertion or replace management’s responsibility for complementary user controls.
Common ICFR Scoping Mistakes That Increase Audit Risk and Cost
Selecting controls based only on account balances and ignoring qualitative or fraud risks.
Treating every control in a process narrative as a key SOX control.
Ignoring disclosures, manual adjustments or significant estimates outside standard transaction flows.
Relying on management reviews without criteria, evidence or follow-up documentation.
Failing to evaluate the reports and underlying systems used by controls.
Overlooking new acquisitions, locations, system migrations or management override.
Using audit-firm testing plans as substitutes for management’s own assessment.
Leaving deficiencies unresolved until the year-end external audit.
For guidance on deficiency severity and corrective action, see MBP Global’s Material Weakness: Examples and Remediation Guide.
ICFR Risk Assessment Checklist for CFOs and SOX Managers
Confirm the applicable SOX reporting and auditor-attestation requirements.
Obtain complete consolidated financial statements, disclosures and risk information.
Set a documented materiality approach and consider qualitative factors.
Identify significant accounts, disclosures and relevant assertions.
Document likely sources of material misstatement and fraud risks.
Understand transaction flows, significant locations and information systems.
Assess entity-level controls and the risk of management override.
Identify key controls and eliminate unsupported redundancy.
Document control owners, precision, frequency and evidence.
Assess application controls, ITGC dependencies and report reliability.
Create or update a risk-control matrix and walkthrough records.
Evaluate design and test operation using risk-appropriate procedures.
Classify deficiencies and assign remediation owners.
Review results with relevant governance stakeholders.
Refresh scoping after transactions, personnel changes and new systems.
For a broader annual compliance checklist, use MBP Global’s SOX Compliance Checklist for Growth-Stage Public Companies.
When Should a Company Seek ICFR Assurance or Specialized Support?
Companies should consider additional expertise when moving toward IPO readiness, approaching a SOX 404(b) attestation requirement, implementing a new ERP, integrating acquisitions, or addressing repeated control deficiencies. An early review of scoping documentation may help management identify gaps before required testing or audit milestones.
Questions to ask before engaging an independent auditor
Is the firm PCAOB-registered and experienced with integrated audits?
How will significant accounts, qualitative risks and assertions affect scope?
What documentation and IT evidence will management need to produce?
How will the team communicate identified deficiencies and timing risks?
How will responsibilities be separated to preserve auditor independence?
What assumptions, deliverables and scheduling dependencies are in the proposal?
Independent auditors provide assurance within applicable professional standards; they cannot take responsibility for management’s ICFR design, operation or conclusions. Companies seeking implementation support should assess permissible arrangements separately under SEC and PCAOB independence requirements.
MBP Global LLP works with SEC registrants and growing businesses on public-company audits and related assurance engagements. Learn about MBP Global Audit & Assurance Services.
Frequently Asked Questions About ICFR Risk Assessment
What is the first step in an ICFR risk assessment?
Begin with the consolidated financial statements, relevant disclosures and potential risks of material misstatement. From there, identify significant accounts, assertions and controls addressing the resulting risks.
Is ICFR risk assessment required for all public companies?
Public companies have financial reporting control responsibilities, but formal management assessment and external auditor-attestation obligations depend on SEC reporting status and applicable transition or exemption provisions.
What is the difference between a risk assessment and a risk-control matrix?
The risk assessment identifies what could materially go wrong and why. An RCM documents the corresponding assertions, selected controls, owners, evidence and evaluation procedures.
Does a key control have to be automated?
No. Manual, automated and entity-level controls can be key if they adequately address a relevant financial reporting risk. Control precision, reliability and operating evidence are more important than the label.
Can entity-level controls replace process controls?
Sometimes, when they operate at a level of precision sufficient to address a specific risk. High-level governance or tone-at-the-top controls usually cannot replace precise controls over significant transactions by themselves.
Does every company need SOX 404(b) attestation?
No. Exemptions and transition provisions can apply, including for qualifying emerging growth companies and non-accelerated filers. Filer classification must be assessed using the applicable SEC rules.
Can an RCM template guarantee SOX compliance?
No. A template organizes work, but conclusions depend on the company’s actual risks, appropriately designed controls, operating effectiveness and evidence.
How often should management refresh ICFR scope?
At least as needed for the company’s reporting evaluation and whenever significant business, accounting, technology, personnel or regulatory changes affect reporting risk. High-risk areas may require more frequent reassessment.
Conclusion: Scope ICFR Around Financial Reporting Risk, Not Control Count
An effective ICFR risk assessment begins with material financial reporting risk and ends with a defensible selection of controls that address it. The strongest scoping programs connect significant accounts to assertions, explain where misstatements may occur, assess entity-level and IT dependencies, and retain evidence supporting management’s decisions.
For growing SEC registrants, disciplined scoping supports clearer oversight, more focused testing and better preparation for future integrated audits. It cannot guarantee lower fees or eliminate deficiencies, but it reduces avoidable complexity and helps management direct resources toward meaningful financial reporting risks.
To evaluate an appropriate independent audit engagement, Discuss your public company audit and ICFR assurance requirements with MBP Global LLP.


