Key IFRS Rules: Concise Technical Statements

Good to see you again. In the previous lesson, you converted scenario facts into separately markable accounting questions. Your issue plan might now contain headings such as “provision or contingent liability?”, “cost of property, plant and equipment”, or “classification of rental income”.

Each heading needs a strong opening: the rule sentence. This lesson develops the first part of the DipIFR writing structure:

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

Your aim is not to reproduce a paragraph of a standard from memory. It is to state the precise requirement needed to resolve the issue, in one sentence that is short enough to be useful under exam time pressure and accurate enough to earn technical credit.

---

What a rule sentence does—and does not do

A rule sentence states the relevant IFRS Accounting Standard requirement in general terms. It tells the marker that you know the test, principle, or accounting outcome before you apply it to the facts.

For example:

Under IAS 37, a provision is recognised when an entity has a present obligation from a past event, a probable outflow of resources is required, and the obligation can be reliably estimated.

This is a good rule sentence because it identifies:

• the relevant standard;
• the accounting item: a provision;
• the recognition conditions; and
• the required outcome: recognition.

It does not say whether this entity has a provision. That is the application and conclusion that follow.

Compare it with these weaker alternatives:

Version	Why it loses effectiveness
“IAS 37 deals with provisions.”	Identifies a topic, but states no rule.
“The company should provide for the legal claim.”	Gives a conclusion without demonstrating the rule or applying facts.
“IAS 37 says provisions and contingencies should be recognised or disclosed depending on probability.”	Too vague; the recognition criteria and outcome are not technically clear.
“Because the lawyers say payment is probable, a provision of $\$280,000$ should be recognised.”	This is application and conclusion, not a general rule.

A useful distinction is:

Part of answer	Main job	Typical wording
Rule	State the IFRS requirement generally.	“IAS 16 requires…”
Application	Connect the requirement to scenario facts.	“As the legal fees were incurred…”
Conclusion	State treatment and financial-statement effect.	“Therefore, $\$80,000$ is included…”

In a short narrative answer, these may form one compact paragraph. But mentally separating them prevents a common weakness: starting immediately with an assertion about the company, without showing why IFRS requires it.

---

The anatomy of a precise one-sentence rule

Most useful rule sentences have four components:

Standard + subject + operative requirement + decisive condition or outcome

A flexible template is:

Under [standard], [subject] must/is required to [treatment] when/if [condition].

For example:

Under IAS 16, the cost of an item of property, plant and equipment includes directly attributable costs of bringing the asset to the location and condition necessary for it to operate as intended by management.

This sentence works because “directly attributable” and “location and condition” are technical terms that determine the issue. It does not waste words defining property, plant and equipment or listing every possible cost.

Four common rule families

The wording changes depending on what the scenario asks you to decide.

Rule family	What the sentence must establish	Example
Recognition	Whether an item is recognised	“Under IAS 37, a provision is recognised when…”
Classification	Which accounting category applies	“Under IAS 32, an instrument is a financial liability if…”
Measurement	How an amount is measured	“Under IFRS 13, fair value is…”
Presentation	Where an amount is reported	“Under IFRS 18, foreign exchange differences are presented…”

The issue question identified in your plan should tell you which family is needed. For instance:

Issue: Does the redemption feature make the preference shares debt or equity?
Needed rule: Classification rule under IAS 32

Issue: Does the January event alter the 31 December figure?
Needed rule: IAS 10 adjusting-event rule

Issue: Where should the foreign-exchange loss be shown in profit or loss?
Needed rule: Presentation rule under IFRS 18

This keeps your technical knowledge selective. You are retrieving the rule that answers this question, not recalling a whole chapter of the standard.

---

A model of concise technical wording: IFRS 13

Fair value is a useful example because an imprecise phrase such as “market value” may miss the technical idea being tested. IFRS 13 defines fair value from the perspective of market participants, rather than from the entity’s own intended use or preferred price.

A concise, exam-ready rule sentence is:

