SaaS Revenue Recognition in India: Why April Cash Is Not April Revenue

The month that looks brilliant and the eleven that follow

A founder closes ₹36 lakh of annual contracts in April. The bank shows ₹36 lakh. The profit and loss shows ₹36 lakh. April looks like the best month the company has ever had, and May looks like a collapse.

Nothing changed in the business. What changed was that the books treated cash as revenue.

Investors spot this immediately, and it costs more than an awkward conversation. It changes what they believe about the growth rate, the churn, and whether anyone here can produce numbers that can be relied on in diligence.

What is SaaS revenue recognition?

SaaS revenue recognition is the practice of recognising subscription revenue over the period during which the service is delivered rather than when the cash is received, in accordance with Accounting Standard 9, with the unearned portion carried on the balance sheet as deferred revenue.

The principle in AS 9 is that revenue from service transactions is recognised as the service is performed. A twelve-month software subscription is performed across twelve months, so it is earned across twelve months, whatever the payment terms say.

Entities applying the Indian Accounting Standards follow Ind AS 115, which reaches the same answer through a five-step model built around performance obligations satisfied over time.

Key terms explained

• Deferred revenue: also called unearned revenue. Cash received or invoiced for a service not yet delivered. It is a current liability, not income.
• Recognised revenue: the portion of the contract earned in the period, which is what belongs in the profit and loss account.
• MRR (Monthly Recurring Revenue): a management metric of contracted monthly value. It is not an accounting figure and does not belong in statutory financials.
• Bookings: the total contract value signed in a period. Neither revenue nor cash.
• Time of supply: the GST concept fixing when tax becomes payable, governed by Section 13 of the CGST Act for services.
• Receipt voucher: the document required under Section 31(3)(d) of the CGST Act when an advance is received against a future supply.

Who this affects

Any business collecting for a service before delivering it. SaaS and software subscriptions are the obvious case, but the same treatment applies to annual maintenance contracts, retainers billed upfront, prepaid course fees, gym and club memberships, and support plans.

The exposure grows with the length of the billing cycle. A monthly subscription business has a small deferred balance and can survive sloppy treatment for a while. An annual-billing business carries a large liability and will produce badly misleading accounts within one quarter of getting this wrong.

The GST problem nobody warns founders about

Here is the part that is specific to India and largely absent from the standard SaaS accounting literature.

Under Section 13 of the CGST Act 2017, the time of supply of services is generally the earlier of the date of issue of invoice or the date of receipt of payment. If you invoice ₹1.2 lakh in April for a twelve-month subscription and the customer pays in April, GST becomes payable in April on the whole amount.

Your accounts recognise ₹10,000 of revenue in April. Your GST return reports ₹1.2 lakh of turnover.

Both are correct. They answer different questions. But the cash consequence is real: you pay tax on the full contract value in month one while eleven-twelfths of it sits on your balance sheet as a liability. Any cash flow forecast that ignores this will be wrong in the first month of a strong sales quarter.

Where an advance is received without an invoice, Section 31(3)(d) requires a receipt voucher to be issued.

For overseas customers the position changes again, because a qualifying export is zero-rated. That is covered separately in selling software to overseas customers, and if you invoice in dollars, subscriptions billed in dollars adds a currency layer on top.

The monthly process

Step 1: Record the invoice as deferred revenue, not sales. Debit the customer, credit Deferred Revenue. Nothing touches the profit and loss account yet.

Step 2: Set up a schedule for every contract. Start date, end date, total value, monthly amount. This schedule is the source of truth and it should live in the accounting system rather than a spreadsheet.

Step 3: Release one period of revenue each month. Debit Deferred Revenue, credit Subscription Revenue, for the amount earned in that month.

Step 4: Handle mid-month starts on a daily basis. A contract starting on 20 April earns eleven days in April, not a full month. Rounding this to whole months is acceptable only if you are consistent and the amounts are immaterial.

Step 5: Pay GST on the time of supply, not on the revenue recognised. Track the two separately from the start. They will never agree and they are not supposed to.

Step 6: Treat upgrades and downgrades prospectively. A mid-term plan change alters the remaining schedule. It does not restate revenue already recognised.

