Skip to main content
Regulatory Council
a promotional graphic telling you that PCI Compliance is no longer an annual exercise and that continuous monitory must be built in
Category: Disclosure & Financial Reporting

Relevant Assertion

Simply put

In a financial statement audit, a relevant assertion is a claim about a transaction, account balance, or disclosure where there is a reasonable possibility that a meaningful error or misstatement could occur. Auditors focus their testing on these assertions because they carry a real risk that the financial statements could be wrong in a way that matters. Not every possible assertion is relevant; only those tied to an identified risk of material misstatement warrant this attention.

Formal definition

A relevant assertion is an assertion about a class of transactions, account balance, or disclosure that has an identified risk of material misstatement, meaning there is a reasonable possibility that the assertion contains a misstatement that could, individually or in aggregate, cause the financial statements to be materially misstated. Audit guidance and standards, including AU-C 315, characterize relevance in terms of this reasonable possibility of material misstatement, and the concept directs where auditors concentrate risk assessment and evidence-gathering procedures. Under standards such as PCAOB Auditing Standard No. 15, the relevance of audit evidence is judged by its relationship to the particular assertion or the objective of the control being tested. The specific application and terminology can vary across auditing frameworks and evolving standard editions, so practitioners should confirm details against the applicable primary standard for their engagement.

Why it matters

The concept of a relevant assertion is central to how modern financial statement audits are scoped and executed. Rather than attempting to test every possible claim embedded in a set of financial statements, auditors direct their limited resources toward the assertions where an error or misstatement could realistically occur and could matter to users of the statements. This risk-based focus, reflected in guidance such as AU-C 315 and referenced in PCAOB standards, is what allows an audit to be both efficient and effective: attention concentrates where the reasonable possibility of material misstatement exists, and less time is spent on areas that carry little consequence.

Because identifying relevant assertions determines where evidence is gathered, an error in this judgment can undermine the entire audit. If an auditor fails to recognize that a particular assertion, such as the valuation of an account balance or the completeness of a disclosure, carries an identified risk of material misstatement, testing may be misdirected and a meaningful misstatement could go undetected. Conversely, treating assertions as relevant when no genuine risk exists can waste effort without improving assurance. The determination is therefore a matter of professional judgment tied directly to the auditor's risk assessment.

The standards and terminology in this area evolve across framework editions and can differ between the AICPA and PCAOB regimes, so the precise application depends on the standards governing a given engagement. Practitioners should confirm details against the applicable primary standard, and the identification of relevant assertions in any specific audit remains a matter of professional judgment rather than a mechanical exercise.

Who it's relevant to

External auditors
For auditors performing financial statement audits, identifying relevant assertions is a foundational step in scoping the engagement. It determines where risk assessment and evidence-gathering procedures are concentrated, and the judgment must be documented and defensible against the applicable standards, whether AICPA (AU-C 315) or PCAOB.
Internal auditors and controls owners
Those responsible for internal controls over financial reporting benefit from understanding which assertions are relevant, because controls are often designed and tested against the objective of addressing a particular assertion. Aligning control objectives with the assertions carrying a reasonable possibility of material misstatement helps focus control activities where they matter most.
Financial reporting and accounting management
Preparers of financial statements make the underlying assertions that auditors evaluate. Understanding how auditors identify relevant assertions helps management anticipate areas of audit focus, particularly accounts, transactions, and disclosures where the risk of material misstatement is reasonably possible.
Audit committees and governance bodies
Those charged with governance oversee the audit process and its outcomes. Familiarity with the concept of relevant assertions supports informed dialogue with auditors about where audit effort is directed and why, and about the risks of material misstatement that shape the audit plan.

Inside Relevant Assertion

Financial Statement Assertion
A representation, whether explicit or implicit, made by management and embodied in the financial statements about the recognition, measurement, presentation, and disclosure of the underlying transactions, account balances, and disclosures. Common assertion categories referenced in auditing literature include existence or occurrence, completeness, accuracy or valuation, rights and obligations, and presentation and disclosure.
Relevance Threshold
An assertion is typically considered 'relevant' when it has a reasonable possibility of containing a misstatement, individually or in combination with others, that could cause the financial statements to be materially misstated. Relevance is a screening judgment applied to each significant account or disclosure to identify where audit or control effort should be focused.
Link to Risk of Material Misstatement
The concept is generally used to connect specific assertions to identified risks of material misstatement, so that controls and audit procedures are designed to address the assertions where those risks are concentrated rather than every possible assertion for every account.
Application in Internal Control Over Financial Reporting (ICFR)
In frameworks often associated with SOX-related ICFR assessments, relevant assertions help scope which controls must be identified, evaluated, and tested. The determination is commonly documented at the level of significant accounts and disclosures.
Documentation and Judgment Basis
Determining which assertions are relevant is a matter of professional judgment, typically supported by an understanding of the entity, its transactions, the account characteristics, and susceptibility to error or fraud. The basis for the judgment is usually documented to make the scoping decision defensible.

Common questions

