If you run a SaaS company in India and have US customers, investors, or auditors asking about ASC 606 compliance, you already know the pressure. Revenue recognition is no longer a back-office problem. It sits right at the centre of how investors read your numbers and how your finance team closes each month.
This guide walks through what ASC 606 means for Indian SaaS companies, where most teams get stuck, and how to set up NetSuite to handle it without breaking your existing reporting.
ASC 606 is the US GAAP revenue recognition standard issued by the Financial Accounting Standards Board (FASB). It replaced older, industry-specific rules with a single five-step model. The goal is to make revenue reporting consistent across industries and geographies.
For Indian SaaS companies, ASC 606 becomes relevant when:
India's own accounting standard, Ind AS 115, follows the same five-step model as ASC 606. The conceptual framework transfers well. The differences show up in specific areas like contract modifications, variable consideration, and disclosure requirements.
Here is how the five steps work in a typical Indian SaaS context:
A contract exists when both parties have approved it and each party's rights and obligations are clear. For SaaS, this is usually your subscription agreement or order form. The challenge comes with multi-year deals signed in rupees with quarterly invoicing.
Each distinct promise to the customer is a separate performance obligation. In SaaS, this often includes:
Many Indian SaaS teams bundle these into a single line item on the invoice. That works for billing, but not for revenue recognition. You need to separate them.
This covers the total consideration you expect to receive. Variable consideration like usage-based pricing, discounts, or refund clauses requires an estimate. You can use either the expected value method or the most likely amount method. For SaaS companies billing in USD or EUR, you also need a clear policy on how you translate variable amounts back into your functional currency.
Once you have separate performance obligations, you allocate the transaction price based on standalone selling prices (SSP). If you sell implementation at ₹5,00,000 separately and your SaaS subscription at ₹10,00,000, that ratio drives how you allocate revenue from a bundled deal.
Revenue is recognised when (or as) a performance obligation is satisfied. For SaaS subscriptions, this is over time. For one-time implementation, it may be at a point in time or over the project period, depending on the contract terms.
These are the areas that create the most friction:
NetSuite's Revenue Management module is built for ASC 606 and IFRS 15 compliance. Here is how the setup maps to the five-step model.
In NetSuite, a Revenue Arrangement corresponds to a contract. Revenue Elements map to performance obligations. When you create an invoice or sales order, NetSuite can automatically create a Revenue Arrangement and assign Elements based on your item setup. You define each item as a revenue element with its own recognition rule ratable, straight-line, or event-based.
NetSuite lets you configure SSPs per item or item category. When a customer buys a bundle, NetSuite applies the residual or relative SSP method to allocate the transaction price. You set this up once, and it applies to all new contracts automatically.
For each element, NetSuite generates a recognition schedule. A 12-month subscription starting 15 March 2026 produces 12 monthly recognition entries. If the contract spans your financial year, NetSuite handles the split across periods without manual intervention.
When a customer upgrades or downgrades, NetSuite handles the modification at the arrangement level. You can reassign elements, adjust the transaction price, and let the system recalculate the recognition schedule prospectively or retrospectively based on your accounting policy.
Here is a practical sequence for teams setting this up for the first time:
1. Audit your existing item master
Identify every item you sell and classify it as a subscription, professional service, one-time product, or support. This classification drives your recognition rules.
2. Define performance obligations
Map each item to a performance obligation type. Set up revenue recognition rules in NetSuite under Setup > Accounting > Revenue Recognition Rules.
3. Set standalone selling prices
Enter SSPs for each item. If you do not have external pricing data, use the adjusted market assessment approach or the expected cost-plus margin approach.
4. Enable Revenue Management on existing transactions
For new contracts, Revenue Arrangements auto-generate if your items are set up correctly. For existing contracts, you may need to create arrangements manually or run a data migration.
5. Reconcile deferred revenue
Run the Revenue Recognition Forecast report in NetSuite and reconcile it against your current deferred revenue balance on the balance sheet. Investigate variances before you close the first period under the new setup.
6. Set up period-end recognition runs
Automate the Generate Revenue Recognition Journal Entries process in NetSuite. Schedule it to run before each period close. This removes manual journal entry errors from the equation.
If your Indian entity reports under Ind AS, Ind AS 115 applies instead of ASC 606. The five-step model is identical. The disclosure requirements differ slightly, and there are specific carve-outs under Ind AS for some transition reliefs.
For companies that need to report under both standards common when you have an Indian operating entity and a US holding company, NetSuite supports multi-book accounting. You can run one book under Ind AS 115 and another under ASC 606 simultaneously, with shared transactions but separate recognition rules.
ASC 606 compliance is table stakes for Indian SaaS companies that want to raise capital from US investors, pursue US enterprise deals, or eventually list on a US exchange. The standard itself is not complicated once you break it down into the five steps. The challenge is implementation at scale without manual workarounds.
NetSuite's Revenue Management module handles the heavy lifting, provided you set it up with the right item classification, SSPs, and recognition rules from the start. Getting these right early saves time during audits, due diligence, and monthly closes.
At SaasWorx, we work with Indian SaaS companies at Series A through pre-IPO stages on their NetSuite implementations, including ASC 606 and Ind AS 115 setups. If your team is working through a similar challenge, we are happy to have a practical conversation about where to start.
