Applying IFRS Rules to Exam Scenarios

Good to see you again. In the previous lesson, you learned to turn an identified issue into a concise IFRS rule sentence. For example, you can now state the IAS 37 provision-recognition test without mixing it with the facts of the case.

The next move is where many DipIFR answers lose marks: application. An application sentence shows why the rule is met, or not met, by these particular facts. It turns technical knowledge into an answer to the examiner’s question.

The structure remains:

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

This lesson concentrates on the middle step. By the end, you should be able to use explicit fact-to-rule reasoning rather than hoping the marker will infer your analysis.

---

Why general knowledge is not enough

The ACCA examiner repeatedly distinguishes between candidates who state IFRS knowledge generally and candidates who use the facts given. A technically correct paragraph can still earn very little if it does not resolve the actual scenario.

The core message is simple:

A rule earns knowledge credit; application earns the marks for answering the scenario.

A marker should not have to perform the last step of reasoning for you. If the scenario says that lawyers assess a claim as likely to be lost, do not write only “a provision is required.” Explain that the legal advice makes an outflow probable.

This is close to the discipline used in audit documentation: an assertion is supported by specified evidence, then a judgement follows. In a DipIFR answer, however, the evidence is the scenario fact and the judgement is the accounting treatment required by IFRS.

---

The anatomy of an application sentence

A strong application usually contains three elements:

$$\text{Scenario fact}\to \text{IFRS criterion}\to \text{Accounting implication}$$

A practical writing template is:

Because [specific fact], [IFRS condition] is/is not met.

Or:

The fact that [specific fact] indicates that [IFRS condition].

Or, when the fact proves an earlier condition:

This event provides evidence that [condition] existed at the reporting date.

The decisive point is that you name both the fact and the technical consequence of that fact.

Component	Example: legal claim	What it does
Fact	“The damage was caused before year end and legal advisers assess a 70% chance of losing the case.”	Selects evidence from the scenario.
IFRS link	“This creates a present obligation from a past event, and an outflow is probable.”	Matches evidence to IAS 37 conditions.
Implication	“The recognition criteria are therefore met.”	Signals the accounting judgement.

Compare the following answers.

Version	Evaluation
“IAS 37 says that provisions are recognised when there is a present obligation, probable outflow, and reliable estimate.”	A correct rule, but no application.
“The entity has a provision because the lawyers said it may lose.”	Mentions a fact, but “may lose” is vague and does not apply the full test.
“The claim arises from damage caused before the reporting date, so it represents a present obligation from a past event. As legal advisers assess a 70% likelihood of losing the case, an outflow is probable.”	Strong application: each important fact is connected to an IAS 37 criterion.

The third version does not need decorative language. It earns credit because the logic is visible.

---

Do not merely replace “entity” with the company’s name

A common weak answer looks like this:

Under IAS 10, adjusting events provide evidence of conditions existing at the reporting date. Alpha’s event is an adjusting event.

This is not a genuine application. The second sentence is simply a conclusion with “Alpha” substituted for “an entity.”

A better version identifies what happened, when it happened, and *why it changes the accounting:

Alpha’s customer was already experiencing serious financial difficulty at 31 December. Its insolvency on 15 January therefore provides further evidence that the receivable was impaired at the reporting date.

The application is not “the insolvency occurred after year end.” That is only a date. The important reasoning is that it confirms a condition that already existed at year end.

The fact–criterion–judgement method

When reading a scenario, make a small annotation beside each issue:

Step	IAS 10 example
Fact	Customer had financial difficulties before 31 December; it entered liquidation on 15 January.
Criterion	An adjusting event gives evidence of a condition existing at the reporting date.
Judgement	The liquidation is evidence of impairment at 31 December.

Then turn it into prose:

The customer’s financial difficulties existed before the reporting date. Its subsequent liquidation therefore provides evidence of impairment at 31 December and is an adjusting event.

The final accounting treatment—such as adjusting the trade receivable and recognising an expected credit loss—belongs in the conclusion. For now, focus on making the reason unmistakable.