Answers to the questions practitioners most commonly ask about Relevant Assertion.

Is a relevant assertion the same thing as a material misstatement?
No. A relevant assertion is a claim, implicit or explicit, that management makes about a class of transactions, account balance, or disclosure (for example, existence, completeness, accuracy, valuation, rights and obligations, or presentation) where there is a reasonable possibility of a misstatement that could be material. A material misstatement is an actual error or omission that could influence the decisions of financial statement users. The relevant assertion identifies where such a misstatement could arise; it is not the misstatement itself. Auditors typically use relevant assertions to focus procedures, but whether any misstatement is ultimately material is a separate evaluation that depends on quantitative and qualitative factors and professional judgment.
Does every assertion for every account need to be tested as a relevant assertion?
Not typically. An assertion is generally considered relevant only where there is a reasonable possibility of a material misstatement associated with it. Many frameworks and auditing standards direct effort toward identifying which assertions carry that possibility for a given account or disclosure, rather than treating all assertions as equally significant. Some assertions may not be relevant for a particular balance because the risk of material misstatement is remote. Determining relevance is a matter of professional judgment informed by the nature of the item, its susceptibility to error or fraud, and the surrounding circumstances, and applicability can vary by engagement and jurisdiction.
How do we determine which assertions are relevant for a specific account or disclosure?
In many audit and control frameworks, relevance is assessed by considering the risk of material misstatement associated with each assertion for the item in question. This often involves examining the nature of the account or disclosure, its susceptibility to error or manipulation, the volume and complexity of underlying transactions, and any factors that increase the reasonable possibility of a material misstatement. The process is typically one of professional judgment rather than a mechanical checklist, and conclusions should be documented so the basis for identifying relevant assertions is defensible. Specific methodologies vary by framework and should be applied consistently with the applicable standards.
How should relevant assertions be linked to controls and testing procedures?
Once a relevant assertion is identified, organizations often map it to the controls intended to address the associated risk of material misstatement, and then design procedures to evaluate whether those controls are designed and operating effectively or, in a substantive approach, to test the underlying data directly. The aim is generally to obtain sufficient appropriate evidence over each relevant assertion. The nature, timing, and extent of procedures typically depend on the assessed risk. Note that no control or procedure can be said to eliminate risk; the objective is to reduce the risk of material misstatement to an acceptably low level as defined within the applicable framework.
Should the identification of relevant assertions be revisited during an engagement?
Often, yes. Because relevant assertions are tied to the assessed risk of material misstatement, changes in circumstances, new information, or findings from procedures performed may affect which assertions are relevant or how much evidence is needed. Many frameworks treat risk assessment as iterative rather than a one-time exercise, so it can be appropriate to reconsider relevance as the engagement progresses. Any revision and its rationale are typically documented. The specific expectations depend on the applicable standards and should be verified against the primary source.
How should the basis for identifying relevant assertions be documented?
Documentation practices vary by framework and organization, but it is generally advisable to record which assertions were identified as relevant, the reasoning supporting that conclusion, and how each relevant assertion connects to the assessed risk and the related controls or procedures. Clear documentation helps make the judgment defensible and supports review. Because documentation requirements can be prescribed by specific auditing or compliance standards and can differ by jurisdiction and sector, the exact form and content should be aligned with the applicable primary source and, where necessary, professional advice.

Common misconceptions

Every assertion is relevant for every account or disclosure.
Relevance is a selective, risk-based judgment. For a given account, only certain assertions typically carry a reasonable possibility of material misstatement; others may not be relevant. Treating all assertions as equally relevant for all accounts can misallocate effort rather than focus it where risk resides.
A relevant assertion is itself a risk or a control.
An assertion is a representation embedded in the financial statements, not a potential event (a risk) nor a measure that modifies risk (a control). Assertions are used to describe where a risk of material misstatement could arise and against which controls and procedures are then designed; they should not be conflated with either the risk or the control.
Once determined, relevant assertions are fixed and do not change.
The set of relevant assertions can change as the entity, its transactions, account characteristics, or the assessed risks change. It is generally reassessed rather than assumed to be static, and the underlying frameworks and their terminology can also evolve across editions.

Best practices

Determine relevant assertions at the level of significant accounts and disclosures, focusing on those with a reasonable possibility of material misstatement rather than applying all assertion categories uniformly.
Explicitly link each relevant assertion to the corresponding risk of material misstatement, so that controls and audit procedures are designed to address the specific assertions where risk is concentrated.
Document the professional judgment and supporting rationale for why particular assertions are or are not relevant for each account or disclosure, to make the scoping decision defensible.
Reassess the set of relevant assertions when the entity, its transactions, account characteristics, or assessed risks change, rather than treating prior determinations as permanent.
Maintain a clear distinction between assertions, risks, and controls in working papers to avoid conflating a representation with a potential event or a control measure.
Verify assertion categories and any framework-specific terminology against the current primary standard or framework edition being applied, since language and categorization can vary and evolve.
Application Security Isn’t Optional Anymore.