What Does IFRS 15 Cover?

1. Why Revenue Recognition Matters

If you’ve ever seen a company book revenue too early, you’ve seen why IFRS 15 matters. Revenue is not just a number that appears when cash moves. It is a signal about when a business has actually earned its income.

That distinction sounds small, but it changes everything:

• Profit can look stronger or weaker depending on timing
• Investors and lenders may misunderstand performance
• Different contracts can be accounted for in very different ways
• Comparing companies becomes misleading if the rules are not followed carefully

Think of it like the Darbar Square of accounting: from a distance, everything can look like one open space. But once you walk through it carefully, you realize it is made of distinct areas, each with its own purpose and boundary. IFRS 15 works the same way. It asks you to stop treating every sale as the same moment and instead ask: what was promised, what was delivered, and when was control actually transferred?

By the end of this course, you will be able to explain why revenue recognition is really about earning, not just billing. You’ll understand the logic behind timing, see why contracts need to be unpacked carefully, and start recognizing the pattern behind common revenue scenarios instead of memorizing exceptions.

That is the anchor for everything that follows:

Revenue is recognized when the customer gets the benefit, not when the invoice is convenient.

Once that idea clicks, the rest of IFRS 15 stops feeling like a rulebook and starts looking like a system.

2. The Core Logic of IFRS 15

Remember earlier when we said revenue is about earning, not just billing? IFRS 15 is the framework that turns that idea into a disciplined way of thinking. It does not begin with the invoice. It begins with a simple question:

What exactly did the customer get, and when did they get it?

That question matters because revenue is really about control. Not just physical possession, and not just legal paperwork. Control means the customer can direct the use of what was promised and receive the benefit from it.

If that sounds abstract, think of it like borrowing a book from a neighbor. The moment the book is in your hands, you can read it, mark it, lend it, and use it for your purpose. The key issue is not who owns it on paper, but who can actually use it. IFRS 15 is asking a similar question about goods and services: who has the power to benefit from what was delivered?

1) Revenue follows performance

A business earns revenue when it performs its side of the agreement. In plain language, if the company still owes the customer something important, then some or all of the revenue may need to wait.

This is the first irreducible idea: an obligation must be satisfied before revenue can be recognized.

Think about ordering a custom meal at a restaurant. If the kitchen has only taken your order, nothing has been earned yet. If the meal is prepared but never served, the experience is still incomplete. The value is recognized when the customer actually receives what was promised. That is the same logic IFRS 15 applies to contracts.

2) A contract is not one thing — it is a bundle of promises

A major source of confusion is treating a contract like a single block. IFRS 15 says that is usually too simple. A contract often contains multiple promises, and each promise may need to be considered separately.

Imagine buying a new laptop that comes with installation, training, and a service plan. You are not really buying one undivided thing. You are receiving a bundle of different benefits:

• the laptop itself
• the setup help
• the training
• the future support

Each part may be delivered at a different time. So revenue may need to be spread across those parts rather than recognized all at once.

Remember earlier when we said the subject is about understanding the system, not memorizing the rule? This is one of the biggest system-level ideas in IFRS 15: separate promises often create separate timing questions.

3) Price and timing are related, but not the same

Another first principle: the amount of revenue and the timing of revenue are connected, but they are not identical questions.

A contract may say the customer will pay a fixed amount. That tells you the total economic value. But it does not automatically tell you when that amount should be recognized.

Think of a water tank. The total capacity of the tank tells you how much water it can hold. But the capacity does not tell you how fast the water is flowing in or out at any moment. In the same way, contract price tells you the total consideration, but revenue recognition still depends on how and when performance happens.

This is why two contracts with the same price can produce very different accounting results if the delivery pattern is different.

4) Timing depends on transfer, not intention

Businesses often intend to earn revenue earlier than the accounting allows. But IFRS 15 does not ask what management hoped would happen. It asks what actually happened in economic terms.

The central timing test is whether control has transferred either:

• over time, if the customer receives and uses the benefit as the business works, or
• at a point in time, if control shifts in a single moment

A useful analogy is a bridge being built. If the customer is effectively getting benefit as the bridge rises brick by brick, the value is being transferred throughout the process. But if the customer receives nothing useful until the bridge is complete and usable, then the benefit arrives at the end.

This is the same idea showing up again: revenue follows the customer’s benefit, not the company’s effort alone.

5) Delivery is not always the end of the story

A lot of people assume that once something is handed over, revenue is obvious. But IFRS 15 pushes deeper. Even after delivery, the seller may still have important obligations, restrictions, or rights that affect whether control truly passed.

For example:

• the seller may need to install or activate the item
• the customer may not be able to use it yet
• the seller may retain a significant right to take back the item if conditions are not met

So the accounting question is not just “Was it physically delivered?” but “Was the customer actually in control of the benefit?”

Think of buying a phone that is locked until activation is complete. You may physically hold it, but if it cannot yet function for you, control has not fully shifted in the economic sense. That is the kind of distinction IFRS 15 wants you to notice.

6) The standard is built to prevent surface-level thinking

IFRS 15 is designed to stop a very human mistake: confusing the appearance of a sale with the substance of a sale.

