The CIMA F1 Provisions vs Contingent Liabilities Mistake (And How to Avoid It)

Every sitting, CIMA F1 candidates lose marks on provisions and contingent liabilities not because they don't know IAS 37 exists, but because they apply it too generously. Faced with any uncertain future cost, the instinct is to book a provision “to be safe”. That instinct is exactly what the examiner is testing, and it is exactly what costs marks.

Why this mistake keeps showing up

IAS 37 looks simple on the surface: if something bad might happen and might cost the business money, provide for it. In reality the standard sets a deliberately narrow gate. A provision is a liability of uncertain timing or amount, but not every uncertain future cost qualifies as a liability at all. Many of the scenarios CIMA F1 uses in questions are designed to look like provisions while actually failing one of the three recognition tests. Candidates who provide for everything “just in case” are marked down for misapplying the standard, not rewarded for caution.

If you want the full technical breakdown of the standard itself, including the wording on obligating events and measurement, a full guide to IAS 37 is worth reading alongside this one. This post focuses purely on exam technique: how to classify a scenario quickly and correctly under exam pressure.

The three-part test IAS 37 actually asks for

A provision can only be recognised when all three of the following are true at the reporting date:

• Present obligation from a past event. An obligating event has already happened, and it leaves the entity with no realistic alternative but to settle the obligation. A future decision the entity could still avoid does not count.
• Probable outflow of resources. It is more likely than not (generally read as over 50%) that economic benefits will have to be paid out to settle the obligation.
• A reliable estimate can be made. The amount can be estimated with enough reliability to put a number in the accounts, even if that number is a range or a best estimate.

If any one of these three fails, you do not have a provision. If the obligation exists and the outflow is possible but not probable, or the amount cannot yet be estimated reliably, you have a contingent liability instead, which is disclosed in the notes but never recognised on the statement of financial position. If the outflow is remote, IAS 37 does not require any mention of it at all.

A simple decision tree for the exam

Under time pressure, run every scenario through the same short sequence rather than relying on gut feeling:

1. Has a past event already created a present obligation, legal or constructive? If no, stop — there is nothing to recognise or disclose.
2. Is the outflow of resources probable (more likely than not)? If no, it is a contingent liability — disclose only, do not provide.
3. Can the amount be estimated reliably? If no, it is still a contingent liability — disclose only, even though the obligation and probable outflow tests were met.
4. If all three tests pass, recognise a provision at the best estimate of the amount required to settle the obligation.

Write this logic into your answer explicitly. Examiners reward candidates who show the test being applied line by line, not just the final classification.

Worked scenario 1: the lawsuit

A customer is suing the company for a faulty product. At the year end, the company's lawyers advise that it is probable the company will lose and estimate damages reliably at $150,000.

Walking through the test: the past event is the sale of the faulty product and the resulting legal claim, which creates a present legal obligation. The outflow is assessed as probable by the lawyers, and a reliable estimate of $150,000 exists. All three criteria are met, so this is a provision of $150,000, recognised as a liability and an expense in the current period.

Worked scenario 2: the warranty obligation

The company sells goods with a one-year warranty covering manufacturing defects. Past experience shows that a small, predictable proportion of units will need free repair or replacement, and the finance team can estimate this cost reliably from historical claims data.

The obligating event is the sale of goods under warranty terms, which creates a constructive and legal obligation immediately, not only when an individual customer actually makes a claim. Because the company has a large population of sales, the outflow across the whole population is probable even though no single customer's claim is certain, and the amount can be estimated reliably using historical trends. This also meets all three criteria and is a provision, measured as the expected value of the total expected cost across all units sold.

Worked scenario 3: the restructuring

The board approves a restructuring plan in a board meeting shortly before the year end, intending to close a division and make staff redundant. No announcement has been made to affected staff or the public, and no implementation has started.

This is the scenario candidates most often get wrong in the other direction, by providing too early. A constructive obligation for restructuring only arises once the entity has a detailed formal plan and has raised a valid expectation in those affected that it will carry the restructuring out, typically by starting implementation or announcing the plan to those affected. A board decision alone, with nothing communicated externally, does not create a present obligation, because the company could still change its mind with no cost. There is no provision and no contingent liability disclosure required at this point, because the first recognition criterion — a present obligation from a past event — is not yet met. Once the plan is announced to employees, the position changes and a provision test should be reapplied.

The exam trap: providing “just in case”

Two habits repeatedly cost marks on this topic. The first is providing for anything uncertain, on the theory that prudence means always recognising the worst case. Prudence under IAS 37 does not override the recognition criteria; if the outflow is not probable or cannot be reliably estimated, recognising a provision anyway is a technical error, not a safe answer. The second habit is disclosing everything regardless of probability, including remote possibilities that IAS 37 explicitly says should not be mentioned at all. Both habits usually come from not applying the three-part test explicitly and instead reaching for a classification that feels safe.

The safest approach in the exam is the opposite of what feels instinctively cautious: apply the test rigorously, state which criterion is met or failed for each part of the scenario, and let that analysis drive the classification, even when the resulting answer is that nothing needs to be recognised or disclosed.

Quick checklist before you write your answer

• Identify the exact past event and confirm it creates a present obligation today, not a future one the company could still avoid.
• Assess probability of outflow as more likely than not, not merely possible.
• Check whether a reliable estimate is genuinely available, or whether the scenario is deliberately withholding one.
• If any test fails, move to contingent liability (disclose) or no action (remote), rather than defaulting to a provision.
• Show your working against all three criteria explicitly, even for scenarios that seem obvious.

This same recognition logic underpins other F1 topics that reward the same disciplined, criteria-by-criteria approach, including deferred tax basics, where candidates similarly lose marks by skipping the underlying test in favour of a quick guess. For the full operational-level syllabus context this topic sits within, see the CIMA F1 Financial Reporting study materials, which cover IAS 37 alongside the other reporting standards examinable at this level.

Getting provisions and contingent liabilities right is less about memorising the standard word for word and more about resisting the urge to be cautious in a way the standard does not actually permit. Practise the three-part test on past paper scenarios until running through it becomes automatic, and the classification marks in this area become some of the most reliable in the whole paper.