Accounting Treatment and Financial Statement Impact

Welcome back. In the previous lesson, you practised the middle of the DipIFR reasoning chain: linking a specific scenario fact to the relevant IFRS criterion. You can now show why a condition is met or not met.

This lesson completes the structure:

$$\text{Rule}\to \text{Application}\to \text{Conclusion}$$

A conclusion is the final accounting decision. It tells the marker exactly what the entity must do and where the effect appears in the financial statements. By the end of this lesson, you should be able to finish each issue with a concise, technically precise treatment sentence rather than leaving the examiner to infer the answer.

---

A conclusion is a decision, not a repetition

The rule states the requirement. The application connects that requirement to the facts. The conclusion gives the resulting accounting instruction.

Consider the difference:

Stage	IAS 37 legal-claim example
Rule	A provision is recognised for a present obligation when an outflow is probable and can be reliably estimated.
Application	The damage occurred before year end and legal advisers consider that the entity is likely to lose the claim; the estimated settlement is CU8 million.
Conclusion	Recognise a CU8 million provision in the statement of financial position and a CU8 million expense in profit or loss.

The conclusion does not need to repeat “because the outflow is probable.” That reasoning has already been established. Instead, it should answer four practical questions:

1. What action is required?
   Recognise, derecognise, measure, reclassify, disclose, capitalise, expense, or adjust.

2. What item is affected?
   A provision, receivable, right-of-use asset, revenue, deferred tax liability, and so on.

3. What is the amount or measurement basis?
   State the supplied or calculated amount where available.

4. What is the financial statement effect?
   Identify the relevant statement and direction: increase or decrease an asset, liability, income, expense, equity, or OCI balance.

A conclusion is normally one sentence, although two short sentences are justified where one issue has distinct statement-of-financial-position and profit-or-loss effects.

---

The core conclusion formula

For most DipIFR issues, this formula is reliable:

$$\text{Required action}+\text{amount or basis}+\text{financial statement effect}$$

A compact template is:

Accordingly, [action] [item] at/by CU[amount] in the [financial statement], with a corresponding [income/expense/equity/liability] effect.

You should adapt the wording to the accounting issue rather than forcing every conclusion into identical language.

Recognition conclusions

Use these when an item must be brought into, or removed from, the financial statements.

Recognise a provision of CU6 million as a liability in the statement of financial position, with a corresponding expense in profit or loss.

Derecognise the receivable of CU400,000 and recognise the resulting loss in profit or loss.

Recognise an expected credit loss allowance of CU30,000, reducing trade receivables and increasing impairment expense in profit or loss.

Measurement conclusions

Use these when the issue is the carrying amount rather than initial recognition.

Measure the investment property at its fair value of CU12 million; the CU900,000 fair value gain is recognised in profit or loss.

The asset should be carried at CU1.4 million after impairment, with the CU600,000 impairment loss recognised in profit or loss.

Classification or presentation conclusions

Use these when the central decision is where, rather than whether, an item appears.

Classify the redeemable preference shares as a financial liability because the issuer must redeem them for cash; the liability is presented in the statement of financial position.

Present the asset separately as held for sale and measure it at the lower of carrying amount and fair value less costs to sell.

Non-recognition and disclosure conclusions

A negative conclusion must still say what happens instead. “No provision is recognised” may be incomplete.

Do not recognise a provision because an outflow is not probable; disclose a contingent liability unless the possibility of outflow is remote.

No adjustment is made to the carrying amount at year end because the event is non-adjusting; disclose the nature and estimated financial effect if material.

The second sentence in each example is important. If recognition fails, the relevant IFRS may still require disclosure.

---

Make the financial statement effect explicit

A conclusion such as “recognise the adjustment” is too vague. It does not identify the item, amount, or destination. Similarly, “expense the amount” may be incomplete if the question also requires the balance-sheet effect.

The following table shows how to convert vague endings into examinable conclusions.

Weak ending	Why it loses clarity	Better conclusion
“A provision is needed.”	No amount, statement, or corresponding expense.	“Recognise a CU8 million provision liability and a CU8 million expense in profit or loss.”
“The asset should be written down.”	Does not state the resulting carrying amount or loss.	“Reduce the asset’s carrying amount to CU1.4 million and recognise the CU600,000 impairment loss in profit or loss.”
“Revenue is CU950,000.”	States a number but not the accounting treatment.	“Recognise revenue of CU950,000 and a CU50,000 refund liability in the statement of financial position.”
“This is a non-adjusting event.”	Classification alone may not answer the reporting requirement.	“Do not adjust the year-end amounts; disclose the event and its estimated financial effect if material.”
“The costs are capitalised.”	Does not identify the asset or distinguish other costs.	“Include the CU120,000 delivery and installation costs in the cost of PPE, increasing non-current assets.”

Do not rely on journal entries alone

A journal entry can help you think, especially where debits and credits clarify the effect. But a journal entry is not always the clearest conclusion in a narrative DipIFR answer.

For example:

$$\text{Dr Expense}\text{CU8 million}$$ $$\text{Cr Provision}\text{CU8 million}$$

is technically useful, but the examiner’s requirement may be better answered by:

Recognise a CU8 million provision liability, with a corresponding expense in profit or loss.

