Welcome to the World of Revenue!
In your CIMA F2 journey, Revenue is one of the most important chapters you will study. Why? Because revenue is the "top line" of the financial statements. It’s often the first thing investors look at to see if a business is growing. In this section, we focus on IFRS 15 Revenue from Contracts with Customers.
Don't worry if this seems tricky at first! Financial standards can sound like a different language, but we’re going to break it down using a simple 5-step model. Think of this model as a checklist that tells you exactly when and how much money you can officially call "revenue."
The Golden Rule: The 5-Step Model
To recognize revenue, you must follow these five steps in order. A great way to remember them is the mnemonic: I Identify Determine Allocate Recognize (I Intend Doing All Revenue). Or simply think of it as the "I-I-D-A-R" process.
Step 1: Identify the Contract with the Customer
Before we talk about money, we need a valid agreement. A contract doesn’t always have to be a 50-page legal document; it can be written, oral, or even implied by standard business practice. For a contract to exist under IFRS 15, it must meet these criteria:
- Both parties have approved it.
- Each party's rights can be identified.
- Payment terms are clear.
- The contract has commercial substance (it actually changes the company’s risk or cash flows).
- It is probable that the company will collect the money.
Step 2: Identify the Performance Obligations
A "performance obligation" is just a fancy term for a promise to provide a good or service. Some contracts have only one promise (selling a loaf of bread), while others have many (selling a phone plus a two-year data plan).
The Key Test: Is it "Distinct"?
A good or service is distinct if:
1. The customer can benefit from it on its own.
2. The promise to transfer it is separate from other promises in the contract.
Example: If you buy a laptop and a software subscription, these are usually distinct. But if you hire a builder to build a wall, the bricks and the labor are NOT distinct because they are used together to create one single output (the wall).
Step 3: Determine the Transaction Price
This is the amount of money the company expects to receive. It’s not always as simple as the price tag! You must consider:
- Variable Consideration: If the price depends on future events (like bonuses for early completion or discounts for bulk buying), you must estimate the amount using either the "expected value" or the "most likely amount."
- Significant Financing Component: If the customer pays much later (or much earlier) than they receive the goods, you might need to adjust for the time value of money using an interest rate.
- Non-cash consideration: If they pay you in something other than cash (like shares), use the fair value of what you received.
Step 4: Allocate the Transaction Price
If a contract has more than one performance obligation (from Step 2), you need to split the total price (from Step 3) between them. We do this based on their Stand-alone Selling Prices (SSP).
The Formula:
To find the amount for one item:
\( \text{Allocated Price} = \frac{\text{SSP of Item}}{\text{Total of all SSPs}} \times \text{Total Transaction Price} \)
Example: You sell a Bundle (Phone + Service) for \$500. Separately, the Phone costs \$450 and the Service costs \$150 (Total SSP = \$600).
The Phone's share: \( \frac{450}{600} \times \$500 = \$375 \).
Step 5: Recognize Revenue when (or as) the entity satisfies a Performance Obligation
This is the moment you finally record the revenue in the books! This happens when control of the promised good or service is transferred to the customer.
Performance Satisfied Over Time:
Revenue is recognized over time if any one of the following three criteria is met:
1. The customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs (e.g., routine cleaning or payroll processing).
2. The entity's performance creates or enhances an asset that the customer controls as the asset is created or enhanced (e.g., building on customer-owned land).
3. The performance does not create an asset with an alternative use to the entity, and the entity has an enforceable right to payment for performance completed to date (e.g., specialised consulting reports or custom machinery).
Performance Satisfied at a Point in Time:
If a performance obligation is not satisfied over time, it is satisfied at a point in time. Indicators that control has passed include: the customer has a present obligation to pay, legal title has transferred, physical possession has transferred, significant risks and rewards of ownership have transferred, and the customer has formally accepted the asset.
Specific Complex Areas
Principal vs. Agent
Sometimes a company sells goods on behalf of someone else (like eBay or a travel agent).
- Principal: If the company controls the good before it is transferred to the customer, it acts as a principal and records the gross amount as revenue.
- Agent: If the company just arranges for another party to provide the goods, it acts as an agent and only records the net commission or fee as revenue.
Sale with Right of Return
When customers have the right to return goods within a specified period, the entity does not treat the return right as a separate performance obligation, but rather as variable consideration:
- Revenue: Recognize revenue only for the goods that are expected not to be returned.
- Refund Liability: Recognize a liability for the cash expected to be refunded to customers.
- Asset for Right to Recover: Recognize an asset (and adjust cost of sales) for the right to recover goods from customers on settling the refund liability, measured at the inventory's former carrying amount less expected recovery costs.
Warranties
Not all warranties are treated the same:
- Assurance-type: A guarantee that the product complies with agreed specifications. This is NOT a separate performance obligation (it is accounted for as a provision under IAS 37).
- Service-type: An optional extended warranty or service provided beyond basic compliance assurance. This IS a distinct performance obligation; part of the transaction price must be allocated to it and recognized as revenue over the warranty coverage period.
Repurchase Agreements
If a company "sells" an asset but agrees (or has the option) to buy it back later, it might not be a sale at all! If the company will buy it back for more than the original price, it is usually treated as a secured loan (financing arrangement) rather than revenue.
Common Pitfalls to Avoid
- Mixing up Steps 2 and 4: Students often forget to check if items are "distinct" before trying to allocate prices.
- Ignoring Time Value: If a payment is due in 2 years, you must discount it to present value if the financing component is significant.
- Recognizing everything at once: If an obligation is satisfied over time, you cannot recognize all revenue up front. You must measure progress using input (e.g., costs incurred) or output methods.
Key Takeaways for Section B
- Control is King: Revenue is recognized when control passes, not necessarily when risk passes or cash is received.
- The 5 Steps are Mandatory: You must apply them in sequence.
- Distinct Promises: Identify whether you are selling one thing or a package of several distinct items.
- Allocation: Always use the relative Stand-alone Selling Price method to split the transaction price.
- Returns and Warranties: Apply variable consideration to return rights and separate service-type warranties as distinct obligations.