If you're building or running a SaaS business, you've probably encountered this. You get paid upfront for a subscription and a one-time onboarding fee, but you end up with confusion about when to consider it revenue. Can I book all of it now? Should I spread it out? What if the customer upgrades or downgrades midway?

In the world of SaaS, a business's billing of its customers has a direct impact on how and when it recognizes revenue. While the five-step model stays the same, the application varies significantly depending on the contract structure, billing frequency, and delivery pattern. Below are the common real-world scenarios that define these differences.

Most SaaS companies bill customers annually or quarterly in advance. However, accounting standards do not permit revenue to be recognized when cash is received. Instead, the revenue must be recognized over time, as the service is delivered.

Customers pay monthly for access. There is typically no deferred revenue, and revenue is recognized in the same month the service is delivered.

A typical SaaS contract might include platform access, onboarding, training and support as a part of the contract that gets billing as a bundle. According to ASC 606 and IFRS 15, these are separate performance obligations. The business must allocate revenue to each and recognize it based on how and when each is fulfilled.

Customers often switch plans mid-cycle, receive promotional pricing, or get billed based on the actual usage. These changes introduce variable consideration and require contract modification, revenue reallocation, and recalculations for the remaining service term.

Some businesses charge based on consumption. For instance, API usage, user access, data storage, etc., they charge the customer again as and when the upper cap is met. This means revenue cannot be recognized until the service is used. Businesses must track usage data and apply the prorated or usage-based revenue rule to stay compliant.

Scenario:
You sign an annual contract worth $1,20,000 with a client. The client pays the full amount upfront. The contract includes $20,000 onboarding and $1,00,000 for uninterrupted access to the software for 12 months.  

Zoho Billing for SaaS Revenue Recognition

Zoho Billing simplifies SaaS revenue recognition by allowing the finance team to define a recognition rule based on the product or service offered.

For this kind of business, the Revenue recognition rule should be set in the following way:

There are two deliverables here: one is Onboarding, and the other is software access.

Although the full payment is collected in advance, you cannot recognize the entire $1,20,000 as revenue immediately. Only the onboarding revenue of $20,000 is recognized in the first month. The remaining $1,00,000 must be recognized evenly over 12 months at $8,333 monthly.

If you look at the reports in Zoho Billing after three months of service rendering, you will see,

Onboarding is complete three months into the contract, and three out of 12 months of application access have been delivered.

After three months, the company will have nine months of software access remaining.

Best Practices for SaaS Revenue Recognition 

• Disaggregate Contract Elements: Break down your subscriptions, onboarding, support, and other one-off deliverables as separate individual obligations.
  
• Use Automated Rules: Configure a Recognition Rule based on the billing method and avoid tracking them manually.
  
• Handle Modifications: Plan changes and upgrades should trigger reallocation of revenue.
  
• Monitor Revenue Waterfall: Visual schedules ensure predictable reporting and forecasting.
  

Up Next: Revenue Recognition in the Professional Services Industry