That is why the standard keeps pushing you to ask:

• What was promised?
• What was actually delivered?
• Did the customer get the benefit yet?
• Is there anything left that is important enough to delay revenue?

These questions work across industries because they are not tied to one type of contract. They are based on the underlying logic of exchange.

Here is the simplest way to hold it in your mind:

The big picture

If you remember nothing else from this section, remember this:

IFRS 15 is a system for matching revenue to real performance.

That is why it feels more analytical than older, more mechanical rules. It makes you slow down and separate the contract into its economic parts.

Once that clicks, later topics like performance obligations, transaction price, allocation, and timing stop looking like isolated terms. They become pieces of the same engine.

And that is the real shift: not learning a list of rules, but learning to see the contract the way IFRS 15 sees it — as a sequence of promises, benefits, and transfers.

3. Building the Five-Step Model

Remember earlier when we said IFRS 15 is a system for matching revenue to real performance? Now we can see the mechanism that system uses. The five-step model is not a list to memorize in isolation. It is a thinking path that helps you answer one question with discipline:

How much revenue belongs here, and when does it belong?

Each step removes one layer of ambiguity. If you think of a contract as a box full of mixed parts, the five-step model helps you open the box, sort the parts, and decide which part of the value should be recognized now and which part must wait.

Why the model exists

A contract can hide complexity in plain sight. One customer might sign one agreement, pay one amount, and still receive several different things over time. If you treat that as a single event, revenue can be distorted. The five-step model prevents that by forcing you to separate:

• what the contract is
• what was promised
• how much value is involved
• how that value should be shared
• when each part is earned

That sequence matters. It mirrors how reality itself unfolds: first the agreement exists, then the promises become visible, then the price is understood, then the promises are matched to value, and only then do we ask when revenue is recognized.

Think back to the earlier idea of a contract as a bundle of promises. The five-step model is how IFRS 15 unpacks that bundle without losing the thread.

Step 1: Identify the contract with a customer

This first step asks a very basic but crucial question: Is there a real agreement that creates enforceable rights and obligations?

That sounds obvious, but it matters because revenue accounting should only begin when there is something real to account for. A vague intention, a handshake with no enforceability, or a draft arrangement is not the same as a contract that creates duties on both sides.

This is where accounting begins to separate business talk from economic commitment. A company may expect a sale, but IFRS 15 waits for a contract that actually binds the parties.

You can think of this like two people agreeing to exchange keys and rent for an apartment. Until the agreement is real enough that both sides can rely on it, there is no accounting structure to recognize. The model begins with enforceability because revenue needs a solid foundation.

Step 2: Identify the performance obligations

This is where the contract gets unpacked into individual promises. Earlier, we saw that a laptop may come with installation, training, and support. Step 2 asks: which promises are distinct enough to count separately?

This step is often where the first real insight appears. A contract is not automatically one deliverable just because it was signed once. A performance obligation exists when the customer can benefit from a good or service on its own, or together with other readily available resources, and when the promise is separately identifiable.

In plain language: if the customer would notice the difference between receiving the parts together versus separately, that may signal separate obligations.

This matters because each obligation may have its own timing. A delivered product may be recognized now, while future support is recognized later. So Step 2 is really about sorting time into pieces.

A useful way to think about it

Imagine a ticket to a concert that includes:

• entry to the show
• a backstage tour before the performance
• a merchandise voucher

These are not all the same thing. Some are delivered at a moment, some over a period, and some only when used. Step 2 asks you to notice those differences before trying to recognize revenue.

Step 3: Determine the transaction price

Once you know what the customer is promised, you ask: what is the total value of the deal?

This sounds like simple arithmetic, but in IFRS 15 it is often more than the sticker price. The transaction price may include fixed amounts, variable amounts, discounts, rebates, bonuses, penalties, or other forms of consideration.

This is where timing and uncertainty begin to matter together.

A company may think it will receive a bonus for meeting a target. But if that bonus is uncertain, the accounting question becomes: how much of that expected amount is actually probable enough to include?

This is one reason IFRS 15 feels like a system rather than a rule list. It does not just ask what the contract says. It asks what the contract is really worth after you consider uncertainty and likelihood.

Remember the water tank analogy from Section 2? Step 3 is about the total amount of water in the system, but not yet about which pipe it flows through. We still need to decide how to divide that value across the promises.

Step 4: Allocate the transaction price

Here the model becomes more interesting. If one contract has multiple performance obligations, and one total price, how do we split the value?

IFRS 15 says the price should be allocated based on relative standalone selling prices. In plain language, each promise should receive a share of the total price that reflects what it would be worth on its own.

This is one of the most important connecting ideas in the standard.

If you buy a bundle of software, setup, and support for one combined fee, the fee is not just left as a single lump. It gets distributed across the components based on their standalone values. That allocation is what later determines how much revenue is recognized for each component as it is delivered.

This is where the model starts to reveal its logic:

1. identify the promises
2. find the total price
3. split the price fairly across the promises
4. recognize each piece when its promise is fulfilled

That sequence is the backbone of IFRS 15.

