Business Central: the Microsoft ERP for growing UK businesses

If you are comparing ERP systems for a growing business, Business Central is very likely on your shortlist. It is Microsoft’s ERP for small and mid-sized companies, sold under the full name Microsoft Dynamics 365 Business Central, and it sits between simple accounting packages and the large enterprise suites. This page explains what it is, who it suits, how licensing works, where it is strong, where it is limited and what a Microsoft partner actually does for you.

We are not affiliated with Microsoft or with any partner. ERP Integrator is a free service that connects you with an ERP integrator suited to your project. The page below is written to help you decide whether Business Central deserves a place in your selection, and to prepare the conversation with an integrator.

What is Business Central?

Business Central is an all-in-one business management system. It covers financial management, sales and purchasing, inventory and warehousing, project accounting, service management and, in the higher licence, light manufacturing. Instead of running accounting in one tool, stock in a spreadsheet and sales in a CRM, you work from a single database in which a sales order, a stock movement and a ledger entry are linked.

It is delivered primarily as a cloud service, which means Microsoft hosts the platform, applies updates and maintains the infrastructure. Your partner configures it for your company, and you pay a recurring licence per user. If you are weighing hosted against self-managed deployment in general, our guide to cloud versus on-premise ERP sets out the trade-offs, and your integrator will confirm which deployment options are available for your case.

The Navision heritage

Business Central is the modern form of a product line that many UK finance teams already know. It descends from Dynamics NAV, which itself came from Navision, a long-established ERP popular with mid-sized businesses across Europe. That history matters for two reasons.

First, the functional depth is real: the product has been refined over many years in finance, distribution and light production. Second, there is a large community of consultants, developers and add-on vendors who know the platform well. If you are a current NAV user, the product will feel familiar in its logic, even though the interface, the architecture and the way you extend it have changed considerably. A move from NAV is a genuine ERP migration project rather than a simple upgrade, and it deserves proper scoping.

Who is Business Central for?

Business Central suits companies that have outgrown entry-level accounting software but do not need, or cannot justify, a large enterprise ERP. Typical profiles include:

• Distributors and wholesalers that manage stock across locations, purchase orders and customer-specific pricing. See our page on ERP for wholesale and distribution.
• Light manufacturers that need bills of materials, production orders and basic capacity planning rather than complex scheduling. Our manufacturing ERP page covers what to look for.
• Professional services firms that bill by project, track time and expenses and want margin visibility per engagement. See ERP for professional services.
• Multi-entity groups that need consolidated reporting across several companies, sometimes in several currencies.
• Businesses already built around Microsoft tools, where Outlook, Excel, Teams and Power BI are part of daily work.

It is a weaker fit where your processes are highly specialised, for example complex process manufacturing or very large-scale warehouse automation. In those cases, you should test the standard product carefully against your real workflows before committing. If you are at an earlier stage and are not sure what class of system you need, start with our guide on ERP for small business.

Licences: Essentials, Premium and Team Members

Business Central is licensed per user and per month. Microsoft publishes three main licence types, and understanding them is the first step towards a realistic budget.

Two cautions apply to these figures. They come from Microsoft’s US page, and Microsoft itself states that displayed prices can differ from the real catalogue price depending on currency, country and regional variant, with the final price appearing at checkout. A UK quotation in pounds sterling will therefore not match the dollar figures exactly. Treat them as an order of magnitude and ask your partner for a written quotation in GBP, with VAT shown separately.

Second, the licence is only one line of the budget. Implementation, data migration, training, integrations, extensions and ongoing support are usually significant and depend on your scope. Our guide to ERP cost breaks down what makes up the total, and the business central prix question is best answered by a scoped quotation rather than a licence list.

Which licence do I need?

A few practical points help avoid over- or under-buying:

