Business Central vs Xero

Business Central vs Xero at a glance

Xero and Business Central are not peer substitutes — they sit on a maturity curve. Xero is a cloud accounting platform built for small businesses: a clean general ledger, bank feeds, invoicing, expense claims, projects on higher tiers, and a large app marketplace. Business Central is Microsoft’s ERP for small and mid-sized companies: it covers the accounting core, then adds inventory, warehouse, purchasing, projects, multi-company, and (on Premium) manufacturing and service management on one shared database.

Most companies do not pick between them on day one. They run Xero until accounting alone stops being enough, then evaluate an ERP — often Business Central if the organization already lives in Microsoft 365. The decision is about timing and triggers, not brand preference. Flectic implements Dynamics 365 and Odoo and works alongside Xero, so the recommendation follows operational reality rather than which product we resell.

Xero vs Business Central pricing in 2026

The two products price on different models, and that difference drives every TCO conversation. Xero sells tiered flat-rate monthly subscriptions per organization — Early, Growing, and Established in the US — with no per-user license fees on the base plan. As of August 2026, regular US list is $25 (Early), $55 (Growing), and $90 (Established) per month; Xero has announced US list increases effective 1 October 2026 to $27 / $59 / $97. Promotional intro discounts (for example 80% off the first three months for eligible new US customers) change the first-quarter bill but not the long-run model.

Business Central is sold per named user. Microsoft’s first list-price increase in more than five years took effect 1 November 2025: Essentials moved from $70 to $80 per user per month, Premium from $100 to $110, and Device from $40 to $45, with higher included storage. Team Members remain $8 per user per month for limited read/approve access. Listed rates assume annual commitment; partner quotes and regional currency can differ.

Because of that structure, Xero stays dramatically cheaper for a small services team, while Business Central becomes easier to justify once you need inventory, warehouse, manufacturing, or multi-entity capability that would otherwise require a stack of Xero add-ons (inventory apps such as Cin7 or Unleashed, multi-entity consolidators, job systems, Power BI-class reporting). Price the capabilities you actually need — Xero plus a full operational stack can approach or exceed BC license cost while still being less integrated.

Capability matrix: accounting vs ERP

Feature walls only help when they map to real decisions. The matrix below is the operational gap that forces graduate conversations — not a claim that Xero is “worse accounting.” For pure ledger work (invoicing, bank rec, sales tax, basic projects), Xero is excellent and often preferable. The break points are operations that an accounting product was never designed to own end-to-end.

On Business Central, license edition matters: Essentials covers finance, sales, purchasing, inventory, warehouse, projects, and multi-company. Premium adds full manufacturing and service order management. Light assembly/kitting can often stay on Essentials; production with routings, machine centers, and capacity planning needs Premium. Confusing those SKUs is a common RFQ mistake.

Where Xero stops and BC starts

Xero’s strengths are real: bank reconciliation, a clean ledger, invoicing, project tracking on higher plans, Hubdoc-style document capture, and a mature marketplace. Its limits define the graduate moment. Native inventory tracks quantities and cost for straightforward goods businesses, but practitioners and inventory vendors still call out ceilings: weak multi-location depth without add-ons, no serious bin-level WMS, no serial/lot traceability in core accounting inventory, limited landed-cost modeling, and no manufacturing BOMs. Inventory Plus (US, optional on Growing/Established) adds multi-location and channel sync for goods-based SMBs — useful, and still not a warehouse or production system.

The same pattern repeats across structure. Multi-entity in Xero means a separate Xero organization per legal entity and consolidation outside the product — spreadsheets or a specialist multi-entity layer. Manufacturing, MRP, and production orders do not exist in Xero natively. Service and job costing is lighter than an ERP project or service module. Each gap is intentional product design: Xero is accounting software, not an ERP. The trap is expecting it to behave like one after the business has already outgrown the model.

Inventory, warehouse, and manufacturing — the decisive gap

For most growing SMBs, inventory is the capability that forces the move. Business Central includes inventory valuation methods (FIFO, average, standard), item tracking by lot and serial number, location and bin-level warehouse management, pick/put-away/ship workflows, and assembly BOMs on Essentials with full production on Premium. Xero can track stock quantities and value for simple catalogues; even with Inventory Plus or marketplace apps (Cin7, Unleashed, Fishbowl-class tools), you still reconcile operational truth back to the ledger — the classic “two systems, one month-end” tax.

Manufacturing is the extreme case. A maker on Xero typically bolts on production or inventory software and posts finished goods and COGS into Xero after the fact. Business Central runs production orders, consumes components, posts labor and overhead, and increments finished goods in the same database as the ledger. For a manufacturer or serious assembler, BC is not a marginal upgrade to Xero — it is a different category of system. Match license to process: assembly/kitting may fit Essentials; capacity, routings, and shop-floor planning need Premium.

