Northwind Compliance Systems: A SaaS Contract With an Implementation, a Mid-Term Module and a Discount Option
Northwind Compliance Systems signed a three-year SaaS contract with a bank on 1 January 20X5: a $1.2 million annual subscription billed each January, plus a one-time $900,000 implementation service delivered in Q1. The configuration work does not modify core code, the bank could use the hosted platform without it, and other customers routinely buy the subscription alone. Total contracted consideration is therefore $4.5 million. In month 7 the bank adds a jurisdiction module with a standalone selling price of $400,000 for the 30-month remaining term, and Northwind accepts $250,000. At the same time it grants an option to buy two further modules at 15% below the $200,000 list price, a discount no other customer receives; procurement indicates a 70% likelihood of exercise. The CFO wants the implementation fee recognised up front because the work was finished in Q1, the module recognised at $250,000 on go-live, and nothing recorded for the option. Subscription revenue has been booked straight-line at $100,000 a month.
1. Identify the performance obligations existing at contract inception and allocate the $4.5 million transaction price. State when each element is recognised.
Read the worked answer
Step 1 - are there three obligations or two?
- The hosted subscription is a stand-ready obligation, satisfied over time across 36 months.
- The implementation is distinct: the bank can benefit from the platform without the configuration, the work does not significantly modify or customise the software, and Northwind routinely sells the subscription without it. It is a separate obligation, satisfied when the bank obtains the benefit of the configured environment (Q1 20X5).
- The option is a material right, not a marketing gesture: 15% is incremental, no other customer gets it, and it therefore incentivises the bank to buy modules it would not otherwise buy at list. It is a separate performance obligation at inception.
Step 2 - standalone selling prices.
- Software: 3 x $1,200,000 = $3,600,000 (observable, sold separately)
- Implementation: $900,000 (observable)
- Option: 2 x $200,000 x 15% = $60,000 of discount, probability-weighted at 70% = $42,000 (a time-value adjustment for the 12-18 month delay is permitted but immaterial here)
- Total SSP = $4,542,000
Step 3 - allocate the $4.5m.
- Software: 3.6/4.542 = 79.3% -> $3,567,000, straight-line over 36 months (~$99,100/month)
- Implementation: 0.9/4.542 = 19.8% -> $892,000, recognised in Q1 20X5
- Option: 0.9% -> $41,600, recognised when the option is exercised (added to the modules delivered) or when it lapses unexercised
The CFO's implicit view that the $900,000 is the implementation's revenue is wrong twice over: it is a performance obligation, so timing follows delivery, and its amount is the allocated $892,000, not the invoice.
2. Apply the month-7 changes. How much revenue attaches to the new module, and how does subscription revenue change prospectively?
Read the worked answer
Step 1 - is the module a distinct good? Yes. The bank can benefit from it with the existing platform and Northwind sells it separately at $400,000.
Step 2 - is it priced at SSP? No: $250,000 against $400,000. When a modification adds a distinct good but the price is not at standalone selling price, the modification is not accounted for as a termination plus a new contract. The unrecognised consideration plus the new consideration is allocated across the remaining, undelivered obligations.
Step 3 - allocate.
- Remaining subscription consideration: 30 months x $100,000 = $3,000,000
- Plus the module fee: $250,000
- Remaining transaction price = $3,250,000
- Remaining SSP: subscription $3,000,000 + module $400,000 = $3,400,000
Allocation:
- Subscription: 3.0/3.4 = 88.2% -> $2,868,000 over 30 months = $95,600/month (down from $100,000)
- Module: 0.4/3.4 = 11.8% -> $382,000 over 30 months = $12,730/month
The module is recognised over the 30 months from go-live (a right to access the hosted service), not on delivery. The $150,000 concession is spread across both remaining obligations, which is the economically sensible answer: the bank negotiated a package discount, not a discount on the module alone. No cumulative catch-up is needed because the change is accounted for prospectively; the option obligation and its $41,600 are unaffected.
3. Evaluate the CFO's three positions, state the corrections, and quantify the approximate effect on 20X5 revenue.
Read the worked answer
Position 1 - implementation up front. Correct in timing (Q1 delivery), wrong in amount: $892,000, not $900,000. Effect versus the CFO's plan: a $8,000 reduction. The bigger risk is that the CFO may be capitalising or deferring the cost side inconsistently - the delivery cost should follow the same pattern as the $892,000 of revenue.
Position 2 - module at $250,000 on go-live. Wrong on both dimensions. Revenue is $382,000 spread over 30 months, so 20X5 (six months) revenue is roughly $76,500, not $250,000 - a deferral of about $173,500 into later periods.
Position 3 - nothing for the option. Wrong. The option is a material right, is a performance obligation, and carries $41,600 of the transaction price. Failing to record it overstates early revenue and understates deferred revenue; it also creates a breakage question if the bank never exercises.
Also unaddressed: the $100,000/month straight-line booking is now wrong twice - $99,100/month for months 1-6 under the original allocation, then $95,600/month from month 7. The cumulative difference is small in 20X5 but the process error signals a control weakness: revenue is being booked on the invoice pattern rather than on a maintained SSP allocation model.
Bottom line for the CFO: restate to an allocation model, recognise the option, and note that the net 20X5 revenue effect is a modest reduction (roughly $180,000) but the deferred revenue balance and every subsequent period are affected. If the contract is material to a covenant or a bonus metric, disclose the correction.