Provisions vs Contingent Liabilities IAS 37 Guide

What Are Provisions vs Contingent Liabilities Under IAS 37?

Provisions vs contingent liabilities is one of the IAS 37 topics where students often know the words but hesitate when the facts change slightly. The useful starting point is simple: a [provision](/glossary#provision) is recorded in the accounts, while a [contingent liability](/glossary#contingent-liability) normally stays out of the numbers and appears in the notes when disclosure is needed. Both deal with uncertainty, but they do not sit in the same place in the financial statements.

IAS 37 covers provisions, contingent liabilities, and [contingent assets](/glossary#contingent-asset). It does not ask you to record every risk management can imagine. It asks whether a past event has created a present obligation, whether an outflow of economic resources is probable, and whether the amount can be estimated reliably. If those three recognition tests are met, the liability is not just a possibility anymore. It becomes a provision.

This matters in Saudi and Gulf accounting work because uncertainty appears everywhere: warranty claims, legal disputes, onerous contracts, customer refunds, site restoration, and restructuring plans. The accountant's job is not to guess pessimistically or optimistically. The job is to classify the uncertainty correctly, measure it with supportable evidence, and explain the treatment clearly enough for an auditor, instructor, or exam marker to follow.

Think of IAS 37 as a gate. If the obligation passes through the gate, it affects the [income statement](/glossary#income-statement) and the [balance sheet](/glossary#balance-sheet). If it does not pass through the gate, the issue may still matter, but it is handled through disclosure rather than a journal entry.

How Do You Decide Between Provisions vs Contingent Liabilities?

The decision starts with a past event. A company cannot recognize a provision for a problem it may choose to create next year. There must be an obligating event before the reporting date. The obligation can be legal, such as a contract or regulation, or constructive, where the company's published policy or established practice has created a valid expectation that it will act.

After the past event, ask three questions.

• Is there a present obligation? The company has little or no realistic alternative but to settle.
• Is an outflow probable? More likely than not, cash or another economic resource will leave the business.
• Can the amount be estimated reliably? The estimate may be uncertain, but it must be supportable.

If all three answers are yes, record a provision. If the obligation is only possible, or if a present obligation exists but outflow is not probable, disclose a contingent liability unless the chance of outflow is remote. If the amount cannot be measured reliably, disclosure is also usually the answer, although IAS 37 treats that as rare.

Here is the working decision table:

This table is a useful companion to [accrual accounting](/learn/what-is-accrual-accounting). Accrual accounting tells you not to wait for cash. IAS 37 tells you not to record uncertainty before it becomes a present obligation with a probable outflow and a reliable estimate.

How Are Provisions Measured and Recorded?

A provision is measured at the best estimate of the expenditure required to settle the obligation at the reporting date. For a single obligation, that may be the most likely outcome adjusted for risk. For a large population of similar items, such as warranties, the expected value method is usually more useful because many small claims create a pattern.

Measurement should include risks and uncertainties, but not double count them. If the cash flows already reflect risk, do not also inflate the discount rate for the same risk. If settlement is far in the future and the time value of money is material, IAS 37 requires present value measurement. The unwinding of the discount is recognized as a finance cost over time.

The [journal entry](/glossary#journal-entry) usually follows a straightforward pattern when the provision first appears:

Later, when the company settles the obligation, it debits the provision and credits cash or payables. If the estimate changes before settlement, adjust the provision up or down through profit or loss unless another standard requires a different treatment.

Be careful with reimbursements. If an insurer or supplier will reimburse the company, the reimbursement asset is recognized only when it is virtually certain. Even then, the reimbursement asset is presented separately from the provision. The expense and reimbursement income may be presented net in the statement of profit or loss, but the statement of financial position should not hide the liability by netting it automatically.

For students, the key is to separate recognition from measurement. Recognition asks whether a provision exists. Measurement asks how much to record. Many wrong answers happen because the student jumps into arithmetic before deciding whether IAS 37 allows recognition at all.

Worked Example: Warranty Provision for a Riyadh Retailer

Assume Riyadh Home Electronics sells appliances with a one-year repair warranty. During 2026, the company sells 4,000 units. Based on past experience and current service data, management expects 6% of units to need minor repairs costing SAR 180 each and 1% to need major repairs costing SAR 900 each. The warranty exists because the sales already happened before year-end and customers have a legal right to repair service.

The expected warranty cost is calculated as follows:

The year-end entry is:

This is a provision, not a contingent liability, because all three IAS 37 recognition tests are met. The sales create a present obligation. Warranty outflows are probable when the population is viewed as a whole. The amount can be estimated reliably using historical repair patterns.

Notice what the accountant should not do. The company should not wait until each individual customer brings a broken appliance. Waiting would understate expenses in the year of sale and overstate profit. The cost belongs in the same period as the related revenue, which is why the warranty logic connects naturally to the [matching principle](/glossary#matching-principle) and the wider [accounting cycle](/learn/accounting-cycle-steps).

Worked Example: Legal Claim and Contingent Liability Disclosure

Now assume Gulf Fitout Co., based in Jeddah, is sued by a customer over a delayed commercial renovation. The customer claims SAR 600,000. At 31 December 2026, the company's lawyer says there is a 35% chance of losing and that the likely settlement, if the company loses, would be between SAR 350,000 and SAR 450,000. The case depends on evidence that will be reviewed in court after year-end.

This is not recorded as a provision at 31 December because the outflow is possible, not probable. The claim may still be important to users, so the company discloses a contingent liability unless management concludes the chance of payment is remote.

A practical note disclosure could say:

No journal entry is recorded at this stage. That surprises some students because a large SAR amount feels important. IAS 37 is not asking whether the case is scary. It is asking whether the recognition criteria are met.

If the facts change next year and the lawyer now says losing is probable with a best estimate of SAR 420,000, the accounting changes then. The company would recognize a provision in that later reporting period:

The change is not an error if the old assessment was reasonable based on the evidence available at the first reporting date. It is a change in estimate driven by new information.

Where Do Contingent Assets Fit Under IAS 37?

Contingent assets are the mirror image students often forget. A contingent asset is a possible asset that depends on uncertain future events outside the company's control. IAS 37 is deliberately cautious here because recognizing gains too early can make performance look better than it really is.

The rule is stricter for assets than for liabilities. A contingent asset is not recognized just because an inflow is probable. It is disclosed when an inflow is probable, and recognized only when realization is virtually certain. Once the inflow is virtually certain, the asset is no longer contingent.

Assume Eastern Tools Co. files an insurance claim after warehouse damage. The claim is SAR 300,000. At year-end, the insurer has not accepted liability, but correspondence suggests recovery is probable. The company may disclose a contingent asset if the amount is material, but it should not recognize a receivable yet. If the insurer formally approves SAR 280,000 after year-end and there is no remaining uncertainty, recognition becomes appropriate at that later point.

This asymmetry is intentional. For obligations, IAS 37 wants liabilities recorded when they are probable and measurable. For possible gains, it wants stronger certainty before recognition. That prevents profit from including income that may never arrive.

The practical takeaway is this: do not offset a provision against a possible recovery unless the reimbursement is virtually certain and separately recognized. A warranty provision, legal provision, or restoration provision should stand on its own. Possible insurance recoveries need their own recognition assessment.

Common Mistakes in Provisions vs Contingent Liabilities

The first mistake is treating every uncertainty as a provision. Management may be worried about future losses, lower demand, or a planned shutdown, but worry is not an obligating event. IAS 37 specifically does not allow provisions for future operating losses because the company has no present obligation at the reporting date.

The second mistake is ignoring constructive obligations. A company can create an obligation through a public policy, repeated practice, or announced plan. If customers reasonably expect refunds because the company has always honored them, the absence of a detailed legal clause does not automatically remove the obligation.

The third mistake is confusing probability with precision. A provision can be recognized even when the exact amount is uncertain, as long as a reliable estimate can be made. Students sometimes reject a provision just because there is a range of outcomes. IAS 37 expects estimates; it does not demand perfect certainty.

The fourth mistake is booking a contingent liability as if disclosure and recognition are interchangeable. They are not. A note disclosure informs users without changing profit or liabilities. A recognized provision changes both.

The fifth mistake is using old estimates without updating them. Provisions are reviewed at each reporting date and adjusted to reflect the current best estimate. A legal case, warranty pattern, or restoration plan can change. The accounting should change with the evidence.

The sixth mistake is using vague labels in the [general ledger](/glossary#general-ledger). “Miscellaneous provision” is not useful. Name the obligation clearly: warranty provision, legal provision, onerous contract provision, or restoration provision. Clear naming makes review and teaching much easier.

How to Practice IAS 37 for Exams and Work

To learn IAS 37 well, practice classifying facts before posting entries. Start every scenario with the same discipline: identify the past event, decide whether a present obligation exists, assess probability of outflow, check whether the amount is reliably measurable, then decide between recognition, disclosure, or no action.

For SOCPA, ACCA, CMA, and university exams, the marks usually sit in the judgment. The arithmetic in a warranty table is useful, but the examiner is testing whether you know why the warranty provision is recorded while the possible legal claim is disclosed. In work, the same logic becomes evidence: legal letters, service history, board approvals, customer communications, contracts, and management estimates.

You can connect this topic to other Accountery articles as you practice. If the scenario involves expected losses on receivables, compare IAS 37 with the IFRS 9 model in [expected credit loss IFRS 9](/learn/expected-credit-loss-ifrs-9). If the obligation comes from dismantling or restoring a leased site, revisit [IFRS 16 lease accounting lessee](/learn/ifrs-16-lease-accounting-lessee). The standards interact, but each has its own recognition trigger.

On Accountery, use practice exercises to train the sequence: classify the obligation, choose disclosure or recognition, calculate the SAR amount, then record the entry only when IAS 37 allows it. Once you can explain the classification before touching the debit and credit columns, provisions vs contingent liabilities becomes much less mechanical and much more professional.