COSO Framework for ICFR: The 5 Components and 17 Principles Explained

COSO Framework for ICFR: The 5 Components and 17 Principles Explained

var(--variable-LoqRZ1RA_)
var(--variable-LoqRZ1RA_)

An effective ICFR framework gives public-company management a practical way to connect financial reporting risks, controls, evidence and accountability. The COSO Internal Control - Integrated Framework is widely used for that purpose: its five interconnected components and 17 principles help companies evaluate whether internal control over financial reporting (ICFR) is designed and operating to provide reasonable assurance about reliable financial statements.

For CFOs, controllers and audit committees, the important question is not whether all 17 principles appear in a spreadsheet. It is whether relevant principles are present and functioning, work together, and support controls that address the company’s risks of material financial statement misstatement. A growing issuer may need a different mix of controls from a global corporation, but both must explain the evidence behind their conclusions.

This guide covers each component and principle, gives financial reporting examples, explains the relationship between COSO and SOX Section 404, and includes an ICFR implementation checklist and sample risk-control matrix. It also explains when external auditor attestation applies and what to consider when evaluating independent audit services.

What Is the COSO ICFR Framework?

COSO (the Committee of Sponsoring Organizations of the Treadway Commission) developed the Internal Control - Integrated Framework to help organizations design, implement and evaluate internal control. Its 2013 version describes five components supported by 17 principles. It is broader than financial reporting alone, but public companies frequently use it as their recognized framework for ICFR assessments.

The SEC permits management to use a suitable, recognized framework, and COSO is a common choice - not the only framework legally acceptable. The framework provides evaluation criteria; it does not prescribe a fixed number of controls, a software vendor, or a uniform audit testing sample size.

COSO and SOX 404: Related but Different

COSO explains how to organize and assess internal control. SOX 404(a) concerns management’s reporting on ICFR for applicable issuers, subject to transition provisions; SOX 404(b) requires independent auditor attestation only for issuers subject to that requirement. A company can use COSO for management purposes without automatically becoming subject to 404(b).

For an overview of reporting responsibilities, see MBP Global’s Internal Control Over Financial Reporting (ICFR) Guide.

The Five COSO Components at a Glance

Component

Principles

Financial reporting focus

1. Control environment

1–5

Integrity, board oversight, responsibility and competence

2. Risk assessment

6–9

Objectives, misstatement risks, fraud and changes

3. Control activities

10–12

Approvals, reconciliations, IT controls and procedures

4. Information & communication

13–15

Reliable data, internal escalation and external reporting

5. Monitoring activities

16–17

Testing, surveillance, deficiencies and corrective action

These components operate together. For example, a revenue review may be well designed, yet fail because the controller lacks timely contract data, users can alter billing records without approval, or management does not follow up on exceptions.

Component 1: Control Environment  -  Principles 1–5

The control environment sets the tone for accurate financial reporting. It includes the conduct of senior management, independent board oversight, accountability and the capabilities of control owners. Weaknesses here can affect many other controls, even when transaction-level checks appear complete.

1. Integrity and ethical values

Management communicates expectations against improper revenue recognition or unauthorized adjustments; a confidential reporting mechanism and documented follow-up support those expectations.

2. Independent board oversight

An appropriately independent audit committee challenges significant estimates, discusses control findings and oversees the independent auditor.

3. Structures, reporting lines and authority

The controller, revenue team, IT function and audit committee have defined responsibilities and escalation paths for material reporting decisions.

4. Commitment to competence

Personnel preparing complex equity or acquisition accounting have relevant skills, training and access to specialist expertise.

5. Accountability for controls

Control owners are identified, performance deadlines are monitored, and repeat exceptions result in corrective action.

Evidence to retain: board and audit committee minutes, organizational charts, delegated authority matrices, training records, policy acknowledgments and follow-up logs. A policy alone is not enough if practice differs from the document.

Component 2: Risk Assessment  -  Principles 6–9

A useful ICFR risk assessment begins with significant financial statements, accounts, disclosures and assertions. The objective is to determine where a material misstatement could occur, then choose controls that sufficiently address those risks.

6. Clear financial reporting objectives

