6.3 Contingent Liabilities & Contingent Assets

6.3 Contingent Liabilities & Contingent Assets

Core Principle: IAS 37 enforces a deliberate asymmetric threshold between obligations and potential economic resources. While conservatism dictates that possible obligations are disclosed to alert capital markets to downside risk, potential economic inflows can never be recognized as assets until their realization is virtually certain.

In corporate financial reporting, commercial enterprises operate amidst legal actions, government audits, customer product disputes, and insurance claims. Determining whether an uncertain future event should be recognized as a balance sheet item, disclosed in the notes, or excluded from reporting entirely is a core technical competency tested on the CPA Australia Financial Reporting examination.

---

1. Contingent Liabilities: Dual Technical Definitions (IAS 37.10)

Under paragraph 10 of IAS 37, the term contingent liability encompasses two distinct legal and accounting scenarios:

1. A Possible Obligation: A possible obligation that arises from past events and whose existence will be confirmed only by the occurrence or non-occurrence of one or more uncertain future events not wholly within the control of the entity; OR
2. An Unrecognized Present Obligation: A present obligation that arises from past events but is not recognised because:
   • It is not probable that an outflow of resources embodying economic benefits will be required to settle the obligation; or
   • The amount of the obligation cannot be measured with sufficient reliability (an extremely rare occurrence in practice).

The Golden Rule of Contingent Liabilities (IAS 37.27)

An entity shall not recognise a contingent liability.

A contingent liability is never recognized as a liability on the Statement of Financial Position. Instead, it is disclosed in the notes to the financial statements, unless the possibility of an outflow of resources embodying economic benefits is remote.

---

2. Contingent Assets: Definition & Asymmetry (IAS 37.10, 31–35)

A contingent asset is defined under IAS 37.10 as:

A possible asset that arises from past events and whose existence will be confirmed only by the occurrence or non-occurrence of one or more uncertain future events not wholly within the control of the entity.

A classic example is an outstanding lawsuit initiated by the entity against a competitor for patent infringement, where the court outcome is subject to legal uncertainty.

The Prudence Principle & Asymmetric Recognition (IAS 37.31)

Paragraph 31 establishes the fundamental accounting rule:

An entity shall not recognise a contingent asset.

Recognizing a contingent asset on the balance sheet would result in the recognition of income that may never be realized, violating the qualitative characteristic of faithful representation and the exercise of prudence.

However, as the probability of recovery increases, the accounting treatment evolves:

• Probable Inflow ($P > 50\%$): The contingent asset is not recognized on the balance sheet, but must be disclosed in the notes to the financial statements (IAS 37.34).
• Virtually Certain Inflow ($P > 95\%$): The asset is no longer contingent! When the realization of income is virtually certain (e.g., a final, non-appealable court judgment has been handed down, or an insurer has formally accepted liability in writing), the asset is recognized as a genuine receivable on the Statement of Financial Position, and the corresponding gain is recognized in profit or loss.

3. The Probability Continuum: Comparative Matrix

The table below summarises the treatments. Only 'probable' (more likely than not) is defined in IAS 37; the 5% and 95% boundaries are informal rules of thumb used for teaching, not thresholds in the standard:

---

4. The Critical Exception: IFRS 3 Business Combinations

While IAS 37 prohibits the recognition of contingent liabilities, candidates must understand a major statutory exception codified in IFRS 3 Business Combinations (IFRS 3.22–23).

The Acquisition-Date Rule

In a business combination, the acquirer must recognize, as of the acquisition date, a contingent liability assumed in a business combination if:

1. It is a present obligation that arises from past events; and
2. Its fair value can be measured reliably.

The Critical Distinction: Under IFRS 3.23, the acquirer recognizes a contingent liability assumed in a business combination even if it is NOT probable ($P \le 50\%$) that an outflow of economic benefits will be required to settle the obligation!

This creates a sharp divergence from standalone IAS 37 accounting:

