Prepare routine note disclosures and test whether financial statement elements are explained completely.
Routine disclosures explain recurring financial statement elements so users can understand the numbers. They are not filler after the statements. A note may be necessary because the amount involves judgment, a policy choice, a risk, a maturity pattern, a related party, or information that cannot fit clearly on the face of the statements.
In Core 1, routine disclosure questions often appear as incomplete draft notes. The task is to identify what is missing and explain why the omission matters to the user.
| Disclosure area | What users need to understand | Typical case evidence |
|---|---|---|
| Accounting policies | How recurring transactions are recognized, measured, and classified. | Revenue policy, inventory cost formula, depreciation method, basis of accounting. |
| Estimates | Where judgment or uncertainty affects amounts. | Useful lives, allowance, warranty accrual, impairment assumptions. |
| Debt | Maturities, security, covenants, interest rates, and current classification. | Loan agreement, covenant calculation, repayment schedule. |
| Capital assets | Cost, depreciation, additions, disposals, impairment, and useful lives. | Asset schedule, depreciation policy, disposal records. |
| Related parties | Nature of relationship, transaction terms, balances, and measurement basis. | Ownership chart, shareholder loans, management fees, family transactions. |
| Commitments and contingencies | Obligations or uncertainties not fully captured by line items. | Contracts, legal letters, purchase commitments, guarantees. |
| Subsequent events | Events after year-end that affect interpretation or disclosure. | Event date, approval date, contract or legal documentation. |
Routine disclosure should answer the practical question: what would a reasonable user misunderstand if this note were absent or incomplete?
A disclosure omission is different from a recognition or measurement error.
| Issue type | Example | Correct response |
|---|---|---|
| Recognition error | Revenue recorded before it was earned. | Correct the revenue and liability or receivable first. |
| Measurement error | Allowance is unsupported or calculated using stale data. | Adjust or support the estimate before drafting the note. |
| Classification error | Current debt shown as long-term. | Reclassify the liability and then disclose debt terms if needed. |
| Disclosure omission | Debt is recorded but covenant and security terms are missing. | Add a note explaining terms relevant to users. |
| Misleading disclosure | A note says “no commitments” while a signed purchase agreement exists. | Correct the note and describe the commitment. |
Do not use disclosure to hide an incorrect number. Fix recognition and measurement first, then disclose what remains important.
Most routine notes need some combination of four elements:
For example, a debt note may need principal, interest rate, maturity, repayment terms, security, covenant information, and current portion. A capital asset note may need opening cost, additions, disposals, accumulated depreciation, depreciation expense, and impairment if relevant.
Policy notes should explain how the entity accounts for significant recurring areas. A policy note is weak if it repeats generic handbook language without matching the entity’s facts.
| Policy area | Useful disclosure focus |
|---|---|
| Revenue | When revenue is recognized and what evidence supports performance. |
| Inventory | Cost formula, valuation basis, write-down policy, and major categories if relevant. |
| Capital assets | Capitalization threshold, depreciation method, useful lives, and impairment review. |
| Financial instruments | Measurement basis, credit risk, interest rate risk, and classification when relevant. |
| Income taxes | Current and deferred tax approach where applicable. |
| Contributions or restricted funds | Recognition method and restrictions for not-for-profit reporting. |
The note should be specific enough that the user can interpret the statement line item.
When reviewing a draft disclosure, ask:
This review is often enough to find the missing point in a Core 1 case.
Good disclosure is complete, specific, and connected to the statements. Poor disclosure is vague, boilerplate, inconsistent, or unsupported.
| Weak note wording | Stronger approach |
|---|---|
| “The company has debt.” | Identify lender, maturity, interest rate, security, repayment terms, and covenant facts when material. |
| “Depreciation is recorded.” | State method, useful lives, and relevant asset categories. |
| “There are related-party transactions.” | Explain relationship, nature, amount, balance, and terms. |
| “Management estimates bad debts.” | Explain the estimate basis and uncertainty if material. |
| “A lawsuit exists.” | Describe nature, financial effect if estimable, and uncertainty. |
The goal is not to write long notes. The goal is to write notes that let users understand material financial statement elements.
| Pitfall | Better approach |
|---|---|
| Treating notes as optional afterthoughts. | Identify what users need beyond the face of the statements. |
| Disclosing instead of correcting. | Fix recognition, measurement, and classification errors first. |
| Copying generic policy wording. | Tailor the policy to the entity’s actual transactions. |
| Omitting maturity and covenant terms for debt. | Include terms that affect liquidity and lender decisions. |
| Ignoring related parties because cash was paid. | Consider relationship, terms, amounts, balances, and disclosure. |