Revenue Cutoff at a Subscription Software Firm
CloudPath, a SaaS company with a December 31 year-end, bills customers annually in advance and recognizes subscription revenue ratably over the 12-month term. In the last week of December, sales closed three large deals: (a) a $240,000 one-year contract signed December 28 with service starting January 1; (b) a $180,000 one-year contract signed December 20 with service starting December 20, billed in full on signing; and (c) a $120,000 one-year contract signed December 29 that bundles 12 months of hosting with a one-time $30,000 implementation service delivered in December. The controller, under pressure to hit a year-end revenue target, proposes recognizing the full $240,000 from deal (a) in December, deferring all of deal (c) until January, and booking deal (b) entirely in December since it was billed. Deferred revenue currently sits at $410,000.
1. Evaluate the controller's three revenue-recognition proposals under accrual accounting and the revenue recognition principle. What amount, if any, should be recognized in December for each deal?
Read the worked answer
Revenue is recognized when the performance obligation is satisfied, not when cash is billed or collected.
- Deal (a), $240,000, service starts Jan 1: No performance obligation is satisfied in December. Recognizing any of it in December is premature. December revenue: $0. The $240,000 billed (if billed) is a liability (deferred/contract liability).
- Deal (b), $180,000, service started Dec 20: Revenue accrues ratably from Dec 20. December covers roughly 12 of 365 days (Dec 20–31). Approximate December revenue = $180,000 × 12/365 ≈ $5,918; the remainder (~$174,082) is deferred. Billing in full does not justify full recognition.
- Deal (c), $120,000 hosting + $30,000 implementation in December: The implementation is a distinct performance obligation delivered in December, so its $30,000 is recognized in December. Hosting revenue is recognized over the 12-month term starting when hosting begins (January), so $0 hosting in December.
Total December revenue across the three deals ≈ $5,918 + $30,000 ≈ $35,918, not the ~$540,000 the controller's approach would produce. The controller's proposals would materially overstate revenue and understate the deferred revenue liability.
2. Deal (c) allocates $30,000 to implementation. Suppose the implementation were NOT distinct (highly integrated with hosting). How would the accounting change, and what is the judgment criterion?
Read the worked answer
If the implementation is not distinct - i.e., the customer cannot benefit from it separately and it is highly integrated with the hosting - then implementation and hosting form a single combined performance obligation. In that case the entire $120,000 (plus the $30,000, i.e., total consideration) is recognized over the combined service period rather than splitting out $30,000 in December.
The judgment criterion is whether the good/service is capable of being distinct (customer can benefit on its own or with readily available resources) and distinct within the context of the contract (separately identifiable, not highly interdependent). If either fails, combine. This changes December revenue from ~$30,000 to ~$0 for that deal, so the classification decision is material and must be documented.