A company knows that a government charge is coming.
It has operated throughout the year. Revenue has been earned. The business has benefited from the market activity that the government intends to levy.
However, the legislation says the final payment becomes due only if a particular condition is met later.
Does the company already have a liability?
That question sounds straightforward until IAS 37, legislation, thresholds and the timing of the relevant activity all begin pulling in different directions.
It is one reason provisions are back on the IASB’s agenda.
The Board has been working on targeted improvements to IAS 37 Provisions, Contingent Liabilities and Contingent Assets, focusing particularly on when a present obligation exists, which costs belong in a provision and which discount rate should be used.
Levies have become one of the most difficult parts of the project.
For ACCA SBR candidates, this is a strong current issues topic because it exposes the difference between knowing that a future payment is likely and deciding whether the accounting liability actually exists today.
Candidates developing this kind of analysis with an ACCA SBR tutor should focus less on memorising the latest meeting decisions and more on understanding the recognition problem the IASB is trying to solve.
A likely payment is not automatically a provision
IAS 37 does not allow a company to recognise a liability simply because management believes money will probably leave the business.
Recognition begins with an obligation.
The entity needs a present obligation resulting from a past event. An outflow of economic resources must also be probable and the amount must be capable of reliable estimation.
This distinction matters.
Management may be almost certain that a business will continue trading next year and therefore incur future operating costs.
That does not mean those costs are liabilities today.
The business can have a detailed forecast, an approved budget and every commercial intention of continuing operations. The future costs still arise from future activity rather than from something the company has already done.
Levies make this distinction harder because legislation can connect several periods and several activities.
Why levies create such awkward timing questions
A levy is broadly a government-imposed charge rather than payment for a specific good or service received in exchange.
The charge might depend on revenue, property values, activity within an industry, possession of a licence or participation in a particular market.
The legislation may then add another condition.
For example, a bank may pay a levy only if it is still operating on a particular date.
A digital business may pay only after annual revenue exceeds a threshold.
A property levy may depend on owning property on a specified date even though the amount reflects activity occurring throughout a longer period.
This creates a tension.
Economically, the charge may appear to relate to activity throughout the year.
Legally, payment may be triggered by one specific event.
Determining which event creates the accounting obligation can materially change when the expense and liability are recognised.
IFRIC 21 created a clear but sometimes uncomfortable answer
Existing guidance on levies sits partly in IFRIC 21.
The basic approach focuses strongly on the activity identified by the legislation as triggering payment.
If the legislation says an entity becomes liable only when a particular activity occurs, the liability is generally recognised when that activity occurs.
This can produce abrupt results.
Imagine a levy based on annual activity but payable only by entities operating on the final day of the year.
Under a strict trigger-based approach, a liability may arise very late even though the company has generated the activity associated with the charge throughout the year.
That can look strange economically.
The first nine months of an interim reporting period may contain no levy expense, followed by a large expense later.
The accounting may follow the legislation accurately while still creating questions about whether the financial statements reflect the economic activity giving rise to the charge.
That is one of the tensions the IASB is trying to address.
The project is trying to clarify the present obligation test
The IASB’s targeted improvements would reorganise the analysis of a present obligation.
The proposed approach identifies three elements within that assessment:
- an obligation condition
- a transfer condition
- a past-event condition
The purpose is not to create provisions whenever a payment looks likely.
It is to explain more clearly why the entity is already responsible for transferring an economic resource.
For a levy, the transfer condition is relatively straightforward because the business pays the government without receiving a new economic resource in exchange.
The difficult question is usually the past-event condition.
What has the entity already done that means the levy relates to past activity rather than future activity?
That question becomes central.
The latest levy approach looks at what government is actually seeking to levy
During the 2026 redeliberations, the IASB has been developing specific application requirements for levies.
The emerging principle focuses on the economic benefit or activity the government is seeking to levy.
That is important because the mechanical wording of legislation may contain several conditions.
Suppose legislation requires both operating during the year and still being present in the market on 31 December.
Which activity really explains the charge?
The latest direction is to identify the economic benefit or activity that best reflects what the government is seeking to levy.
That could lead to a different timing outcome from focusing only on the final legal trigger.
However, these developments remain part of an ongoing standard-setting project.
SBR candidates should therefore describe them as proposed or tentative rather than treating them as existing mandatory accounting.
A levy can accumulate over time
One particularly important idea is that some obligations may build progressively.
Suppose a levy is based on revenue generated during the year.
The business earns revenue from January onwards.
If revenue is the activity the government is seeking to levy, the past-event condition may be met progressively as that activity occurs.
The resulting present obligation could therefore accumulate over the reporting period rather than appearing only on one date.
This can provide a closer connection between the expense and the activity generating it.
It also creates more estimation.
At an interim reporting date, management may need to assess the amount attributable to activity completed so far and consider whether the remaining recognition conditions are satisfied.
That is more complicated than waiting for one legal trigger.
The trade-off is between simplicity and economic representation.
Thresholds create another layer
Many charges become payable only when a company exceeds a specified threshold.
A digital services levy might apply only once relevant revenue exceeds a particular amount.
An environmental charge might become payable only after emissions pass a specified level.
Current practice may delay recognition until that threshold is crossed.
The IASB’s proposed approach to threshold-triggered costs takes a different view.
The activity below the threshold may still contribute to the total amount that eventually creates the payment.
The past-event condition could therefore begin to be satisfied before the threshold itself is reached.
However, that does not automatically mean a provision is recognised.
Management must still consider whether it is probable that the threshold will ultimately be exceeded.
This distinction is critical.
The past-event condition and the probability of payment are related, but they are not the same test.
An example makes the difference clearer
Imagine a company pays a levy if annual qualifying revenue exceeds £100 million.
By 30 September, qualifying revenue is £85 million.
Management expects full-year qualifying revenue of £120 million.
A simplistic approach might say there is no liability because the £100 million threshold has not yet been crossed.
The emerging IASB logic is more nuanced.
The £85 million of activity already completed contributes to the annual activity being levied.
The past-event condition may therefore be developing throughout the year.
Management would then consider whether it is probable that the threshold will be exceeded and whether the other recognition criteria are met.
If the forecast suggested full-year revenue of only £90 million, the conclusion could be different because payment would not be probable.
This produces a better SBR discussion than simply stating that the threshold has or has not been reached.
Future operating costs remain future costs
The IASB’s work has also reinforced an important boundary.
Businesses cannot use the revised thinking to start recognising normal future operating expenditure.
An organisation may know that continuing its business next year will require wages, maintenance, insurance, energy and regulatory compliance expenditure.
Those costs arise from future operations.
Unless a past event has created a present obligation, no provision exists merely because management expects to incur them.
This principle prevents provisions becoming reserves for expected future spending.
For candidates, it provides a useful test.
Ask what the company has already done.
Then ask whether that past activity has created a responsibility it cannot realistically avoid.
If the answer depends entirely on activity that has not happened yet, recognition is unlikely to be appropriate.
Climate-related costs could make this increasingly relevant
The debate extends beyond conventional government levies.
Threshold-triggered obligations can arise in environmental regulation.
A company may incur a charge only when greenhouse gas emissions exceed a specified level.
That creates the same question.
Does the obligation arise only when the threshold is crossed, or does activity below the threshold contribute progressively to the obligation?
This is where current reporting developments begin to connect.
Climate reporting is not separate from financial accounting.
Environmental legislation can affect provisions, forecasts, asset values, operating costs and cash flows.
An SBR candidate who recognises these connections can produce a much stronger answer than someone who treats sustainability as an isolated narrative topic.
Discount rates are also being addressed
Recognition is only part of the IAS 37 project.
Once a provision exists, the business must measure it.
Long-term provisions may include decommissioning liabilities, environmental restoration costs and other obligations that will not be settled for years.
The time value of money can therefore materially affect the reported amount.
The IASB has tentatively supported requiring a discount rate reflecting the time value of money using a risk-free rate, without adjusting for non-performance risk.
This is intended to improve comparability.
If companies use significantly different approaches to credit or non-performance risk, similar obligations can produce different reported provision amounts.
The proposed approach aims to reduce that variation.
It would also require disclosure of the discount rates used and how they were determined.
The costs included in a provision matter too
Another targeted improvement concerns the costs included when an obligation requires the transfer of goods or services.
The emerging approach is that directly related costs would include both incremental costs and an allocation of other costs directly related to settling obligations of that type.
This can matter significantly.
Suppose a company has an environmental restoration obligation.
Management may initially include only external contractor costs.
However, internal staff, equipment and other directly related resources may also contribute to settlement.
The measurement needs to reflect the relevant costs rather than whichever expenses are easiest to identify.
For SBR candidates, this creates a familiar lesson.
Recognition answers whether a liability exists.
Measurement answers how large it should be.
Do not mix the two.
Management judgement creates governance risk
Provisions affect profit immediately.
Recognising a larger provision reduces current profit.
Delaying recognition improves current earnings.
Using a higher discount rate can reduce the present value of a long-term liability.
Excluding directly related costs can do the same.
These effects create incentives for management bias.
An audit committee should therefore challenge significant provisions carefully.
The board should understand what event created the obligation, whether the probability assessment is reasonable, which cash flows are included and what discount rate has been used.
Where the accounting depends on new or proposed guidance, management should distinguish existing requirements from expected future changes.
A tentative IASB decision cannot be used simply because it produces a preferred result.
How this could appear in SBR
Imagine a group operating in several countries.
One government imposes a levy on businesses generating revenue in a particular sector. Payment is due only if annual revenue exceeds a threshold.
Another jurisdiction imposes a charge on companies operating in the banking sector on the final day of the reporting period.
The group also has a long-term environmental restoration provision.
Management argues that no levy should be recognised until the legal payment conditions are fully satisfied and uses a discount rate containing a substantial adjustment for its own credit risk when measuring the restoration liability.
There are several issues.
A strong candidate would separate them.
The levy questions require analysis of the activity the government is seeking to levy and the role of any threshold.
The environmental provision requires separate consideration of measurement and discounting.
The candidate should also explain that the IASB’s targeted improvements are still being finalised rather than automatically applying the proposed treatment.
That distinction demonstrates both technical knowledge and professional judgement.
Current issues answers need careful language
This topic is a good example of why current issues revision needs discipline.
It is easy to read about an IASB meeting and write as though the standard has already changed.
That is dangerous.
IAS 37 remains the applicable standard.
The IASB has published an exposure draft and made subsequent tentative decisions during redeliberations.
Indicative drafting has been prepared for the levy requirements, but final amendments have not yet replaced the existing requirements.
An exam answer should make that status clear.
You can explain the proposed direction and why it may improve reporting without presenting it as law.
That is part of professional communication.
What candidates should remember
The detailed levy examples can become complicated, but the core logic is manageable.
Start with the obligation.
Identify what activity or economic benefit the government is actually seeking to levy.
Determine whether relevant activity has already occurred.
Consider whether the obligation develops progressively.
If a threshold exists, separate the past-event assessment from the probability that the threshold will ultimately be reached.
Then deal with measurement separately.
Candidates following an ACCA SBR course should practise that reasoning through short scenarios rather than trying to memorise every stage of the IASB’s redeliberations.
What to do next
Provisions have always required judgement because they sit between certainty and uncertainty.
Levies make that difficulty particularly visible.
A company may know a payment is likely without having a liability.
Another company may not yet have reached the final legal trigger, but the economic activity creating the obligation may already be taking place.
The accounting question is therefore not simply:
“Will we probably pay?”
It is:
“What has already happened that creates the present obligation?”
That is the question behind the IASB’s current work.
It is also the question SBR candidates should learn to ask first.
