What do Business Central licences cost per user?

Microsoft publishes list prices for Dynamics 365 Business Central per user and month: Essentials 69.30 euros, Premium 95.30 euros and Team Members 6.90 euros, each with annual billing and excluding VAT. The actual cost question, however, is not decided by the price but by the allocation: how many people genuinely need a full licence, and how many mainly work in read mode?

What arises alongside the licences: the four cost blocks of an implementation

What AI costs on top: What does Copilot cost in Business Central?

The list prices at a glance

Business Central is licensed per named user and month. There are two full licences and one low-cost additional role. Essentials covers finance, sales, purchasing, inventory and projects. Premium additionally contains manufacturing and service order management. Team Members is intended for staff who mainly read, record time or maintain simple data.

As at 21 September 2026 Microsoft lists the following prices for Germany per user and month with annual billing, excluding VAT: Essentials 69.30 euros, Premium 95.30 euros, Team Members 6.90 euros. Microsoft expressly notes that these figures serve information purposes and may differ from the actual list price.

Source: Microsoft: Dynamics 365 Business Central pricing, retrieved 21 September 2026

The rule behind it matters: within one environment you cannot mix Essentials and Premium. If some of your users need manufacturing or service handling, Premium applies to all full licences. That rule shifts the calculation more than any discount.

How many full licences do you really need?

In almost every project the first estimate of full licences is too high. It comes about by taking the headcount and reducing it roughly. The sound figure arises differently: you walk through the processes and ask per role whether documents are recorded there or only information is read.

Typical candidates for Team Members are managers who look at reports, staff in production who report back times and quantities, and colleagues in service who look up master data. The difference between 69.30 euros and 6.90 euros per person and month adds up considerably across the workforce and across the years.

Conversely: a licensing plan that is too tight produces workarounds. If a role may formally only read but practically has to post, shared accounts appear under which several people work. That saves licence cost and costs traceability, and at the latest during the first audit it becomes uncomfortable.

What is often forgotten in the licence calculation

Three items rarely appear in licence comparisons and still arise. The first are apps from the marketplace. Many useful extensions, for example for document management, payments or industry-specific functions, are also billed per user or per environment. An add-on at ten euros per user and month can raise licence costs by a seventh.

The second item are additional environments. Production, test and development are included to a certain extent, beyond that further sandboxes cost money. For projects with parallel development that is a real, plannable item.

The third item is AI. Copilot functions are partly included, compute-intensive agents are billed through a consumption model. That is no reason to go without, but it belongs in the calculation because it grows with usage rather than with the number of users.

Why the licence is the smallest lever

Calculated over five years, licences typically make up the smaller part of total cost in mid-sized projects. The larger part sits in consulting, data migration, interfaces and in the time of your own team. Anyone who negotiates ten percent off the licences and saves on project preparation has lost on balance.

That is not an argument against careful licence planning. Allocating the roles is worthwhile, and it stays worthwhile, because licence costs recur every month. It is an argument against the order in which many projects are calculated.

The sensible order is: first clarify processes and roles, derive the licence structure from that, and in parallel calculate the blocks that genuinely decide the budget. Then the licence count is a result and not an assumption.