Native Microsoft fabric
Lives inside Microsoft 365 (Outlook, Teams, Excel, SharePoint), Power Platform, Power BI, and Azure. Operators stay in tools they already use. No third-party glue layer to maintain.
§ SOLUTION · MICROSOFT DYNAMICS 365 BUSINESS CENTRAL
Mid-market ERP that
Mid-market ERP that
grows with the firm,
not against it.
Business Central is Microsoft's cloud-native ERP for mid-market organizations that have outgrown QuickBooks or Sage but should not yet be paying for Dynamics 365 F&O or SAP S/4HANA. It lives inside the Microsoft fabric your team already uses, ships with Copilot built in, and implements in 12 to 20 weeks instead of years.
This page is the honest brief. Who it fits, who it doesn't, what it costs, what Platine brings to the table — and where we tell buyers to walk away.
Honest fit assessment.
BC is not "for everyone." Two columns below — the buyers it serves well, and the buyers it does not.
→ Right fit
When BC wins.
- 50 to 500-person organizations growing past QuickBooks, Xero, Sage 50, or Sage 100
- Multi-entity finance — companies, currencies, intercompany eliminations, consolidation
- Project-driven services firms (engineering, IT, consulting, agencies) that need PSA + accounting in one estate
- Light to mid-complexity manufacturing (BOM, MRP, light shop floor) — distribution, wholesale
- Quebec & Canadian operators that need bilingual UI, GST/QST/HST handling, and Loi 25 readiness
- Microsoft-aligned IT estates already running Microsoft 365, Azure, or Power Platform
→ Not the right fit
When we'll point you elsewhere.
- Very small businesses (under ~15 finance users) — QuickBooks Online or Xero usually wins on cost and speed
- Process manufacturing at scale (chemicals, pharma at industrial volume) — Dynamics 365 F&O or SAP S/4HANA fits better
- Public-sector budget accounting, fund accounting, or grant management — specialized vertical platforms outperform
- Organizations that have already built a deep, working ecosystem on NetSuite or Oracle Cloud ERP — migration cost rarely justifies the move
- Buyers who want infinite customization without governance — BC rewards extensions, punishes per-tenant code surgery
One integrated estate, not seven point solutions.
Business Central is Microsoft's cloud ERP for the mid-market, descended from the Navision (NAV) lineage that has been delivering for European mid-cap manufacturers since the 1980s. It covers financial management, sales and CRM, purchasing and supplier management, inventory and warehousing, project accounting, service management, and light manufacturing in a single Dataverse-backed tenant.
It is the Microsoft answer for the gap between small-business accounting (QuickBooks, Xero) and full enterprise ERP (Dynamics 365 Finance & Operations, SAP S/4HANA, Oracle Cloud ERP). Native to the Microsoft fabric — Outlook, Teams, Excel, Power BI, Power Platform — it removes most of the integration tax that historically defines mid-market ERP cost.
BC is licensed per user (Essentials or Premium tier), runs cloud-first (with on-prem available for compliance reasons), and ships monthly platform updates. The extensibility model is extensions, not customizations — code lives in tenant-isolated AL extensions that survive every platform release.
Five reasons that hold up under pressure.
Copilot built in
AI assist for journal-line creation, sales-quote drafting, item description generation, and inventory analysis — without bolt-on agents. The same Copilot foundation extends to your Power Platform automations.
Mid-market timeline
Cloud-first means typical implementation in 12–20 weeks for a single-entity mid-market deployment — versus 12–18 months for SAP S/4HANA or Oracle NetSuite at comparable scope.
AppSource ecosystem
Several thousand certified extensions for industry verticals — manufacturing add-ons, EDI, AvaTax, advanced WMS, project accounting. You buy capability instead of building it.
Predictable per-user pricing
Essentials and Premium tiers, transparent per-user monthly cost. No per-module gating shell games. CFO can model TCO at year-three on a napkin.
Methodology applied to this platform.
We are a methodology firm that works extensively with Microsoft Dynamics — not a Microsoft reseller. The four-phase loop documented in Approach is exactly what every BC engagement runs on:
Listen. We sit with finance, operations, and the people who'll live with BC daily. We map the chart of accounts you actually use, not the one you wish you used. We surface the workflows that pretend to be in your current system but live in spreadsheets.
Diagnose. Current state mapped. Data quality assessed. Customizations in the legacy system catalogued. Microsoft Solution Assessment run if useful. Output: a written recommendation that names the BC scope, the migration approach, and the cases where BC is not the right answer.
Design. Tenant configured for your operating model. Localization (Quebec, Canada, bilingual). Extensions selected from AppSource where they fit; thin custom AL where they don't. Data migration mapped from source. Change-management approach for the operators.
Deliver. Phased go-live, hypercare, knowledge transfer to your team. Monthly Microsoft platform updates absorbed without per-tenant breakage because we built on extensions, not customizations. The runbook is yours.
Honest scope. Honest cost.
What the data shows.
-
40,000+
Organizations running Dynamics 365 Business Central worldwide as of Microsoft's most recent reporting — one of the fastest-growing cloud ERPs in the mid-market.
— Microsoft Ignite & Dynamics customer-base disclosures -
12–20 wks
Typical implementation duration for single-entity mid-market BC deployments — meaningfully shorter than the 12–18 months common for SAP S/4HANA or Oracle Cloud ERP at equivalent scope.
— Industry implementation benchmarks (Forrester Wave / Gartner Cloud ERP) -
70%+
Of new Dynamics ERP licenses Microsoft sells annually go to the cloud, not on-prem — a structural shift away from legacy NAV / GP / SL.
— Microsoft FY disclosures, Dynamics 365 segment
What buyers actually ask.
01 We're still on Dynamics NAV (or GP, or SL). What's the migration path? +
NAV → BC is the well-trodden path: the data model is the closest match, and Microsoft offers tooling for upgrade. GP and SL → BC are re-implementations, not upgrades — the data goes through a transformation layer. We always start with a diagnostic that costs the upgrade vs. re-implementation honestly. Some organizations are better off staying on GP for one more year and migrating to BC at a planned milestone.
02 How does BC handle multi-entity, multi-currency, intercompany? +
Native, including consolidations and intercompany eliminations. Each legal entity is its own company in BC. Currency is handled at the journal level. For complex group structures (10+ entities, multi-jurisdiction), expect to layer in additional configuration discipline — but the foundation is in the box.
03 What does Copilot in BC actually do today? +
Item description generation, sales line summarization, journal-line completion, narrative analysis on dashboards, and a chat interface across BC data. It is meaningfully useful for daily operator tasks — not yet a replacement for analyst judgment. Capability is shipping monthly; a 12-month-old feature list is already stale.
04 Should we customize, or stick with extensions? +
Extensions, always. Per-tenant customization (the old NAV C/AL world) is incompatible with Microsoft's cloud upgrade cadence. AL extensions live in the AppSource ecosystem and survive every monthly platform update. Any BC partner who proposes per-tenant customization in 2026 is selling you future pain.
05 Is BC bilingual for Quebec operations? +
Yes — French (Canada) is a first-class locale, and the UI ships translated. GST / QST / HST are handled in the localization. Bilingual reporting and bilingual master data require some setup discipline; we treat it as a baseline, not an extra.
06 Total cost of ownership at year three — what does it look like? +
For a 60-user single-entity mid-market deployment: licenses ($35–$120/user/month depending on tier × 36 months), one-time implementation ($120K–$280K depending on complexity), plus 5–10% of original implementation cost annually for managed support. Per-tenant customization is excluded by design. Detail varies — we cost it explicitly in Phase 02.
07 Who owns the data, the configuration, the extensions? +
You. Always. Data is yours and exportable in standard formats. Configuration is yours. Extensions developed for you ship with source code in your repository. We are not a reseller — there are no licensing commissions back to Platine. The recommendation is the recommendation.
08 When is BC the wrong answer? +
Listed in the "Not the right fit" column above. Honest cases: very small shops, very heavy process manufacturing, deeply specialized verticals (public sector grant accounting, healthcare claims processing). We say so during diagnosis instead of forcing the engagement.
§ — INTERROGATIVE
Considering Business Central?