• Essentials versus Premium is mostly a question of manufacturing and service management. If you produce goods with production orders, or manage service contracts and repair orders, Premium is the relevant licence. If you buy and sell goods or services without production, Essentials is usually the starting point.
• Team Members is designed for people who do not work in the system all day: a manager who approves purchase orders, an employee who submits time or expenses, someone who checks a report. It is much cheaper per user, but its rights are limited, so your partner should map each role to a licence rather than assuming.
• Mixing licences is normal. A typical company has a handful of full users in finance and operations and a larger group of occasional users.

Ask your partner to produce a user-by-user licence map during scoping. It is one of the easiest ways to keep the recurring cost under control.

Integration with Microsoft 365

The strongest argument for Business Central, for many companies, is how naturally it sits inside the Microsoft environment. In day-to-day use that shows up in several ways:

• Excel: users can open lists and journals in Excel, edit them and publish the changes back, which suits finance teams who live in spreadsheets.
• Outlook: customer and vendor information can be consulted from the mailbox, and documents such as quotes and invoices can be sent directly.
• Teams: records can be shared in conversations, which shortens approval chains.
• Power BI: reporting can draw on Business Central data to build dashboards for management.
• Power Platform: Power Automate and Power Apps allow workflows and simple apps to be built around the ERP without heavy development.
• Single sign-on: users sign in with their existing Microsoft identity, which simplifies access management for your IT team.

This closeness reduces training time and resistance to change, because users stay in tools they already know. It also means that part of the value comes from how well your Microsoft 365 tenant is organised. A partner who understands both the ERP and your wider Microsoft setup will deliver a more coherent result than one who treats the ERP in isolation.

Extensions and AppSource

Business Central is designed to be extended rather than rewritten. Microsoft’s application marketplace, AppSource, lists apps built by independent software vendors, covering needs such as advanced warehouse management, payment processing, industry-specific modules, document capture, reporting tools and connectors to other systems.

The extension model has two practical consequences:

1. You can add a capability without modifying the core. Because extensions are separate from the standard application, Microsoft’s regular updates are designed to apply without breaking your customisations, provided the extensions are maintained.
2. Your partner may also develop bespoke extensions for requirements that no existing app covers. This is useful but should be kept proportionate: every custom feature has to be tested, maintained and sometimes reworked when the platform evolves.

A sound approach is to use the standard product first, then a maintained AppSource app where the gap is real, and custom development last. When you assess a partner, ask how they decide between the three, and who is responsible for upgrades of the apps you rely on.

Localisation and UK requirements

An ERP has to speak the language of local accounting and tax. Microsoft states that it provides the Business Central localisation directly in 21 countries, including Austria, Belgium, Germany, France, Italy, Mexico, the Netherlands, Spain, Switzerland and the United Kingdom. For other countries, localisation is available through apps developed by partners and found on the marketplace.

For a UK company, being in the group of directly supported countries is reassuring: the product is built with local chart-of-accounts conventions, VAT handling and statutory formats in mind. It does not remove the need for validation. You should ask your partner to demonstrate, with your own data or realistic test data, how the system handles:

• VAT returns and Making Tax Digital for VAT, including how submissions to HMRC are produced and by which route;
• Multi-currency transactions, including exchange rate updates and revaluation, which matter if you trade in euros or dollars after Brexit;
• Bank reconciliation and payment files for the banks you actually use;
• Construction or sector-specific schemes, if they apply to your activity;
• Electronic invoicing requirements and the ability to exchange structured invoices. Our guide to ERP and e-invoicing explains the principles.

If you operate in several countries, check each entity’s localisation separately, because the situation can differ from one country to the next.

Strengths and limits

No ERP is ideal for every company. A balanced view of Business Central looks like this.

Where it is strong

• Familiarity for users: the Microsoft look and feel, Excel and Outlook integration and a common sign-in make adoption easier.
• Breadth for a mid-market product: finance, supply chain, projects and light manufacturing are in one platform.
• A large partner ecosystem: many Microsoft partners work with it, which gives you choice and makes it easier to replace a provider if necessary.
• A mature extension marketplace: AppSource reduces the need for bespoke code.
• Regular cloud updates: the platform evolves without you managing upgrade projects in the traditional sense.
• Reporting and analytics: through Power BI and Excel, management reporting is accessible to non-specialists.