---

Apply each decisive condition, especially in recognition questions

Some IFRS rules contain several conditions. Do not write a generic phrase such as:

“All IAS 37 conditions are satisfied.”

That may be technically possible, but it leaves your reasoning hidden. A concise answer can apply each condition directly.

Assume the scenario states:

• A company contaminated land during the year.
• It has publicly committed to restore the site after extraction.
• The restoration cost is reliably estimated at CU8 million.
• Settlement is expected in five years.

A high-quality application could read:

The contamination occurred during the reporting period, so the obligating event has already occurred. The company’s published restoration commitment creates a constructive obligation because it gives affected parties a valid expectation that restoration will be undertaken. As the estimated cost is CU8 million, the obligation can be reliably measured.

Notice the discipline:

• The fact “contamination occurred” is connected to the past event.
• The public commitment is connected to a constructive obligation.
• The estimate is connected to reliable measurement.

There is no need to restate every detail of IAS 37 before each sentence. You stated the rule once; now demonstrate that the facts meet it.

When a condition is not met

Negative application is equally important. Suppose legal advisers say a claim has only a 25% chance of success against the entity.

Weak:

There is no provision because the claim is unlikely.

Better:

Although the legal claim relates to events before the reporting date, legal advisers assess only a 25% probability that the entity will lose the case. A cash outflow is therefore not probable, so the IAS 37 recognition criterion is not met.

This earns marks because it acknowledges the relevant fact, identifies the missing criterion, and reaches a reasoned judgement. Do not treat every uncertain obligation as automatically a provision.

---

Applying a measurement rule: explain what the number represents

Application is not limited to narrative recognition tests. In computational questions, a number needs an explanation. A calculation without reasoning can lose the “explanation” marks; a narrative answer without figures can lose the “figure” marks.

For example, assume an IFRS 15 contract provides for the sale of 200 goods at CU5,000 each, and returns are expected to be 5%.

A weak answer is:

Revenue is CU950,000.

The figure may be correct, but the marker cannot see why it is correct.

A stronger application is:

The customer has a right to return the goods, so the transaction price includes variable consideration. As Delta expects 5% of the 200 goods to be returned and the estimate is supportable, revenue is recognised only for the 95% expected not to be returned: $200\times 5,000\times 95\%$, or CU950,000.

The explanation does three jobs:

1. identifies the fact: a right of return;
2. links it to the rule: variable consideration;
3. explains the calculation basis: expected retained goods.

The official model answer below is useful because it repeatedly moves from IFRS 15 principles to the particular contract, expected return rate, amounts, and financial-statement effects.

The model is deliberately fuller than every answer needs to be. In the exam, your length should reflect the marks available. The habit to copy is not “write every step of IFRS 15”; it is “state only the relevant rule and apply it to the facts that matter.”

---

Application vocabulary that makes your reasoning visible

Use linking words that reveal the direction of your analysis. They make exam English more precise and reduce the temptation to write vague conclusions.

Purpose	Useful wording
Introduce a relevant fact	“In this case, …”; “Here, …”; “The scenario states that …”
Show evidence	“This indicates that …”; “This demonstrates that …”; “This provides evidence that …”
Match a condition	“Accordingly, the recognition criterion is met.”; “Therefore, control has transferred.”
Show a condition is absent	“However, this does not establish …”; “Therefore, the probability threshold is not met.”
Explain a calculation	“This is calculated as … because …”; “Only the amount relating to … is recognised.”
Move toward the conclusion	“Consequently, …”; “Accordingly, …”; “It follows that …”

Avoid phrases that sound decisive but contain no analysis:

Vague phrase	Why it is weak	Better replacement
“This is in line with IFRS.”	Does not identify the relevant condition.	“This means control of the goods transferred on delivery.”
“The standard applies.”	Every issue has a standard; the examiner needs the rule’s effect.	“The right of return makes the transaction price variable.”
“It should be accounted for correctly.”	Gives no treatment or reasoning.	“The settlement confirms the obligation that existed at year end.”
“The company must follow IAS 16.”	States an obvious standard reference.	“The delivery and installation costs were necessary to bring the asset to the location and condition required for use.”

