Identify and report non-routine events that affect fair presentation, disclosure, and professional judgment.
Unusual events are transactions or conditions that do not follow the entity’s normal operating pattern. They require extra judgment because routine accounting procedures, recurring journal-entry logic, and ordinary disclosure habits may not capture the economic substance of the event.
In Core 1, the issue is usually to recognize that the fact pattern is no longer routine. The answer should identify the event, determine the financial reporting effect, and explain whether recognition, measurement, presentation, disclosure, tax, assurance, finance, or control consequences follow.
| Unusual event | Primary reporting question | Evidence to inspect |
|---|---|---|
| Restructuring or closure | Is there an obligation, impairment, severance cost, lease exit cost, or disclosure need? | Board approval, communication to affected parties, contracts, cost estimates, closure timeline. |
| Discontinued activity | Does the disposal or shutdown change presentation, impairment, or user interpretation? | Sale agreement, operational separation, decision authority, cash flow impact. |
| Major lawsuit or claim | Should a liability, asset recovery, or contingency disclosure be recognized? | Legal correspondence, counsel assessment, settlement history, insurance coverage. |
| Fire, flood, cyber incident, or other loss | What asset, liability, insurance, going-concern, or disclosure effect exists? | Damage reports, insurance policies, restoration costs, business interruption data. |
| Share-based or unusual compensation | Is the arrangement compensation, equity, liability, or disclosure-sensitive? | Board minutes, employee agreements, vesting terms, settlement terms. |
| Fair value estimate | Is the estimate supportable and appropriately disclosed? | Valuation report, market inputs, assumptions, sensitivity analysis. |
| Subsequent event | Does the event confirm a condition at year-end or arise after year-end? | Event date, year-end conditions, financial statement authorization date. |
The answer should connect the event to the statements. Naming the event is not enough.
An event is unusual in a Core 1 case when it changes the type of analysis required. A sale of inventory is routine for a retailer. A sale of a major division is not. A normal supplier invoice is routine. A supplier dispute that may require a provision or disclosure is not.
Use these questions:
If several answers are yes, treat the item as an unusual event and slow down the analysis.
Unusual events often raise recognition and measurement questions before presentation can be settled.
| Question | Application |
|---|---|
| Has an asset been impaired? | Compare carrying amount to expected recovery using the relevant framework and evidence. |
| Has a liability been incurred? | Determine whether the entity has an obligation and whether the amount can be estimated reliably. |
| Is the cost period-specific or future-oriented? | Separate past obligations from future operating losses or strategic plans. |
| Is an insurance recovery recognized separately? | Do not net unsupported recoveries against losses unless recognition is justified. |
| Is fair value based on observable inputs or management assumptions? | Explain reliability, uncertainty, and disclosure implications. |
| Is the event after year-end? | Decide whether it adjusts existing conditions or only requires disclosure. |
Avoid the weak response of saying “disclose if material” without deciding whether the statements themselves must change.
Unusual events can make ordinary presentation misleading. A user may need to understand that current-year earnings include a one-time gain, a major loss, a discontinued activity, or a change in risk exposure.
Fair presentation may require:
The goal is not to make the event look better or worse. The goal is to make the financial statements understandable.
Unusual events frequently affect other parts of a Core 1 response.
| Area | Possible implication |
|---|---|
| Tax | Accounting treatment may not equal taxable treatment; insurance proceeds, losses, restructuring costs, and timing differences may need separate tax analysis. |
| Assurance | The event may require legal confirmation, external valuation, subsequent-event procedures, or management representation. |
| Finance | Covenants, liquidity, valuation, and lender communication may change. |
| Controls | The entity may need approval, documentation, and review controls for non-routine entries. |
| Strategy | The event may affect stakeholders, operations, risk appetite, and future reporting. |
Mention these only when they follow from the facts. A concise integrated point is stronger than a long unrelated list.
Use this order for unusual event questions:
This sequence keeps the response focused. It also prevents a common error: treating an unusual event as if the standard recurring entry is enough.
| Pitfall | Better approach |
|---|---|
| Treating all unusual events as disclosure-only. | Decide first whether recognition or measurement changes are required. |
| Recording management’s estimate without support. | Identify the evidence needed for amount, timing, and uncertainty. |
| Ignoring tax and insurance consequences. | Separate accounting loss, insurance recovery, and tax treatment when facts support them. |
| Calling every large item “extraordinary.” | Use precise presentation language under the applicable reporting basis. |
| Overwriting elective-depth analysis. | At Core 1 depth, identify the reporting issue and apply the available facts without inventing missing technical detail. |