# A Founder's Guide to SaaS Revenue Recognition Basics (India Edition)

Sooner or later — a fundraise, an acquisition, your first audited financials — someone will ask why your "₹2 crore revenue" doesn't match your bank statements. This guide explains revenue recognition (rev rec) in plain language, with the India-specific wrinkles founders actually hit.

The Core Principle: Recognise Revenue as You Earn It

Under Ind AS 115 (India's version of ASC 606), you recognise subscription revenue ratably over the service period — not when cash arrives. Sell a ₹12 lakh annual contract on 1 April? You've earned ₹1 lakh by 30 April. The remaining ₹11 lakh is deferred revenue: cash in the bank, but a liability until delivered.

This is why a fast-growing SaaS company can collect crores while reporting modest revenue — and why investors care about both numbers separately.

The Five-Step Model (Simplified)

  1. Identify the contract — signed order form or accepted terms.
  2. Identify performance obligations — usually one (platform access), but setup fees, training, or premium support can be separate.
  3. Determine transaction price — including any variable discounts.
  4. Allocate price across obligations.
  5. Recognise each obligation as it's satisfied — subscriptions over time, one-time onboarding often upfront.

    6. Terms That Change Your Numbers

    Annual prepaid contracts

    Cash upfront, revenue monthly. Great for working capital; creates growing deferred revenue as you scale.

    Monthly billing

    Revenue and cash roughly align. Simpler books, weaker balance sheet.

    Annual contract paid in instalments

    Common with Indian SMB buyers. Revenue still recognises monthly, but cash trickles in — watch receivables. If instalments are financed through a vendor-financing platform like KredFlow, you typically collect the full amount upfront from the financier while the buyer pays monthly; rev rec stays unchanged, but your receivables risk shifts away.

    Usage-based pricing

    Recognised as usage occurs — matching gets trickier; keep clean metering records.

    India-Specific Wrinkles

    GST ≠ revenue

    GST collected (18% on B2B SaaS) never touches your P&L. Book net of GST. Confusing the two inflates "revenue" by nearly a fifth.

    TDS deductions

    Customers may deduct TDS (e.g., 194J/194O) before paying. Track it — it's your tax credit, not a discount.

    Forex contracts

    If you bill overseas customers in USD, recognise at exchange rates over the service period; FX swings hit other income, not subscription revenue.

    Mistakes That Blow Up Due Diligence

    • Booking full annual value as revenue on signing. The classic founder error; instantly restated by auditors.
    • Mixing bookings, billings, and revenue in investor updates. Define all three and report consistently.
    • Ignoring unbilled AR — revenue recognised but not yet invoiced (monthly-billed annual deals).
    • No contract repository. Every deal should have a dated, signed document retrievable in seconds.

    What Investors Actually Check

    In diligence, expect scrutiny of: MRR/ARR reconciliation to recognised revenue, deferred revenue roll-forward month over month, churn against billed vs recognised figures, and consistency between your pitch deck metrics and your books. Clean rev rec signals operational maturity — sloppy rev rec invites a discount on your valuation.

    Practical Setup for Early Teams

    You don't need enterprise software on day one:

    1. A single spreadsheet tracking every contract: start date, term, value, recognition schedule.
    2. Monthly close ritual: update deferred revenue, reconcile collections to invoices.
    3. An accountant who knows Ind AS 115 — worth the fee long before your first audit.

      4. The Takeaway

      Revenue recognition isn't bureaucracy; it's the honest translation of your growth into numbers others can trust. Get it right early, and every future fundraise conversation starts ahead instead of behind.

      Mini Case: One Contract Through the Model

      ₹11.8 lakh annual contract (₹10 lakh + 18% GST), signed 1 July, paid in full 5 July, plus ₹60,000 one-time implementation completed in July.

      • Cash in July: ₹12.4 lakh.
      • Revenue in July: ₹83,333 (1/12th of subscription) + ₹60,000 implementation = ₹1,43,333.
      • Deferred revenue at 31 July: ₹9,16,667.
      • GST payable: on invoice value, independent of recognition schedule.

      Twelve months later, cumulative recognised revenue equals ₹10,60,000 — matching total contract economics excluding GST. If your books can produce those four numbers for any contract within minutes, you're ahead of most seed-stage companies walking into diligence. Build the spreadsheet once; update it monthly; thank yourself at the term sheet.