Select frameworks and criteria for financial statement and other assurance subject matter.
Criteria selection determines whether an assurance engagement has a valid basis for evaluation. Before designing procedures, the practitioner must know what framework, rule, policy, benchmark, contract term, or other criteria will be used to judge the subject matter.
The practical task is to separate the subject matter from the criteria, evaluate whether the criteria are suitable for users, and explain how the criteria affect procedures, evidence, and reporting.
This lesson focuses on how to:
Do not confuse what is being evaluated with the basis used to evaluate it. The subject matter is the object of evaluation. The criteria are the standard used to judge it.
| Element | Meaning | Example |
|---|---|---|
| Subject matter | The thing being measured or evaluated. | Financial statements, grant compliance, greenhouse gas data, service outcomes, controls, or performance measures. |
| Criteria | The benchmark, framework, rule, policy, or standard used to evaluate the subject matter. | Accounting framework, funding agreement, legislation, board policy, service standard, or published methodology. |
| Evidence | Information obtained to support the practitioner’s conclusion. | Records, reconciliations, confirmations, observations, system reports, inspection, or reperformance. |
| Conclusion | The practitioner communication based on the criteria and evidence. | Assurance report, exception communication, management letter point, or other conclusion. |
For example, “use of restricted grant funds” is subject matter. The grant agreement, eligible-cost rules, reporting deadline, and documentation requirements are criteria. Procedures should be designed against those criteria, not against a generic idea of good grant management.
Criteria need to be strong enough for assurance work. If they are weak, biased, incomplete, or unavailable to users, the practitioner may not be able to accept the engagement or issue a meaningful conclusion.
| Quality | Question to ask | Weakness to discuss |
|---|---|---|
| Relevance | Do the criteria help users make the intended decision? | Criteria measure something different from the user’s real need. |
| Completeness | Do the criteria cover all important aspects of the subject matter? | Key conditions, exclusions, thresholds, or disclosures are missing. |
| Reliability | Would different practitioners apply the criteria consistently? | Criteria are vague or depend too heavily on subjective judgment. |
| Neutrality | Are the criteria free from management bias? | Criteria are selected to produce a favorable result. |
| Understandability | Can intended users understand the criteria and conclusion? | Criteria are unclear, hidden, or too technical for intended users. |
| Availability | Are the criteria available to users or described in the report? | Users cannot understand the basis of the conclusion. |
Criteria do not need to be perfect, but weaknesses must be addressed. The response may be to clarify the criteria, restrict the report to specified users, add disclosure, change the engagement type, or decline assurance if the criteria are not suitable.
Framework choice affects users, procedures, and reporting. A financial statement framework that is appropriate for one user group may be inappropriate for another.
| Framework type | Best fit | Reporting implication |
|---|---|---|
| General-purpose financial reporting framework | Broad users need financial statements prepared for common information needs. | Reporting is usually designed for broad distribution. |
| Special-purpose financial reporting framework | Specified users need information prepared under a contract, regulator, lender, or funder requirement. | Report may need to describe the basis and restrict distribution or use. |
| Contract or grant criteria | Users need assurance over compliance with terms. | Procedures and findings should map directly to each term. |
| Internal policy or board-approved criteria | Governance needs assurance over compliance or performance. | Criteria must be clear, approved, and available to intended users. |
| Performance or service criteria | Users need assurance over outcomes, efficiency, effectiveness, or service quality. | Criteria must define measurement basis and acceptable thresholds. |
Special-purpose frameworks are not automatically weak. They can be appropriate when specified users understand the basis and the report clearly explains the framework and use limitation.
Criteria selection is not a front-end formality. It changes the rest of the engagement.
| If criteria are | Effect on engagement |
|---|---|
| Too vague | Procedures may not be capable of producing persuasive evidence. |
| Biased toward management | The practitioner may need different criteria or should not accept the engagement. |
| Restricted to specified users | Report wording and distribution may need restriction. |
| Incomplete | Additional criteria, disclosure, or scope clarification may be needed. |
| Changed during the engagement | Planning, evidence, and report wording may need revision. |
Criteria also affect evidence sufficiency. If the criteria require approval before spending restricted funds, evidence should address timing and approval, not only whether the amount was recorded. If the criteria require a service outcome, evidence should address the outcome measure and data quality, not only expense totals.
Weak criteria should lead to an engagement response, not just a criticism.
| Weakness | Possible response |
|---|---|
| Criteria are incomplete | Ask management to clarify or supplement criteria before accepting or reporting. |
| Criteria are not available to users | Describe the criteria in the report or restrict distribution to users who understand them. |
| Criteria are biased | Recommend neutral criteria or decline if management insists on biased criteria. |
| Criteria are too subjective | Define measurable thresholds, evidence expectations, and documentation requirements. |
| Criteria conflict with user needs | Reassess engagement objective, scope, and report form. |
The stronger response explains whether the weakness affects acceptance, scope, procedure design, or report wording.
| Step | Question | Output |
|---|---|---|
| 1. Subject matter | What is being evaluated? | Financial, compliance, control, performance, or other subject matter. |
| 2. Users | Who needs the conclusion and what decision will they make? | User decision need. |
| 3. Criteria | What framework, rule, policy, or benchmark applies? | Selected criteria. |
| 4. Suitability | Are the criteria relevant, complete, reliable, neutral, understandable, and available? | Criteria evaluation. |
| 5. Assurance effect | How do criteria affect procedures, evidence, and reporting? | Planning and report consequence. |
Use this sequence when a case includes a special-purpose framework, grant agreement, board policy, compliance requirement, performance measure, control objective, or proposed management-defined benchmark.
| Pitfall | Correction |
|---|---|
| Confusing subject matter with criteria. | State both separately before designing procedures. |
| Assuming any management policy is suitable. | Test relevance, completeness, reliability, neutrality, understandability, and availability. |
| Ignoring report use. | Explain whether the report is general purpose, special purpose, or restricted to specified users. |
| Designing procedures before criteria are clear. | Confirm the evaluation basis first. |
| Treating criteria selection as unrelated to reporting. | Link criteria to conclusion wording and user understanding. |