Business Central licence pricing: what it costs per user

Two numbers people confuse

"How much does Business Central cost" has two separate answers, and mixing them up is the most common budgeting mistake.

Licences are a predictable monthly subscription paid to Microsoft, priced per user. Implementation is a one-off project paid to a partner, priced by scope. The first is easy to calculate to the dollar. The second varies by a factor of five between two companies of the same size.

Licence prices per user

Microsoft list prices, effective 1 November 2025 and still current in August 2026. Prices are per user per month, billed annually.

Licence type	Price	Who it is for
Essentials	$80	Finance, sales, purchasing, inventory, projects, warehouse. The default choice for most companies
Premium	$110	Adds manufacturing and service management
Team Member	$8	Read data, approve documents, enter timesheets and expenses
Device	$45	A shared workstation used by several people in turn

Two constraints shape the arithmetic. Essentials and Premium full users cannot be mixed in the same environment — the choice applies company-wide. And Team Member is intentionally restricted: it cannot create sales or purchase orders, so it is not a cheaper substitute for an operational user.

Getting the user mix right

This is where most of the avoidable overspend happens. Companies count headcount and buy that many full licences.

In practice a workforce splits into three groups. People who work in the system daily — accountants, warehouse staff, sales — need full licences. People who only look at data and approve things — department heads, directors — need Team Member. And shared terminals, such as a goods-in station, are covered once by a Device licence rather than per person.

Worked example for a 25-person distributor:

Group	Licence	Count	Monthly
Finance, sales, purchasing	Essentials	12	$960
Managers and approvers	Team Member	10	$80
Warehouse terminals	Device	2	$90
Total			$1,130

The naive version — 25 Essentials licences — costs $2,000 a month. The difference over three years is close to $31,000, purely from classifying users correctly.

You can model your own mix in the cost calculator: five questions, no sign-up required.

What implementation costs depend on

Implementation is quoted per project, and the honest answer to "how much" is that it depends on five things.

• Number of areas. Finance only is a different project from finance plus warehouse plus manufacturing.
• Data migration. The volume and, more importantly, the tidiness of what you are bringing across. Duplicated customers and inconsistent item codes turn into billable hours.
• Customisation. Every deviation from standard behaviour is development, testing and long-term maintenance.
• Integrations. Bank, e-commerce, POS, EDI, courier services — each one is a separate piece of work.
• Training. Chronically underestimated, and the single largest determinant of whether people actually use the system.

The full breakdown with stage-by-stage figures is in the implementation cost article.

Costs that surface later

Three items regularly appear after the budget has been signed off.

Storage above the included allowance. Every tenant includes a base amount of database capacity plus an increment per full user. Heavy attachment use or many years of migrated history can exceed it, and additional capacity is billable.

Extensions from AppSource. Ready-made add-ons for EDI, advanced warehousing or reporting carry their own per-user subscriptions on top of the Microsoft licence.

Support after go-live. The first three months after launch generate the most questions. Whether that sits inside the project fee or is billed separately should be written into the contract, not assumed.

Thinking in three-year terms

Comparing an ERP purchase on the first invoice is misleading. The useful figure is total cost of ownership over three years: licences plus implementation plus support plus the extensions you will realistically add.

Against that horizon, a cheaper initial quote that relies on heavy customisation often ends up more expensive, because every update requires retesting the custom code. Staying close to standard functionality is usually the cheaper path, even when it means adjusting a process rather than the software.

Frequently asked questions