"Multi-entity accounting software" shows up in almost every RFP from a company running more than one legal entity, and it means something different in nearly every vendor's mouth. Some vendors mean the ability to keep two sets of books straight without a spreadsheet bridging them. Some mean rolling those books into one consolidated statement with intercompany eliminations already removed. Those are not the same purchase, and a demo that shows one convincingly can leave a buyer assuming the other is covered too. I'm Patrick. del.ai migrates NetSuite customers to Odoo, so I have a commercial stake in how multi-entity accounting software gets evaluated here. Read the argument on its own terms, not on who's making it. This piece breaks the category into the layers a buyer is comparing and checks what NetSuite OneWorld and Odoo multi-company each automate today. It also names the one layer where Odoo's free tier genuinely falls short.
Every vendor selling into this category is technically telling the truth when it says it supports multi-entity accounting. The trouble is that "multi-entity accounting" bundles three separable capabilities that mature at very different rates. A vendor can be genuinely strong at one while shipping nothing at another.
Layer one is entity-level books. Each legal entity gets its own chart of accounts, its own tax rules, and its own statutory close, all inside one system instead of scattered spreadsheets or separate instances. This is the layer every serious ERP solved years ago, NetSuite and Odoo included.
Layer two is intercompany operations. An invoice raised by one entity against another needs to generate a matching record on the other side automatically, in the right currency. Nobody has to re-key it by hand every month.
Layer three is group-level consolidation: taking every entity's correct, closed books and rolling them into one set of statements for the board. Intercompany balances get eliminated so the group number doesn't double-count money that moved between entities under common ownership.
The buying mistake is treating these three as one feature. A sales demo built around layer one, entities holding separate books cleanly, tells a buyer nothing about whether layer three works, or whether it exists at all. Layer one is table stakes today. Layer three is where the category separates vendors, and it's usually the layer buyers check last, if they check it at all before signing.
This article uses that three-layer framework throughout: what to check before buying, layer by layer, and where NetSuite OneWorld and Odoo multi-company each land on layers one and two. It closes with a direct answer on where the group-level layer stands in Odoo today.
This checklist comes from a vendor with a named capability limit of its own: del.ai's migration target, Odoo, doesn't ship free cross-entity consolidation today. That gap is named directly later in this article rather than left for a buyer to discover mid-evaluation. With that disclosed, four checks apply to any multi-entity accounting software, del.ai's included. First, does each entity's close hold up to its own audit independent of every other entity, with its own chart of accounts and statutory reports. Second, are intercompany eliminations automatic, or does someone re-key both sides of every intercompany transaction into a spreadsheet each month. Third, is consolidated financial statement generation native to the system, or a bolt-on tool layered on top of it. Fourth, if you left this vendor tomorrow, who owns the resulting code and data, and can you take it with you.
Source: NetSuite OneWorld and Odoo Community product documentation, 2026.
At the entity level, this comparison is closer than most vendor conversations suggest. NetSuite OneWorld and Odoo Community both let each legal entity hold a complete, separate set of books inside one system. Each entity keeps its own chart of accounts, its own tax rules, its own statutory reporting. That has been a solved problem on either system for years.
Intercompany documents follow a similar pattern. An invoice raised by one company against another generates the matching bill on the other side automatically. It posts in whichever functional currency each entity uses, and nobody re-enters the transaction by hand. That removes exactly the kind of manual re-keying that eats a Controller's Monday in a multi-entity close.
Multi-currency checks out the same way. On a live Odoo 18 Community instance we probed directly on July 22, 2026, every journal entry and every company record carries built-in multi-currency fields, and that same probe found 170 currencies loaded in the instance. Dedicated foreign-exchange gain and loss accounts sit on the company record alongside a currency exchange journal. That is real, transactional multi-currency, not a description lifted from a features page. NetSuite advertises meaningfully broader currency coverage than Odoo's verified 170. For most multi-entity groups transacting in a much smaller number of currencies, that gap rarely changes the buying decision.
Localization is stronger on the Community side than most buyers expect. That same Odoo 18 Community instance, probed directly on July 22, 2026, carries 232 country-specific modules, all LGPL-3 licensed, covering tax rules, fiscal positions, and country e-invoicing or e-filing requirements, installable out of the box and several already active. The one named exception is Intrastat: a search for an Intrastat module in that instance came back empty, so EU Intrastat declarations are not available on Community today.
None of this is the full entity-level rundown, and repeating it here would only pad this article without adding anything a buyer weighing this purchase needs.
What none of the above touches is the layer above entity books and intercompany documents, where multi-entity accounting software purchases get complicated. That layer is rolling everything into one set of group statements.
del.ai's own product has a real gap here, and it belongs in the first sentence rather than the last. Odoo's financial consolidation engine is Enterprise-only, and we found no free replacement for it. No, multi-entity accounting software and financial consolidation software are not the same purchase, even though they surface in the same searches. Multi-entity accounting software keeps several sets of entity-level books straight and lets them see each other. Financial consolidation software takes those already-correct books and rolls them into one set of group statements. Intercompany balances get eliminated so the group number does not double-count money that moved between entities. We checked the OCA candidate repository most likely to fill that gap, OCA/account-consolidation, across three Odoo versions (17.0, 18.0, and 19.0) in 2026. It came back empty on every branch, not even a stub module. Some buyers instead price a dedicated consolidation or EPM tool sitting on top of whichever ERP they run, worth pricing separately from either vendor's native answer.
Source: ↗ (GitHub repository, verified empty on 17.0, 18.0, and 19.0 branches, checked July 2026).
NetSuite OneWorld ships native multi-subsidiary consolidation as part of the product a OneWorld customer already pays for at that tier. Consolidated financial statements, currency translation, and standard eliminations run inside the platform without a separate purchase.
Renewing every year is the specific consequence of where Odoo's Consolidation app sits: proprietary, subscription-priced, and outside the LGPL core del.ai deploys. The argument that runs through the rest of a del.ai migration is that you own the code and stop paying a renewal once you're on it. That argument does not apply to this one module. Running it means licensing Enterprise specifically for consolidation.
We also checked the closest adjacent capability: single-entity financial statement reporting, the report definitions a consolidation would eventually roll up. The one candidate module we found for it is AGPL-3 licensed rather than LGPL-3. That distinction matters more than it looks. Running it unmodified carries no obligation. Modifying it and running the modified version as a network service obliges you to publish the modified source to users of that service. That matters if the goal is owning sellable IP rather than generating a report.
Three honest paths exist today for a buyer who needs the group-level layer and is looking at Odoo.
That third path is worth stating as a rule rather than leaving it implied, because it is the question OneWorld buyers ask next.
del.ai migrates NetSuite customers to Odoo, and the honest answer here decides whether that applies to you specifically: no, running NetSuite OneWorld does not automatically disqualify you. The exclusion runs by capability, not by NetSuite tier. A OneWorld tenant qualifies for a del.ai migration unless it uses transfer pricing, per-jurisdiction statutory reporting, or complex intercompany eliminations. Those are the same three capabilities this article has already named as the ones Odoo's free tier does not cover today. Any NetSuite tier below OneWorld qualifies outright, with no additional check needed. A OneWorld tenant that is not using those three specific capabilities gets evaluated the same way as any other NetSuite customer. The evaluation runs on NetSuite spend, employee count, and the rest of the discovery conversation, not on the OneWorld label by itself. That distinction is worth stating plainly rather than leaving OneWorld customers to assume the worst from a features page.
Source: NetSuite OneWorld tier and Odoo feature comparison, vendor documentation, 2026.
None of the capability detail above matters if the board has already told finance there is no new line item for this. So here is the cost side, modeled rather than observed: del.ai has zero completed migrations to date, so nothing below is a customer result. It is the same illustrative cost model built for every discovery call.
The full cost stack for staying on NetSuite includes more than the license. It also includes the Alliance Partner retainer, SuiteApps, the BI and ETL tooling layered on top, and the internal admin headcount it takes to run all of it. Together, that stack runs $210,000 to $680,000 all-in over the relevant multi-year horizon, depending on how much of it a given company carries. A OneWorld tenant tends to sit toward the higher end of that range because more subsidiaries and more integrations accumulate more of every layer. It is not because OneWorld itself is priced differently.
A del.ai migration, for qualifying migrations within the signed scope document, is a fixed fee starting ~$50k, with hosting from ~$2k/mo afterward. That is funded by the NetSuite spend already being cut, not a new budget line finance has to justify separately. The migration check is the renewal check that would otherwise have gone to NetSuite or an Alliance Partner.
This math holds the same way for a qualifying OneWorld tenant as it does for a Standard-tier tenant. The capability check from the section above, whether the tenant uses transfer pricing, per-jurisdiction statutory reporting, or complex eliminations, is a separate question from the cost math here. A more expensive NetSuite tier is not the same thing as an automatic exclusion, and buyers should not conflate the two.
At the discovery stage, del.ai's floor is $120,000 or more a year in NetSuite spend and 50 to 500 employees, with no hard revenue cutoff. Below that spend level, the fixed migration fee does not have enough NetSuite cost to fund itself against.
del.ai migrates NetSuite mid-market customers to Odoo, and a OneWorld tenant still qualifies for that migration unless it uses transfer pricing, per-jurisdiction statutory reporting, or complex intercompany eliminations. Automated cross-entity financial consolidation with eliminations is not available for free in Odoo today, and that is the gap this article named directly rather than leaving for a sales call.
The buying rule that follows applies to any vendor selling multi-entity accounting software, not only del.ai. Ask which of the three layers, entity books, intercompany operations, or group-level consolidation, a given demo is showing you. A demo will usually show the layer that is finished, because that is the layer that looks good in fifteen minutes. Entity-level separation and intercompany documents are the layer most vendors demo, because that layer is genuinely solved on most modern systems. Consolidation is the layer that gets glossed over, described in a sentence, or left for the second call. It is the layer where the real differences between vendors, and between editions of the same vendor's product, live.
For del.ai specifically: any NetSuite tier below OneWorld qualifies outright. A OneWorld tenant qualifies unless it needs the three capabilities named above, and that is said here, in writing, before an SOW rather than discovered partway through one.
Built for mid-market companies on NetSuite spending $120,000 or more a year, OneWorld tenants included, as long as transfer pricing, per-jurisdiction statutory reporting, and complex intercompany eliminations are not part of the setup.
30 minutes, no pitch. Bring your actual entity structure and consolidation setup, and we will walk it against what is actually free in Odoo today, before anything gets signed.
Sources
1. Original analysis. External citation checked directly. ↗ (GitHub, verified empty on the 17.0, 18.0 and 19.0 branches, checked July 27, 2026).