Business Central vs NetSuite: Where Each One Wins for a Multi-Entity Group
Business Central and NetSuite both run a group of legal entities from one system, and the difference is not in the feature list. NetSuite puts every subsidiary into one account and one hierarchy, up to 250 of them. Business Central puts companies into environments, and each environment is tied to one country. That single architectural choice decides most of what follows: how you consolidate, how you localise, how you update, and what you pay for.
We should be clear about where we write from. Asio Services implements Business Central and nothing else. We have never delivered a NetSuite project and will not pretend otherwise. What we can do is compare the two architectures and the two cost models from documented facts, in the same spirit as our comparison of Business Central and Odoo, and tell you which questions a group’s finance and operations leadership should settle before either vendor gets a demo slot.
What does “multi-entity” mean in each product?
NetSuite’s answer is OneWorld. Oracle’s documentation describes it as a single NetSuite account managing records and transactions for multiple subsidiaries across tax jurisdictions and currencies. Subsidiaries sit in one hierarchy that rolls up to a root subsidiary. Each subsidiary has its own nexus, meaning its tax jurisdiction, and its own base currency, and consolidated reports can be produced for all child subsidiaries of any parent in the tree, in that parent’s currency. The limit is 250 subsidiaries per account, including the root, and subsidiary licences are counted by combination of country and base currency.
Business Central’s answer has three layers. A Microsoft Entra tenant holds environments. Each environment is tied to one country and its localisation, and runs on one database. Each environment holds companies, one per legal entity, up to 300. A subscription includes one production environment and three sandboxes. If your subsidiaries are in two countries, you buy a second production environment through your reseller, because Microsoft’s own guidance is explicit: environments are particular to a country, so an organisation working in several countries needs one per country.
The consequence is the sentence to remember. In NetSuite the group is one database with a tree inside it. In Business Central the group is a set of databases, one per country, with companies inside each. Both are legitimate. They are not interchangeable, and they suit different groups.
Where does NetSuite genuinely win?
Three cases, stated honestly.
Many countries, light local operations. A group with subsidiaries in eight countries, each one a sales or service entity with a small team, gets from OneWorld what Business Central has to assemble: one hierarchy, one chart-of-accounts policy, consolidation at any node of the tree without moving data between databases. In Business Central the same group runs eight environments and consolidates through the consolidation feature, which does work across environments through an API Microsoft provides at no charge, but it is a data transfer you set up and run, not a view.
Consolidation as the daily product. If the group’s headquarters lives in consolidated numbers, intercompany eliminations and currency translation all day, OneWorld was built around exactly that. Business Central consolidates well, and handles different charts of accounts, fiscal years, currencies and partial ownership percentages, but its centre of gravity is the operating company, not the holding.
One global instance as a governance choice. Some groups want one database on principle: one place to secure, one place to audit, one version everywhere. NetSuite gives that by design. Business Central gives you one tenant and one identity, but several databases, each updated on its own schedule.
Where does Business Central win?
Operational depth in each entity. Where subsidiaries are factories, warehouses or distribution businesses rather than sales offices, the weight shifts. Business Central Premium carries manufacturing and service management in the base product. The experience is set company by company, so a holding company can run Essentials while a plant runs Premium in the same tenant, and each user’s licence decides which companies they can open. The consolidation step becomes a small price for having each entity run on a system built for its operations.
Localisation delivered by the vendor, for some countries. Microsoft’s country availability page for Business Central online lists well over 150 countries and regions, but Microsoft itself localises only about twenty of them: the United States, Canada, Mexico, the United Kingdom, France, Germany, Spain, Italy, Belgium, the Netherlands, the Nordics, Switzerland, Austria, Czechia, India, Australia and New Zealand. Everywhere else, the localisation is a partner app installed on the international W1 base. The localisation is fixed when the environment is created, by the country you choose. NetSuite covers local tax reporting through a tax reporting framework supplemented by regional and country localisation SuiteApps installed on the account. Both work. The difference is who assembles it, and it only holds for the countries Microsoft localises: there, the country comes with the environment. For a subsidiary in Poland, Portugal, Brazil or Singapore, Business Central works the way NetSuite does everywhere: the country is a set of components you add and keep compatible with each other. A group should check which side of that line each of its subsidiaries falls on before counting localisation as a Business Central advantage.
A public price. Microsoft publishes its list price: 80 dollars per user per month for Essentials, 110 for Premium, 8 for Team Members, paid yearly. You can compute the licence line of a 200-user group on the back of an envelope before you talk to anyone. Oracle publishes no NetSuite price list. Every figure you find online comes from a partner or a negotiation, and the structure is a platform subscription plus modules plus users, with subsidiaries licensed by country and currency combination. That is not a criticism of the price. It is a statement about when you learn it.
The Microsoft estate. If the group runs on Microsoft 365, Business Central sits inside Excel, Outlook, Teams and Power BI in a way a Microsoft-heavy finance team notices within a week. That is a real switching cost against any non-Microsoft ERP, NetSuite included. How Business Central’s multi-company setup leans on that estate is covered elsewhere on this blog.
How do the two cost models actually differ?
Both are subscriptions. Both bill by user. The difference is in what else is metered, and when you find out.
In Business Central the metered items are documented by Microsoft: users by type, additional production environments, and database capacity above the included 80 GB plus 2 GB per Essentials user and 3 GB per Premium user. A group in four countries budgets four production environments. Nothing else is hidden, and the real cost of a Business Central implementation sits in services, not licences.
In NetSuite the metered items are the platform tier, the modules you activate, user licences by type, and subsidiary licences. The amount is negotiated deal by deal. The question a group should ask is not what year one costs, but what year four will.
The right comparison is therefore not licence against licence. It is a five-year model with the growth of the perimeter in it: two acquisitions, one new country, a doubling of warehouse headcount. Run both products through that model and the gap almost always moves, sometimes in each direction.
What does change cost, once you are live?
Update cadence is nearly identical, and neither vendor lets you skip a round. NetSuite delivers two scheduled version upgrades a year, applied to your account on Oracle’s staggered calendar. Business Central online delivers a major update every April and October, with a minor update in the months between, and each major comes with a five-month window in which you choose the date, environment by environment.
Customisation is where the models diverge. NetSuite is customised in SuiteScript, a JavaScript API, alongside its configuration and workflow tools, inside the single account. Business Central is customised in AL, delivered as extensions that sit beside the base application and never modify it. We maintain extensions of close to a thousand objects on Business Central online that go through every monthly update without intervention, and that discipline is built from the first object.
For a multi-entity group the practical question is scope. In NetSuite a script applies to the account and must be written to respect the boundary between subsidiaries. In Business Central an extension is installed per environment; a country can run a different version, or none, and one country’s problem stays in one database. Whether that is isolation or fragmentation depends on how your group is governed, and that is the real subject.
Which questions actually decide it?
We do not run this decision from a feature matrix. We start with three questions, and their answers usually make the product choice for you.
How many countries, and how heavy is each entity? Count the legal entities, then the countries, then rank each entity by operational weight: holding, sales office, service business, warehouse, plant. Many countries with light entities points to a single-instance model. Few countries with heavy entities points to Business Central. Many countries with heavy entities is the case where both need real work, and where a demo is the wrong next step.
Where does the group’s pain actually sit? The founding observation of our practice is that most expensive ERP failures in multi-entity groups are not technical. Nobody decided them. The software encoded the missing decision, faithfully, at scale. If your consolidation is late because subsidiaries do not share a chart-of-accounts policy, neither product fixes that. If a plant cannot close its month because inventory valuation was never defined, neither product fixes that either. That is the ground of our root cause consulting for ERP programmes, not of a product sheet.
Who will own the system in year three? A single global instance rewards a strong central finance function that owns the configuration. A per-country environment model rewards groups where subsidiaries have real operational autonomy and local IT capacity. Pick the architecture that matches how the group is actually run, not how the org chart says it is.
If you want those three answers written down before you take a vendor call, that is what our clarity assessment for a multi-entity ERP decision produces. It is deliberately neutral on the product, and if the answers say NetSuite, we will tell you.
FAQ
Can Business Central run all subsidiaries in one database, like NetSuite? Only if they share a country. An environment is tied to one localisation, so a group operating in several countries runs one environment per country and consolidates across them. Within one country, up to 300 companies can share an environment.
Is NetSuite always more expensive than Business Central? No, and nobody can tell you from a list price, because NetSuite has no public one. Business Central’s licence cost is predictable per user. NetSuite’s is negotiated across platform, modules, users and subsidiaries. Compare them on a five-year model that includes the entities you expect to add.
Does Asio Services implement NetSuite? No. We implement Business Central only, and this comparison is written from that position, using documented facts on both sides. When a group’s profile points to NetSuite, we say so rather than sell the wrong system.
Do both products force their updates? Yes. NetSuite delivers two scheduled upgrades a year on Oracle’s calendar. Business Central online delivers two majors, in April and October, plus minor updates in between, with a five-month window to schedule each major, environment by environment.