Revenue Recognition for SaaS Companies
Revenue Recognition for SaaS Companies – How IFRS 15 applies to every SaaS contract type – multi-element bundles, setup fees, usage-based pricing, professional services, free trials, discounts, and the judgements that determine when each euro is earned.
5 Key Takeaways From This Page
IFRS 15 (Revenue from Contracts with Customers) has been effective since 2018 and applies to any Estonian company that reports under IFRS or that has investor or lender requirements specifying IFRS-compliant accounts. It replaced all previous revenue standards with a single comprehensive framework.
A performance obligation is a distinct promise to transfer a good or service to a customer. Identifying all the separate promises in a SaaS contract – access to software, setup, support, training, professional services – determines how the total price is split and when each portion is recognised.
When a contract contains multiple performance obligations, the total transaction price is allocated based on each obligation’s standalone selling price (SSP) – the price the company would charge if it sold that obligation independently. SSP is estimated using observable data where possible.
Performance obligations are satisfied either over time (continuously, like subscription access) or at a point in time (one-off, like a setup completion or software delivery). These produce fundamentally different revenue timing patterns.
Usage-based pricing, volume discounts, refund rights, and performance bonuses create variable consideration – amounts the company may receive but cannot be certain of. IFRS 15 requires these to be estimated and constrained to amounts unlikely to reverse.
What does IFRS 15 mean for a SaaS company’s revenue recognition? Every contract with a customer must be analysed through the five-step model: identify the contract, identify distinct performance obligations within it, determine the transaction price, allocate the price to each obligation based on standalone selling prices, and recognise revenue as each obligation is satisfied. For most SaaS businesses, the core challenge is handling the mix of subscription access (over time), setup fees (point in time or over time), and variable elements like usage-based pricing. This page works through each scenario in full.
Section 1 – The IFRS 15 Five-Step Model Applied to SaaS
Each step in detail – what it means and how it applies to a typical SaaS contract
Step 1 – Identify the Contract
A contract under IFRS 15 is an agreement that creates enforceable rights and obligations. For SaaS, this is typically: a signed MSA (Master Service Agreement) plus an order form, an accepted online terms of service at the time of payment, or a click-through agreement at checkout. The contract must have commercial substance – there must be a genuine exchange of consideration. Free plans with no payment are not contracts under IFRS 15.
Important: IFRS 15 requires that it be probable the company will collect the consideration it is entitled to. If there are serious doubts about collectability, the contract does not qualify and no revenue is recognised until collection is probable.
| Contract Element | Examples in SaaS | Revenue Recognition Implication |
|---|---|---|
| Signed MSA + order form | Enterprise customers; annual contracts > €5,000 | Full IFRS 15 analysis; likely multi-element |
| Online checkout (click-through ToS) | SMB and self-serve customers; monthly plans | Simpler single-element; standard recognition |
| Free trial with auto-conversion | Customer signs up free, converts to paid | Contract inception depends on enforceable rights and obligations and the IFRS 15 contract criteria, not the first payment date. Recognise revenue as the contracted services are provided. |
| Verbal or email agreement | Informal arrangements with early customers | Risky – document as written contract as soon as possible |
| Letter of intent (not yet binding) | Pre-sales negotiations | Not a contract – no revenue until binding agreement |
Step 2 – Identify Performance Obligations
A performance obligation exists for each distinct good or service promised in the contract. A good or service is distinct if: (a) the customer can benefit from it on its own or together with other readily available resources, and (b) it is separately identifiable from other promises in the contract. In SaaS, most contracts contain multiple promises – the question is which of these are distinct enough to be separate performance obligations.
| Promise in SaaS Contract | Distinct? | Reasoning | Performance Obligation? |
|---|---|---|---|
| Access to the SaaS platform (subscription) | Yes | Customer can use it independently; core value | Yes – over time |
| Onboarding session (1 x video call) | Likely No | Customer cannot separately benefit; highly interdependent with subscription | Bundle with subscription – same recognition |
| Implementation / migration services | Depends on whether the service is distinct under IFRS 15 | Assess whether the customer can benefit from the service separately and whether it is separately identifiable from the SaaS subscription | Recognise over time or at a point in time depending on how the performance obligation is satisfied |
| Dedicated customer success manager | Maybe | If generic support: No. If specific deliverables agreed: Yes | Analyse case by case |
| Training materials (self-serve knowledge base) | No – usually | Included in subscription; not separately sold | Part of subscription obligation |
| Custom integrations / API development | Depends on the IFRS 15 distinctness criteria | A custom integration is not automatically a separate performance obligation | Recognition depends on whether the obligation is distinct and whether the over-time recognition criteria are met |
| Technical support SLA (premium tier) | Yes – if distinct tier sold | Separately priced; customer can benefit independently | Yes – over time across the support period |
Step 3 – Determine the Transaction Price
The transaction price is the amount of consideration the company expects to be entitled to in exchange for delivering the promised goods or services. For simple fixed-price SaaS, this is straightforward – the contract value is the transaction price. Complexity arises when the contract contains variable elements: discounts, refund rights, usage-based components, milestone payments, or consideration payable to the customer.
| Pricing Element | Transaction Price Impact | Recognition Approach |
|---|---|---|
| Fixed monthly/annual fee | Equal to contract value | Recognise ratably over contract term |
| Volume discount (e.g. 20% off above 100 seats) | Reduce transaction price by expected discount | Estimate discount expected and apply to full contract price |
| Refund right (no-questions-asked 30-day refund) | Constrain by probability of refund | Create refund liability; release if refund period expires |
| Usage-based overage (€10 per API call above limit) | Variable consideration; actual-usage recognition may apply under the relevant allocation rules or the right-to-invoice practical expedient | Where estimation is required, include only amounts for which a significant reversal of cumulative revenue is highly unlikely; reassess at each reporting date |
| Noncash consideration | Measure at fair value in accordance with IFRS 15; where fair value cannot be reasonably estimated, use the standalone selling price of the goods or services promised to the customer | Measure the noncash consideration received or promised; recognise the allocated revenue when or as the performance obligation is satisfied, not automatically at contract inception |
| Customer loyalty points / future discounts | Separate performance obligation only if the customer receives a material right | Allocate consideration to the material right; recognise it as the related goods or services are transferred, or when the option expires |
Step 4 – Allocate the Transaction Price
When a contract has multiple performance obligations, the transaction price is allocated to each obligation in proportion to its standalone selling price (SSP). The SSP is the price at which the company would sell that obligation separately to a standalone customer. If the company sells each element independently, observable SSPs can be used. If not, SSP must be estimated.
Transaction Price Allocation – €12,000 Enterprise Contract (12-Month Subscription + Implementation)
| Performance Obligation | SSP (Standalone) | Allocation % | Allocated Amount | Recognition |
|---|---|---|---|---|
| SaaS subscription (12 months @ €800/month) | €9,600 | 66.67% | €8,000 | €666.67/month for months 1–11; €666.63 in month 12 |
| Implementation project (estimated 40 hrs @ €120/hr) | €4,800 | 33.33% | €4,000 | If distinct: over time when the relevant criteria are met; otherwise at the point control transfers |
| Total contract price | €14,400 total SSP; €12,000 transaction price | 100% | €12,000 | Allocation uses unrounded SSP ratios |
In this example, the customer received a €2,400 discount on the combined package vs standalone prices. IFRS 15 requires the discount to be allocated proportionally to both obligations – not entirely to the subscription or entirely to the implementation. The implementation is allocated €4,000 rather than its €4,800 SSP, reflecting its share of the combined discount. If the company recognised the full €4,800 implementation revenue at project completion, it would overstate revenue in the implementation period and understate it over the subscription term.
Step 5 – Recognise Revenue as Performance Obligations Are Satisfied
Revenue is recognised when (or as) each performance obligation is satisfied – when control transfers to the customer. The critical question is: is this obligation satisfied over time or at a point in time?
Satisfied continuously as the customer has access to the software. Recognised ratably (1/n per period) unless another method better reflects delivery.
If services are delivered over a project period and the customer receives value as work progresses, use percentage-of-completion method based on hours or milestones.
If the customer receives a distinct deliverable (a configured system, a completed migration), recognise at the point of delivery and acceptance.
A perpetual licence to use software as-it-stands, with no ongoing update obligation, is recognised at the point the licence is granted and the customer can use it.
Section 2 – Revenue Recognition Timing by Contract Type
Visual timelines showing when different SaaS contract components generate revenue
Monthly vs Annual vs Multi-Year – Recognition Timing
The timing of revenue recognition varies significantly across contract types. The visual below shows how each contract type generates P&L revenue across a 12-month period for a contract starting 1 January.
| Contract / Item | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Monthly sub (€100/month × 12) | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 |
| Annual sub paid upfront (€1,200) | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 | €100 |
| Distinct setup service completed in January (€400) | €400 | |||||||||||
| Implementation (50% done Mar, 100% Jun) | €300 | €300 | ||||||||||
| 2-year contract (€600/year × 2) | €50 | €50 | €50 | €50 | €50 | €50 | €50 | €50 | €50 | €50 | €50 | €50 |
An interesting feature of the table above: a monthly subscriber and an annual subscriber paying the same amount per month generate identical P&L revenue each month. The only difference is that the annual subscriber’s cash was received upfront (creating a deferred revenue liability that releases monthly), while the monthly subscriber’s cash arrives in the same month as recognition. From a revenue recognition perspective, the two are identical. From a cash flow perspective, annual billing is significantly better – which is why SaaS companies typically offer a discount to encourage annual plans.
Multi-Element Contract – Full Recognition Schedule
When a contract contains multiple performance obligations allocated at different amounts with different timing, the recognition schedule becomes the central document for the engagement. The schedule below illustrates a €12,000 enterprise contract with both subscription and implementation components.
Multi-Element Contract – Revenue Recognition Schedule (12 Months)
Contract: Enterprise customer, €12,000 total
Performance Obligation 1: SaaS subscription
Allocated: €8,000 | Monthly recognition: €666.67 (months 1–11); €666.63 (month 12)
Performance Obligation 2: Implementation project
Allocated: €4,000 | Method: milestone completion
Milestone 1 (50% complete, end of month 2): €2,000 recognised in M2
Milestone 2 (100% complete, end of month 3): €2,000 recognised in M3
Month 1: Subscription €666.67 + Implementation €0 = €666.67
Month 2: Subscription €666.67 + Implementation M1 €2,000 = €2,666.67
Month 3: Subscription €666.67 + Implementation M2 €2,000 = €2,666.67
Month 4 onwards: Subscription €666.67 only
Months 4–11 (8 months × €666.67): €5,333.36
Month 12: €666.63
Total 12-month recognition: €666.67 + €2,666.67 + €2,666.67 + €5,333.36 + €666.63 = €12,000
* Equals total contract price – confirms schedule is complete
* Cash received on contract signing (month 1): €12,000
* Balance of cash that is deferred revenue at end of month 1:
€12,000 received − €666.67 recognised = €11,333.33 deferred
Section 3 – Setup Fees and Onboarding Revenue
The most commonly mis-recognised element – when setup fees are distinct and when they are not
The Central Question: Is the Setup Fee Distinct?
Setup and onboarding fees are one of the most judgment-intensive revenue recognition areas in SaaS. Whether they are recognised at completion or spread over the subscription term depends entirely on whether the setup constitutes a distinct performance obligation – meaning whether the customer could benefit from the setup independently, separate from the ongoing subscription.
| Setup Fee Type | Distinct? | Recognition Method | Journal Entry Timing |
|---|---|---|---|
| Simple account creation (automated) | Usually not a separate performance obligation | Allocate and recognise the related consideration as the underlying subscription service is provided; the recognition period must be determined from the enforceable contract and related performance obligations | Release to revenue monthly; not at activation |
| Manual data migration | Assess whether the service is distinct and whether the IFRS 15 over-time criteria are met | If distinct, recognise over time where the IFRS 15 over-time criteria are met; otherwise when control transfers. If not distinct, recognise with the combined performance obligation. | Recognise over time or at a point in time based on how control of the service transfers |
| Custom configuration with customer-specific rules | Distinctness must be assessed case by case | Recognition depends on whether the performance obligation satisfies the IFRS 15 over-time criteria | Follow the recognition pattern of the identified performance obligation; completion-only recognition is appropriate only when it is satisfied at a point in time |
| Standard onboarding call (1 hour introduction) | No – routine setup support | Spread over subscription term | Bundle with subscription; do not separate |
| Technical integration build (API connections) | Only if both IFRS 15 distinctness criteria are met | If distinct, assess over-time recognition; otherwise recognise at transfer of control. If not distinct, combine with the related service. | Follow satisfaction of the identified performance obligation; go-live alone does not determine timing |
| Training programme (5 sessions, own team) | Separate pricing does not determine distinctness; assess whether the customer can benefit and whether the promise is separately identifiable | If distinct, allocate consideration even when training is included in a package; recognise as the training is delivered | Recognise allocated revenue as distinct sessions are delivered; otherwise follow the combined obligation |
Non-Distinct Setup Fee – Amortisation Example
Setup fee received: €500 (not distinct – bundled with subscription)
Monthly subscription: €99/month
Total contract consideration: €500 + (€99 × 12) = €1,688
Option A: Recognise setup fee at contract inception (INCORRECT under IFRS 15)
Month 1: €500 + €99 = €599 (overstates month 1 revenue)
Months 2–12: €99 each (understates ongoing revenue)
Option B: Recognise the consideration allocated to the non-distinct setup activity over the period in which the related performance obligation is satisfied. The period should not automatically be based on estimated customer lifetime.
Historical data: average customer stays 24 months
The setup fee should not automatically be amortised over a 24-month estimated customer lifetime. Revenue must follow the period over which the related performance obligation is satisfied under IFRS 15.
Subscription monthly recognition: €99/month
Total monthly recognised: €99 + €20.83 = €119.83/month for 24 months
If the contract is terminated, reassess the remaining contract liability under IFRS 15. The remaining balance should not automatically be released to revenue merely because the customer cancels.
* The deferred portion is a liability until the subscription and expected life passes
* Update expected customer life estimate annually based on actual churn data
Section 4 – Variable Consideration and Usage-Based Pricing
How to estimate, constrain, and update variable revenue components
What Counts as Variable Consideration
Variable consideration is any element of the transaction price that is not fixed. In SaaS, the most common sources are: usage-based overages (customer pays more if usage exceeds a base amount), volume discounts on seats or transactions, performance bonuses tied to outcomes, refund rights, and penalties for service level failures. Each must be estimated and constrained under the variable consideration constraint.
| Variable Element | Example | Estimation Approach | Constraint Test |
|---|---|---|---|
| Usage overages | €0.05 per API call above 10,000/month | Assess the applicable variable-consideration rules, including whether the usage relates specifically to a distinct service period | Recognition may be based on actual usage where the amount allocated to the satisfied performance obligation is consistent with IFRS 15 |
| Volume discounts | 10% off if customer exceeds 50 seats | Most likely amount (will they exceed 50 seats this year?) | Reflect the expected contractual discount and restrict revenue so that a significant reversal is highly unlikely. Apply the discount to the purchases covered by its terms; do not automatically discount the whole contract. |
| Refund rights | 30-day money-back guarantee | Expected value of refunds based on historical refund rate | Recognise net of expected refunds; release when refund period expires |
| Performance SLA credits | 5% rebate if uptime falls below 99.9% | Expected value based on historical uptime performance | Reduce consideration by expected SLA credits and restrict revenue so that a significant reversal is highly unlikely. Credits reduce revenue; they are not additional revenue to include or exclude. |
| Early termination fees | Customer pays 3 months of remaining fees if cancels early | Most likely outcome (usually recognise on termination) | Recognise when cancellation confirmed and amount fixed |
Usage-Based Revenue – The Practical Approach
Pure usage-based pricing (like pay-per-API-call or per-minute pricing with no minimum) creates a specific recognition challenge: the consideration depends entirely on the customer’s future behaviour, which cannot be fully estimated at contract inception. The right-to-invoice practical expedient applies only where the amount the entity has a right to invoice corresponds directly with the value to the customer of the entity’s performance completed to date. It is not automatically available for every usage-based SaaS contract. – i.e., actual usage-based revenue each month.
Usage-Based Revenue Recognition – Monthly Actual Basis
Contract: Pay-per-use API platform, €0.05/call, billed monthly in arrears
January actual API calls: 48,000
January revenue recognised: 48,000 × €0.05 = €2,400
February actual API calls: 62,000
February revenue recognised: 62,000 × €0.05 = €3,100
* No estimation required – invoice equals delivery
* But: if contract has a minimum monthly fee (€500/month minimum):
Minimum fee is recognised regardless of actual usage
If usage billing exceeds minimum: recognise higher amount
January: max(€500, €2,400) = €2,400 recognised
Minimum fee acts as floor; usage billing is variable above it
Hybrid model (flat fee + overages):
Base subscription: €299/month (recognise €299 each month)
Included: 5,000 API calls/month
Overage: €0.05/call above 5,000
March actual calls: 8,200 = 3,200 overage calls
March overage revenue: 3,200 × €0.05 = €160
March total recognised: €299 + €160 = €459
Section 5 – Multi-Year Contracts and Significant Financing
When long-term contracts contain a financing component – and how to account for it
Multi-Year Contracts – Recognition Over the Full Term
Multi-year SaaS contracts (2-year, 3-year) are common at the enterprise tier and are often offered with a total price discount relative to purchasing individual years. Recognition is straightforward: the total contract price is allocated to each year (or to each performance obligation across years) and recognised ratably. The deferred revenue balance at any point represents the remaining unearned contract value.
| Contract Type | Recognition Pattern | Deferred Revenue Behaviour | Key Accounting Risk |
|---|---|---|---|
| Monthly rolling contract | Recognise as the monthly service is provided | Advance payments for undelivered service are contract liabilities; billing or payment after delivery may create a receivable or contract asset | Churn creates immediate revenue loss; no smoothing |
| Annual contract, upfront payment | €1,200 ÷ 12 = €100/month | Balance starts at €1,200, reduces by €100/month, zero at year-end | If cancellations spike, deferred balance needs adjustment |
| 2-year contract, upfront payment | Total ÷ 24 months | Balance starts at 24 months’ value; reduces monthly | Long deferred revenue window; document expected customer life |
| 2-year contract, annual invoicing | Recognise revenue as the performance obligations are satisfied; invoicing timing does not by itself determine revenue recognition | Year 1 deferred: invoice 1 value; Year 2 invoiced in month 12 | Ensure Y2 invoice is not premature revenue recognition |
| Enterprise with annual true-up | Base + variable usage | Deferred for base; variable recognised monthly as usage occurs | Separate fixed and variable elements; apply constraint test |
The Significant Financing Component – When It Applies to SaaS
IFRS 15 requires adjustment for a significant financing component when there is a significant difference between the amount of promised consideration and the cash selling price of the goods or services. In SaaS, this arises if a company collects a multi-year contract payment significantly in advance and the time value of money is material.
A practical expedient in IFRS 15 allows companies to ignore the financing component if the period between when the customer pays and when the good or service is transferred is one year or less. Most SaaS contracts – even annual ones – fall within this one-year window, making the adjustment unnecessary. Multi-year upfront contracts may require analysis.
| Scenario | Financing Component? | Practical Action |
|---|---|---|
| Monthly subscription – payment and delivery same month | No | No adjustment needed |
| Annual subscription – payment at start, delivery over 12 months | No – one-year practical expedient applies | No adjustment needed; use expedient |
| 2-year subscription – full payment at start | Maybe – analyse if interest rate and amount are material | If a significant financing component exists, recognise interest expense and increase the contract liability before recognising the related service revenue |
| 3-year+ contract with full upfront payment | Likely yes at large contract values | Apply IFRS 15.60–65 where significant financing exists: recognise interest expense separately and increase the contract liability; recognise service revenue as performance occurs |
| Instalment plan slower than delivery | Financing exists – seller is financing the customer | Where significant financing exists, recognise service revenue at its cash selling price equivalent and recognise interest income separately over the financing period |
Section 6 – Free Trials, Discounts, and Promotional Pricing
How to handle revenue recognition when the commercial price is not what it appears
Free Trial Periods
Free trials require careful handling: are they part of the contract or a separate pre-contract marketing activity? Under IFRS 15, if the trial is unconditional (the customer can leave after the trial with no obligation), the trial is a marketing activity – no contract exists during the trial period, and no revenue is recognised. The contract begins only when the customer agrees to pay.
If the trial is conditional – for example, the trial requires a credit card that will be charged unless the customer cancels – a contract exists from the start of the trial. Do not recognise expected subscription payments merely by probability-weighting potential conversions. Revenue recognition depends on enforceable consideration and satisfaction of the IFRS 15 contract and performance-obligation requirements. In practice, most SaaS companies use the probability that the customer converts to paid and recognise zero revenue during the trial period, with revenue beginning at the first payment.
| Trial Type | Contract During Trial? | Revenue During Trial | Revenue After Conversion |
|---|---|---|---|
| Free trial, no credit card required | No revenue contract during a genuinely free trial with no enforceable payment commitment | None for a standalone free trial | Recognise as paid services are provided once the contract criteria are met, irrespective of payment date |
| Free trial with credit card, auto-convert | A card alone does not establish an IFRS 15 revenue contract; assess enforceable rights and obligations | Zero if there is no enforceable consideration; if a committed paid contract includes a free period, allocate consideration over the promised services | Recognise as the contracted services are provided; conversion probability alone does not determine recognition |
| Freemium plan (permanent free tier) | Acceptance of terms alone does not establish an IFRS 15 revenue contract where there is no consideration | Zero for a genuinely free standalone tier | Recognise the premium consideration as the contracted premium services are provided |
| Trial with guaranteed refund option | A refund right does not automatically prevent a qualifying contract | Recognise revenue as services are provided, net of expected refunds and subject to the variable-consideration constraint; recognise a refund liability | Expiry of refund rights does not justify recognising revenue for services still to be delivered |
Discounts and Promotional Pricing
When a company charges a discounted price – a launch promotion, a customer referral discount, an annual plan saving – the transaction price is the discounted amount. There is no separate revenue recognition for the ‘undiscounted’ value of the service. The discount is the commercial price agreed; the undiscounted price is not relevant to revenue recognition.
The complexity arises when a discount on one element is effectively a material right for a future purchase – for example, a SaaS company offering a 40% discount on a second year of subscription if the customer renews. This renewal option at a meaningful discount may be a separate performance obligation: the customer is effectively receiving an option to renew at a below-market price, and a portion of the year-one price must be allocated to this option and deferred until the option is exercised or lapses.
If your SaaS contract offers a renewal at a price that is meaningfully below the then-current market price (not just a standard loyalty discount), IFRS 15 requires you to assess whether this constitutes a material right – a separate performance obligation. The test: would the customer pay the original contract price specifically to get the right to renew at the discounted price? If yes, you must allocate a portion of the original transaction price to this option and recognise it only when the option is exercised or expires. For most early-stage SaaS with standard renewal pricing, this is not material. For enterprise contracts with significant locked-in renewal discounts, it requires analysis.
Section 7 – Journal Entries for Common SaaS Revenue Scenarios
The complete accounting entries for the scenarios most SaaS companies encounter
Scenario A – Monthly Subscription, Payment and Recognition in Same Month
Monthly Subscription – €199 Paid and Recognised
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Cash / Stripe | €199.00 | |
| Revenue – Monthly Subscriptions | €160.48 | |
| VAT Payable – KMD (24%, included in €199) | €38.52 |
* Payment received and revenue recognised in the same month. No deferred revenue. VAT of 24% applied if customer is Estonian; reverse charge if EU B2B; no VAT if non-EU or UK.
Scenario B – Annual Subscription, Upfront Payment
Annual Subscription – €2,388 Paid on 1 January (Monthly rate €199)
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Cash / Stripe | €2,388.00 | |
| Deferred Revenue – Annual Subs | €1,925.81 | |
| VAT Payable – KMD (24%, included in €2,388) | €462.19 |
* Cash received upfront. Revenue deferred in full. €1,925.81 ÷ 12 = €160.48 recognised each month as subscription service is delivered (€160.53 in month 12 to clear rounding). VAT on full invoice amount collected immediately and remitted on January KMD.
Annual Sub – Monthly Revenue Release (each month Jan–Dec)
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Deferred Revenue – Annual Subs | €160.48 in Jan–Nov; €160.53 in Dec | |
| Revenue – Annual Subscriptions | €160.48 in Jan–Nov; €160.53 in Dec |
* No cash movement – just deferred to recognised. Repeated 12 times. After month 12, deferred balance is zero.
Scenario C – Multi-Element: Subscription + Implementation
Contract Received – €12,000 (Subscription + Implementation)
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Cash | €12,000.00 | |
| Deferred Revenue – Annual Subs (allocated €8,000) | €8,000.00 | |
| Deferred Revenue – Implementation (allocated €4,000) | €4,000.00 |
* Full cash received. Both performance obligations deferred. Note: VAT treatment depends on timing of supply – consult accountant for jurisdiction-specific VAT on multi-element contracts.
Implementation Milestone 1 – 50% Complete (Month 2)
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Deferred Revenue – Implementation (only if over-time recognition applies and 50% progress is reliably measured) | €2,000.00 | |
| Revenue – Professional Services | €2,000.00 |
* 50% of implementation value recognised at milestone 1 completion and customer acceptance. Milestone 2 (remaining €2,000) recognised at full completion.
Monthly Subscription Release – Each Month
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Deferred Revenue – Annual Subs | €666.67 in months 1–11; €666.63 in month 12 | |
| Revenue – Annual Subscriptions | €666.67 in months 1–11; €666.63 in month 12 |
* Subscription portion (€8,000 ÷ 12) released monthly. Month 12 release is €666.63 to eliminate rounding difference. Simultaneous with milestone recognition in months 2 and 3.
Scenario D – Usage Overage (Hybrid Model)
Month with Usage Overage – Base €299 + €160 Overage
| Account | Debit (DR) | Credit (CR) |
|---|---|---|
| Cash / Stripe (base + overage invoice) | €459.00 | |
| Revenue – Monthly Subscriptions | €299.00 | |
| Revenue – Usage Add-ons | €160.00 |
* Base subscription recognised as agreed; overage recognised in month of usage (invoiced in arrears). Both are fixed and determinable at invoice date – no estimation required once usage is measured.