IFRIC 21
Published
Levies
Addresses when to recognise a liability to pay a levy imposed by government, clarifying that the obligating event is the activity described in the legislation that triggers payment.
1
Conceptual Framework Linkage
Why levies needed a specific interpretation
Levies imposed by government are COMMON but often poorly understood in accounting terms. They share characteristics with taxes (imposed by government, often mandatory) and with provisions (a present obligation for a past event), but they fit NEITHER category neatly. IAS 12 governs income taxes (explicitly excluded from IFRIC 21), and IAS 37 governs provisions – but neither addresses levies specifically. IFRIC 21 fills this gap by applying IAS 37's recognition criteria to levies, with a specific focus on the OBLIGATING EVENT.
The Conceptual Framework's definition of a liability – a present obligation arising from past events – applies to levies just as it applies to any other obligation. IFRIC 21's contribution is to identify the EXACT POINT at which the past event (the obligating event) occurs for a levy.
The obligating event as the recognition trigger
IFRIC 21's central insight is that the obligating event for a levy is the ACTIVITY DESCRIBED IN THE LEGISLATION THAT TRIGGERS PAYMENT – not the passage of time, not the imposition of the levy, and not the preparation of financial statements. This means that if a levy is triggered by reaching a certain threshold of activity (e.g. revenue above £10m), the obligating event is the ACTIVITY that crosses the threshold, not the later date when the levy is assessed or paid.
2
Scope & Definitions
What IFRIC 21 covers
IFRIC 21 applies to LEVIES IMPOSED BY GOVERNMENT – specifically, mandatory payments to government that are not income taxes (excluded under IAS 12), not fines or penalties (excluded because they are not for services received), and not amounts accounted for under IFRS 2 or IFRS 9. The key characteristic is that the levy is IMPOSED ON AN ENTITY in connection with performing a SPECIFIED ACTIVITY.
TYPICAL FACT PATTERNS
Banking levies imposed on financial institutions based on balance sheet size Carbon taxes or environmental levies based on emissions produced Industry-specific levies triggered by revenue or transaction thresholds Regulatory fees based on the scale of regulated activities
Key definitions
Obligating event
The activity described in the legislation that triggers the payment of the levy – the past event that creates the present obligation under IAS 37.
Levies
Mandatory payments to government imposed in connection with performing a specified activity, excluding income taxes, fines, and penalties.
3
The Obligating Event Principle
The core recognition principle
ScenarioObligating eventRecognition timing
Levies based on revenue thresholdThe activity of generating revenue that crosses the thresholdWhen revenue crosses the threshold – not when the levy is assessed or paid
Levies based on balance sheet itemsThe activity of holding the relevant balance sheet item at the reporting dateAt the reporting date when the balance sheet item exists
Levies based on transactionsThe activity of undertaking the relevant transactionWhen the transaction occurs – not at a later assessment date
Annual levies based on prior year activityThe activity in the prior year that triggered the current year levyAt the reporting date – the prior year activity is complete
⚠️ The obligating event is ALWAYS the activity that triggers the levy, NOT the passage of time between the activity and the assessment date. This means that if a levy is assessed annually based on prior year activity, the obligating event occurs during the prior year, and the liability must be recognised at the END OF EACH REPORTING DATE during the prior year.
4
Point-in-Time vs Progressive Recognition
Point-in-time recognition – when the obligating event is a single moment
Where the levy is triggered by a SPECIFIC ACTIVITY that occurs at a point in time (e.g. a transaction, crossing a threshold, or holding an asset at a date), the liability is recognised AT THAT POINT. There is no progressive recognition – the full liability is recognised when the activity occurs, even if the levy amount is not determined until a later date.
Progressive recognition – when the obligating event is a continuing activity
Where the levy is triggered by a CONTINUING ACTIVITY (e.g. holding a balance sheet item for the entire reporting period), the liability is recognised PROGRESSIVELY as the activity occurs. For example, a levy on average deposits held during the year would be recognised as deposits are accumulated, not as a single point-in-time event.
5
The No Realistic Alternative Trap
Avoiding the "we could avoid the levy" argument
IAS 37's definition of a present obligation requires that the entity has NO REALISTIC ALTERNATIVE to settling the obligation. For levies, IFRIC 21 makes clear that this test is applied to the ACTIVITY THAT TRIGGERS THE LEVY – not to whether the entity could stop the activity. If the entity HAS engaged in the triggering activity, the levy obligation exists regardless of whether the entity could have avoided it by not engaging in that activity. The "no realistic alternative" test applies to SETTLING the obligation, not to AVOIDING the triggering activity.
For example, if a bank holds deposits that trigger a banking levy, the bank has no realistic alternative to settling the levy once the deposits exist – even though the bank could theoretically close its deposit business to avoid future levies. The levy obligation is recognised when the deposits exist, not when the levy is paid.
6
Interim Reporting Consistency
Applying IFRIC 21 in interim financial statements
IFRIC 21 requires that the obligating event principle be applied CONSISTENTLY across interim and annual reporting. This means that if a levy is triggered by an activity that occurs during an interim period, the liability is recognised IN THAT INTERIM PERIOD – not deferred to the annual reporting date. The entity cannot wait until year-end to recognise a levy that was triggered by an activity that occurred in Q1 or Q2.
INTERIM REPORTING APPLICATION
Levies triggered by interim-period activities are recognised in that interim period The measurement of the levy at interim dates follows the same principles as at year-end If the levy amount depends on year-end data (e.g. annual balance), the interim estimate is updated each period
⚠️ A common mistake is to recognise levies only at the annual reporting date. IFRIC 21, applied consistently with IAS 34, requires that levies be recognised at each interim reporting date based on the obligating events that have occurred to date.
7
Worked Example – Threshold-Triggered Levy
Example: Banking levy on total assets
A banking levy is imposed at £0.01 per £1 of total assets held at year-end. The levy is assessed in the following year based on the prior year's closing balance sheet. The bank's total assets were £5bn at 31 December 20X1 and £5.5bn at 31 December 20X2. The levy rate changed to £0.015 per £1 in 20X3. The levy is payable in March of the following year.
20X1 year-end:
Obligating event: holding £5bn assets at 31 December 20X1
Levy liability = £5bn × £0.01 = £50m
Recognised in 20X1 financial statements
20X2 year-end:
Obligating event: holding £5.5bn assets at 31 December 20X2
Levy liability = £5.5bn × £0.01 = £55m
Recognised in 20X2 financial statements
20X3 year-end:
Obligating event: holding £5.5bn assets at 31 December 20X3 (assuming unchanged)
Levy liability = £5.5bn × £0.015 = £82.5m
Recognised in 20X3 financial statements
Payment dates: £50m paid in March 20X2, £55m paid in March 20X3, £82.5m paid in March 20X4.
Key point: The liability is recognised at each year-end based on the assets HELD AT THAT DATE, not when the levy is paid.
Obligating event: holding £5bn assets at 31 December 20X1
Levy liability = £5bn × £0.01 = £50m
Recognised in 20X1 financial statements
20X2 year-end:
Obligating event: holding £5.5bn assets at 31 December 20X2
Levy liability = £5.5bn × £0.01 = £55m
Recognised in 20X2 financial statements
20X3 year-end:
Obligating event: holding £5.5bn assets at 31 December 20X3 (assuming unchanged)
Levy liability = £5.5bn × £0.015 = £82.5m
Recognised in 20X3 financial statements
Payment dates: £50m paid in March 20X2, £55m paid in March 20X3, £82.5m paid in March 20X4.
Key point: The liability is recognised at each year-end based on the assets HELD AT THAT DATE, not when the levy is paid.
8
Worked Example – Activity-Based Levy
Example: Levy on transactions above a threshold
A levy of 0.5% is imposed on the value of all property transactions above £1m. The levy is payable within 30 days of each transaction. During Q1 20X1, the company completed three qualifying transactions: £1.5m (January), £2.0m (February), and £1.2m (March).
January transaction:
Obligating event: completion of £1.5m transaction
Levy liability = £1.5m × 0.5% = £7,500
Recognised in January (Q1 interim period)
February transaction:
Obligating event: completion of £2.0m transaction
Levy liability = £2.0m × 0.5% = £10,000
Recognised in February (Q1 interim period)
March transaction:
Obligating event: completion of £1.2m transaction
Levy liability = £1.2m × 0.5% = £6,000
Recognised in March (Q1 interim period)
Q1 total levy recognised: £7,500 + £10,000 + £6,000 = £23,500
Key point: Each transaction triggers a SEPARATE obligating event. The levy is recognised transaction-by-transaction as the qualifying activity occurs, not as a lump sum at quarter-end.
Obligating event: completion of £1.5m transaction
Levy liability = £1.5m × 0.5% = £7,500
Recognised in January (Q1 interim period)
February transaction:
Obligating event: completion of £2.0m transaction
Levy liability = £2.0m × 0.5% = £10,000
Recognised in February (Q1 interim period)
March transaction:
Obligating event: completion of £1.2m transaction
Levy liability = £1.2m × 0.5% = £6,000
Recognised in March (Q1 interim period)
Q1 total levy recognised: £7,500 + £10,000 + £6,000 = £23,500
Key point: Each transaction triggers a SEPARATE obligating event. The levy is recognised transaction-by-transaction as the qualifying activity occurs, not as a lump sum at quarter-end.
9
Disclosure
What IFRIC 21 requires
Description of the levy and the activity that triggers it The amount of the levy recognised during the period The amount of the levy unpaid at the reporting date The obligating event(s) that caused the levy to be recognised Any changes in the levy rate or the activity threshold during the period
10
Judgments & Estimates
Where judgement matters most
SIGNIFICANT JUDGEMENTS
Identifying the obligating event in complex legislation with multiple trigger conditions Determining whether the levy is within IFRIC 21's scope (not an income tax, fine, or penalty) Assessing whether the entity has a realistic alternative to settling the levy
SIGNIFICANT ESTIMATES
The amount of the levy when the rate depends on data not yet available at the reporting date Timing of interim levies when the activity is ongoing
11
IFRIC 21 vs US GAAP
Comparison – IFRIC 21 vs US GAAP
FeatureIFRIC 21 (IFRS)US GAAP
Obligating eventThe activity described in legislation that triggers paymentSimilar principle – the event that makes payment unavoidable
Recognition timingWhen the triggering activity occursWhen the triggering activity occurs
Income taxes excludedExplicitly excluded under IAS 12Governed by ASC 740 – different framework entirely
Interim reportingApplied consistently at each interim date per IAS 34ASC 270 governs interim reporting; similar principle applies
12
Statement Mapping
Where every IFRIC 21 event lands
EventStatement(s) affectedNotes
Levy liability recognisedSOFP SOPLProvision recognised under IAS 37; expense in profit or loss
Levy paidSOFP SOPLSettlement of liability; cash outflow in financing or operating activities
Levy rate changeSOPL SOFPChange in estimate – accounted for prospectively
13
Related Standards
Cross-reference map
StandardConnection
IAS 37Supplies the underlying recognition and measurement framework IFRIC 21 applies specifically to levies
IAS 12Governs income taxes, explicitly excluded from IFRIC 21's scope
IFRIC 6The earlier interpretation whose obligating-event reasoning IFRIC 21 generalises to all levies
IAS 34Governs interim reporting, into which IFRIC 21's obligating-event timing is applied consistently
Quick-reference glossary
Obligating event
The activity described in the legislation that triggers payment of the levy – the past event that creates the present obligation under IFRIC 21.
Minimum funding requirement
A statutory or regulatory requirement that an employer maintain a minimum level of assets in a defined benefit plan, potentially restricting access to surplus.
14
Glossary
Obligating event
The activity described in the legislation that triggers payment of the levy – the past event that creates the present obligation under IFRIC 21.
Levy
A mandatory payment to government imposed in connection with performing a specified activity, excluding income taxes, fines, and penalties.
No realistic alternative
The IAS 37 test for a present obligation – the entity has no realistic alternative to settling the obligation, applied to the settlement rather than the triggering activity.
Financial statement key
BS Balance sheet
IS Income statement
SE Statement of changes in equity
OCI Other comprehensive income
SCF Statement of cash flows
History & Development
May-2013
In May 2013 the International Accounting Standards Board issued IFRIC 21 Levies. It was developed by the Interpretations Committee.