I have watched a Series B conversation collapse in real time. The investor’s associate pulled up the deferred revenue schedule and set it next to the MRR deck the founder had shared in the data room. The founder had been reporting ₹2.2 crore in monthly recurring revenue. The deferred revenue balance implied something closer to ₹1.4 crore. The gap was not a rounding error.
It was a methodology error, one the founder had been making for eighteen months, compounding with every contract renewal. That meeting ended without a term sheet. The founder was not trying to deceive anyone. He simply did not understand the difference between what he had booked and what he had actually earned.
This confusion sits at the heart of a quiet problem running through India’s SaaS ecosystem. With Indian SaaS on track toward $50 billion by 2030, and startups granted over $12 billion in ESOPs in 2025 alone, the mechanics of financial reporting have never mattered more. Investors at growth stages are no longer accepting management decks at face value.
They run Quality of Earnings analyses, rebuild MRR waterfalls from raw transaction data, and reconcile bank accounts before they shake anyone’s hand. The founders who survive that scrutiny are the ones who got their revenue accounting right from the beginning.
The Confusion That Kills Deals
A booking is a signed contract. It is not revenue. Revenue is what you have earned by delivering a service. In SaaS, you earn revenue one day at a time, over the subscription period. A customer signs a ₹12 lakh annual contract and pays upfront. That cash hits your account. What just happened on your income statement? Nothing yet. The ₹12 lakh sits on your balance sheet as a contract liability, deferred revenue. Each month, ₹1 lakh moves from that liability into recognized revenue. After twelve months, the full amount is earned. Not before.
Ind AS 115, which superseded Ind AS 11 and 18 from April 2018, codifies exactly this logic. Its American counterpart ASC 606 operates on the same framework. Both ask one question: has the performance obligation been satisfied? For SaaS, the performance obligation is ongoing access. The customer receives and consumes it simultaneously, day by day. Revenue follows time elapsed, ratably, over the contract period. The old “transfer of risks and rewards” test under Ind AS 18 was replaced with something more precise: the transfer of control. In a subscription, that transfer happens continuously.
Where founders go wrong is treating the cash receipt as the recognition event. What makes this particularly dangerous in SaaS is the compounding effect: multi-year contracts and annual prepayments create large upfront cash flows that have nothing to do with current-period earned revenue. The faster the business grows, the more violently that gap misrepresents actual health.
How the Inflation Happens in Practice
My experience is that most MRR inflation in Indian SaaS is structural, not deliberate. Founders build MRR dashboards in spreadsheets using invoiced amounts as input. Implementation fees, one-time onboarding charges, professional services, and pilot payments end up alongside recurring subscription fees. The aggregate gets reported as MRR. Three patterns surface repeatedly. Counting committed-but-not-live customers, where a signed contract is treated as live revenue before the customer has gone live.
Carrying churned accounts while the team tries to save the relationship. Treating deferred revenue as earned income, recognizing the entire annual cash receipt upfront. One accounting firm documented startups inflating reported revenue by 300 percent through this mechanism alone.
There is also a newer pattern VCs have started calling “vibe revenue”: pilots counted as subscriptions, contracts with easy exit clauses reported as committed ARR, one-time deals annualized into run rates. One venture capital firm described a company claiming $325,000 in ARR that traced back to a two-week proof-of-concept. None of it was revenue under any standard. It was a number that felt true.
The ESOP Layer Almost Nobody Talks About
There is a second accounting dimension that intersects with this problem and receives far less attention. Indian startups granted over $12 billion in ESOPs in 2025, yet more than 60 percent struggle with proper valuation and expense recognition. The consequences show up in two places.
The first is EBITDA inflation through ESOP exclusion. Under Ind AS 102, ESOP expense is recognized over the vesting period as employee compensation cost. This is a real cost representing dilution to every existing shareholder. Yet a remarkable number of Indian startups report “EBITDA before ESOP costs” as their primary profitability metric, stripping out what can be crore-level annual expenses to present a cleaner headline number. Sophisticated investors add the cost back in a QoE exercise and adjust the valuation multiple accordingly.
The second complication arises when equity instruments are granted to customers rather than employees. If a SaaS company issues warrants to a customer as part of securing a commercial contract, both Ind AS 115 and ASC 606 treat the fair value of that equity as a reduction to the transaction price, not an additional expense. A ₹2 crore contract with warrants worth ₹40 lakh yields reported revenue of ₹1.6 crore. Many founders building enterprise relationships through equity-linked commercial structures do not know this rule exists. Their reported revenue is overstated from the moment the contract is signed.
What Investors Actually Check
The moment a serious investor opens a data room, the MRR deck is not the first document their team reads. They read the audited financials, look for the deferred revenue balance, and reconcile. A growing SaaS business with annual prepayment customers should show a growing deferred revenue balance. If reported revenue is rising but deferred revenue is falling, revenue is being recognized faster than it is being earned. Proof-of-cash analysis goes further, reconciling bank receipts against reported revenue. Two investor-backed companies have lost financing rounds after this reconciliation forced restatements.
A QoE team rebuilds the MRR waterfall from contract-level transaction data. They look at the billings-to-revenue ratio, which in a prepaid SaaS business should be above 1.0. They examine cohort-level gross revenue retention, which should exceed 80 percent for a business with genuine product-market fit. Net Dollar Retention at elite SaaS companies runs above 120 percent. Gross margin below 60 percent raises questions about whether the business is truly software.
The math of materiality matters here: a ₹80 lakh overstatement can sit below an auditor’s materiality threshold and receive no comment. At a 20x ARR multiple, that same misstatement translates to ₹16 crore of inflated acquisition price. QoE analysis has no materiality threshold. Every rupee gets reconciled.
The India Evidence Is Already Here
The consequences of getting this wrong are not hypothetical. One edtech company at a $22 billion peak valuation booked entire multi-year course payments on day one instead of ratably over the contract period. When the forced restatement came, losses for a single financial year expanded 19 times over. Two audit firms resigned. The company entered insolvency.
An automotive services startup reported monthly revenue of ₹194 crore. The actual figure was approximately half that. A forensic audit during a Japanese investor’s due diligence uncovered it. The company laid off 70 percent of its workforce. A fashion technology company sent three different revenue figures for the same financial year to different shareholders, against actual net revenue that was a fraction of any of them.
The company was liquidated in early 2024. SEBI’s 2025 enforcement action against a listed drone technology company found 35 percent of reported FY24 revenue was fictitious. Without it, the company would have reported a pre-tax loss of ₹3.91 crore instead of the ₹8.44 crore profit it had claimed. NFRA issued 70 disciplinary orders in FY24 alone, with revenue recognition listed as a priority inspection area.
The Discipline That Survives Due Diligence
Clean financial reporting is a fundraising advantage, not a compliance exercise. Three things every SaaS CFO or finance lead should verify before the next board meeting: whether the deferred revenue balance is maintained correctly for every annual prepayment contract, whether ESOP expense under Ind AS 102 is flowing through the P&L over the vesting period rather than being stripped from profitability metrics, and whether equity instruments granted to commercial counterparties have been treated as transaction price reductions.
The investors writing large cheques are not confused about the difference between bookings and earned revenue. They have seen too many founders who were. Getting this right before they arrive in the data room is not a defensive act. It is the work of a CFO who understands that financial integrity is the foundation on which everything else in a fundraising process is built.