Business Central pricing tiers explained

Business Central's pricing looks deceptively simple — four named-user SKUs, one price each, all per user per month. The real cost lives in the choices around those SKUs.

Essentials

The default full-user licence. Covers financials, sales and purchasing, projects, inventory, warehouse, distribution, and basic supply chain. Most users in most companies are Essentials.

Premium

Essentials plus manufacturing and service management. There's one critical rule: in a single tenant, every full user must be on the same SKU — either all Essentials or all Premium. You cannot mix. So if your three-person service department needs Service Management, every other full user upgrades to Premium too. This is the single most surprising piece of BC pricing.

Before accepting the Premium jump, do the arithmetic properly. The uplift applies to the whole full-user population, so the real question is not "is Premium worth it for the service team?" but "is Premium worth the uplift times every full user?" For a fifty-user tenant with three service technicians, an AppSource service-management ISV running on Essentials frequently wins on cost alone — and several capable ones exist. The same logic applies in reverse: a genuine manufacturer with routings and capacity planning shouldn't try to fake it on Essentials with spreadsheets to save the uplift.

Team Members

A low-cost licence for users who only need read access plus a narrow set of write actions — time entry, expense entry, approving documents, updating their own data, and consuming reports. Not for posting transactions, processing orders, or maintaining items. Trying to use Team Members for general data entry is the most common compliance failure on BC audits.

External Accountant

A free licence for the customer's external accountant, with the rights of a full user, scoped to one company. Used heavily in markets where SMBs rely on external bookkeepers.

Device licences

Available for shared shop-floor terminals where multiple users log in across a shift on the same device. Priced per device rather than per user, which makes them the right answer for warehouse scanning stations and production terminals staffed across shifts — three shifts of two operators on one terminal is one device licence, not six Essentials.

Attach pricing in mixed tenants

If a user already holds a qualifying Dynamics 365 base licence — say Sales Enterprise — Business Central can be added as an attach licence at a substantial discount, and vice versa. The rule is that the most expensive app must be the base. In companies running CRM and BC side by side this is worth modelling per user before signing anything; the mechanics are covered in Dynamics 365 licensing explained.

How to size the user mix

The exercise that pays for itself: list every person who will touch the system and write down what they do, not which department they sit in. The classic mis-sizings, in order of frequency:

• Essentials for report readers. Managers who "need access to everything" usually consume reports. That's Team Member — or better, a Power BI report and no BC licence at all.
• Essentials for approvers. Someone whose only actions are approving purchase documents and expense reports fits Team Member exactly.
• Named users for shared stations. Warehouse and shop-floor terminals want Device licences.
• Stockpiling for seasonality. Named licences can be reassigned as staff change; handle seasonal peaks by reassignment, not by buying for the maximum headcount.

Companies routinely over-buy full users by 20–30% because the default answer to "what licence?" was Essentials for everyone. Revisit the split twice a year against actual usage — BC's admin views show last login and effective permissions, which is all the evidence a downgrade decision needs.

Hidden cost #1: storage

Database capacity beyond the included quota is billed in GB. A heavy transactional tenant with several years of history hits the threshold eventually — but moving documents (attachments) to SharePoint/OneDrive keeps the BC database lean.

Hidden cost #2: environments

Additional production environments are extra. Sandboxes are mostly free up to a limit.

Hidden cost #3: API calls

Each tenant has a generous but finite API call quota. Chatty Power Automate flows or integrations can exceed it and need optimisation or capacity add-ons.

Hidden cost #4: ISV add-ons

Country localizations, vertical apps, integrations — each priced per user per month and stack on top of the base. Individually small, collectively a real monthly line; a typical mid-market tenant carries three to six paid AppSource apps.

Where the actual numbers live

Deliberately absent from this article: exact prices. Microsoft adjusts BC list pricing roughly annually (most recently upward), and any number written here would mislead within a year. The authoritative sources are the published price list on Microsoft's site and the Business Central licensing guide PDF — check both at renewal, not just at purchase. As a rough 2026 orientation: full users sit in the tens of dollars per user per month, Team Members under ten, and Premium carries an uplift of roughly 40% over Essentials.

Budget the base licences, then double the total for year-one realism — implementation, ISVs, and integration work reliably match or exceed the licence line. The full licence-type detail (External Accountant scope, Team Member entitlements, compliance) is in Business Central licensing and pricing, and the whole-platform view in Dynamics 365 licensing explained.