Under IFRS 13, fair value is the price that would be received to sell an asset or paid to transfer a liability in an orderly transaction between market participants at the measurement date.

Notice what makes it reliable:

• It uses an exit price, not the cost to acquire an asset.
• It refers to an orderly transaction, not a forced sale.
• It uses market participants, rather than management’s preferred valuation.
• It is a single sentence, yet no decisive part of the definition is omitted.

If the issue concerns a non-financial asset and its possible alternative use, a more relevant sentence would be:

Under IFRS 13, the fair value of a non-financial asset reflects its highest and best use from the perspective of market participants.

The lesson is not that you must always quote a definition. It is that where a definition is the rule that decides the issue, it must be stated with its critical qualifiers intact.

---

From broad knowledge to a usable rule sentence

When drafting a rule from memory, use a short internal process. Do this in your plan before writing the final paragraph.

1. Identify the exact decision

Start with the issue question, not the standard title.

Weak starting point: IAS 10
Useful starting point: Does the January settlement change the year-end amount?

2. Retrieve the test and the outcome

Ask two questions:

1. What condition is IFRS testing?
2. What accounting treatment follows if it is met?

For IAS 10, the core link is:

Evidence of a condition existing at reporting date
→ adjust amounts recognised in the financial statements

That becomes:

Under IAS 10, an entity adjusts amounts recognised in its financial statements for events after the reporting period that provide evidence of conditions existing at the end of the reporting period.

3. Remove the scenario facts

A rule sentence should apply to any entity facing the same issue. Remove names, dates, amounts, and case-specific assertions.

Draft containing facts	Rule sentence
“Because Falcon settled in January, it must reduce the legal provision to $\$280,000$.”	“Under IAS 10, an entity adjusts recognised amounts for events after the reporting period that provide evidence of conditions existing at the reporting date.”
“The machine training cost is not part of Falcon’s asset.”	“Under IAS 16, expenditure on staff training is recognised as an expense rather than included in the cost of property, plant and equipment.”
“The customer received the goods in December, so the sale is revenue.”	“If a performance obligation is not satisfied over time, IFRS 15 requires revenue to be recognised at the point in time when control of the promised good or service transfers to the customer.”

4. Test for one complete sentence

“One sentence” means one complete technical proposition, not necessarily one short line. A provision rule has three linked conditions; it would be misleading to split or omit them merely to make it shorter.

However, do not combine unrelated requirements:

Poor: “IAS 16 says that directly attributable costs are capitalised, training is expensed, depreciation starts when available for use, and assets are derecognised on disposal.”

That is four possible issues disguised as one rule. State only the rule needed for the issue heading. If the scenario raises training expenditure and depreciation, use two short rule–application–conclusion units.

---

Accuracy comes from qualifiers, not length

Technical writing is often made inaccurate by replacing IFRS terms with approximate everyday language. Use the standard’s decisive words where you know them.

Avoid	Prefer	Why it matters
“likely payment”	“probable outflow”	IAS 37 uses a specific recognition threshold.
“future event”	“event after the reporting period providing evidence of conditions existing at year end”	Distinguishes adjusting from non-adjusting events under IAS 10.
“market value”	“price in an orderly transaction between market participants”	Captures the IFRS 13 fair-value concept.
“expense in profit or loss”	“operating expense” or another correct category where required	IFRS 18 requires a category-specific answer.
“loan-like shares”	“contractual obligation to deliver cash or another financial asset”	Captures the IAS 32 liability test.

Precision does not mean copying every exception in the standard. It means including the qualification that matters to the issue. If an exception is relevant to the stated facts, either include it in the rule sentence or deal with it directly in the application.

For example, this is too broad:

“Income from investment property is always investing income.”

It ignores an important IFRS 18 exception for an entity whose specified main business activity is investing in such assets. A safely scoped rule is:

Under IFRS 18, an entity without a specified main business activity classifies rental income and fair value changes from investment property in the investing category of profit or loss.