Why allocation matters so much

Without allocation, a business could accidentally or intentionally shift value toward the parts that are delivered sooner, making revenue appear earlier than it should. Allocation keeps the accounting anchored to the economics of what was actually promised.

That is the same anti-illusion principle we saw earlier: IFRS 15 keeps the appearance of a sale from overpowering its substance.

Step 5: Recognize revenue when or as performance obligations are satisfied

This is the final step, but it is not the place where the model starts. That is important. Many people begin with the timing question. IFRS 15 begins earlier because timing only makes sense after the contract has been understood.

Revenue is recognized when the customer gains control of the promised good or service. Sometimes that happens at a point in time. Sometimes it happens over time.

This is where all the earlier ideas come together:

• If there is one obligation, revenue may come in one moment.
• If there are several obligations, revenue may be spread out.
• If the price is uncertain, the amount may need care.
• If the promises are distinct, the revenue must be tracked separately.

So Step 5 is not “the revenue step” in isolation. It is the result of all the earlier steps working together.

How the five steps connect in real life

Let’s make the whole system visible.

Suppose a company sells a machine with installation and a one-year service plan.

At first glance, it looks like one sale. But the five-step model asks different questions:

• Is there a valid contract? Yes.
• Are there separate promises? Machine, installation, service plan.
• What is the total price? One combined amount.
• How should the price be split? Based on relative standalone values.
• When is revenue recognized? The machine may transfer at delivery, installation may be recognized when completed, and service over time.

Now the picture changes completely. The contract is no longer a single blob. It is a timeline of obligations.

That is the breakthrough: IFRS 15 turns a contract into a sequence of earned value events.

A Nepal-relevant example: telecom bundles

Imagine a customer in Kathmandu buys a phone plan that includes a handset, SIM activation, and twelve months of service. On the surface, it may look like one purchase. But the accounting logic sees more structure.

The handset may be transferred now, activation may be a small separate service, and the monthly network service continues over time. The total consideration cannot just be dumped into one moment because the customer does not receive everything at once.

That kind of bundled arrangement is exactly why the five-step model exists. It helps you see where value is delivered now and where it is still being earned later.

The hidden pattern underneath all five steps

If you zoom out, the five-step model is really doing three things:

1. It identifies the legal and economic container — the contract
2. It separates the contents — the performance obligations
3. It matches value to delivery — the transaction price and recognition timing

That is the whole logic of IFRS 15 in motion.

The aha moment

Remember earlier when we said revenue recognition is about earning, not just billing? The five-step model is the practical expression of that idea.

It stops you from asking, “When did we invoice?” and forces you to ask, “What did we actually deliver, and what part of the price belongs to that delivery?”

That is why this model is so powerful. It does not just tell you what to record. It trains you to think like the standard:

• start with the contract
• unpack the promises
• measure the consideration
• allocate the value
• recognize revenue as control transfers

Once you can see that chain, IFRS 15 begins to feel less like a compliance exercise and more like a map of economic reality.

And once that happens, the next challenge becomes much more interesting: what makes a performance obligation distinct, and how do we tell when control has truly transferred? That is where the next section becomes sharper.

4. From Rule to Professional Judgment

You’ve now done something important: you’ve moved from seeing IFRS 15 as a set of terms to seeing it as a way of thinking.

That is the real shift.

Earlier, revenue looked like a number tied to an invoice. Then it became clearer: revenue follows performance, not paperwork. After that, the five-step model gave you the engine — contract, promises, price, allocation, recognition. Now all of that starts to feel less like accounting vocabulary and more like professional judgment.

What you can see now

You are no longer asking only, “What does the rule say?”

You can now ask the deeper questions that accountants actually rely on:

• What was really promised?
• What did the customer actually receive?
• Is this one promise or several?
• Does revenue belong now, or later?
• Is the appearance of a sale hiding unfinished performance?

That is a big upgrade in thinking. It means you can look at a contract and stop being trapped by the surface wording.

Remember earlier when we said IFRS 15 prevents surface-level thinking? That idea is now yours. You know why a bundled deal is not always one unit, why control matters more than billing, and why timing depends on delivery of benefit. Those are not separate facts anymore. They are one system.

What changes for you now

This is where understanding becomes capability.

Before, a contract scenario may have felt like a test of memory. Now it becomes a test of clarity. You can slow down a transaction, separate the promises, and ask where the value truly belongs. That means you can read revenue scenarios with more confidence and explain your reasoning without guessing.

You now think more like someone who can diagnose revenue timing instead of just repeating definitions.

The final idea to keep

If you remember only one thing from this course, let it be this:

IFRS 15 is not asking when cash moved. It is asking when value was earned.

That single idea connects everything:

• why revenue matters
• how control works
• why contracts must be unpacked
• how the five-step model fits together

So when you meet a new scenario, don’t look for the quickest label. Look for the underlying relationship between promise, performance, and transfer. That is the professional habit IFRS 15 is trying to build.

And now you have it.

You’re not just reading the standard anymore — you’re starting to see the logic inside it. That is what professional judgment feels like: not certainty about every answer, but confidence that you know how to think.