Define reporting requirements under the applicable framework and identify the disclosures and assertions management must support.

7. Identify and analyze risks

Assess where misstatements could occur, considering transaction volume, complexity, estimates, related parties and qualitative factors.

8. Consider fraud risk

Examine management override, unusual journal entries, incentives to accelerate revenue, and unauthorized transactions.

9. Identify significant change

Reassess scoping after acquisitions, ERP migrations, new financing arrangements, leadership turnover or new accounting guidance.

Example: A SaaS issuer introduces usage-based pricing. The company should revisit the revenue assertions, data completeness, calculation accuracy, contract terms and system controls rather than assuming last year’s controls remain sufficient.

For a deeper scoping approach, review MBP Global’s ICFR Risk Assessment and Key Controls Guide (confirm the live URL before publication).

Component 3: Control Activities  -  Principles 10–12

Control activities translate identified risks into work that can be performed and evidenced. A control should have a clear objective, responsible owner, frequency, procedure and documentation that permits appropriate review.

10. Select and develop control activities

Use controls proportionate to the risk, such as account reconciliations, independent journal entry reviews or approvals over material transactions.

11. Establish technology-related general controls

Address financial-system access, privileged users, program changes, interface reliability and system operations that support automated or IT-dependent controls.

12. Put policies into practice

Convert control descriptions into executable procedures with exception thresholds, evidence retention and escalation requirements.

Example: A controller reviews a monthly revenue variance report. To be a useful key control, the review should specify expected tolerances, whether the data is complete and accurate, what causes investigation, and how exceptions are resolved. “Management reviews revenue” is usually too vague to demonstrate precision.

Component 4: Information and Communication  -  Principles 13–15

Even a carefully designed control can fail if data is incomplete, system extracts are unreliable, or significant accounting issues are not communicated promptly.

13. Obtain relevant, high-quality information

Validate the completeness and accuracy of reports used for reconciliations, controls and management estimates.

14. Communicate internally

Establish reporting channels so finance, operations, IT, compliance and the audit committee know what exceptions require escalation.

15. Communicate externally

Support relevant communications to external auditors, regulators, service organizations and other parties, consistent with applicable requirements.

Example: If a financial reporting review relies on an ERP export, management should understand report parameters, completeness checks and possible manual edits. A sign-off on a flawed export does not solve the underlying evidence problem.

Component 5: Monitoring Activities  -  Principles 16–17

Monitoring determines whether controls continue working after initial implementation. It can include ongoing supervisory reviews, internal testing, audit committee oversight and separate evaluations, depending on risk.

16. Conduct ongoing or separate evaluations

Use appropriately designed monitoring and testing to identify controls that are missing, inconsistent or no longer fit for purpose.

17. Evaluate and communicate deficiencies

Assess findings promptly, determine severity individually and in combination, assign remediation owners and report material issues to the appropriate level.

Example: Repeated late reconciliations should trigger investigation of staffing, workflow, system problems and review quality. Simply marking exceptions “closed” does not demonstrate that the root cause has been resolved.

Where testing identifies serious deficiencies, use the Material Weakness Remediation Guide to organize corrective work and evidence.

How the 17 Principles Work Together in an ICFR Assessment

COSO effectiveness is not a vote in which 14 of 17 “passes” automatically means controls are effective. Management evaluates whether the relevant principles are present and functioning, whether the five components operate together and whether identified deficiencies undermine ICFR effectiveness. Professional judgment is required.

Entity-Level Controls vs. Process-Level Controls

Level

Typical example

What it contributes

Entity-level

Audit committee oversight; fraud risk procedures

Sets governance, monitoring and organization-wide expectations

Process-level

Monthly bank reconciliation; revenue review

Addresses specific accounts and assertions

IT-related

ERP access review; tested change approval

Supports integrity of automated and system-dependent controls

Entity-level controls may influence or directly address financial reporting risks, depending on their precision. Their existence does not automatically eliminate the need for process controls. The auditor’s top-down approach under PCAOB AS 2201 evaluates those relationships when determining audit testing.

A Practical ICFR Framework Implementation Process

Step 1: Determine reporting obligations and framework

