Business Central vs Sage X3: Two Opposite Ways to Hold a Multi-Entity Group
Sage X3 and Business Central both run a group of legal entities, and they hold the complexity in opposite places. Sage X3 puts every company of the group into one folder, one database, and absorbs the differences between countries through parameters: legislations, accounting models, ledgers. Business Central splits the group into environments, one per country, each with its own companies, and links them back together through intercompany and consolidation. The first model holds complexity inside one structure. The second holds it by partitioning. Most of what a group will live with for the next ten years follows from that choice.
Where we write from: Asio Services implements Business Central and nothing else. We have never delivered a Sage X3 project and will not pretend to. What we can do is compare the two architectures, the two cost models and the two ways of absorbing change from documented facts, as we did for Business Central against NetSuite, and say which questions a group’s finance and IT leadership should settle before either vendor gets a demo slot.
How does each product hold several companies?
Sage X3 is organised around the folder. Sage’s documentation defines a folder as a complete reference, identified by a code, that holds all the parameters, all the management rules and all the data. Inside it, legal companies and sites share one set of referentials. A customer or supplier record is created once for the folder, and an optional activity code lets each company keep its own exceptions on it, such as tax rule, payment terms or accounting code. Legislation is an attribute the system deduces from the company or site in context, and one folder can host companies under different legislations once the multi-legislation activity code is switched on. The folder currency is set at creation and cannot be changed afterwards.
Business Central is organised around the environment. A Microsoft Entra tenant holds environments. Each environment is tied to one country and its localisation, runs on its own database, and holds up to 300 companies, one per legal entity. A subscription includes one production environment and three sandboxes; each additional production environment bought through a reseller brings three more sandboxes and 4 GB of tenant-wide database capacity. Microsoft’s guidance is explicit: environments are particular to a country, so a group working in several countries needs one environment per country.
The sentence to remember: in Sage X3 the group is one database in which the differences between countries are parameters. In Business Central the group is several databases in which the differences between countries are the databases. Sage X3’s heritage explains its model. The product descends from Adonix, a French vendor Sage acquired in 2005, and it grew up in a mid-market where several legal entities under one roof is the ordinary case.
What does the single-folder model buy, and what does it demand?
The single folder buys shared referentials without integration. One item master, one business partner base, one set of units and currencies, visible to every company, with company-level exceptions where the law differs. It buys accounting at group depth: each legal company is tied to an account core model, and one model can carry up to ten ledgers, in up to five ledger currencies, each ledger with its own chart of accounts, and up to twenty dimension types, nine of them per ledger. A company can post the same entry to a local statutory ledger and an IFRS ledger at once, in different charts and currencies, and analyse it on nine axes.
What it demands is design before data. The account core model must exist before the legal company that uses it. The folder currency is fixed at creation. Sage’s own help advises switching multi-legislation on only when you are about to use it, because it slows some parameter screens. Each is a decision the group must have made before the first company exists, and each is expensive to revisit once entries are posted. The single folder is a powerful container precisely because it forces the group to decide its structure up front.
What does the environment model buy, and what does it demand?
The environment model buys isolation and predictability. A country runs on its own database with the localisation Microsoft or a partner built for it, updated on its own schedule. A plant in one country can run Premium with manufacturing while a holding elsewhere runs Essentials, because the experience is set company by company. And the price is public: Microsoft lists 80 dollars per user per month for Essentials, 110 for Premium and 8 for Team Members, paid yearly. Additional environments and database capacity above the included 80 GB plus 2 GB per Essentials user and 3 GB per Premium user are the only other metered items.
What it demands is assembly. Shared referentials are not free: the same customer in two countries is two customer records unless the group synchronises them. Intercompany trading works across environments and even across tenants, but connecting a partner in another environment means registering an app in Azure, exchanging connection details and renewing a client secret before it expires. Consolidation across environments runs through an API Microsoft provides at no charge, and it handles different charts of accounts, fiscal years, currencies and partial ownership, but it is a transfer you configure and run, not a view. Dimensions are unlimited, but only two are global and eight are shortcut fields on lines. The environment model keeps each unit simple by pushing the group’s shape into the connections between units.
How do the cost models differ?
Sage X3 is sold on quotation. Sage publishes no price list, and the licence comes either as a perpetual licence with an annual maintenance fee or as a subscription, on your own servers or hosted by Sage or a partner. Hosting, database licences and infrastructure are lines you or your partner carry. The question a group should ask is not what the licence costs, but which lines exist at all: licence, maintenance, hosting, database, upgrade projects, and who owns each one in year four.
Business Central is sold on a list. Users by type, additional environments, database capacity. A group in four countries budgets four production environments and knows its licence line before the first call. The real cost of a Business Central implementation is then in services, migration and the assembly work described above, not in the licence.
The honest comparison is a five-year model that includes the perimeter’s growth: two acquisitions, one new country. In the single-folder model an acquisition is one more company in an existing structure. In the environment model a new country is a new environment, a new localisation and a new set of connections. Run both products through that model and the gap moves, sometimes in each direction.
What does change cost once you are live?
This is where the two products are most opposite.
Sage X3 ships two releases a year, named by year and half, and 2026 R1 carries the internal version number 12.0.39. Nothing is applied to your folder on Sage’s calendar. Upgrading is a project you schedule, test and run on your own instance, and Sage’s own support blog notes that upgrades rarely fail because of the patch itself; they fail because the upgrade touches the whole technology stack around the application. Customisation is written in Sage’s own 4GL script inside the folder, under development guidelines that ask you not to develop inside standard entities and to group specific fields in specific screens or tabs. The freedom is real, and so is the consequence: every specific you write is yours to carry through every upgrade, and the upgrade is yours to run.
Business Central online applies a major update every April and October and a minor one in the months between. Each major opens a five-month window in which you pick the date, environment by environment, followed by a one-month grace period, after which the update is enforced and incompatible extensions are uninstalled to let it through. Customisation is written in AL 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 update without intervention, and that discipline is built from the first object, not retrofitted. The freedom is narrower. The consequence is that the vendor runs the upgrade, and your only job is to have code that survives it.
The practical difference is who owns time. With Sage X3 the group owns its version and pays for it with upgrade projects it must fund and staff. With Business Central, Microsoft owns the version, and the group pays with a discipline it must keep, twice a year, in every environment.
Which questions actually decide it?
We do not run this decision from a feature list. Three questions, and their answers usually make the product choice for you.
Where does the group’s complexity actually sit? Count the legal entities, then the countries, then the ledgers each entity must keep. Many entities in one or two countries, multi-GAAP reporting and shared master data point to the single-folder model. Few entities per country, each with heavy local operations, point to Business Central. Many countries with heavy local operations is the case where both products need real work, and where a demo is the wrong next step.
Who will own the system in year three? Sage X3 rewards a group with a central IT and finance function that can own an instance, its parameters and its upgrades. Business Central rewards a group whose subsidiaries have real operational autonomy and which prefers to rent the platform’s evolution rather than run it. Pick the architecture that matches how the group is actually run.
What has not been decided? 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. A folder built before the group agreed its account core model, or a set of environments built before the group agreed its intercompany rules, fails in the same way and for the same reason. That is the ground of our root cause consulting for ERP programmes, and it comes before either product. How Business Central’s multi-company setup gets decided in practice is covered elsewhere on this blog.
If you want those three answers written down before a vendor call, that is what our clarity assessment for a multi-entity ERP decision produces. It is neutral on the product, and if the answers say Sage X3, we will tell you.
FAQ
Can Business Central put all subsidiaries in one database, like a Sage X3 folder? 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 links them through intercompany and consolidation. Within one country, up to 300 companies share an environment.
Does Sage X3 force updates the way Business Central online does? No. Sage ships two releases a year, but the upgrade is a project you schedule on your own instance. Business Central online applies two majors a year within a five-month window you choose, then enforces the update.
Is Sage X3 cheaper than Business Central? Nobody can say from a list price, because Sage publishes none. X3 is quoted per project, as a perpetual licence plus maintenance or as a subscription, with hosting on top. Business Central’s licence is public and per user. Compare them on a five-year model that includes the entities you expect to add.