Revenue Management: #5 Revenue Recognition in SaaS

Revenue Management: #5 Revenue Recognition in SaaS

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?

How do SaaS companies manage revenue recognition and stay compliant?   

Revenue Recognition Scenarios in SaaS 

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.


Annual Contract Paid Upfront

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.


For example, a $12,000 annual contract with $1000 onboarding. $1000 will be recognized immediately during billing, and $11,000 is spread across 12 months.

Monthly Billing

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


Example: $500 per month subscription recognized monthly as it is earned.

Bundled Pricing

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.


Example: A $10,000 contract includes $2000 for setup, $6000 for software access, and $2000 for support. Revenue is recognized based on the timeline of each deliverable.

Amendments & Discounts

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.


Example: A new allocation and recognition schedule must be set up if a customer moves from a $1000/month plan to a $1500/month plan mid-year.

Usage Based or Tiered Pricing

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.


Example: $0.10 per API call. If a customer makes 10,000 calls in March, $1000 is recognized in that month.

These scenarios illustrate the diverse billing models in SaaS and their direct impact on revenue recognition timing. Businesses that manage multiple pricing plans, onboarding services, or usage billing must ensure their recognition strategy aligns with the service delivery. This is where automation becomes critical.

InfoScenario:
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.

 

For onboarding

For Software Access

Recognition Frequency

Once

Monthly

Recognition Method

One-Time (Daily)

Evenly Distributed

Recognition Time

Period Start

Period End

 

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.


Reports in Zoho Billing

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


i) Recognized Revenue Report

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

Component

Recognized Revenue

Description

Onboarding

$20,000

Fully recognized in Month 1

Software Access

$25,000

$8333/month for 3 months out of ($1,00,000)

Total Recognized

$45,000

Recognized at the end of 3 months

 


ii) Deferred Revenue Report

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

Component

Deferred Amount

Software Access

$75,000 (9 months x $8333)

Total Deferred

$75000

 


iii) Revenue Waterfall Report

Months

Onboarding

Software Access

Total​

Month 1

$20,000

$8,333

$28,333

Month 2

-----

$8,333

$8,333

Month 3

-----

$8,333

$8,333

Month 4 (upcoming)

-----

$8,333

$8,333

Month 5 (upcoming)

-----

$8,333

$8,333

Month 6 (upcoming)

-----

$8,333

$8,333

Month 7 (upcoming)

-----

$8,333

$8,333

Month 8 (upcoming)

-----

$8,333

$8,333

Month 9 (upcoming)

-----

$8,333

$8,333

Month 10 (upcoming)

-----

$8,333

$8,333

Month 11 (upcoming)

-----

$8,333

$8,333

Month 12 (upcoming)

-----

$8,333

$8,333

 

Idea

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.

 

    • Sticky Posts

    • Community Learning Series | Digest #5 — September 2020

      Dear customers, We're happy to bring you the September edition of our #CommunityDigest! Keep track of your subscription KPIs right from your smartphone: Last month, we enhanced our Android mobile app to help our customers get daily updates on their business health. We got to know from a lot of customers that this has made their job much more easier because they no longer have to keep a reminder to manually check on the previous day's revenue or activations. If you have not downloaded it yet, here's

    • Community Learning Series | Digest #4 - August 2020

      Dear customers, We hope you're staying safe and healthy. I'm happy to bring you the fourth edition of our #CommunityDigest with some brand-new updates from us. 1. Daily Business Updates (for Android users) The Zoho Subscriptions Android app has got a cool new update: You can now get a push notification to your smartphone that lets you know how many activations and cancellations have taken place, and what's the net revenue for the previous day. The best part is, you can tell the app when exactly you

    • Community Learning Series | Digest #3 - July 2020

      Dear customers, We hope you're staying safe and healthy. We're glad to bring you the July edition of our #CommunityDigest. New community members can view our previous newsletters here. This time, we have two major updates and three interesting topics for you: 1. Zoho Subscriptions Developer Community Since the inception of Zoho Subscriptions, our team believed that the recurring billing platform we provide should be able to offer an extensive API library that empowers businesses to automate most

    • Introducing: Community Learning Series | Digest #1 - May 2020

      Dear customers, We hope you are staying safe and healthy. Helping businesses manage their customer subscriptions more efficiently has always been, and always will be, our goal at Zoho Subscriptions. We strongly believe this is possible if we grow together as a community and share what we know with each other. To nurture this shared learning experience, here is our brand-new Community Learning Series! ​ Welcome to the first edition of our digest! Each edition of our community digest includes guides