Skip to content
ObligaAI

What Is Revenue Recognition?

On this page

Revenue recognition is the accounting principle that decides when a business records revenue and how much it records. It is not the same as sending an invoice or collecting cash. Revenue is recognised when the business transfers the goods or services it promised, in the amount it expects to be entitled to in exchange.

Two standards set the rules for most companies. Under US GAAP it is ASC Topic 606, Revenue from Contracts with Customers. Under IFRS Accounting Standards it is IFRS 15, issued by the IASB in May 2014 alongside the introduction of Topic 606 into the FASB Codification. IFRS 15 applies to annual reporting periods beginning on or after 1 January 2018.

Both standards start in the same place: the contract. That is why revenue recognition matters to contracts teams as much as to accountants. If the contract terms are read wrongly, the revenue numbers will be wrong too.

This page is general information, not accounting advice. The right treatment depends on the applicable standard, the facts and the wording of each contract. Check specific cases with your auditors or accounting advisers.

Revenue Recognition in Plain Terms

The core idea is simple. A business records revenue as it does what it promised, not when the paperwork is sent or the money arrives.

The IFRS Foundation describes the objective as reporting useful information about “the nature, amount, timing and uncertainty of revenue and cash flows” from a contract with a customer. Put differently, the numbers should show what the business has actually earned so far.

Three questions sit underneath every revenue entry:

  • What did we promise? The goods or services in the contract.
  • How much will we get for it? The price, including any amounts that can move.
  • When did we deliver it? At a single point in time, or over a period.

Each answer comes from the contract, its amendments and any side agreements. That makes the contract the source document for revenue.

Get up to 9% back on your contracts

How the Five-Step Model Works

ASC 606 and IFRS 15 use the same five-step model. The ACCA’s summary of the IFRS 15 steps gives practical examples of each.

Each of the five steps depends on what the contract and its amendments actually say.

Step 1: Identify the contract with the customer

A contract is an agreement that creates enforceable rights and obligations. It can be written, oral or implied by customary business practice. The parties must have approved it, it must have commercial substance, and the customer must have the ability and intention to pay. Related contracts may need to be combined when they were negotiated as a package.

Step 2: Identify the performance obligations

A performance obligation is a distinct promise to transfer a good or service. A software subscription, an implementation project and a support plan sold together may be three obligations or one. It depends on whether each is distinct in the context of the contract.

Step 3: Determine the transaction price

The transaction price is the amount the business expects to be entitled to. It includes fixed fees and variable consideration such as discounts, rebates, refunds, performance bonuses and usage-based fees. A significant financing component can also adjust the price.

Step 4: Allocate the transaction price

The price is spread across the performance obligations based on their relative standalone selling prices. A bundle discount is usually spread across all obligations unless there is evidence it relates to only some of them.

Step 5: Recognise revenue when each obligation is satisfied

Revenue is recorded when, or as, control of the good or service passes to the customer. Some obligations are satisfied at a point in time, such as delivering equipment. Others are satisfied over time, such as a monthly service, where progress is measured with an input or output method.

Variable Consideration and Contract Modifications

Two areas cause most of the judgement calls: amounts that can change, and contracts that change.

Variable consideration

When part of the price is uncertain, the business estimates it. ACCA’s summary describes two methods: an expected value across a portfolio of similar contracts, or the single most likely amount when there are only two possible outcomes. The estimate is then constrained. Under IFRS 15, variable consideration is included only to the extent it is highly probable that a significant reversal of revenue will not occur later.

Common sources of variable consideration in commercial contracts include:

  • usage tiers and overage fees;
  • volume rebates and tiered discounts;
  • refunds and credits the contract says the customer may be owed;
  • milestone or performance bonuses;
  • price concessions and rights of return.

Contract modifications

A contract modification is a change in scope, price or both that the parties approve. According to PwC’s revenue guide, approval can be in writing, oral or based on customary business practice. Depending on the facts, a modification is accounted for in one of three ways:

  1. As a separate contract, when it adds distinct goods or services at their standalone selling prices.
  2. Prospectively, as if the old contract ended and a new one began, when the remaining goods or services are distinct.
  3. With a cumulative catch-up, when the remaining goods or services are not distinct, for example a partly completed single obligation.

This is where a contract amendment or a side letter becomes an accounting event. If finance does not know a change was agreed, the revenue schedule will not reflect it.

Why Revenue Recognition Matters

Revenue is usually the largest number in the income statement and one of the most watched. Getting it right affects reported results, forecasts, covenants, commissions and tax.

It also matters operationally. KPMG’s revenue handbook for software and SaaS notes that ASC 606 requires entities to make significant judgements and estimates, and that contract modifications continue to raise questions. Those judgements are only as good as the inputs. The inputs are contract terms.

Typical problems that start in the contract, not in the ledger:

  • an annual price escalation clause that nobody applied;
  • a minimum purchase commitment or take-or-pay term that changes what the customer owes;
  • a promotional discount that expired but kept being given;
  • a renewal on different terms that never reached the billing system.

Each can affect both what is recognised and what is billed. When terms are missed, the result can be contract value leakage: value the contract says you earned that never shows up in invoices.

A Worked Example With Illustrative Figures

The figures below are illustrative only. They show the mechanics, not how any specific contract should be accounted for.

A software company signs a one-year contract on 1 January:

  • SaaS subscription for 12 months: list price $120,000
  • Implementation service, delivered in January: list price $30,000
  • Bundle discount: the customer pays $135,000 in total
  • Usage overage: $2 per transaction above 50,000 transactions a year

Step 1. One approved contract with enforceable terms.

Step 2. Assume the subscription and the implementation are distinct. That gives two performance obligations.

