A separate contract is not pooled with the original obligations, so there is nothing to allocate across. AI Suite's $10,500 price is recognized on its own.
First half is locked
42,309.37 + 5,950.68 = 48,260.05. These are the amounts already earned across Jan–Jun and they are not rewritten. Closed periods stay closed.
Recognized above its sale price
AI Suite was sold for 7,500 but is recognized at 9,642.00, because in a pooled modification its discount is shared across every remaining obligation rather than staying on its own line.
Core CRM · ratable
$85,320, recognized ratably over 365 days. Same daily amount every month, before and after July. March, a 31-day month, shows $7,246.36.
Premium Support · ratable
$12,000, a flat $1,000-a-month entitlement. March recognizes $1,019.18 for its 31 days.
AI Suite · separate contract
$10,500, purchased 1 Jul and recognized ratably over its own 184-day window at $57.0652/day.
AI Suite begins
July has 31 days at $57.0652/day = 1,769.02.
Everything is recognized
85,320 + 12,000 + 10,500 = 107,820, every dollar of the transaction price. Each column ties to its Step 4 allocation exactly.
Billed whole, up front
The entire $10,500 is invoiced when AI Suite is purchased on 1 Jul, even though it covers Jul–Dec. That is the billing-versus-revenue gap in one number.
Fully unwound
By 31 Dec the $10,500 billed has been fully earned, so deferred revenue on AI Suite closes at zero.
RevRec recipes / New performance obligation at SSP
Recognize revenue fora new performance obligation at SSP
A customer already under contract buys something new mid-term, priced at its standalone selling price. Here's how Chargebee RevRec handles it.
The problem
How a new performance obligation complicates revenue recognition
When the new item is distinct and priced at its standalone selling price, ASC 606-10-25-12 (and IFRS 15.20) requires an entity to account for the change as a separate contract rather than a modification of the one already in place.
What that means
The original contract's allocation is never reopened.
Every obligation already on it keeps the amount it was allocated at signing.
The new obligation gets its own transaction price,
its own allocation, and its own recognition schedule, independent of everything that came before it.
The example
The contract we will work through
Northwind Labs signs a one-year contract with Relay CRM on 1 January 2027: 90 seats of the core CRM plus a flat premium support fee. Six months in, on 1 July, they purchase the AI Suite add-on at its list price. Every number on this page comes from the order form below.
Sample order form
Order Form · Relay CRM
Customer: Northwind Labs, Inc. | Term: 1 Jan 2027 to 31 Dec 2027
CT-2027-0455 Executed 18 Dec 2026
1 · Original order (effective 1 Jan 2027)
Line
Product
Qty
Rate
Service window
Annual fee
IM-101
Core CRM (per seat)
90
$79 / mo
1 Jan – 31 Dec 2027
$85,320.00
IM-102
Premium Support (flat)
1
$1,000 / mo
1 Jan – 31 Dec 2027
$12,000.00
Original contract value
$97,320.00
2 · Mid-term purchase (effective 1 Jul 2027)
Line
Product
Qty
Rate
Service window
Fee
IM-103
AI Suite add-on
1
$1,750 / mo
1 Jul – 31 Dec 2027
$10,500.00
Grand total consideration
$107,820.00
Term & cancellation. Non-cancellable for the initial term. The mid-term purchase does not change the December 31 end date of the original lines.
Northwind Labs
VP Finance
Relay CRM, Inc.
Revenue Operations
Here's how each of the five ASC 606 steps applies to this contract.
STEP 01
Identify the contract
The question
Is the July purchase a new contract, or a change to the one signed in January?
A separate contract. AI Suite is distinct and priced at its standalone selling price, so it's accounted for as its own arrangement.
The SSP test
AI Suite lists at $20,000 / yr. The service window runs 1 Jul to 31 Dec, which is 184 days, so the prorated SSP is $20,000 × 184 / 365 = $10,082. Northwind's charged price is $10,500 (per the order form above), which is ~4.1% above the prorated SSP. Chargebee RevRec lets you configure an "at or near SSP" threshold to operationalize ASC 606's separate-contract test against your accounting policy. In this example, the threshold is set to 5%. The 4.1% variance falls within it, so the add-on passes and is treated as a separate contract.
What this step establishes
Original contract value in scope
$97,320.00
Modification date
1 Jul 2027
Modification type
Separate contract
How Chargebee RevRec handles the separation
Once the SSP test passes, Chargebee RevRec lets you choose whether to carve the new obligation out of the allocation pool within the same Order, or separate it into its own Order entirely.
STEP 02
Identify the performance obligations
The question
How many promises are in this arrangement now that AI Suite has been added?
Three: Core CRM, Premium Support, and AI Suite, each standing on its own.
Core CRM and Premium Support are unchanged from January, both recognized ratably over the year. AI Suite is recognized ratably too, but over its own six-month window rather than blended into the other two.
Priced below SSP, AI Suite would instead join the original two as a single modified arrangement. Step 4 works that case in full, alongside the one where it stands alone.
STEP 03
Determine the transaction price
The question
What's the transaction price now that AI Suite is part of the picture?
$97,320 for the original contract, unchanged, plus $10,500 for AI Suite. Both fixed, nothing to estimate.
What this step establishes
Original contract transaction price
$97,320.00
Separate contract (AI Suite)
$10,500.00
Total consideration across both
$107,820.00
STEP 04
Allocate the transaction price
The question
How does the $10,500 split across obligations?
It doesn't. AI Suite is a separate contract, so the full $10,500 belongs to it, and the original $97,320 keeps the allocation it already had.
Here's how the $107,820 splits by obligation.
A
B
C
1
Obligation
SSP basis
Allocated
2
Core CRM
$85,320.00
$85,320.00
3
Premium Support
$12,000.00
$12,000.00
4
AI Suite (separate contract)
$10,082.00
$10,500.00
5
Total
$107,402.00
$107,820.00
AI Suite's transaction price is its charged amount, $10,500, independent of SSP. The original obligations keep their existing allocation.
If AI Suite had been priced below SSP
Suppose Northwind had negotiated AI Suite down 25%, to $7,500 for the six months. That's below its $10,000 SSP for the window, so it fails the SSP test, and the July purchase becomes a modification of the original contract instead of a separate one. The standard's prospective method then runs in three moves.
Move 1|Freeze what is already earned: prior allocation × 181 pre-mod days ÷ 365
A
B
C
D
1
Line
Prior allocation
Fraction earned
Frozen
2
Core CRM
85,320.00
181 / 365
42,309.37
3
Premium Support
12,000.00
181 / 365
5,950.68
4
Frozen through 30 Jun
48,260.05
Move 2 & 3|Remaining pool = 104,820 total − 48,260.05 frozen = 56,559.95, split by SSP over the last 184 days
A
B
C
1
Line
Remaining SSP
Post-mod allocated
2
Core CRM
43,010.63
41,132.75
3
Premium Support
6,049.32
5,785.20
4
AI Suite
10,082.19
9,642.00
5
Remaining pool
56,559.95
Premium Support is the one to watch. Nobody renegotiated it, yet its full-year revenue moves from $12,000 to $11,735.88 (5,950.68 frozen + 5,785.20 after), since the new discount spreads over the remaining term and pulls a little off every line. That's the difference the SSP test decides.
STEP 05
Recognize the revenue
The question
What does monthly revenue look like once AI Suite is added?
The original $266.63 per day keeps recognizing, unchanged, all year. AI Suite adds a new $57.07 per day layer starting 1 July.
All three obligations are recognized ratably, so revenue is daily. Core CRM and Premium Support run at a combined $266.63 per day across all 365 days. AI Suite runs at $57.07 per day across its own 184-day window from 1 July.
Monthly recognized revenue, by obligation
Core CRMPremium SupportAI Suite
$0
$4K
$8K
$12K
Jul 1 · AI Suite purchased
$8K
$7K
$8K
$8K
$8K
$8K
$10K
$10K
$10K
$10K
$10K
$10K
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Bar heights vary slightly by month because recognition is daily: a 31-day month earns more than a 30-day month.
The recognition schedule
Every column below sums to its Step 4 allocation, and the grand total ties to the $107,820 transaction price.
E|= B + C + D (total recognized in the period)
A
B
C
D
E
1
Period
Core CRM
Premium Support
AI Suite
Total recognized
2
2027-01
7,246.36
1,019.18
0.00
8,265.54
3
2027-02
6,545.10
920.55
0.00
7,465.65
4
2027-03
7,246.36
1,019.18
0.00
8,265.54
5
2027-04
7,012.60
986.30
0.00
7,998.90
6
2027-05
7,246.36
1,019.18
0.00
8,265.54
7
2027-06
7,012.60
986.30
0.00
7,998.90
8
2027-07
7,246.36
1,019.18
1,769.02
10,034.56
9
2027-08
7,246.36
1,019.18
1,769.02
10,034.56
10
2027-09
7,012.60
986.30
1,711.96
9,710.86
11
2027-10
7,246.36
1,019.18
1,769.02
10,034.56
12
2027-11
7,012.60
986.30
1,711.96
9,710.86
13
2027-12
7,246.34
1,019.17
1,769.02
10,034.53
14
Full year
85,320.00
12,000.00
10,500.00
107,820.00
Billing versus revenue on AI Suite
AI Suite is invoiced in full, $10,500, the moment it's purchased in July, but earned only over the six months it covers. The gap sits as deferred revenue and unwinds to zero by December.
E|closing deferred revenue = B (opening deferred revenue) + C (billed) − D (recognized)
A
B
C
D
E
1
Period
Opening Deferred Revenue
Billed
Recognized
Closing Deferred Revenue
2
2027-07
0.00
10,500.00
1,769.02
8,730.98
3
2027-08
8,730.98
0.00
1,769.02
6,961.96
4
2027-09
6,961.96
0.00
1,711.96
5,250.00
5
2027-10
5,250.00
0.00
1,769.02
3,480.98
6
2027-11
3,480.98
0.00
1,711.96
1,769.02
7
2027-12
1,769.02
0.00
1,769.02
0.00
Disclaimer This page is not accounting advice.
Start building
See Chargebee RevRec do this on your contracts
Chargebee RevRec runs the SSP test on every mid-term purchase, keeps separate contracts separate, and reallocates only when the rules require it, with every number traceable back to the order form.