Identify presentation, disclosure, related-party, and subsequent-event effects in short cases.
Presentation and disclosure issues ask whether the statements communicate the right information in the right place. A transaction may be measured correctly but still presented poorly or disclosed inadequately. In a Day 3 short case, the response should identify whether the issue requires an adjustment, a reclassification, a note disclosure, or follow-up before the statements are finalized.
Related-party transactions and subsequent events often appear in this area because they affect user understanding. The numbers may not be the only issue. Users may need to understand who was involved, whether the transaction was at arm’s length, whether an event provides evidence about conditions at the reporting date, or whether a later event should be disclosed because it changes user decisions.
| Reporting issue | What to decide | What to communicate |
|---|---|---|
| Presentation | Where an item belongs in the statements. | Reclassification, separate presentation, or clearer line item. |
| Disclosure | What users need to understand. | Note content, uncertainty, related party, policy, or risk explanation. |
| Related party | Whether relationship affects measurement, disclosure, or risk. | Nature of relationship, transaction, balance, terms, and user effect. |
| Subsequent event | Whether later information confirms an existing condition or creates a new event. | Adjustment, disclosure, or no change with rationale. |
| Missing support | Whether the reporting conclusion is supportable. | Document, confirmation, agreement, or management representation needed. |
Presentation determines where and how an item appears in the financial statements. Disclosure explains information users need that may not be clear from the numbers alone. The difference matters. A balance may need to be reclassified on the statement, disclosed in the notes, or both.
For example, a loan due within the next operating cycle may need different presentation from long-term debt. A restricted cash balance may need clear classification and disclosure. A major uncertainty may not change the amount immediately but may require note disclosure. The answer should state the reporting action rather than saying “disclose properly.”
Disclosure should be specific. Name what users need to know: nature of the transaction, amount, timing, uncertainty, assumptions, commitments, guarantees, related-party relationship, or subsequent event. A generic statement that disclosure is needed is not enough.
flowchart LR
A["Reporting fact"] --> B{"Does the amount change?"}
B --> C["Adjustment"]
B --> D["No amount change"]
C --> E["Presentation or classification"]
D --> F["Disclosure or no current effect"]
E --> G["User implication"]
F --> G
Use the map to decide whether the response needs an adjustment, a reclassification, a note, or a no-change conclusion. Many weak answers say “disclose” when the issue actually requires an amount change or a classification change.
| Reporting action | Use it when | Example wording |
|---|---|---|
| Adjustment | The recorded amount is wrong. | “Increase the liability because the obligation existed at year-end.” |
| Reclassification | The amount is recorded but shown in the wrong place. | “Present the balance as current because repayment is due within the next operating cycle.” |
| Separate presentation | Users need the item visible on the face of the statements. | “Show the discontinued or restricted item separately if it changes user interpretation.” |
| Note disclosure | The amount may be correct but users need context. | “Disclose the nature, amount, uncertainty, and terms of the commitment.” |
| No current change | The event does not affect the current reporting period. | “No adjustment is needed, but management should monitor future-period effects.” |
Related-party facts can affect recognition, measurement, disclosure, and risk. The issue may be whether the transaction occurred on normal terms, whether an amount is collectible, whether a balance is properly classified, or whether users need disclosure about the relationship and terms.
The response should separate economic substance from relationship. A related-party sale may still be valid, but the relationship may affect pricing, collectability, disclosure, and user interpretation. A loan to an owner may require classification and disclosure different from a third-party receivable. A management fee may need support for services performed and reasonableness.
Avoid assuming that related-party means improper. The professional issue is transparency and support. State the relationship, transaction, reporting consequence, and follow-up evidence needed.
| Fact | Why users care | Response move |
|---|---|---|
| Owner or family member is involved | Terms may not be market-based. | Disclose relationship, transaction nature, amount, balance, and terms when required. |
| Loan or receivable from related party | Collectability and classification may be unclear. | Assess repayment terms, allowance, current/non-current classification, and disclosure. |
| Management fee or rent | Service value and price may need support. | Identify support for services, market terms, and approval. |
| Asset transfer | Valuation and gain or loss may be affected. | Confirm fair value support and disclose relationship and terms. |
| Guarantees or commitments | Users need to understand exposure. | Explain obligation, amount, uncertainty, and relationship. |
Subsequent events require attention to timing and evidence. Some later events provide evidence about conditions that existed at the reporting date. Others indicate conditions that arose after the reporting date. The response should identify the timing, the condition, and the reporting implication.
Examples include customer bankruptcy, lawsuit settlement, asset damage, financing changes, sale of property, covenant breach, or discovery of an error. The question is whether the later event changes recognition or measurement at the reporting date, requires disclosure, or simply affects future-period reporting.
Do not memorize labels without applying facts. Explain why the event confirms an existing condition or creates a new condition. If the evidence is incomplete, recommend obtaining the document, legal letter, sale agreement, or other support that determines treatment.
| Later event | Key question | Reporting implication |
|---|---|---|
| Customer bankruptcy after year-end | Did financial difficulty exist at year-end? | May affect receivable allowance or disclosure. |
| Lawsuit settlement after year-end | Does it confirm an existing obligation? | May affect provision amount or disclosure. |
| Asset damage after year-end | Did the damage occur after the reporting date? | Usually future-period effect unless it reveals prior impairment. |
| Financing obtained after year-end | Does it affect going concern or covenant disclosure? | May require disclosure even if no current adjustment. |
| Sale of asset after year-end | Does the sale price provide evidence about year-end value? | May support measurement or disclosure depending on facts. |
Presentation and disclosure are user-facing. A response should explain why the information matters to lenders, owners, boards, management, regulators, or other users if the case points to them. A disclosure is not merely compliance; it helps users understand risk, uncertainty, relationships, commitments, and comparability.
The statement effect should be clear. If an adjustment is required, name the account or item affected. If only disclosure is required, state that no adjustment is made but note disclosure is needed. If the event does not affect the current statements, state why and note any future-period consideration if relevant.
| Pitfall | Better approach |
|---|---|
| Treating disclosure as a vague add-on. | State the specific information users need. |
| Ignoring related-party implications. | Discuss relationship, terms, amount, support, and disclosure. |
| Misclassifying subsequent events. | Use timing and evidence to decide adjustment or disclosure. |
| Forgetting statement impact. | Name the adjustment, reclassification, or note effect. |
| Assuming every related-party transaction is wrong. | Focus on transparency, support, and user understanding. |
Use a fact-user-reporting effect pattern. Identify the fact that creates a presentation or disclosure issue, explain why users need the information, and state the reporting effect. This structure keeps the response concise while showing why communication matters.
Presentation and disclosure answers are strongest when they move beyond “include a note.” They should tell management what must be shown, why it matters, and what support is needed.