Confirm the company’s SEC reporting classification, applicable management assessment requirements, and whether independent SOX 404(b) attestation applies. Document why COSO is the selected recognized framework.

Step 2: Scope significant accounts, locations and assertions

Identify areas with a reasonable possibility of material misstatement. Consider qualitative risks alongside amounts, including fraud, nonroutine transactions and complex estimates.

Step 3: Map risks to the COSO principles

Create a principle-level mapping showing the relevant risks, control objectives and evidence. Avoid treating the mapping as a substitute for testing.

Step 4: Select key controls using an RCM

Specify the control owner, frequency, report dependencies, relevant assertion and expected documentation. Avoid duplicate controls that do not add meaningful coverage.

Step 5: Evaluate design and implementation

Walk through transactions and assess whether controls could prevent or detect material misstatements in time.

Step 6: Test operation and evaluate exceptions

Select appropriate procedures and evidence depending on frequency and risk. Investigate exceptions and combined deficiencies.

Step 7: Remediate and retest

Address underlying causes and build sufficient operating history before concluding that corrected controls function effectively.

Step 8: Prepare management reporting

Document assessment rationale, significant judgments, deficiencies, communications and the basis for conclusions as of the reporting date.

Sample COSO-to-ICFR Risk-Control Matrix

This example is an illustrative template, not a regulatory form or one-size-fits-all controls inventory. Adapt it to the business and retain actual operating evidence.

COSO principle

Risk / assertion

Illustrative control

Evidence / owner

7  -  Risk analysis

Revenue completeness and accuracy

Controller reconciles billing detail to GL monthly

Signed reconciliation; controller

8  -  Fraud

Management override of entries

Independent review of unusual period-end journal entries

Review log; CFO or delegate

11  -  Technology

Unauthorized changes affect calculations

Access privileges and production changes reviewed

Access log/change tickets; IT

13  -  Quality information

Incomplete system-generated report

Report parameters and totals validated before key review

Validation trail; finance analyst

17  -  Deficiencies

Repeat failures persist

Exceptions tracked to resolution and retested

Issue register; SOX program owner

For a complex company, additional RCM fields often include entity, system, financial statement line item, relevant assertion, materiality/risk rating, control type, frequency, key/non-key rationale, report dependencies, testing period and deficiency status.

COSO Framework Checklist for CFOs and SOX Managers

Governance and risk scoping

  • Document the recognized framework selected and management’s rationale.

  • Confirm issuer classification and reporting responsibilities.

  • Assess significant accounts, disclosures, fraud and management override risks.

  • Reevaluate material changes in operations, personnel and systems.

Control design and information quality

  • Map relevant risks to components, principles and key controls.

  • Assign owners, frequencies and expected evidence for each key control.

  • Evaluate ITGCs and completeness/accuracy of key system reports.

  • Test whether management reviews have sufficient precision.

Testing, monitoring and communication

  • Evaluate design and operating effectiveness using risk-based evidence.

  • Track exceptions, assess severity and aggregate related deficiencies.

  • Communicate significant deficiencies and material weaknesses appropriately.

  • Retest remediated controls and retain evidence supporting conclusions.

Checking every box does not establish effective ICFR. Management must support its conclusions through suitable evaluation procedures and evidence.

Common ICFR Framework Mistakes That Create Audit Readiness Problems

Treating 17 principles as 17 required controls

The principles are criteria, not a mandated list of one control per principle. Multiple controls may support one principle, and an individual control can support several.

Documenting controls without verifying operation

A written policy is not evidence that approvals, reconciliations and reviews were performed effectively.

Overlooking information used in controls

Inaccurate system reports or manual spreadsheets can undermine otherwise sensible management reviews.

Applying last year’s scope to a changed business

New systems, acquisitions or business models can change the financial reporting risk profile.

Confusing auditor testing with management ownership

An external audit is not a replacement for management’s own ICFR evaluation and evidence.

Assuming technology automatically means compliance

Software can help organize risk-control matrices and testing, but it cannot establish adequate governance, precision or independent assurance by itself.

SOX 404(a), SOX 404(b) and the External Auditor’s Role