---

IFRS 18: presentation wording now earns technical credit

For the December 2026 DipIFR sitting, “recognised in profit or loss” may be incomplete where the question requires a statement-of-profit-or-loss classification. IFRS 18 requires the relevant category to be stated.

For example, where foreign exchange differences are the issue, a concise rule is:

Under IFRS 18, foreign exchange differences are presented in the same category of profit or loss as the income and expenses from the items that gave rise to those differences.

This can then be applied clearly:

The exchange loss arose on a trade receivable; therefore, it is presented in the operating category of profit or loss.

The first sentence is the rule. The second is application and conclusion. The separation is clean and marker-friendly.

---

A compact rule bank: patterns worth practising

The following are models of the level of detail to aim for. They are not a substitute for learning the underlying standards; they show how to turn that knowledge into one usable sentence.

Issue	Concise rule sentence
Provision recognition	Under IAS 37, a provision is recognised when an entity has a present obligation from a past event, a probable outflow of resources is required, and the obligation can be reliably estimated.
PPE cost	Under IAS 16, the cost of an item of property, plant and equipment includes directly attributable costs of bringing the asset to the location and condition necessary for it to operate as intended by management.
Research expenditure	Under IAS 38, expenditure on research is recognised as an expense when incurred.
Development expenditure	Under IAS 38, development expenditure is capitalised only when the specified recognition criteria, including technical feasibility and probable future economic benefits, are met.
Revenue at a point in time	If a performance obligation is not satisfied over time, IFRS 15 requires revenue to be recognised when control of the promised good or service transfers to the customer.
Financial liability	Under IAS 32, an instrument is a financial liability when the issuer has a contractual obligation to deliver cash or another financial asset.
Estimate change	Under IAS 8, a change in an accounting estimate is recognised prospectively in profit or loss in the period of change and, where relevant, future periods.
Adjusting event	Under IAS 10, an entity adjusts amounts recognised in its financial statements for events after the reporting period that provide evidence of conditions existing at the reporting date.

Read these as structures, not as isolated phrases to memorise. In each one, identify:

1. the standard;
2. the item or decision;
3. the operative verb—“recognised”, “capitalised”, “adjusts”, or “presented”; and
4. the condition that makes the result apply.

---

Your pre-writing quality check

Before moving from your issue map into prose, audit each planned rule sentence quickly.

[ ] Have I named the relevant IFRS Accounting Standard?
[ ] Does the sentence answer the exact accounting question in my heading?
[ ] Have I included the decisive test, threshold, or measurement basis?
[ ] Have I used technically correct terminology rather than vague substitutes?
[ ] Is the rule general, with scenario facts reserved for application?
[ ] Does it contain one complete accounting proposition and one full stop?
[ ] Have I avoided unnecessary definitions, exceptions, and standard summaries?

A practical target is usually 20–35 words. Some recognition rules legitimately need more because several conditions must be met. Conversely, a rule such as “research expenditure is expensed when incurred” should remain short; adding unrelated IAS 38 detail reduces point-per-mark efficiency.

The next stage is to attach each sentence to the decisive facts from the scenario. A technically correct rule earns useful credit, but marks are secured most reliably when the answer explicitly explains why this entity meets—or does not meet—the rule.

---

Key takeaways

A high-quality IFRS rule sentence is a concise, general statement of the requirement that resolves a specific issue. Build it from:

$$\text{standard}+\text{subject}+\text{requirement}+\text{condition or outcome}$$

Keep facts, figures, and entity-specific judgements out of the rule; they belong in the application. Use exact technical qualifiers—such as “probable”, “control”, “orderly transaction”, and the correct IFRS 18 category—because those words often determine whether the treatment is correct.

You should now be able to take an issue heading from your plan and draft a precise rule sentence before writing anything else. In the next lesson, you will turn that rule into a direct application to the facts, using explicit “because” reasoning that earns marks rather than leaving the marker to infer your logic.