A SaaS company with one entity can run revenue recognition from a billing tool and a spreadsheet for longer than most auditors would like. Add a US subsidiary, a customer billed in euros and a reseller agreement between two group companies, and the same setup starts to produce schedules that nobody can reconcile to the group report.
The question changes at that point. Finance needs a schedule for each contract, and it also needs to know which entity owns that revenue, in which currency, and how the deferred balance in each ledger rolls up into consolidated figures. This guide compares the main ways to do that and gives you the contracts to test them with.
Light is one of the options below. We describe each approach with links to product information and to the more detailed comparisons on this site, and we suggest where Light fits and where it does not.
What makes revenue recognition harder across entities?
The accounting standard stays the same when you add an entity. ASC 606 and IFRS 15 share the same five-step model, so the contract analysis does not change because a second company signs it. The operational work around that analysis grows in four places.
- The contracting entity. The entity that signs and invoices the customer owns the revenue and the deferred balance. A platform has to keep that link from the contract line to the ledger of the right company.
- Currency. A contract billed in euros by a US entity creates deferred revenue in a foreign currency. Finance needs the original amount, the rate used and the presentation in group currency.
- Intercompany flows. When one group company resells another's software, both ledgers record the transaction and the group report has to eliminate it. Revenue metrics should leave those internal sales out as well.
- Period control. Credits, amendments and late invoices arrive after a period closes. The platform should post the effect into an open period with a clear trail, rather than reopen a period your auditors have already reviewed.
The SaaS revenue recognition guide works through a single subscription, and the revenue recognition buyer's guide covers the single-entity tests. This guide adds the group layer on top.
Which platforms should a global SaaS company compare?
This shortlist reflects Light's assessment of public product information, including the comparisons published on this site. It is a guide to fit, rather than an independent ranking.
| Approach | Example products | When to include it | What to establish before buying |
|---|---|---|---|
| Suite ERP with a revenue module | NetSuite OneWorld | The project covers finance and wider operations across subsidiaries | Which revenue module the proposal includes, and the implementation scope |
| Financial management platform | Sage Intacct | The group needs multi-entity accounting and consolidation with a finance-led project | The revenue module, its configuration and how schedules reach consolidation |
| AI-native general ledger | Rillet | You want a modern ledger with revenue recognition and plan to keep separate spend and payment tools | Which workflows the ledger covers itself and which stay in connected systems |
| Billing and revenue layer beside a ledger | Maxio, Chargebee, Stripe Billing | Billing complexity is the main problem and the current ledger works | How revenue and deferred balances sync into each entity's ledger, and who reconciles them |
| Finance platform with billing and revenue built in | Light | You want contracts, revenue schedules, AR, AP and consolidation in one system of record | Coverage of your contract types against your approved revenue policy |
NetSuite OneWorld
Best for: groups buying an ERP that covers finance alongside orders, inventory or projects.
NetSuite OneWorld supports multiple subsidiaries, currencies and consolidated reporting. Revenue recognition sits in a module of the wider suite, so ask the vendor or partner which one the proposal includes and what it costs to configure.
Check carefully when: the business is a software company with simple operations. The NetSuite alternatives guide covers pricing and implementation cost, and our NetSuite comparison sets out where Light differs.
Sage Intacct
Best for: finance-led projects that need multi-entity accounting and group reporting.
Sage Intacct's consolidation documentation describes multi-entity and multi-currency reporting with drill-down into consolidation journals. Confirm the revenue management module in the proposal and test a contract amendment through to the consolidated report. See our Sage Intacct comparison.
Rillet
Best for: teams that want an AI-native ledger with revenue recognition and plan to keep their existing spend tools.
Rillet's product overview describes its general ledger, AI features, revenue recognition and reporting. Its integration catalog lists spend providers it connects to. If you want to reduce the number of finance systems, ask which payment, card and expense workflows remain elsewhere. Our Rillet comparison covers the differences.
Maxio, Chargebee and Stripe Billing
Best for: companies whose main gap sits in billing, with a ledger they intend to keep.
These products sit beside the general ledger rather than replacing it. Maxio combines subscription billing, revenue recognition and SaaS metrics and syncs into a separate ledger. Chargebee runs subscription billing and syncs invoices one way into accounting systems such as NetSuite, QuickBooks, Xero or Sage Intacct. Stripe Billing handles subscriptions and collection, and works with Light through the Stripe integration.
Check carefully when: the group has several entities. Each sync adds a reconciliation between the billing record and each ledger, and someone on the team owns every difference.
Light
Best for: SaaS groups that want contracts, revenue schedules, receivables, payables and consolidation in one system of record.
Light's subscription management product covers contract-based billing and revenue recognition templates for IFRS 15 and ASC 606 workflows. Release templates schedule revenue on a straight-line, by-days or daily basis while keeping the exact contract total. Credits applied to invoices adjust deferred revenue by product. A release that falls in a closed period rolls into the earliest open period instead of failing.
Those schedules post into the ledger of the entity that owns the contract. Multi-entity accounting and consolidation then carry them into group reporting, and SaaS metrics read MRR, ARR and deferred revenue from the same contracts and ledger while excluding sales to your own group companies.
What to ask Light to demonstrate: an annual contract billed by one entity in a foreign currency, a mid-term upgrade, a credit note and the group deferred revenue roll-forward that results.
Check carefully when: your contracts depend on judgments such as allocating a transaction price across several performance obligations with variable consideration. Bring those contracts to the demo and confirm any gap directly, instead of assuming that a standard's label covers every arrangement.
How should you test a platform with your own contracts?
Give every vendor the same contracts and write down the expected result before the session. The point is to see the full path from contract to group report, so ask for each case to finish in the consolidated figures.
| Case | What good evidence looks like |
|---|---|
| A 12-month prepaid contract billed by the US entity to a German customer in euros | Monthly releases in euros, the rate used, and the deferred balance in both entity and group currency |
| A mid-term upgrade on that contract | The revised schedule, the catch-up entry and the history of the change |
| A credit note in month seven | The adjustment to deferred revenue by product, with the original release preserved |
| An invoice posted after the period closed | The release landing in the first open period, with a trail a reviewer can follow |
| A resale between two group companies | Revenue in the selling entity, cost in the buying entity and the elimination in the group report |
| The group deferred revenue roll-forward | Opening balance, billings, releases and closing balance that tie to each entity's ledger |
These are evaluation cases, not claims about which vendor passes them. The worked intercompany elimination and the group revenue example give you numbers to start from.
Should billing and revenue live in the ledger or beside it?
Both setups work, and the right one depends on where your complexity sits.
A billing and revenue layer beside the ledger suits a company with complex pricing, one or two entities and a ledger that already closes on time. You keep a specialist tool where it earns its place, and you accept a sync and a reconciliation for each entity.
A single system of record suits a group where the entities, currencies and intercompany flows cause more work than the pricing does. The contract, the invoice, the schedule and the consolidated report share one record, so there is nothing to reconcile between them. You trade some billing depth for that, so test your most unusual price plan before you decide.
“You put best-of-breed tools around it, so you don't need that much from a finance system. You just need it to run smooth and be really easy to integrate.”
KeyShot shows the second route. Before Light, its finance stack ran separate revenue recognition, payables, expense and bank-connector tools around e-conomic, Excel and Xero. Today AR, AP and the general ledger run on Light across its Danish and US entities, while HiBob, Salesforce and Abacum stay connected. One story does not predict your result, but it shows the scope to discuss.
Frequently asked questions
What is multi-entity revenue recognition? It is the process of recognizing contract revenue in the correct period for each legal entity in a group, in that entity's currency, and carrying the result into consolidated reporting with intercompany sales eliminated.
Do ASC 606 and IFRS 15 need different software? Both standards use the same five-step model, so one platform can support both. Confirm which framework each entity reports under and where your approved policies differ, then test those contracts in the demo.
Can a billing tool handle revenue recognition on its own? Some billing tools include revenue schedules. In a group, you still need those schedules to reach the right entity's ledger and the consolidated report, so evaluate the sync and the reconciliation as part of the tool.
What should a revenue recognition demo include? A foreign-currency contract, an amendment, a credit note, a late invoice after period close and an intercompany resale, each followed through to the group deferred revenue roll-forward.
When does a SaaS company need multi-entity revenue recognition? Usually when it opens a second legal entity that signs or invoices customers. From that point, deferred revenue sits in more than one ledger and the group report has to combine them.
Product information from earlier Light comparisons, checked between September 28 and October 6, 2026, and Light's product documentation as of November 2026. Features, availability and commercial terms vary by edition, country and contract. Confirm them in the proposal for your business.
