IFRIC 21 Levies: When to Recognise a Liability and How It Works
Author
Sai Manikanta Pedamallu
Published
Reading Time
15 min read
Table of Contents
IFRIC 21 Levies: When to Recognise a Liability and How It Works
By Sai Manikanta Pedamallu (ACCA, CMA US, CSCA US, CGMA, ACMA, Dip IFRS, M.Com, MBA, MA)
Lead Instructor, Global Fin X | www.globalfinx.in/manikanta
Before IFRIC 21, different entities recognised levy liabilities at different points in time for identical obligations. Some recognised annually at the start of the year. Others spread recognition across the year. Others recognised at year-end based on full-year activity. The same statutory levy produced different financial statements across entities applying IAS 37 to the same facts.
IFRIC 21, effective from 1 January 2014, ended that diversity. It answers one specific question: when does a liability to pay a government levy arise? The answer is tighter and more specific than many preparers expected, and it creates results that are counterintuitive in the context of interim reporting.
Scope: What IFRIC 21 Covers
IFRIC 21 applies to levies imposed by governments on entities. A levy is an outflow of resources embodying economic benefits, imposed by governments in accordance with legislation, other than income taxes within the scope of IAS 12, fines or penalties imposed for breaches of legislation, and payments made to acquire goods or services.
The scope exclusions matter in Indian practice. GST paid by an entity is within IFRIC 21's scope as a levy to the extent it represents a cost to the entity (output tax collected net of input tax credit). However, where GST is fully recoverable through the credit mechanism, the net levy is effectively zero. The gross GST output tax is not a "levy" under IFRIC 21 in the same sense, because the entity is collecting it on behalf of the government. Where GST creates an irrecoverable cost (for example, input tax on exempt supplies), IFRIC 21's timing principles apply to that net irrecoverable amount.
Income taxes are outside scope. MAT (Minimum Alternate Tax) under Section 115JB/115JBB of the Indian Income Tax Act is an income tax for Ind AS 12 purposes, not a levy under IFRIC 21. The obligating event question for MAT is addressed under IAS 12, not IFRIC 21.
Regulatory fees, infrastructure levies, banking sector levies, and statutory contributions that are not income taxes fall within IFRIC 21's scope.
The Core Principle: The Obligating Event
The obligating event that gives rise to a liability to pay a levy is the activity that triggers the payment of the levy, as identified by the legislation.
This is the single most important sentence in IFRIC 21. The obligating event is determined by looking at the legislation itself and identifying what activity, when performed by the entity, creates the legal requirement to pay. It is not:
The date the levy is calculated. The date the levy is paid. The date the financial year begins. The date the entity decides to continue operating.
It is the activity that triggers the payment, as defined by law.
The Going Concern Non-Obligation
An entity does not have a constructive obligation to pay a levy that will be triggered by operating in a future period as a result of the entity being economically compelled to continue to operate in that future period. The preparation of financial statements under the going concern assumption does not imply that an entity has a present obligation to pay a levy that will be triggered by operating in a future period.
This resolves the most common pre-IFRIC 21 error: recognising a full-year levy liability at the start of the year because the entity knows it will operate for the full year. The going concern assumption does not create a present obligation. An entity planning to operate for 12 months and pay a full-year levy has no obligation at the start of those 12 months unless the legislation says the obligating event is something that has already occurred.
Three Levy Structures and Their Recognition Patterns
Structure 1: Progressive Levy (Revenue-Triggered)
If the obligating event is the generation of revenue over a period of time, the corresponding liability is recognised as the entity generates that revenue.
A levy calculated as a percentage of annual revenue, where the legislation specifies that the levy is triggered progressively as revenue is generated, creates a liability that grows throughout the year in proportion to revenue earned.
Indian example: a financial sector regulatory fee calculated as a percentage of total assets under management or total revenue, where the legislation ties the payment obligation to the generation of business activity, follows this structure. At 30 June (mid-year), the entity recognises a levy liability proportional to the revenue generated to that date, not a half-year portion of the expected full-year levy.
The distinction is subtle but matters for interim reporting. The liability at any point during the year reflects revenue earned to that date multiplied by the levy rate. The full-year expected levy is not recognised until the full year's revenue has been generated.
Structure 2: Point-in-Time Levy (Date-Triggered)
Where the legislation specifies that the levy arises on a particular date, the entire levy liability is recognised on that date. Nothing before it; the full amount on that date.
Example: a bank levy calculated on deposits held as at 1 January each year. The obligating event is holding deposits at 1 January. An entity holding deposits at 31 December and at 1 January has a full levy liability at 1 January, with nothing recognised at 31 December.
In interim financial reporting, this produces a distinctive pattern. A company with a calendar year-end that pays a levy triggered at 1 April (the start of Q2) has no levy liability at 31 March (Q1 end) even though the full levy will be known and calculable. At 1 April, the full levy liability appears. This is the correct treatment; it is counterintuitive but required by IFRIC 21.
For an entity with a 31 March year-end, the same 1 April trigger means the full levy liability appears on day 1 of the new financial year, not in the closing financial statements.
Structure 3: Minimum Threshold Levy
If the obligating event is the reaching of a minimum activity threshold, the liability is recognised when that minimum threshold is reached. Before the threshold is reached, there is no present obligation, even if the entity expects to reach the threshold before year-end.
Example: a levy imposed only on entities whose annual revenue exceeds Rs. 500 crore. The levy is calculated on total annual revenue. An entity with Rs. 300 crore of revenue at 30 September and expected full-year revenue of Rs. 650 crore has no levy liability at 30 September. The obligating event (reaching Rs. 500 crore) has not yet occurred. Once the revenue crosses Rs. 500 crore (say on 15 November), the liability is recognised for the full levy calculated on revenue to that date, and continues to accumulate as additional revenue is generated.
The full levy (including the portion relating to the first Rs. 500 crore) is recognised as a liability at the date the threshold is crossed, not just the incremental portion above Rs. 500 crore. The amount of the liability is based on the revenue generated to date, including the first CU50 million revenue.
The Debit Side: Asset or Expense?
IFRIC 21 addresses only the liability recognition question. It explicitly does not address whether the corresponding debit is an asset or an expense. That question is answered by other standards.
For most levies, the debit is an expense in profit or loss in the period the liability is recognised. A revenue-linked levy recognised progressively produces an ongoing levy expense matching the progressive revenue generation. A date-triggered levy produces a one-time expense on the trigger date.
Where an entity prepays a levy before the obligating event has occurred, the prepayment is recognised as an asset (prepaid expense). An entity shall recognise an asset if it has prepaid a levy but does not yet have a present obligation to pay that levy.
This creates an important asymmetry: if an entity is required to pay a levy on 1 April triggered by 1 April activity, and it pays early on 15 March, the payment is a prepaid asset at 31 March. The liability and expense arise on 1 April when the obligating event occurs. The prepayment is released at that point.
Annual vs Interim Financial Statements: The Same Principles Apply
One of IFRIC 21's explicit conclusions is that the recognition principles for levies are the same in interim financial reports as in annual financial statements. There is no "spreading" or "accrual" of a levy to match it to periods it will benefit.
If the obligating event occurs over a period of time, the liability is recognised progressively; if the obligating event is reaching a minimum threshold, the liability is recognised when the minimum threshold is met.
This means:
A date-triggered levy at 1 April produces the entire levy liability in Q1 (April to June) of an entity with a March 31 year-end. It does not spread across four quarters even though the levy notionally relates to a full-year period.
An entity cannot anticipate a levy in Q4 financial statements simply because it knows it will cross a threshold in Q1 next year.
In the Indian context, where quarterly results under SEBI requirements are reviewed by auditors and disclosed publicly, IFRIC 21's interim treatment can produce striking quarter-on-quarter movements that investors and analysts sometimes misinterpret as operational volatility.
Indian Banking Sector: RBI Regulatory Fees
Indian scheduled commercial banks pay various fees and levies to the RBI, including fees for regulatory supervision and deposit insurance premiums to DICGC (Deposit Insurance and Credit Guarantee Corporation).
DICGC premium is calculated on insured deposits and paid semi-annually. The obligating event is holding insured deposits at the assessment date specified in the legislation. The liability for each half-year's premium arises at the assessment date, not ratably across the entire period.
This means an Indian bank at its 31 March year-end must assess whether DICGC assessment dates fall before or after year-end. Where the assessment date is within the financial year, the full premium is a liability at that date. Where it falls in Q1 of the next year, no liability exists at 31 March.
The same analysis applies to any banking sector regulatory levy that is assessed on a particular date based on a balance or activity at that date.
India-Specific: The Compound Levy Question
The Indian tax and regulatory landscape includes numerous levies at the intersection of IFRIC 21 and IAS 12:
Surcharge and cess on income tax: These are additional charges levied on income tax liability. Because they are computed as a percentage of income tax, they are within IAS 12's scope rather than IFRIC 21. The liability recognition follows IAS 12's current tax recognition framework.
Goods and Services Tax (GST) for exempt supply entities: Entities making primarily exempt supplies (hospitals, educational institutions) cannot recover input tax credits on many purchases. The irrecoverable GST becomes a levy cost. The obligating event is the acquisition of the goods or services giving rise to the irrecoverable credit. IFRIC 21 applies to this timing.
Sector-specific levies: SEBI's annual fee on market intermediaries, IRDAI levies on insurers, and TRAI levies on telecom companies are all government levies within IFRIC 21's scope. The legislation for each defines the triggering activity and therefore the obligating event.
Customs duties on imports: An import duty is triggered when goods cross the customs frontier. The obligating event is importation. The liability arises at the point of import, not at the date of ordering or contracting.
Ind AS 29 and IFRIC 21: Hyperinflation Context
Post 46 in this series covers IAS 29, but one interaction is worth noting here: where an entity operates in a hyperinflationary economy and applies IAS 29's restatement approach, levy liabilities denominated in local currency are restated along with other monetary items. The IFRIC 21 timing principles still determine when the liability first arises; IAS 29 then governs subsequent measurement.
Ind AS and IFRIC 21
Ind AS has adopted IFRIC 21 without modification. The principles apply identically to Indian entities. The ICAI's guidance on Ind AS 37 (which corresponds to IAS 37) includes IFRIC 21's conclusions as part of the standard framework.
| Area | IFRIC 21 | Ind AS / IFRIC 21 India |
|---|---|---|
| Obligating event: activity identified by legislation | Same | Same |
| Progressive levy: recognised as activity occurs | Same | Same |
| Date-triggered levy: full amount on trigger date | Same | Same |
| Threshold levy: recognised when threshold reached | Same | Same |
| Going concern: no constructive obligation for future levies | Same | Same |
| Interim reporting: same principles as annual | Same | Same |
| Prepayment before obligating event: asset | Same | Same |
| MAT: outside IFRIC 21, within IAS 12 | Not applicable | Same; MAT is income tax under Ind AS 12 |
| GST irrecoverable credit: IFRIC 21 applies | Not applicable | Applies on acquisition of goods/services |
What Big 4 Auditors Focus On
Obligating event identification. Auditors test whether the entity has correctly identified the triggering activity as defined by the specific legislation for each material levy. A general assumption that levies accrue ratably across the year without examining the legislation is not acceptable.
Interim balance sheet consistency. For entities preparing interim financial reports, auditors verify that levies triggered after the interim period-end are not pre-recognised, and that levies triggered before or at the period-end are recognised in full. The most common error is spreading a date-triggered levy across four quarters instead of recognising it fully in the quarter when the trigger occurs.
Prepayment classification. Where levies are prepaid before the obligating event, auditors verify the prepaid is correctly classified as an asset, not expensed at payment date.
Threshold levies: recognition timing. For threshold-triggered levies, auditors test when the threshold was actually crossed and whether the liability (including the levy on activity below the threshold) was recognised at that specific date.
Dip IFRS Exam Angle
IFRIC 21 appears in Dip IFRS both as a standalone scenario question and embedded in questions about interim reporting. The standard is short and its conclusions are precise, making it a good source of examiner questions where candidates lose marks through imprecise understanding.
Most tested areas:
Identifying the obligating event: given a description of a levy (its calculation basis, payment date, and legislative trigger), determine when the liability arises. The obligating event is the activity identified by legislation, not the payment date or the reporting date.
Going concern non-obligation: a company that knows it will operate for the full year and will therefore owe a full-year levy cannot recognise the full-year liability at the start of the year. The obligation arises as the triggering activity occurs.
Interim reporting: a date-triggered levy produces the full liability in the quarter when the trigger date falls, not spread across all four quarters. This is consistently tested in exam scenarios involving Q1 or Q2 interim reports.
Prepayment: where an entity pays a levy before the obligating event, the payment is an asset at the reporting date.
Common traps:
Recognising a full annual levy at 1 January because the entity will pay it later that year. The obligating event must have occurred.
Spreading a date-triggered levy across four quarters as a practical approximation. IFRIC 21 prohibits this. The full amount is recognised in the quarter the trigger occurs.
Confusing the levy calculation basis (which may reference a prior period) with the obligating event (which is the current period activity). The fact that a levy is calculated on prior-year revenue does not mean the prior-year activity was the obligating event; the current-year triggering activity (generating revenue) is still the obligating event if that is what the legislation specifies.
FAQ
Does IFRIC 21 apply to penalties for non-compliance with laws?
No. Fines and penalties for breaches of legislation are outside IFRIC 21's scope. They are assessed under IAS 37 as provisions or contingent liabilities based on probability of the penalty being imposed.
What if the levy rate changes during the year?
The levy is recognised using the rate applicable at the date of the obligating event. If legislation changes the rate during the year and the obligating event has already occurred at the old rate, the liability is remeasured at the new rate from the effective date of the change.
Is a bank deposit insurance premium paid to DICGC within IFRIC 21?
Yes. DICGC premiums are levies within IFRIC 21's scope. The obligating event is the assessment date specified by DICGC regulations when the insurable deposits are held. The premium liability arises at that assessment date for each half-year.
Can an entity accrue a levy in advance of the obligating event to match it with related revenues?
No. IFRIC 21 explicitly prohibits anticipatory recognition. Matching principles under IAS 18 (or IFRS 15 for revenue) do not override the liability recognition principle in IAS 37 as interpreted by IFRIC 21. The liability cannot be recognised before the obligating event, even if the entity would prefer earlier recognition for matching purposes.
How does IFRIC 21 interact with IAS 20 government grants?
They are separate frameworks. IAS 20 governs the accounting for grants received from governments (income recognition). IFRIC 21 governs levies paid to governments (liability recognition). Where a levy and a related grant exist, the gross amounts are presented separately unless specific offsetting criteria are met.
Does IFRIC 21 apply to environmental levies in India?
Yes, to the extent environmental charges are imposed by government under legislation and are not income taxes, fines, or payments for services. The obligating event is the specific activity (pollution, production of regulated substances) that the legislation identifies as the trigger.
Enroll with Global Fin X
IFRIC 21 is a short interpretation with precise, testable conclusions. The obligating event framework, the going concern non-obligation, threshold levy mechanics, and interim reporting treatment are all directly examined in Dip IFRS. Our programme covers IFRIC 21 alongside the full IAS 37 series with detailed lectures, worked examples, exam-style MCQs, and a dedicated LMS for working professionals.
Enroll Now: Dip IFRS Programme
Faculty profile: www.globalfinx.in/manikanta
This is Post 45 of the Global Fin X IFRS Series. Previous: IAS 37 vs IFRS 9: When a Financial Liability Provision Meets ECL. Next: Post 46: IFRS 3 Business Combinations: Acquisition Method and Identifying the Acquirer.