Revenue Recognition for SaaS Companies: What Founders Need to Know

Why Revenue Recognition Matters for SaaS

Revenue recognition determines when and how you record revenue in your accounts. For SaaS companies, this is more complex than it sounds because you often collect cash before you have earned the revenue. A customer who pays £12,000 upfront for an annual subscription has given you cash, but you have not yet delivered twelve months of service. Getting this wrong distorts your financial statements, misleads investors, and can create serious problems during due diligence.

The fundamental principle is straightforward: you recognise revenue when you deliver the service, not when you receive the cash. For a monthly SaaS subscription, you recognise one month of revenue each month. For an annual upfront payment, you recognise one-twelfth each month and carry the rest as deferred revenue on your balance sheet.

The Five-Step Framework Under IFRS 15 and ASC 606

Both IFRS 15 and ASC 606 use the same five-step model for revenue recognition. First, identify the contract with the customer. Second, identify the distinct performance obligations in the contract. Third, determine the transaction price. Fourth, allocate the transaction price to each performance obligation. Fifth, recognise revenue as each performance obligation is satisfied.

For a simple SaaS subscription, this is relatively straightforward: one contract, one performance obligation (access to the software), one price, recognised over the subscription period. Complexity arises when you bundle implementation, training, support tiers, or usage-based components into a single contract.

Common Revenue Recognition Challenges in SaaS

The first challenge is bundled contracts. If you sell a £50,000 annual subscription that includes £10,000 of implementation services, you need to separate these into two performance obligations and recognise them differently. The implementation revenue is recognised when the implementation is complete. The subscription revenue is recognised monthly over the contract term.

The second challenge is usage-based pricing. If part of your revenue comes from API calls, data storage, or transaction volumes above a base tier, you recognise that usage revenue as it occurs, not when the contract is signed. This requires systems that can track and report usage accurately.

The third challenge is contract modifications. Upgrades, downgrades, add-ons, and renewals all need to be assessed for whether they represent a new contract or a modification of the existing one. The accounting treatment differs significantly depending on this classification.

Deferred Revenue: Your Balance Sheet Friend

Deferred revenue is cash you have collected for services you have not yet delivered. It sits as a liability on your balance sheet because you owe the customer future service. For SaaS businesses that collect annually upfront, deferred revenue can be substantial and is actually a positive signal to investors because it represents committed future revenue.

During due diligence, acquirers and investors scrutinise your deferred revenue schedule closely. They want to see that it reconciles to your contract terms, that it unwinds predictably into recognised revenue, and that there are no unusual patterns that suggest aggressive recognition.

Practical Revenue Recognition for Early-Stage SaaS

If you are pre-Series A and using cash-basis accounting or simplified accruals, you do not need to implement the full five-step model immediately. But you do need to get two things right from the start. First, never recognise annual upfront payments as revenue in the month received. Always spread them over the contract period. Second, keep a clean deferred revenue schedule that reconciles to your MRR.

These two practices ensure your SaaS metrics are accurate, your financial statements are credible, and you avoid a painful restatement when you raise your next round and investors bring in accountants to review your numbers.

How a Fractional CFO Gets Revenue Recognition Right

A fractional CFO designs your revenue recognition policy, ensures it complies with the relevant accounting standards, and builds the systems and processes to apply it consistently. They set up the deferred revenue schedule, train your finance team, and review the treatment of complex contracts.

At Scale With CFO, we help SaaS companies implement revenue recognition that satisfies investors, auditors, and acquirers from day one. Book a free discovery call to discuss your revenue recognition needs.