The sentence identifies both financial-statement effects in the language of the requirement. Use journal entries when specifically requested, or when they efficiently clarify a complex issue; do not let them replace the final conclusion.

---

Worked conclusions: turning analysis into an answer

The conclusions below follow naturally from the applications you practised previously. Notice how each final sentence is shorter than the rule and application, but more decisive.

1. IAS 10: customer insolvency after year end

Application: The customer was in serious financial difficulty at 31 December. Its liquidation on 15 January provides further evidence that the receivable was impaired at the reporting date.

Conclusion:

Treat the liquidation as an adjusting event; reduce the trade receivable by the required expected credit loss allowance and recognise the corresponding impairment loss in profit or loss.

The conclusion identifies:

• the IAS 10 treatment: adjusting event;
• the item: trade receivable;
• the measurement outcome: expected credit loss allowance;
• the profit-or-loss effect: impairment loss.

It does not need to restate the customer’s financial difficulty. That was the application.

2. IFRS 15: expected customer returns

Assume 200 items are sold for CU5,000 each, and returns of 5% are expected.

$$200\times \text{CU}5,000\times 95\%=\text{CU}950,000$$

Application: The customer has a right to return goods, creating variable consideration. The entity expects 5% of the goods to be returned, so it expects to retain consideration for only 95% of sales.

Conclusion:

Recognise revenue of CU950,000 and a refund liability of CU50,000 in the statement of financial position, rather than recognising revenue of CU1 million.

This is stronger than merely writing “Revenue is CU950,000.” It explains the treatment of the consideration not expected to be retained.

3. IAS 16: expenditure related to a new machine

Assume delivery and installation cost CU120,000, while staff training cost CU15,000.

Application: Delivery and installation were necessary to bring the machine to the location and condition required for its intended use. Training occurs after the machine is ready for use and does not meet that criterion.

Conclusion:

Include the CU120,000 delivery and installation costs in the cost of the machine, increasing non-current assets, but recognise the CU15,000 training cost as an expense in profit or loss.

There are two separately markable treatments, so one carefully constructed sentence makes both clear.

4. IAS 37: a claim with an unlikely outflow

Application: The claim relates to events before the reporting date, but legal advisers assess only a 25% chance that the entity will lose the case. An outflow is therefore not probable.

Conclusion:

Do not recognise a provision; disclose a contingent liability unless the possibility of an outflow is remote.

This conclusion does not say “ignore the claim.” It gives the correct alternative reporting consequence.

---

Common conclusion errors and how to correct them

Error 1: Ending with a label rather than a treatment

“This is an adjusting event.”

That identifies the category, but not the required action.

Improve it:

“This is an adjusting event; reduce the receivable to reflect the year-end impairment and recognise the loss in profit or loss.”

Error 2: Giving a number without meaning

“The impairment is CU600,000.”

A number is usually a calculation result, not a complete conclusion.

Improve it:

“Reduce the asset to its recoverable amount of CU1.4 million and recognise a CU600,000 impairment loss in profit or loss.”

Error 3: Mixing fresh reasoning into the conclusion

“As legal advisers believe the entity will probably lose and the obligation came from damage before year end, a provision is recognised.”

This is not wrong, but it repeats the application and still omits the financial statement effect.

Improve it:

“Recognise a CU8 million provision liability, with a corresponding expense in profit or loss.”

Keep the logic in the application paragraph; let the conclusion be the decision.

Error 4: Using imprecise verbs

Avoid weak verbs such as “deal with,” “show,” “record correctly,” or “adjust accordingly.” They conceal the accounting treatment.

Prefer precise verbs:

• recognise
• derecognise
• measure
• capitalise
• expense
• reclassify
• present
• disclose
• reverse
• allocate

For example, “the cost should be dealt with under IAS 16” gives the marker almost nothing. “Capitalise the directly attributable installation cost within PPE” is precise and mark-efficient.

---

A fast final-sentence routine

When planning an issue, reserve a short line for the conclusion before starting to write. Complete these prompts:

Planning prompt	Example answer
Action	Recognise
Item	Provision liability
Amount/basis	CU8 million
Statement effect	Liability in SFP; expense in P/L

Then turn it into one sentence:

Recognise a CU8 million provision liability in the statement of financial position, with a corresponding expense in profit or loss.

Before moving to the next issue, perform this quick check:

• Use a decisive accounting verb.
• Name the affected asset, liability, income, expense, equity, or disclosure.
• Include the amount, carrying amount, or measurement basis if the scenario provides one.
• State the relevant financial statement effect.
• Do not repeat the rule or all the scenario facts.
• Where recognition is prohibited, state the required disclosure or alternative treatment.

This routine is particularly useful under time pressure. The conclusion should be the part of your paragraph that a marker can underline as the answer to the requirement.

---

Key takeaways

A DipIFR conclusion is the final, concise decision that follows your rule and application. Its usual structure is:

$$\text{Action}+\text{item}+\text{amount or basis}+\text{financial statement effect}$$

A strong conclusion does not merely label an event, state an unexplained calculation, or repeat the IFRS rule. It tells the reader exactly what to recognise, measure, present, derecognise, or disclose—and where the effect appears.

You now have the full rule–application–conclusion structure. The next lesson focuses on editing a technical paragraph for sharper exam English, accurate terminology, and point-per-mark efficiency.