SaaS Revenue Recognition Audit: Multi-Element Contracts, SSP and Hosting Licenses

A SaaS client's order form rarely contains one product. It can bundle a subscription, an implementation project, premium support, training and sometimes a downloadable component, all at one discounted price. How the transaction price is split across those promises sets when revenue shows up. For an auditor, the split is the risk. This guide covers where the judgments sit and how to test them.

Step one: is there a license at all?

SaaS is a service in most arrangements, recognized as the customer receives it. A software license, with its different timing, enters only when the arrangement meets the criteria in ASC 985-20-15. A hosting arrangement includes a license only if both of these are true:

1. The customer can take possession of the software at any time during the hosting period without a significant penalty.
2. The customer can feasibly run the software on its own hardware or contract with an unrelated party to host it.

If either fails, the arrangement is a service contract regardless of what the paper calls it. If both are met, the license is assessed for whether it is distinct from the rest of the contract. It is distinct only if the customer can benefit from it on its own or with readily available resources and it is separately identifiable from the cloud service. If the customer must use both together to get any benefit, they form one performance obligation.

Auditors should read the contract, not the product label. A client that sells a "license" to a hosted platform with termination penalties for taking the code has a service. A client that lets customers install and run a module locally has a license component to separate.

Step two: what are the distinct performance obligations?

The usual candidates are the subscription, implementation or onboarding, premium support, training, data migration and any on-premises software. For each, ask whether the customer can benefit from it on its own or with readily available resources, and whether it is separately identifiable from the other promises. Implementation is the common judgment. If third parties routinely configure the platform, or the vendor sells implementation alone, it supports a separate obligation recognized as the work is performed. If the work is proprietary and customizes the service so the subscription cannot function without it, it is combined and recognized with the subscription.

Read the client's policy memo against actual contracts. Policies written for the standard order form fail on negotiated deals when the terms differ.

Step three: standalone selling price

Once obligations are identified, the price is allocated by relative standalone selling price (SSP). Management must maximize observable inputs and apply its method consistently. The methods are:

• Adjusted market assessment. Start from competitors' prices and adjust for entity-specific factors.
• Expected cost plus a margin. Estimate the costs normally considered in pricing and add a supportable margin.
• Residual approach. Subtract the observable SSPs of other items from the total price. Under ASC 606-10-32 it is permitted only when the same item is sold to different customers for a broad range of amounts, or when the item has not yet been sold standalone and has no established price.

The residual approach is intentionally limited. Where it leaves a nominal amount for something that clearly sells for much more, the method is not appropriate. Under the same section, results must be compared against all reasonably available observable evidence.

An entity cannot assert it is unable to estimate SSP. Test the SSP support: price lists, sales data by deal size and segment, discount approvals and any renegotiated pricing. Stale price lists and a single flat SSP for all customer sizes are weak support.

Step four: allocating discounts

A discount is allocated proportionately across all performance obligations under ASC 606-10-32. It goes to fewer than all obligations only if all three criteria in that section are met: the entity regularly sells each item standalone, regularly sells some of them as a bundle at a discount, and that bundle discount is substantially the same as the contract discount. Clients that book the entire discount against implementation, which is recognized early, or against subscription, which is recognized later, are choosing the answer.

Worked example

This is an illustrative example. A customer signs a one-year contract for $135,000. Standalone selling prices are $120,000 for the subscription, $30,000 for implementation and $10,000 for premium support, a total of $160,000. The discount is $25,000. No bundle evidence supports allocating it to fewer than all items, so it is spread proportionately. The contract price is 84.375 percent of total SSP.

The subscription and support are recognized over the 12-month term, which is $8,437.50 per month for the subscription. If implementation is distinct, $25,312.50 is recognized as the work is completed, for example as hours are delivered. If the client had instead booked the whole $25,000 discount against the subscription, implementation revenue would be $30,000 and the subscription $95,000. That moves $4,687.50 of revenue into the implementation period. The error is invisible in total contract value and visible only in the allocation.

Audit procedures

1. Select contracts by risk: multi-element deals, non-standard terms, modifications, large discounts and period-end signings.
2. Read each contract for the license test, distinct obligations, termination rights, acceptance clauses and usage-based fees.
3. Re-perform the allocation. Tie each SSP to documented support.
4. Test the timing pattern: ratable subscription, milestone or hours-based implementation, and usage-based fees against system reports.
5. Test contract modifications and renewals for whether they are separate contracts or adjust the existing one.
6. Test cutoff on contracts signed in the weeks before and after year end, including start dates and customer access.
7. Reconcile billing, deferred revenue and revenue by customer. See deferred revenue schedule and revenue recognition audit procedures.

PBC items

• Signed order forms, master agreements and amendments for selected customers
• SSP analysis and price lists, with the policy memo
• Revenue allocation workbook by contract
• Billing register, deferred revenue rollforward and ARR or contract list
• Implementation project reports with hours or milestones
• Usage reports for variable fees
• Discount approval records

Red flags

• Sales-side side letters, free months or termination rights not in the order form
• A single SSP applied to every customer
• Residual approach used for items that are regularly sold separately
• Implementation recognized upfront while the subscription is delayed
• Revenue that spikes in the final month of the period with start dates before customer access
• Policy memos that do not match contract terms

Sources

• FASB ASC 985-20-15, Software, Costs of Software to Be Sold, Leased, or Marketed (hosting arrangement criteria)
• FASB ASC 606-10-32, Revenue from Contracts with Customers, Allocating the Transaction Price (standalone selling price, residual approach, discount allocation)

CORAA prepares ready-to-review audit files for US CPA firms; see /us.

AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error