Allocating and recognizing a $1.2M deal with hardware, services, and a purchase option
Meridian signed a deal with total consideration of $1.2M. List prices are $400,000 for hardware delivered in month two, $150,000 for implementation performed across months one to three, and $750,000 for a three-year subscription starting in month three. The customer received a 10 percent discount on the package. The contract also grants an option to buy 200 additional seats in year two at 15 percent below list, and Meridian's normal range for such volume is 10 to 18 percent off. In year two the customer exercises the option. Leadership wants a report showing contracted value, billings, and recognized revenue side by side.
1. Identify the performance obligations, including the option, and allocate the transaction price.
Read the worked answer
Three performance obligations plus an assessment of the option.
- Hardware: distinct, customer can benefit on its own, and the implementation does not significantly modify it. Point-in-time obligation.
- Implementation: distinct if it is configuration and setup the customer could perform with another provider and it does not significantly customize the subscription. If it substantially modifies the software's functionality, it fails the distinct test and merges into the subscription.
- Subscription: distinct, recognized over time.
- The option: a material right only if the 15 percent discount exceeds what the customer would get without entering the contract. Meridian's normal range is 10 to 18 percent, so 15 percent is within the range a customer could obtain anyway. No material right, and nothing to allocate.
Allocation: on relative standalone selling price. Hardware has an observable price. Subscription SSP is list less the discount typically granted, which is not 10 percent by assumption. Implementation SSP is typically cost plus a margin where no observable price exists.
The 10 percent discount is not specific to one obligation, so it is allocated proportionately across all three. The residual approach is not available here because observable prices exist for the hardware and subscription.
2. Set the recognition pattern for each obligation, then address the year-two option exercise.
Read the worked answer
Hardware: recognized at the point control transfers, month two. Billing before delivery creates a contract liability; delivery before billing would create a contract asset.
Implementation: recognized over time as performed across months one to three, if distinct. If the customer receives and consumes the benefit as work proceeds, an input measure such as labor hours is appropriate. If the obligation was merged into the subscription, everything shifts to ratable over the combined term - a materially different answer, which is why the distinct assessment matters more than the arithmetic.
Subscription: ratable over 36 months from service start in month three. The first two months carry hardware and services revenue only, so total revenue is not flat.
Year-two option: since the discount is within the normal range, the exercise is priced at standalone selling price and is not a contract modification. Treat the 200 seats as a separate contract: allocate their price to the new seats and recognize from their start date to the existing end date. Do not re-spread the original subscription revenue. Had the discount been outside the normal range, the option would have carried a material right, and revenue would have been deferred on the original contract as the customer effectively prepaid for the discount.
3. Design the contracted value, billings, and recognized revenue report, explaining where the three diverge and what reconciliations it needs.
Read the worked answer
The three measures answer different questions: total contract value is what was signed, billings are what was invoiced, revenue is what has been earned. They diverge at defined points, and the report must show the divergence rather than net it away.
Structure it as a waterfall by period: opening deferred balance, plus billings, minus revenue recognized, equals closing deferred balance. Then split the closing balance into contract liability (billed ahead of performance) and contract asset (performed ahead of billing). Both occur here: the annual subscription billed in advance sits as a liability, and implementation performed before a milestone is billed sits as an asset.
The most common failure is a waterfall that only tracks deferred revenue and silently drops contract assets. The second is a report that rolls forward subscription billings on an annual cycle against monthly revenue, producing a sawtooth that finance misreads as an error - the sawtooth is correct and should be annotated.
Reconciliations required: the closing deferred balance to the general ledger, recognized revenue by obligation to the schedule, and remaining backlog to contract term and quantity. For the year-two seats, report them as an incremental contract so the original deal's numbers stay stable and comparable period over period.