• Standalone Acquiree (prior to acquisition): Probability of outflow is 30% $\rightarrow$ IAS 37 prohibits recognition; disclose as a contingent liability.
• Consolidated Acquirer (at acquisition date): Fair value is $400,000 $\rightarrow$ IFRS 3 mandates recognition of a $400,000 liability on the acquisition-date consolidated balance sheet (which increases recognized goodwill).

Subsequent Measurement under IFRS 3.56

After initial recognition, the acquirer measures the recognized contingent liability at the higher of:

1. The amount that would be recognized in accordance with IAS 37 (the best estimate to settle the obligation); and
2. The amount initially recognized less, if appropriate, the cumulative amount of income recognized in accordance with the principles of IFRS 15 Revenue from Contracts with Customers.

---

5. Required Disclosures under IAS 37

Transparency is paramount for provisions and contingencies because of the subjective judgements involved in their measurement.

1. Provision Movement Schedule (Reconciliation) (IAS 37.84)

For each class of provision, an entity must disclose a tabular reconciliation showing:

• Opening carrying amount at the beginning of the period;
• Additional provisions made in the period, including increases to existing provisions;
• Amounts used (incurred and charged against the provision) during the period;
• Unused amounts reversed during the period (where an outflow is no longer probable);
• The increase during the period in the discounted amount arising from the passage of time (unwinding of discount) and the effect of any change in the discount rate; and
• Closing carrying amount at the end of the period.

Exam Tip — Comparative Information Relief: Paragraph 84 contains an explicit disclosure concession: Comparative information is NOT required for the provision movement reconciliation table. Preparers report only the current year's movements.

2. Qualitative & Narrative Disclosures (IAS 37.85)

For each class of provision, the notes must describe:

• A brief description of the nature of the obligation and the expected timing of any resulting outflows of economic benefits;
• An indication of the uncertainties about the amount or timing of those outflows (including key assumptions about future events);
• The amount of any expected reimbursement, stating the amount of any asset that has been recognized for that expected reimbursement.

3. Contingent Liability Disclosures (IAS 37.86)

Unless the possibility of any outflow in settlement is remote, an entity must disclose for each class of contingent liability:

• A brief description of the nature of the contingent liability;
• An estimate of its financial effect (measured applying the best estimate principles of IAS 37.36–52);
• An indication of the uncertainties relating to the amount or timing of any outflow; and
• The possibility of any reimbursement.

4. The Prejudicial Disclosure Exemption (IAS 37.92)

In extremely rare disputes with external parties (such as high-stakes commercial litigation), disclosing some or all of the information required by IAS 37 can be expected to prejudice seriously the position of the entity in the dispute.

In such cases, IAS 37.92 grants an exemption: the entity does not need to disclose the detailed calculations or financial estimates. However, the entity must disclose:

• The general nature of the dispute;
• The fact that the required information has not been disclosed; and
• The reason why disclosing the information would cause serious prejudice.

---

6. Comprehensive Worked Technical Scenarios

Scenario 1: Multi-Claim Legal Dispute (Evaluating Probability Bands)

At 30 June 2026, Horizon Mining Ltd is involved in three distinct legal disputes. Horizon's financial year ends on 30 June 2026. Legal counsel provides formal probability opinions for each case:

1. Claim A (Breach of Supply Contract): A supplier is suing Horizon for $3,000,000 for terminating a haulage contract. Legal counsel advises that Horizon has breached the agreement, and it is probable (80% likelihood) that the court will award damages of $2,200,000 in late 2026.
   • Accounting Treatment: Satisfies all three criteria of IAS 37.14 (present legal obligation from past breach, probable outflow of 80%, reliable estimate of $2,200,000). Recognize a Provision for Litigation of $2,200,000 on the Statement of Financial Position and debit legal expense in profit or loss.