Management maintains and assesses ICFR under the applicable SEC requirements. Where SOX 404(b) applies, the independent auditor performs an integrated audit under PCAOB AS 2201 and expresses an opinion on ICFR effectiveness as of the assessment date. Qualifying emerging growth companies and non-accelerated filers generally have exemptions from 404(b), and newly public companies may receive applicable transition relief. The filer-status analysis must be specific to the issuer.

The independent auditor uses the same suitable, recognized framework selected by management for the ICFR audit. The auditor applies a top-down, risk-based approach, but management’s assessment procedures and the auditor’s testing need not be identical. SEC and PCAOB independence rules also limit an audit firm’s ability to design or operate controls that it then audits.

Companies evaluating the attestation threshold should consult MBP Global’s SOX 404(a) vs. 404(b) Guide (verify the current published URL).

When Should a Company Seek ICFR Assurance or Specialist Support?

External support may be appropriate when an IPO is approaching, an issuer expects a change in SOX 404(b) applicability, existing testing indicates material weaknesses, a major acquisition changes consolidation risk, or management cannot demonstrate reliable controls over material accounts.

Questions to Ask Before Engaging an Audit Firm

  • Is the firm PCAOB-registered and experienced in integrated audits of similar issuers?

  • How will the audit team assess entity-level controls, significant accounts and assertions?

  • Which management records and control evidence should be prepared in advance?

  • How are independence limitations handled if the company also needs control implementation advice?

  • Who leads the engagement, and how are significant deficiencies communicated to the audit committee?

When planning ICFR work, consider the different roles of management, internal audit, a separate readiness adviser and the independent auditor. Companies should not hire the same auditor to take over prohibited control-design or management functions.

MBP Global LLP provides public-company assurance services. Explore Audit & Assurance Services to discuss an appropriate independent audit or ICFR attestation engagement.

Frequently Asked Questions About the ICFR Framework

What is an ICFR framework?

It is a recognized basis for organizing and evaluating controls intended to provide reasonable assurance over reliable financial reporting. COSO’s 2013 Internal Control - Integrated Framework is widely used by SEC registrants.

What are the five COSO components?

Control environment, risk assessment, control activities, information and communication, and monitoring activities.

How many COSO principles are there?

The 2013 COSO framework identifies 17 principles across the five components. Management considers how the principles are present and functioning together.

Does the SEC require the COSO framework?

No. The SEC requires a suitable, recognized framework for management’s assessment where applicable; COSO is common, but other qualifying frameworks may be acceptable.

Is COSO compliance the same as SOX 404 compliance?

No. COSO is a framework for internal control; SOX Section 404 establishes applicable assessment and attestation obligations.

Does every public company need a SOX 404(b) audit?

No. Auditor attestation depends on reporting classification and applicable exemptions or transition provisions.

What is a risk-control matrix?

An RCM links a financial reporting risk to the relevant assertion, control activity, owner, frequency and evidence. It can also map controls to COSO principles.

Do companies need 17 separate key controls?

No. The 17 principles are not a required count of key controls. Scoping depends on financial reporting risk and the controls that sufficiently address it.

Can ICFR software replace auditor judgment?

No. Software may organize evidence and automate workflows but does not determine effective controls or replace the independent auditor’s professional responsibilities.

What happens if a COSO principle is not functioning?

Management evaluates the resulting deficiencies and how the components operate together; serious deficiencies can contribute to a conclusion that ICFR is ineffective.

Conclusion: Use COSO to Strengthen Financial Reporting, Not Just Pass a Checklist

The COSO ICFR framework helps financial leadership turn a broad compliance obligation into a structured assessment of governance, risks, control activities, information quality and monitoring. Its 17 principles are most useful when management connects them to actual misstatement risks, assigns control ownership, retains reliable evidence and addresses deficiencies promptly.

For public companies and IPO candidates, that approach supports more reliable financial reporting and better preparation for the applicable SEC and PCAOB audit requirements. A well-run ICFR program remains management’s responsibility; external assurance provides an independent opinion where required.

To discuss SEC and PCAOB audit requirements with an independent firm, visit MBP Global’s Audit & Assurance Services.