Multi-entity, intercompany, and consolidation

The second common trigger is corporate structure. A group running two or more legal entities in Xero runs a separate organization per entity and consolidates externally. That works for two simple entities and becomes painful as entity count, currencies, and intercompany volume grow. Multi-entity analysis of Xero stacks repeatedly flags per-entity app overhead (payroll, AP automation, inventory connectors multiplied by every org) and manual elimination work. Business Central supports multiple companies in one environment, intercompany posting between them, and financial consolidation including currency translation.

This matters beyond accounting convenience. Intercompany sales, shared costs, and transfer pricing are error-prone across separate ledgers, and spreadsheet consolidation is exactly the fragile process an ERP is meant to remove. If your group has more than two entities, multi-currency operations, or meaningful intercompany volume, native multi-company capability often justifies the move on its own — even before warehouse or manufacturing enters the brief.

Add-on stack TCO and graduate triggers

Headline Xero pricing understates total cost once operations expand. Growing goods or multi-entity businesses commonly bolt on inventory, CRM, job/project tools, advanced reporting, and payroll — each with its own subscription and reconciliation path. Partner write-ups of mid-market Xero stacks (especially outside pure services) often show hundreds to low thousands of dollars per month in combined app spend before anyone has bought ERP licenses. That is not an argument that every Xero customer should move; it is an argument to model stack cost, not just the Established plan fee.

Use concrete triggers, not vibes. Stay on Xero if you are single-entity, services-led or light inventory, and month-end still closes cleanly without hero spreadsheets. Plan a move when two or more of the following are true for more than a quarter.

Integration, Power Platform, and the stack

Xero integrates well within its lane — bank feeds, a mature app marketplace, and clean APIs — but it sits outside the Microsoft productivity and analytics stack. Business Central is a first-class Microsoft citizen: shared identity with Microsoft 365, surfaces in Teams and Outlook, and native connections to Power BI, Power Apps, and Power Automate. Copilot capabilities are embedded in Business Central for day-to-day assistance; some agent-style features are metered via Copilot Credits. For an organization already standardized on Microsoft, that depth is a real productivity advantage; for one that is not, it is a secondary factor.

Integration cuts both ways. If your team is well served by Xero’s ecosystem and has not hit operational ceilings, Microsoft stack gravity alone is not a reason to migrate. Treat ecosystem depth as a tiebreaker among businesses that already need inventory, multi-entity, or manufacturing — not as the primary trigger. The primary triggers remain operational: capabilities accounting software was never built to provide as a single system of record.

Choose Xero if… / Choose Business Central if…

Choose Xero if you are a small services firm, freelancer, nonprofit with simple books, or simple trader whose needs are genuinely accounting — invoicing, bank reconciliation, sales tax, basic expenses and projects — and you do not carry multi-location inventory, manufacture products, or run multiple entities. In that profile Xero is cheaper, faster to adopt, and the better tool; Business Central would buy modules you will not use and seats you will resent at $80–$110 each.

Choose Business Central if you have hit one or more graduate triggers: real inventory or warehouse complexity, manufacturing or assembly that belongs in the ledger, multiple legal entities with intercompany or consolidation needs, or operational reporting that accounting software plus spreadsheets cannot produce reliably. In those cases BC is not an “upgrade” to Xero — it is a different category that removes the integration tax of bolting operations onto a ledger. Also shortlist BC when Microsoft 365 is already the company standard and finance wants one identity plane with operations.

Alternatives exist (Odoo, NetSuite, industry ERPs). The fair comparison is always “Xero + stack” versus “ERP year-one licenses + implementation,” not $90 versus $80 on a pricing page alone.

Migrating from Xero to Business Central

Migration is usually phased rather than big-bang. The hard part is rarely the software install — it is data and process cleanup. A practical sequence: (1) clean and standardize the chart of accounts, customers, suppliers, and items in Xero; (2) decide opening balances and cutover date at a period boundary; (3) load masters and balances into Business Central; (4) stabilize finance postings; (5) enable inventory, warehouse, projects, or manufacturing only after the accounting core is trusted. Resist migrating years of transactional history by default — opening balances and clean masters usually matter more than full history, which is expensive and rarely used day to day.

Typical SMB timelines land around two to four months for a focused Xero-to-BC finance-plus-inventory cutover; multi-entity manufacturing programs run longer (often four to eight months in partner estimates for mid-complexity groups). The most common failure mode is migrating dirty data: duplicate customers, inconsistent item codes, and an untidy chart of accounts move with you. Clean in Xero first. A scoped implementation partner compresses risk; doing it alone without a cutover plan usually stretches the project and leaves the new system messier than the old one.

Frequently asked questions