2. Claim B (Groundwater Contamination Lawsuit): A regional agricultural group has sued Horizon for $10,000,000 alleging soil seepage. Senior hydrogeologists and independent legal barristers conclude that Horizon's containment barriers met statutory codes, but complex judicial precedents create legal exposure. Counsel estimates that Horizon's chance of losing is 35% (possible, but not probable). If lost, damages would be approximately $6,000,000.
   • Accounting Treatment: Because the outflow is possible (35%) but not probable ($P \le 50\%$), Criterion 2 of IAS 37.14 is not met. Horizon cannot recognize a provision on its balance sheet. Because the risk is not remote ($P \ge 5\%$), Horizon must disclose a contingent liability in the notes, describing the nature of the claim, an estimate of the $6,000,000 exposure, and the geological uncertainties.
3. Claim C (Frivolous Patent Action): A disgruntled former contractor alleges patent infringement and demands $5,000,000. Intellectual property barristers advise that the claim has no legal merit, assessing the probability of any financial award against Horizon at 2% (remote).
   • Accounting Treatment: The probability is remote ($P < 5\%$). Under IAS 37.86, no balance sheet provision is recognized, and no footnote disclosure is required.

---

Scenario 2: Counterclaim & Insurance Asset (Contingent Asset vs Virtually Certain)

In relation to Claim A above, Horizon Mining Ltd initiated two independent recovery actions:

1. Counterclaim Against Logistics Broker: Horizon filed a $1,500,000 counterclaim alleging misrepresentation by the intermediary broker. Legal counsel advises that Horizon has a strong case and that winning the award is probable (70% likelihood), with an expected judgment in mid-2027.
   • Accounting Treatment: This represents a contingent asset. Under IAS 37.31, recognition on the Statement of Financial Position is strictly prohibited because realization is not virtually certain. Under IAS 37.34, because the inflow is probable (>50%), Horizon must disclose the contingent asset in the notes, describing the nature of the claim and the $1,500,000 estimate. No income is recognized in profit or loss.
2. Commercial Liability Insurance Claim: Horizon lodged a formal insurance claim under its commercial liability policy to recover the $2,200,000 Claim A damages. On 26 June 2026, the insurance syndicate issued an unconditional written deed of settlement agreeing to pay $1,800,000 directly to Horizon upon receipt of the final court order for Claim A.
   • Accounting Treatment: Because the insurer has formally and unconditionally accepted liability in writing, recovery of the $1,800,000 is virtually certain ($P > 95\%$). The $1,800,000 is no longer a contingent asset. Horizon must recognize an Insurance Reimbursement Asset of $1,800,000 on its balance sheet (as a current asset) and may credit $1,800,000 against litigation expense in profit or loss.

---

Scenario 3: M&A Acquisition-Date Accounting under IFRS 3 vs IAS 37

On 1 October 2026, Titan Conglomerate Ltd acquires 100% of the voting shares of Vanguard Engineering Pty Ltd for $50,000,000.

At the acquisition date, Vanguard is defending an employment class-action lawsuit. Vanguard's legal advisers believe Vanguard has an 80% chance of successfully defending the suit, estimating only a 20% probability of an economic outflow. On a standalone basis under IAS 37, Vanguard disclosed the dispute as a contingent liability and recognized no balance sheet liability.

However, independent valuation specialists engaged by Titan determine that market participants would price the fair value of the legal liability at $750,000 at 1 October 2026.

Consolidated Accounting Treatment at Acquisition Date:

• Under IFRS 3.23, because the class-action reflects a present legal obligation resulting from past employment events prior to acquisition, and its fair value can be measured reliably at $750,000, Titan must recognize a $750,000 liability on the consolidated acquisition-date balance sheet.
• This $750,000 liability reduces the acquiree's net identifiable assets, which increases the recognized acquisition goodwill by $750,000.
• Under IFRS 3, the fact that an economic outflow is not probable ($P = 20\%$) does not prevent acquisition-date recognition!