The most efficient word in an application sentence is often because. It forces you to state the causal connection:

The installation costs are capitalised because they were necessary to bring the machine to the location and condition required for its intended operation.

That is far stronger than:

The installation costs are capitalised. IAS 16 applies.

---

Four recurring application patterns

1. Classification: identify the decisive characteristic

For an IAS 32 issue, do not describe an instrument as “loan-like.” Find the contractual term that determines classification.

The preference shares must be redeemed for cash in five years. The issuer therefore has a contractual obligation to deliver cash, which is the defining feature of a financial liability.

The relevant fact is compulsory redemption in cash—not the instrument’s title, dividend rate, or label.

2. Recognition: match facts to conditions

For IAS 38 development expenditure:

The project has passed the research stage, and management has demonstrated technical feasibility and the availability of resources to complete the product. The expenditure incurred after those criteria were met may therefore qualify for capitalisation.

Be careful with timing. Expenditure incurred before the criteria are met is not retrospectively capitalised merely because the project later succeeds.

3. Measurement: explain the basis of the amount

For IAS 16 directly attributable costs:

The delivery and professional installation costs were necessary to make the production line capable of operating as intended. They are therefore directly attributable to bringing the asset to the required location and condition.

By contrast:

Staff training takes place after the machine is ready for use and does not bring it to the condition necessary for operation. It is therefore recognised as an expense rather than included in the asset’s cost.

The contrast matters: both costs may be connected with a new machine commercially, but only one meets the IAS 16 cost criterion.

4. Post-reporting-date events: distinguish new conditions from evidence

For IAS 10, always ask:

Did the event create a new condition after year end, or provide evidence about a condition already present at year end?

A fire at a warehouse in January, where no damage or obligation existed at 31 December, normally creates a new condition. It is not adjusting merely because it is material.

The fire occurred after the reporting date and did not relate to a condition existing at 31 December. It is therefore a non-adjusting event.

That is short, but it applies both the timing and the nature of the condition.

---

A fast drafting routine for the exam

For each separately markable issue, use this sequence in your plan:

1. Circle the decisive fact.
   Look for dates, contractual terms, legal advice, management commitments, percentages, payment terms, or evidence of control.

2. Write the rule condition beside it.
   For example: “right of return” becomes “variable consideration”; “mandatory cash redemption” becomes “contractual obligation to deliver cash.”

3. Draft one explicit link using “because,” “therefore,” or “this indicates.”
   If you cannot write this link, you may not yet know why the fact matters.

4. Calculate only after the accounting basis is clear.
   Label your calculation so that the marker sees what it measures.

5. State the treatment separately.
   The next lesson will refine this final conclusion sentence and its financial-statement effect.

A compact plan might look like this:

Issue: January customer insolvency

Rule: IAS 10 adjusts recognised amounts for events giving evidence
      of conditions existing at the reporting date.

Application: Financial difficulties existed at 31 December;
             January insolvency confirms year-end impairment.

Conclusion: Adjust receivable / recognise required impairment loss.

The application is the middle line. It is neither a generic standard summary nor the final instruction to adjust the receivable. It is the bridge that proves why the conclusion follows.

---

Key takeaways

An effective DipIFR application sentence makes the logic explicit:

$$\text{specific fact}\to \text{IFRS criterion}\to \text{judgement}$$

Do not simply repeat the rule with the company’s name added. Select the decisive scenario fact, state what it proves under the IFRS requirement, and explain calculations rather than presenting unexplained figures.

Useful exam phrasing includes:

• “Because …, the criterion is met.”
• “This provides evidence that …”
• “However, this does not establish …”
• “Therefore, the recognition threshold is not met.”

The next lesson will complete the rule–application–conclusion structure by focusing on concise conclusion sentences: the required accounting treatment, amount, and financial-statement effect.