Step 3. The fixed price is $135,000. The company expects about 55,000 transactions, which would mean $10,000 of overage. Because usage is uncertain, it assesses the constraint. For simplicity, assume the usage-based fee relates only to the subscription and is recognised as the usage occurs.

Step 4. Standalone selling prices total $150,000. The $135,000 is allocated in proportion:

ObligationStandalone priceShareAllocated price
Subscription$120,00080%$108,000
Implementation$30,00020%$27,000
Total$150,000100%$135,000

Step 5. Implementation revenue of $27,000 is recognised in January when the work is done. Subscription revenue is recognised over time at $9,000 a month. Overage revenue is recognised when transactions exceed the threshold.

Illustrative: the bundle discount is spread across both obligations, so January carries $36,000 and each later month $9,000.

Now add an amendment. On 1 July the parties sign a change adding 20 more users for the remaining six months at the standard price. If that is a distinct service at standalone selling price, it is a separate contract. If the amendment had instead cut the price of the existing seats, it would follow the modification rules above. Either way, the revenue team has to know the amendment exists and what it says.

Revenue Recognition vs Billing, Cash and Deferred Revenue

These terms are related but not the same.

  • Billing is when an invoice is issued. A customer may be billed annually in advance while revenue is recognised monthly.
  • Cash collection is when payment arrives. It can come before or after revenue is recognised.
  • Deferred revenue (a contract liability) arises when a customer pays or is billed before the business has performed.
  • Unbilled revenue (often a contract asset or receivable) arises when the business has performed and earned revenue but has not yet invoiced it.
  • Contract value measures such as annual contract value and total contract value are commercial metrics. They are not revenue figures under ASC 606 or IFRS 15.

A mismatch between the three timelines (earned, billed, collected) is normal. A mismatch between the contract and the bill is a problem.

How Contract Data Feeds Revenue Recognition

Revenue teams need a reliable view of what each contract actually says, including every amendment. In practice that means tracking:

  • fees, price lists and payment terms;
  • escalators and their effective dates;
  • usage tiers, minimums and overage rates;
  • discounts and when they expire;
  • milestones and acceptance terms;
  • renewal terms, notice periods and changes at renewal;
  • service levels and any credits owed to the customer.

Many teams keep this in spreadsheets or rely on memory. That breaks down as contract volumes grow and amendments pile up. Contract obligation management and contract intelligence aim to make those terms searchable and traceable to the source clause, so finance can check the revenue schedule and the billing against the signed agreement.

Where ObligaAI Fits

ObligaAI is not an accounting system and does not book revenue. Your ERP, billing and revenue tools keep doing that. ObligaAI works beside them as an overlay, not a replacement.

On the customer side, ObligaAI’s revenue leakage check reads fees, escalators, usage tiers, discounts, minimums, milestones and renewal terms into plain-language obligations, each with a confidence score and a link to the exact passage. It then matches contracts, order forms, renewals, price lists and usage reports against invoices. Where they differ, it shows the clause, the invoice, the shortfall, its dollar value and a recommended action. Examples include price uplifts not applied, usage under-billed, discounts past expiry and milestones not invoiced.

Findings are advisory. They are suggestions with the clause attached, never automatic changes. No invoice is changed until the right person signs it off. For revenue teams, that gives a contract-backed view of terms to check against billing and the revenue schedule. The accounting judgement stays with your finance team and auditors.

You can start free with no credit card, or start a conversation about how it would sit beside your current setup.

Revenue Recognition Questions Answered

Is revenue recognised when the invoice is sent?

Not necessarily. Revenue is recognised when a performance obligation is satisfied. An invoice can be issued before, at the same time as, or after that point.

Are ASC 606 and IFRS 15 the same?

They share the same five-step model and core principle and were introduced together in 2014. Some details and wording differ between them, so check the standard that applies to your reporting.

How do price escalators affect revenue recognition?

A contractual escalator changes the transaction price for future periods. If it is missed, both billing and recognised revenue can be understated. The treatment depends on the contract wording and the facts.

Does a contract amendment always change revenue?

Not always. An approved change in scope or price is a contract modification, and it may be treated as a separate contract, prospectively or with a cumulative catch-up. Some amendments change only administrative terms and have no revenue effect.

What is variable consideration?

Any part of the price that can change, such as usage fees, discounts, rebates, refunds or performance bonuses. It is estimated and then limited by a constraint so that revenue is not likely to reverse later.

Is this page accounting advice?

No. It is general information. Treatment depends on the applicable standard, the facts and the contract wording. Speak to your auditors or accounting advisers about specific cases.

Sources

Live links added above: the four sources (found by web search on 12 November 2026) and the ObligaAI contract obligation glossary page (confirmed live on 5 November 2026). The terms below match ObligaAI glossary entries drafted in this project. Link them once the pages are published and the slugs are confirmed.

Anchor text in articleSuggested slugStatus
contract amendment (two mentions)/glossary/contract-amendmentDrafted; not confirmed live
side letter/glossary/side-letterDrafted; confirm slug
price escalation clause/glossary/price-escalationDrafted; confirm slug
minimum purchase commitment/glossary/minimum-purchase-commitmentDrafted; confirm slug
take-or-pay/glossary/take-or-payDrafted; confirm slug
contract value leakage/glossary/contract-value-leakageDrafted; confirm slug
annual contract value; total contract value/glossary/annual-contract-value; /glossary/total-contract-valueDrafted; confirm slugs
contract intelligence/glossary/contract-intelligenceDrafted 11 Nov; not confirmed live
notice periods/glossary/contract-notice-periodDrafted; confirm slug

ASC Topic 606 has no link, because no official FASB page was confirmed. If you want one, link to the FASB Accounting Standards Codification page for Topic 606 after checking

More in Billing & Finance

Get up to 9% back on your contracts

Start with a few contracts of your own and see what ObligaAI finds.