Step 7: Handle refunds and cancellations against the liability first. A cancellation in month three reverses the unearned nine months from Deferred Revenue, not from revenue already earned.

Step 8: Reconcile the deferred revenue balance every month. Opening balance plus new billings less revenue recognised less refunds should equal the closing balance, and it should tie to the contract schedule line by line.

What the numbers look like

A ₹1,20,000 annual subscription invoiced and collected on 1 April:

Total revenue for the year is ₹1,20,000. Total cash in April was ₹1,20,000. The two numbers are equal only over the full term, and they are never equal in any single month.

Common mistakes

• Booking collections as revenue. Revenue tracks the sales calendar rather than the service delivered, and every strong month is followed by an apparent collapse. Bill to the liability, release monthly.
• Keeping the schedule in a spreadsheet. One person owns it, it drifts from the ledger, and it cannot be audited. Use the deferred revenue module in your accounting system.
• Presenting MRR as revenue in statutory accounts. Statutory financials disagree with the investor deck and diligence stalls. MRR is a management metric. Keep it in the management pack.
• Ignoring the GST timing difference. A large tax payment lands in a month the accounts show as modestly profitable. Forecast GST on billings, not on recognised revenue.
• Reversing revenue on cancellation. Earned revenue disappears retrospectively and the comparatives stop meaning anything. Reverse the unearned balance only.

Penalties and consequences

Section 128 of the Companies Act 2013 requires every company to keep books of account that give a true and fair view of the state of affairs, and a persistent failure exposes the officers in default to penalties under that Act.

Under Section 13 of the CGST Act 2017, tax on a service becomes payable at the earlier of invoice or receipt of payment, and failure to pay by the due date attracts interest at 18 per cent per annum under Section 50(1).

Where turnover is understated in a GST return, Section 73 permits recovery of the tax with interest and a penalty of 10 per cent of the tax or ₹10,000, whichever is higher, rising to 100 per cent under Section 74 where suppression is alleged.

Under Section 62 and Section 63 of the Income-tax Act 2025, books must be maintained and, where applicable, audited, and the method of accounting followed is reported in Form No. 26, so an inconsistent revenue recognition policy is visible on the face of the audit report. Where your books must be stored is disclosed in the same form.

How these provisions interact

Accounting Standard 9 recognises revenue as the service is performed, while Section 13 of the CGST Act fixes the time of supply at the earlier of invoice or payment, so GST on an annual subscription falls due in month one against revenue that will be recognised across twelve.

Section 31(3)(d) of the CGST Act requires a receipt voucher where payment is received before an invoice is issued, which means the deferred revenue balance in the books should be traceable to either a tax invoice or a receipt voucher for every contract.

Under mercantile accounting, taxable business income follows the revenue recognised under the accounting policy consistently applied rather than the cash collected, so the deferred revenue liability is also what keeps the income tax computation aligned with the accounts.

Cash treatment against accrual treatment

If a raise is on the horizon, this is one of the first things a diligence team tests. Our note on raising your first institutional round covers the wider process, and what a virtual CFO actually does sets out the reporting layer that usually has to come first.

Key takeaways

• Subscription revenue is recognised as the service is performed under Accounting Standard 9, so an annual contract collected upfront is recognised across twelve months with the unearned portion carried as deferred revenue, a current liability.
• Under Section 13 of the CGST Act 2017 the time of supply of services is the earlier of invoice or payment, so GST on an annual subscription is payable in the first month even though eleven-twelfths of the amount has not yet been earned.
• Deferred revenue must be reconciled monthly against the contract schedule, with opening balance plus billings less revenue recognised less refunds tying to the closing balance.
• Monthly Recurring Revenue is a management metric and not an accounting figure, so it belongs in the investor pack rather than in statutory financial statements prepared under Section 128 of the Companies Act 2013.

Frequently asked questions

If the numbers have to stand up to diligence

The rebuild is rarely difficult, but it is easier before a term sheet than during one. Setting up contract schedules, moving billings to the liability, and separating the GST timing from the revenue timing is a few days of work on a book of a hundred contracts.