Automated ASC 606 compliance for complex SaaS revenue
Enso calculates your performance obligations, applies the correct recognition method for each, and posts journal entries automatically to NetSuite or your ERP. No revenue accountant spreadsheets required.
Book a Demo| Month | Usage | Recognized | YTD | Status |
|---|---|---|---|---|
| Jan 2025 † | 6.2M reqs | $8,333 | $8,333 | Posted |
| Feb 2025 | 9.8M reqs | $9,800 | $18,133 | Posted |
| Mar 2025 ◀ | 13.4M reqs | $13,400 | $31,533 | Posted |
| Apr 2025 | ~16M reqs | $16,000 | $47,533 | Forecast |
From signed contract to recognized revenue
Enso reads your contracts and identifies each performance obligation, including subscription access, implementation, usage, and support, and allocates the transaction price across them.
For each obligation, Enso applies the correct recognition method: ratable over the term, at a point in time, or usage-based as events occur.
Revenue and deferred revenue entries are posted to your ERP each period. Forecasts are available for obligations not yet satisfied.
Recognize revenue correctly without a team of spreadsheets
- Variable Consideration Handled
Usage-based revenue, milestone payments, and refund reserves are estimated and constrained per ASC 606 variable consideration guidance.
- Multi-Element Arrangements
Standalone selling prices are calculated per element and used to allocate contract value across obligations, keeping your order to cash process compliant from contract to recognized revenue.
- Modification Support
Contract modifications, including expansions, downgrades, and cancellations, trigger a re-assessment and update recognition schedules prospectively or cumulatively.
- Audit-Ready Documentation
Every recognized amount links to the contract, the obligation, and the accounting method applied. Auditors get documentation automatically.
We used to have two accountants spending a week every quarter just on rev-rec schedules. Enso runs it continuously and the schedules are always current.
Common questions
- Yes. US companies use Enso under ASC 606, the primary standard for US GAAP revenue recognition. European and UK companies use IFRS 15, which shares the same five-step model. Indian companies reporting under Ind AS 115 are also supported, as Ind AS 115 closely mirrors IFRS 15. Jurisdiction-specific disclosure requirements, including 10-K breakdowns for US public companies and statutory notes for Indian companies, can be configured separately.
- Usage-based revenue falls under the sales- and usage-based royalty exception, which permits recognition when the usage occurs. Enso applies this automatically when your contract includes usage pricing.
- Enso separates the minimum (recognized ratably) from the variable overage (recognized as usage occurs) and manages the contract asset / liability balance that results from the timing difference.
- For US SEC filers, Enso produces ASC 606 disclosures including disaggregation of revenue by product and geography, remaining performance obligation schedules, and deferred revenue rollforwards for 10-K and 10-Q filings. European companies under IFRS 15 get equivalent disclosures structured for annual reports and interim statements. For Indian companies under Ind AS 115, Enso generates the required notes covering revenue recognition policies, contract balances, and unsatisfied performance obligation schedules.
Does Enso support ASC 606, IFRS 15, and India Ind AS 115?
How does Enso handle usage-based revenue under ASC 606?
What if our contract has a minimum commitment plus usage overages?
What disclosure data does Enso generate for US, EU, and India financial reporting?
Related features
Ready to see it in action?
Book a 30-minute demo and see how Enso handles your specific billing and revenue workflows.
