Welcome to Provisions and Events After the Reporting Period!

In the world of Financial Reporting, things aren't always black and white. Sometimes, a company knows it owes money, but it’s not exactly sure how much or when it will have to pay. Other times, something important happens just after the year ends, and we have to decide if we should change our "old" accounts to reflect this "new" news.

This chapter covers two very important rules: IAS 37 (Provisions, Contingent Liabilities and Contingent Assets) and IAS 10 (Events after the Reporting Period). Don't worry if these sound a bit technical—we're going to break them down into simple, everyday concepts!

1. What is a Provision? (IAS 37)

A provision is simply a liability where there is uncertainty about the timing or the amount. Think of it like this: If you know you have to pay your electricity bill of \$100 next Tuesday, that’s an accrual. But if you think you might lose a court case and have to pay "somewhere around \$10,000" at some point in the future, that’s a provision.

The Three Golden Rules for Recognition

You can only record a provision in the financial statements if you meet all three of these criteria. If even one is missing, you cannot record it as a provision!

1. Present Obligation: You have a duty to pay because of something that happened in the past. This can be:
- Legal: Based on a contract or law.
- Constructive: Based on the company's past actions (e.g., a "no questions asked" refund policy that customers expect you to honor).

2. Probable Outflow: It is more likely than not (greater than 50% chance) that you will have to pay money.

3. Reliable Estimate: You must be able to calculate a sensible figure for the amount.

Memory Aid: "P.O.R."

To remember the rules, think of POR:
- Present Obligation
- Outflow (Probable)
- Reliable Estimate

How do we measure a Provision?

We should use the "best estimate."
- For a single obligation (like one big lawsuit), we use the most likely outcome.
- For a large population of items (like product warranties on thousands of small gadgets), we use an expected value (a weighted average of all possible outcomes).

Quick Tip: If the time value of money is significant (the payment is far in the future), we must discount the provision to its present value using this formula:
\( \text{Present Value} = \frac{\text{Future Value}}{(1 + r)^n} \)

2. Specific Cases in IAS 37

There are a few "famous" scenarios that ACCA examiners love to test:

Onerous Contracts

This is a contract where the unavoidable costs of fulfilling it are higher than the benefits you'll get from it.
Example: You signed a lease for a shop for \$5,000 a month, but you've closed the shop and can't sub-let it. You are "stuck" paying for nothing. You must recognize a provision for the least net cost of exiting the contract.

\n\n

Restructuring

\n

When a company decides to close a division or move its headquarters, it's called restructuring. You can only create a provision for these costs when:\n
1. There is a detailed formal plan.\n
2. You have raised a valid expectation in those affected (e.g., you've started implementing the plan or announced it to the staff).

\n

Common Mistake to Avoid: Never include costs like retraining staff or marketing the new image in a restructuring provision. These relate to the future, not the past!

\n\n
Key Takeaway:
\n

A provision is a "maybe" in amount or time, but a "must" in obligation. If it's not probable (>50%), it's not a provision!

\n\n

3. Contingent Liabilities and Assets

\n

What if you don't meet all three "POR" rules? We then look at Contingencies.

\n\n

Contingent Liabilities

\n

A contingent liability is a "possible" obligation (less than 50% likely). \n
- Probability > 50%: Record a Provision in the accounts.\n
- Probability 5% to 50% (Possible): Don't put it in the accounts, but disclose it in the notes.\n
- Probability < 5% (Remote): Do nothing. Forget about it!

\n\n

Contingent Assets

\n

These are potential inflows of money (like a court case you are winning). We are much stricter here because we don't want to look "too good" before the money actually arrives (Prudence!).\n
- Virtually Certain (>95%): Record as an Asset.\n
- Probable (50% - 95%): Disclose in the notes.\n
- Possible or Remote (< 50%): Do nothing. Do not disclose!

\n\n

4. Events After the Reporting Period (IAS 10)

\n

Imagine your year-end is 31 December. You are busy preparing the accounts in January, but the accounts won't be officially signed (authorized) until March. Anything that happens between 31 December and the date of authorization is an "event after the reporting period."

\n\n

Adjusting Events

\n

These are events that provide evidence of conditions that existed at the year-end. We must go back and change our 31 December numbers.

\n

Real-World Example: A customer owed you \$1,000 on 31 December. In February, they go bankrupt. This is an adjusting event because they were likely in financial trouble on 31 December; we just didn't know it yet. We should write off that debt in the year-end accounts.

Non-Adjusting Events

These are events that relate to conditions that arose after the year-end. We do not change the 31 December numbers, but if they are big, we explain them in the notes.

Real-World Example: A fire destroys your warehouse on 15 January. On 31 December, the warehouse was perfectly fine. This is a non-adjusting event. You don't change the assets in the accounts, but you must tell the shareholders about the fire in the notes.

The "Going Concern" Exception

If an event happens after year-end that means the company is no longer a going concern (it can't survive), you must change the entire basis of the accounts to the "break-up basis," even if the event happened after the year-end. This is the ultimate adjusting event!

Quick Review Box:

Adjusting: Evidence of old conditions (e.g., court case settled, bad debts, stock sold for less than cost).
Non-Adjusting: Brand new conditions (e.g., dividends declared, fires/floods, issuing new shares).

Summary of Key Points

1. Provisions: Record when an obligation is probable and can be estimated.
2. Contingent Liabilities: Disclose if possible; ignore if remote.
3. Contingent Assets: Disclose if probable; record if virtually certain.
4. IAS 10 Adjusting: "Existing condition" = Change the numbers.
5. IAS 10 Non-Adjusting: "New condition" = Note only.

Don't worry if this seems tricky at first! The key is to always ask yourself: "Did this condition exist at the balance sheet date?" and "Is it more likely than not?" Master these two questions, and you'll master this chapter!