Link assertions, risk of material misstatement, and evidence-source decisions to financial reporting issues.
Risk of material misstatement is the risk that financial statements or disclosures are wrong before assurance work detects and corrects the issue. Core 1 does not require a full audit file. It requires the ability to identify the risk, connect it to assertions, and select evidence that responds to the risk.
The useful answer is specific: which account or disclosure is at risk, what assertion is affected, what fact creates the risk, and what evidence would address it.
| Risk fact | Likely assertion or issue | Evidence direction |
|---|---|---|
| Sales recorded near year-end with weak shipping support. | Revenue occurrence and cut-off. | Contracts, shipping records, subsequent returns, customer confirmations. |
| Inventory count is informal or unsupervised. | Existence, completeness, and valuation. | Count procedures, reconciliation, count sheets, sales after year-end. |
| Receivables are aging and customers are slow to pay. | Valuation and collectability. | Aging, subsequent receipts, credit history, allowance analysis. |
| Debt covenants are close to breach. | Classification, disclosure, and going concern. | Loan agreements, waiver evidence, covenant calculations, forecasts. |
| Management changed estimate assumptions. | Valuation, accuracy, and bias. | Assumption support, external data, sensitivity analysis, prior estimate outcomes. |
| New system went live during the year. | Completeness and accuracy of data. | Conversion reconciliations, access review, report testing, exception reports. |
| Related-party transactions are undocumented. | Measurement, presentation, and disclosure. | Agreements, approvals, payment records, relationship documentation. |
Assertions help translate business facts into assurance responses.
Financial-statement-level risk affects the statements broadly. Assertion-level risk affects a specific class of transactions, account balance, or disclosure.
| Risk level | Example | Response |
|---|---|---|
| Financial-statement level | Management is under pressure to meet a debt covenant and controls are weak. | Increase professional skepticism and consider broader effects across estimates, cut-off, and classification. |
| Assertion level | Receivables may be overstated because customers are not paying. | Focus on receivable valuation through aging and subsequent receipts. |
| Financial-statement level | New accounting staff lack training and reconciliations are late. | Consider pervasive reporting reliability concerns. |
| Assertion level | Inventory quantities may be wrong because the count was not controlled. | Focus on inventory existence and completeness. |
A Core 1 response should identify both when the facts support both. Do not call a narrow receivable issue a pervasive risk unless it affects the broader statements.
Assertions are not labels to memorize. They guide evidence.
| Assertion | Practical question |
|---|---|
| Occurrence | Did the recorded transaction actually happen? |
| Completeness | Were all transactions or liabilities recorded? |
| Accuracy | Was the amount recorded correctly? |
| Cut-off | Was the transaction recorded in the right period? |
| Valuation | Is the balance measured at a supportable amount? |
| Existence | Does the recorded asset or liability exist? |
| Rights and obligations | Does the entity own the asset or owe the liability? |
| Presentation and disclosure | Is the item classified and explained properly? |
For example, a supplier invoice received after year-end may raise completeness of payables and cut-off of expenses. A receivable from a struggling customer raises valuation more than occurrence.
Evidence should match the assertion and risk.
| Assertion or issue | Stronger evidence source |
|---|---|
| Revenue occurrence | Customer order, shipping evidence, service completion evidence, cash receipt. |
| Revenue cut-off | Shipping terms, delivery date, service-period evidence, invoices before and after year-end. |
| Receivable valuation | Subsequent receipts, customer correspondence, aging, credit review. |
| Inventory existence | Count observation, count reconciliation, test counts, third-party confirmations. |
| Inventory valuation | Recent sales, cost records, obsolescence review, write-down analysis. |
| Liability completeness | Subsequent payments, unmatched receiving reports, supplier statements, legal letters. |
| Estimate reasonableness | External data, historical outcomes, sensitivity analysis, independent recalculation. |
| Disclosure completeness | Agreements, minutes, legal letters, financing documents, related-party records. |
Evidence from outside the entity is often more persuasive than unsupported management representation, but the right source depends on the assertion.
Certain facts heighten risk:
When those facts appear, explain how they change the nature, timing, or extent of work. More risk usually means more persuasive evidence, more focused procedures, or earlier communication.
Use this order for misstatement-risk questions:
This framework makes the answer concrete and evidence-driven.
| Pitfall | Better approach |
|---|---|
| Naming a risk without an assertion. | State what could be wrong: occurrence, completeness, valuation, cut-off, classification, or disclosure. |
| Selecting evidence because it is familiar. | Match evidence to the assertion and risk. |
| Overrelying on management explanation. | Seek support from documents, external evidence, recalculation, or subsequent events. |
| Confusing statement-level and assertion-level risks. | Identify whether the risk is pervasive or specific. |
| Ignoring risk response. | Explain how the risk changes work, evidence, or communication. |