Where to be careful

• Licence costs add up when many users need full access. Careful role mapping is essential.
• Deep industry functions may require third-party apps or development, which adds cost and dependencies.
• Cloud updates are continuous, so your extensions and integrations must be tested and kept compatible.
• Implementation quality varies between partners. The product is capable, but the result depends heavily on the team that configures it.
• Heavily customised requirements can be easier to satisfy in a more open or more flexible platform. If flexibility and cost per user are central to your thinking, compare it with Odoo and read our comparison of Odoo vs Business Central.

How does it compare with other ERPs?

Business Central rarely stands alone in a selection. Companies commonly weigh it against:

• SAP Business One, another ERP aimed at small and mid-sized businesses. Our comparison of SAP Business One vs Business Central sets out the differences in approach and ecosystem.
• Oracle NetSuite, a cloud-native ERP often considered by faster-growing or multi-entity companies. See NetSuite vs Business Central.
• Sage, familiar to many UK finance teams, with a page on Sage for context.
• Odoo, a modular platform with an open-source community edition, covered on our Odoo page.

To see how these options relate to each other, our overview of ERP software is a good starting point, and the guide on how to choose an ERP gives a method that is independent of any one publisher.

The role of the Microsoft partner

Business Central is sold and delivered through a network of Microsoft partners, sometimes called Dynamics 365 partners or Business Central integrators. Their role is much larger than reselling licences. A competent partner will typically:

1. Clarify your requirements, turning business needs into a scope, a licence plan and a project plan. A written ERP requirements template helps this stage.
2. Configure the system: chart of accounts, dimensions, approval workflows, document layouts, user roles and security.
3. Migrate your data, deciding what to bring across, cleaning it and loading it with proper reconciliation.
4. Select and install extensions, and develop custom ones when justified.
5. Connect other systems, such as e-commerce platforms, banks, shipping providers or a CRM.
6. Train your users and support the go-live period.
7. Provide ongoing support and manage updates, so that new releases do not disrupt your operations.

Because the same product can deliver very different outcomes depending on the team, choosing the partner is as important as choosing the software. Our guide on choosing an ERP integrator lists the questions to ask: sector experience, references you can verify, how they handle change requests, who will actually work on your project and what happens after go-live.

What to ask a prospective partner

• Which of my processes will run on standard Business Central, and which need an extension?
• How will you map my users to licences, and what will the recurring cost look like in pounds?
• How do you handle VAT, Making Tax Digital and multi-currency in a UK setup?
• Who owns the maintenance of the apps and integrations after go-live?
• What does a typical project plan look like, and what are the dependencies on my team?

Avoid being drawn into a detailed technical conversation too early. A good partner begins with your business, not with the software.

Avoiding common project problems

Most ERP difficulties come from project management rather than from the software. The recurring causes are an unclear scope, too much customisation, weak data preparation, insufficient involvement from the business and underestimated training. Our article on ERP project mistakes describes them in detail, and the guide to ERP implementation walks through the phases of a typical project.

With Business Central, three habits make a particular difference:

• Start with the standard processes and challenge every request for custom behaviour.
• Appoint an internal project owner from finance or operations, not only from IT.
• Plan for the update cycle from day one, including who tests new releases and how integrations are monitored.

Next step: describe your project

If Business Central looks like a plausible fit, the most useful next step is to describe your company, your sector, your approximate number of users and your key requirements. We will connect you with an integrator suited to your project, at no cost to you. You can see exactly how the process works on our how it works page, and you can return to the home page at any time.

You are under no obligation to choose Business Central, or any particular publisher. The aim is to give you a qualified conversation with a professional who knows the product, so that you can compare approaches on solid ground and decide with confidence.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.