The problem
Why a ramp complicates revenue recognition
A ramp deal is a single multi-year contract whose commercial terms change on a schedule agreed at signing. A few things change across these arrangements:
RevRec recipes / Multi-year contracts with ramps
When a customer commits for several years with prices that step up or down on a schedule, billing follows that commercial agreement, but revenue recognition has to follow what you actually deliver. Here's how Chargebee RevRec handles it.
The problem
A ramp deal is a single multi-year contract whose commercial terms change on a schedule agreed at signing. A few things change across these arrangements:
What shifts across a ramp
when the customer commits to more production workspaces in later periods
as volume or tier discounts change with commitment levels
when a later contract modification adds or removes a promised good or service
This recipe uses an initial-order quantity and unit-price ramp agreed entirely at signing. No scope changes occur mid-term. Every year brings a visible commercial change: year one establishes the deal, year two narrows the discount on the same one workspace, and year three doubles quantity with a larger volume discount.
ASC 606 ties revenue to delivery, but invoicing on a ramp follows the billing schedule instead. So what you invoice and the revenue you can recognize are two different numbers.
The example
Northwind Labs wants Cadence AI Workspace for its production teams and is willing to lock in three years to get a better rate. They start with one workspace, keep one through year two, and add a second in the final year. It is one order form, signed once, with all three years priced up front. Every number on this page comes from it.
The Vendor shall provide, and the Customer shall purchase, annual production workspace licenses for Cadence AI Workspace (the "Service") for the periods set out in the schedule below. The Vendor's published list price for the Service is $400,000 per workspace-year. In consideration of the Customer's multi-year commitment hereunder, the Vendor grants the tiered pricing set out below, which shall apply to the corresponding annual periods for the duration of the Term.
| Year | Licensed workspaces | Item discount | Rate / workspace-year | Annual fee |
|---|---|---|---|---|
| 2027 | 1 | 20% | $320,000 | $320,000 |
| 2028 | 1 | 15% | $340,000 | $340,000 |
| 2029 | 2 | 32.5% | $270,000 | $540,000 |
| Total Contract Value | 4 workspace-years | $1,200,000 |
This Order Form is non-cancellable for the full 36-month term. The Customer's commitment to all three annual tranches is firm and enforceable at signature, and the annual fees are payable in full on a fixed annual billing basis.
Fees are the fixed annual subscription amounts shown above and are invoiced annually in advance.
This sounds obvious, but it is the most consequential decision on the page, because it sets how much money the later steps get to work with. ASC 606 says a contract lasts only as long as both sides have enforceable rights and obligations. So the question is not really about the product; it is about the contract itself. What is the customer obligated to pay, and for how long?
Here the answer is the cancellation clause in the order form. There is no right to walk away, so all three years are enforceable now and the contract term runs the full 1 January 2027 to 31 December 2029. The other ASC 606 contract criteria are met here as well, including probable collectibility. Had the customer been able to cancel at each anniversary, only year one would be enforceable and the accounting would restart every year. (A separate question, whether those three years are one promise or three, is the next step; this step is only about the term.)
| Contract term | One term, 36 months |
| Enforceable at signature | All three annual tranches |
| Amount in scope across the term | $1,200,000 |
Each day of workspace access is substantially the same and has the same pattern of transfer. ASC 606 therefore accounts for the daily services together as one series performance obligation, not three separate promises.
Why this matters for what comes next: because all three years deliver the same promise, they can be compared on a single measuring stick even when licensed quantity changes. Workspace-days provide that consistent measure of progress in Step 5. If year three had included something genuinely different, say a new product module, it would have been a separate promise needing its own pricing.
Because the full ramp was agreed at signing, the scheduled pricing changes and year-three quantity increase are part of the original contract rather than new negotiations each year.
The signed order form fixes all three annual fees, making the transaction price $1,200,000.
That $1,200,000 is allocated to the single series performance obligation, and RevRec uses it to build the revenue schedule across the term.
The three annual order-form lines are billing and quantity tranches, not separate performance obligations. Step 4 does not divide consideration among them or weight years by standalone selling price. The entire transaction price attaches to the single series promise identified in Step 2.
| Transaction price | $1,200,000 |
| Performance obligations | 1 |
| Allocated to the series | $1,200,000 |
The customer has workspace access every day, so revenue is earned every day, not in a lump when the invoice lands.
Revenue per workspace-day works out to $1,200,000 ÷ 1,461 = $821.36, applied against each year's own workspace-days.
| Year | Licensed workspaces | Workspace-days | Share of total service | Invoiced | Revenue recognized |
|---|---|---|---|---|---|
| 2027 | 1 | 365 | 24.98% | $320,000 | $299,795 |
| 2028 | 1 | 366 | 25.05% | $340,000 | $300,616 |
| 2029 | 2 | 730 | 49.97% | $540,000 | $599,589 |
| Total | 4 | 1,461 | 100% | $1,200,000 | $1,200,000 |
Billing follows the commercial ramp; recognized revenue follows workspace-days delivered. The two don't match in any single year. They only agree across the full contract.
Measure of progress flattens the rate, not the total. The chart below shows it.
Because billing and revenue move differently, every period updates the contract balance. Chargebee RevRec tracks it in a rollforward: each period opens with the previous closing balance, adds new billings, subtracts revenue earned, and carries the remainder forward. A positive closing balance is Deferred Revenue (contract liability): invoiced consideration awaiting recognition. It ties back to zero by the end of the contract.
| Period | Opening balance | Billed | Revenue | Closing balance |
|---|---|---|---|---|
| 2027 Q1 | 0 | 320,000 | 73,922 | 246,078 |
| 2027 Q2 | 246,078 | 0 | 74,743 | 171,335 |
| 2027 Q3 | 171,335 | 0 | 75,565 | 95,770 |
| 2027 Q4 | 95,770 | 0 | 75,565 | 20,205 |
| 2028 Q1 | 20,205 | 340,000 | 74,743 | 285,462 |
| 2028 Q2 | 285,462 | 0 | 74,743 | 210,719 |
| 2028 Q3 | 210,719 | 0 | 75,565 | 135,154 |
| 2028 Q4 | 135,154 | 0 | 75,565 | 59,589 |
| 2029 Q1 | 59,589 | 540,000 | 147,844 | 451,745 |
| 2029 Q2 | 451,745 | 0 | 149,487 | 302,258 |
| 2029 Q3 | 302,258 | 0 | 151,129 | 151,129 |
| 2029 Q4 | 151,129 | 0 | 151,129 | 0 |
Disclaimer This page is not accounting advice.
Ramps, mid-term expansions, and multi-element deals: these contracts break spreadsheets. Chargebee RevRec handles them on the billing system you already have, keeps you compliant with ASC 606 and IFRS 15, and shows its work on every number.