The liability follows the legislative trigger
Ind AS 37 Appendix C identifies the obligating event for a levy as the activity that triggers payment under the legislation. A past-year revenue base may measure a levy without itself creating the present obligation. A liability is not recognised merely because management expects to continue operating. Read the actual levy legislation before deciding whether recognition occurs on one date, progressively, or only after a threshold. Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium.
Confirm that the charge is within scope
The Appendix addresses levy liabilities within Ind AS 37, including those whose timing and amount are certain. It excludes outflows within other standards, such as income taxes within Ind AS 12, and fines or penalties for breaches of legislation. A contractual payment to government for an asset or service is not a levy under its definition. Entities are not required to apply this Appendix to liabilities from emissions-trading schemes. Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium.
Keep measurement and the obligating event separate
If the legally specified trigger is generating revenue in the current period, earlier revenue used to calculate the charge is necessary to the measurement but not sufficient to create the obligation. Economic compulsion to continue business and the going-concern assumption do not themselves create a present obligation for a levy triggered by future operations. Avoid mechanically accruing one-twelfth of every annual charge each month. Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium.
Progressive activities and minimum thresholds differ
Appendix C paragraph 11 recognises a liability progressively when the obligating activity itself occurs over time. Paragraph 12 recognises an obligation triggered by reaching a minimum activity threshold when that threshold is reached, consistently with the Appendix's principles. The amount then recognised depends on the legislation: a charge on all revenue after a threshold is not the same as a charge only on the excess. Do not invent a universal threshold formula. Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium.
Interim dates follow the same principles
Paragraph 13 applies the same recognition principles in interim and annual reports. Do not anticipate a future trigger merely to smooth an interim result. Paragraph 14 requires recognition of an asset where a levy has been prepaid but there is not yet a present obligation. When the liability arises, determine the debit-side accounting under the relevant standards; Appendix C does not itself decide whether the cost becomes an asset or expense. Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium.
How to use the following illustrations
Every model levy below is expressly fictional. No rate, threshold or trigger is represented as an actual Indian tax or government charge. Each example states its assumed legislative terms to explain the accounting principle. Real engagements require the applicable enactment, amendments, assessment period and trigger evidence. Calculating an amount correctly does not establish that its legal trigger has occurred. Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium.
Applicable primary references
Ind AS 37 Appendix C, paragraphs 2–14, ICAI 2025–26 compendium
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Fixed activity date
Fictional terms impose ₹12 lakh only if the entity operates on 31 March. At 28 February, before that activity date, the model liability is nil. If the entity operates on 31 March, the liability is ₹12 lakh then. An unsupported April–February accrual of ₹11 lakh, at ₹1 lakh for each of those eleven months, would not create a present obligation before the stated trigger. Calendar proration is not the recognition rule in this model.
Illustrative example 2: Progressive revenue generation
Fictional terms impose 2% as current-period revenue is generated, without a minimum threshold. Revenue of ₹40 lakh and then ₹60 lakh creates liabilities of ₹0.8 lakh and ₹1.2 lakh, cumulatively ₹2 lakh on ₹100 lakh. The activity, rather than the calendar alone, supports progressive recognition.
Illustrative example 3: Threshold on the whole base
Fictional terms impose 1% of all current-period revenue once revenue reaches ₹100 lakh. At ₹80 lakh there is no obligation under these terms. At ₹120 lakh the recognised liability is ₹1.2 lakh, not ₹0.2 lakh on the excess. Actual legislation could prescribe a different base; this model expressly uses the whole base.
Illustrative example 4: Prior revenue measures a future-trigger charge
Fictional terms use prior-year revenue of ₹80 lakh and a 2% rate, but trigger payment only on commencing the next year's specified activity. The measured charge is ₹1.6 lakh. Before that activity occurs there is no model liability; once it occurs, the ₹1.6 lakh liability arises. The prior-year amount supplies measurement, not an earlier trigger.
Illustrative example 5: Payment before the obligation
A company pays ₹10 lakh before the fictional levy activity occurs. There is not yet a present obligation. Appendix C's model result is a ₹10 lakh prepayment asset, not a levy liability merely created by the cash payment. When the trigger later occurs, assess the liability and the appropriate accounting for the prepaid amount.
Illustrative example 6: Settle a recognised levy without re-recognition
An independently established levy liability is ₹12 lakh after the trigger. Cash payment is ₹8 lakh, leaving ₹4 lakh payable. Recording another ₹8 lakh of levy cost solely because it is paid would duplicate that part of the original liability recognition. The debit-side classification at initial recognition remains a separate accounting question.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify the charge | Government, legislation and reason it is a levy in scope. |
| 2 | Exclude other standards and penalties | Documented scope conclusion. |
| 3 | Read the current legislation | Operative terms and amendments for the relevant period. |
| 4 | Identify the obligating activity | Precise event, date or activity over time. |
| 5 | Separate the measurement base | Prior/current revenue or other legally specified measure. |
| 6 | Test any threshold | Exact boundary and whole-base versus excess-base rule. |
| 7 | Determine reporting-date liability | Evidence of whether the activity has occurred. |
| 8 | Apply the same interim principles | No unsupported smoothing or anticipation. |
| 9 | Reconcile prepayments and settlements | Cash, prepayment asset and outstanding liability. |
| 10 | Determine presentation and debit treatment | Applicable other standards and evidence-linked final working. |
Sixteen practitioner FAQs
1. Which guidance addresses levy liabilities?
Ind AS 37 Appendix C.
2. What is the obligating event?
The activity triggering payment under the applicable legislation.
3. Does a prior-year revenue base always create a prior-year liability?
No. Distinguish the measurement base from the activity that triggers payment.
4. Does an annual description require monthly accrual?
No. Recognition follows the obligating event, which may or may not occur progressively.
5. When is progressive recognition appropriate?
When the legislatively specified obligating activity occurs over time.
6. What happens with a minimum activity threshold?
Recognise the corresponding obligation when the threshold is reached, consistently with the Appendix's principles and legal terms.
7. Must every threshold charge apply only to the excess?
No. Read whether legislation charges the whole base or only the excess.
8. Does expected continuation of business create the future levy obligation?
Economic compulsion alone does not do so under the Appendix.
9. Does the going-concern assumption create that obligation?
No. It does not replace the future legislative trigger.
10. Are interim recognition principles different?
The Appendix requires the same recognition principles for interim and annual reporting.
11. What if the levy is prepaid before an obligation exists?
Paragraph 14 requires recognition of an asset on the stated facts.
12. Does the Appendix decide whether the eventual debit is an expense?
No. Other standards determine whether the cost gives rise to an asset or expense.
13. Are income taxes within Ind AS 12 covered here?
They are excluded from the Appendix's levy definition.
14. Are fines for breaches of legislation covered?
They are excluded by the stated definition.
15. Are contractual payments to government automatically levies?
No. Payments to acquire an asset or service under a contract do not meet this definition merely because government is the counterparty.
16. Are the illustrated rates actual Indian charges?
No. The model legislative terms are explicitly fictional and demonstrate recognition mechanics only.
Conclusion
Apply Ind AS 37 Appendix C to levy liabilities by separating the obligating activity, measurement base, threshold, reporting date and any advance payment.