Services
Industry
Resources
Company
Summarize this blog post with:
There is a moment in every SaaS company's life when the board asks for net revenue retention and gets three different numbers from three different people. Sales pulls it from the CRM. Finance pulls it from the ledger. The founder quotes the figure from last quarter's deck.
None of them are lying. They are using different definitions, different cohorts and different treatment of currency movement.
This is not a reporting inconvenience. It is a valuation problem. Investors now treat metric hygiene as a proxy for operating discipline, and diligence teams find the inconsistency within a week.
A SaaS & Software company runs two parallel measurement systems, and confusing them causes most of the trouble.
Revenue recognition is the accounting system. It follows Ind AS 115 in India, or ASC 606 under US GAAP. It answers the question: how much revenue may we report in this period?
Unit economics is the operating system: ARR, NRR, CAC, LTV and payback. It answers the question: is this business efficient, and is it getting more or less efficient?
They use overlapping data and different rules. ARR is not revenue. Bookings are not ARR. Cash collected is none of the above. Any company that treats them as interchangeable eventually restates something.
The five-step model is straightforward to recite and awkward to apply to subscription businesses.
1. Identify the contract with the customer.
2. Identify the performance obligations in it.
3. Determine the transaction price.
4. Allocate that price across the performance obligations.
5. Recognise revenue as each obligation is satisfied.
This maps closely to how NetSuite structures revenue recognition against performance obligations, which is worth reading alongside this section if you are configuring ARM for the first time.
• Implementation and onboarding fees: If setup is not a distinct performance obligation, the fee spreads across the subscription term rather than landing upfront. Many Indian SaaS companies recognise it upfront and later discover they should not have.
• Multi-year contracts with ramped pricing: Revenue usually recognises evenly over the term rather than following the invoice schedule, creating deferred revenue and contract asset balances that need tracking.
• Usage-based components: Variable consideration must be estimated and constrained, then trued up. This is the fastest-growing area of complexity as AI-linked consumption pricing spreads.
• Contract modifications: Mid-term upgrades, downgrades and co-terminating renewals each follow different treatment depending on whether the added goods are distinct and priced at standalone value the same logic covered in our guide to project-based billing and revenue recognition.
• Discounts across a bundle: Allocation must follow standalone selling price, not the discount as written on the order form.
Handle 40 contracts this way in a spreadsheet and it works. Handle 400 and it does not. The failure is rarely dramatic. It is a slow drift where deferred revenue no longer ties to the contract population and nobody notices until an auditor asks for a rollforward. Our ASC 606 guide for Indian SaaS companies walks through the US-GAAP equivalent for teams reporting to overseas investors.
Revenue automation inside a tech ERP does four things.
• Holds the contract as data - Term, price, billing schedule, performance obligations and modifications live in structured fields, not in a PDF.
• Generates the revenue schedule automatically - Each obligation gets its own schedule, running on the correct pattern, recalculated when the contract changes.
• Posts deferred revenue and contract balances by rule - No manual journals for standard scenarios.
• Produces the waterfall - Opening deferred revenue, additions, recognised, closing reconciled, auditable, on demand.
This is the same layer our End-to-End NetSuite Implementation and Integration & Automation teams configure for growing SaaS clients, and where AI in NetSuite increasingly helps estimate and true up usage-based variable consideration automatically.
NetSuite's advanced revenue management and SuiteBilling for companies already on NetSuite, plus Zuora Revenue, Maxio, Chargebee, Ordway, Stripe Revenue Recognition and Sage Intacct in the wider market. Selection usually turns on pricing model complexity rather than company size — usage-based and hybrid pricing narrows the field quickly. See our roundup of the best ERP systems for software companies for a fuller comparison.
Metrics fail because of definitions, not calculations. Fix the definitions first and write them down.
Contracted recurring subscription value annualised. Exclude one-time services, exclude pass-through hardware, and decide explicitly whether committed usage counts. Publish that decision.
Recurring revenue from a cohort at the end of a period divided by that cohort's recurring revenue at the start, including expansion, contraction and churn, excluding new logos. Fix the cohort definition and the currency treatment before you calculate anything.
Fully loaded sales and marketing spend to acquire new customers, divided by new customers acquired in the same period. Include salaries, commissions, tooling and allocated overhead. Exclude customer success if you count it under retention, and apply that rule consistently.
CAC divided by new customer monthly recurring revenue, multiplied by gross margin. The gross margin term matters, a rupee of revenue is not a rupee of recoverable contribution.
Average revenue per account, multiplied by gross margin, divided by revenue churn rate. Calculate by segment and then weight. Blended LTV across enterprise and SMB customers is a number with no meaning.
Benchmark data has tightened considerably since the growth-at-any-cost period, and 2026 figures reward efficiency over speed.
Benchmarkit's 2026 report, covering 342 B2B SaaS companies, put the median Rule of 40 score at 25 percent, up from 15 percent the prior year, with the top quartile at 43 percent. Median CAC payback improved to 16 months from 18, while top-quartile companies recovered acquisition cost within six months. ARR per employee rose to roughly 175,000 US dollars, up 17 percent year on year.
Retention data varies sharply by segment, which is why blended benchmarks mislead. Enterprise SaaS with high average contract value tends to sit near 118 percent NRR. Mid-market sits closer to 108 percent. SMB-focused SaaS sits below 100 percent, meaning the average SMB SaaS business shrinks from its existing base without new logos.
Pricing model shows a structural gap too. Usage-based pricing posted median NRR around 108 percent against roughly 95 percent for seat-based models, a pricing architecture difference, not an execution difference.
One more finding worth noting for anyone building an AI feature roadmap: a large majority of B2B SaaS companies with AI functionality in their product do not charge incrementally for it. If that describes you, your unit economics will show the cost of AI inference without the corresponding revenue.
The breaking point is predictable.
• Contract volume passes the point where manual schedule maintenance is reliable.
• Pricing models diversify, so one template no longer fits.
• Investors start asking for cohort-level retention, not aggregate churn.
• Audit expectations rise, and the auditor wants a deferred revenue rollforward that ties.
• Someone leaves, and the model they built has no documentation.
The signal to watch is not company size. It is the number of exceptions in the spreadsheet. Once more than one in ten contracts needs manual handling, the model is already unreliable, a pattern we cover in more depth in revenue loss from untracked subscriptions and in how Indian SaaS startups prepare for Series B diligence.
Write the definitions document first. One page per metric — formula, inclusions, exclusions, cohort basis, currency treatment, owner. Get the CFO and CEO to sign it.
Make the ERP the source: Contract data belongs in the ERP, not the CRM. The CRM holds pipeline. The ERP holds obligations.
Automate revenue schedules before dashboards: Metrics built on unreliable revenue data are decorative.
Segment everything: Report NRR, CAC and LTV by segment and by pricing model. Blended figures conceal exactly the problems you need to find.
Reconcile ARR to recognised revenue every month: The bridge between them should be explainable in five lines. If it takes twenty, something is wrong.
Version the definitions: When a definition changes, restate history and note the change. Silent redefinition is the fastest way to lose investor trust.
This is exactly the reporting layer our SuiteAnalytics & BI practice builds on top of NetSuite, and it pairs well with the NetSuite CFO dashboards guide if you want the daily-tracking view as well as the monthly metrics pack.
Indian SaaS companies selling overseas carry a specific set of considerations that ERP configuration needs to reflect.
Export of services attracts its own GST treatment, including the choice between supplying under a letter of undertaking without payment of tax, or paying and claiming refund. Place of supply rules determine whether a transaction qualifies as an export at all, particularly for intermediary services. Foreign currency invoicing creates translation differences that must not contaminate ARR movement analysis, which is why constant-currency reporting matters.
There is also the newer statutory backdrop. The Income-tax Act, 2025 took effect from 1 April 2026, replacing the 1961 Act and introducing the unified tax year concept. Section references across internal documentation, ERP tax configuration and templates need review this year. The Income Tax Department's guidance on the new Act is the primary reference.
For companies planning a raise or an exit, one habit pays for itself repeatedly: keep a monthly metrics pack with signed definitions from the beginning — the same discipline behind why tech IPOs standardise on NetSuite for investor reporting. Diligence teams do not just check the numbers. They check whether the numbers have been calculated the same way for the last twenty-four months.
ARR is the annualised value of contracted recurring subscriptions at a point in time. Recognised revenue is the amount reported in the income statement for a period under Ind AS 115 or ASC 606. A contract signed on the last day of a quarter adds fully to ARR and almost nothing to that quarter's recognised revenue.
Usage-based fees are variable consideration. Estimate the amount, apply the constraint so recognised revenue is not likely to reverse significantly, and true up as actual usage is known. Where usage-based fees relate directly to distinct periods of service, allocating them to those periods is often appropriate.
It depends on segment. Enterprise-focused SaaS medians sit near 118 percent, mid-market near 108 percent, and SMB-focused SaaS below 100 percent. Usage-based pricing models post materially higher NRR than seat-based models. Benchmark against your own segment, not a blended industry figure.
When more than roughly one in ten contracts needs manual treatment in the spreadsheet, or when investors begin requesting cohort-level retention data. Company size matters less than contract complexity and pricing model diversity.
Either treatment is defensible, provided it is documented and applied consistently. Most companies exclude customer success from CAC and treat it as a retention cost. What damages credibility is switching between treatments across periods.
SaaS finance rewards precision more than most sectors, because the metrics are the story. Revenue recognition keeps you compliant. Unit economics tell you whether the business works. Neither survives long in a spreadsheet once contracts get interesting.
The companies that raise well and exit well are rarely those with the best numbers. They are the ones whose numbers have meant the same thing for two years.
SaasWorx works with technology and SaaS companies on ERP-based revenue recognition, billing structure and the metric layer that sits above them.
