Microsoft Dynamics 365 Business Central
Connect finance and operations
without building unnecessary complexity.
DisconnectedConnected
Business Central brings financial control, purchasing, sales, inventory and day-to-day operations into one Microsoft platform, helping organisations replace disconnected systems, spreadsheets and manual work with a clearer operating core.
Choose the platform because it fits the operating model, not because of company size alone.
The short version
What Business Central is, and what it is for.
Everything below this point is detail. This is the part a leadership team needs before deciding whether the conversation is worth having.
What it is
A connected Microsoft finance and operational platform for organisations whose operating model can be supported responsibly without unnecessary enterprise complexity.
The problem it addresses
Finance, purchasing, sales, inventory and operations running apart, held together by spreadsheets, duplicate information, reconciliation and manual intervention.
The business outcome
A connected operating and financial core, where operational activity and its financial consequence can be understood together rather than reconstructed afterwards.
How the decision is made
Through a structured platform assessment against the future operating model, not against company size, turnover or headcount.
It tends to suit organisations where
- Standardisation is achievable and the business is willing to adopt standard process.
- Operational complexity is manageable rather than continually exceptional.
- Finance and operations genuinely need connecting, not just reporting on.
- Enterprise complexity does not justify a heavier platform.
- The future operating model can be understood, agreed and governed.
It may not be the responsible platform where complexity deepens around
- Multiple legal entities with materially different operating models, statutory requirements, controls or processes
- International operation with meaningful statutory localisation
- Routine, high-volume or complex intercompany activity
- Manufacturing models that need capability beyond the selected production model
- Automated or specialist warehouse execution
- Planning requirements beyond connected demand, stock and supply
- Formal enterprise controls and segregation of duties
- Integration landscapes with several business-critical dependencies
- A group or global template that must govern local variation
When the business outgrows the current system
The problem is rarely just the finance software.
Most organisations reach Business Central because the way work moves between departments has become harder to see, not because the ledger stopped working.
When several of these conditions appear together, it is worth assessing the wider operating model rather than assuming the accounting system is the only constraint.
Finance and operations are disconnected
Orders, purchasing, inventory and finance do not share a common process.
Spreadsheets run important work
Planning, reporting, reconciliation or operational decisions happen outside the core system.
Reporting takes too long
Management information needs manual preparation and reconciliation.
Inventory is hard to trust
Stock availability and movement are difficult to understand consistently.
Purchasing lacks visibility
Commitments and supplier activity are hard to see in context.
Growth adds administration
More revenue creates more manual work rather than more leverage.
Change is difficult
Small process improvements require disproportionate effort.
The current system no longer fits
The business has outgrown its accounting package, legacy ERP or disconnected application landscape.
ERP should make the business easier to run. Not simply give finance another system.
The value of Business Central comes from connecting the processes that create the financial result, not only recording that result afterwards.
One operational core
Connect the processes that create the financial result.
Three operating streams feed one financial and reporting core. When they share a common process, finance stops reconstructing the story after the event.
Sell
- Sell
- Fulfil
- Invoice
- Collect
Connect the order to stock, fulfilment and cash.
Buy
- Buy
- Receive
- Invoice
- Pay
See supplier commitment before it becomes an invoice.
Plan
- Plan
- Stock
- Move
- Replenish
Keep demand, availability and replenishment in one place.
FinanceInsight
Every stream lands in the same financial core, so reporting explains the business rather than reconstructing it.
Capability in business terms
What Business Central can connect, and why each part matters.
Open only what is relevant to your operation. Each area explains the business decision it supports rather than listing menu items.
- General ledger, payables, receivables and banking
- Cash management and cash flow
- Fixed assets, VAT and tax handling
- Dimensions, budgets and financial periods
- Approval controls and financial reporting
- Finance sees the impact of operational activity without rebuilding the story afterwards
Capability, licensing and scope are four different questions.
A capability existing in the Microsoft product does not mean it is included in your licences, in your edition, or in your project. We separate them deliberately, and we confirm licensing and edition entitlement against current Microsoft licensing at the point of qualification.
Platform capability
What Business Central can do as a Microsoft product.
Licensing and edition
What your licences and edition actually entitle you to use.
Implementation scope
What is agreed, configured, tested and adopted in your programme.
Extensions and ISVs
Capability supplied by a third party, with its own licensing and lifecycle.
Additional Microsoft services
Power Platform, Azure, Fabric and wider Dynamics 365 applications, licensed separately.
From transaction to insight
Reporting should explain the business, not reconstruct it.
Standard reporting, role centres, financial reports, Excel and Power BI each have a place, with data platform integration where the requirement genuinely needs it.
Start with the decisions leaders need to make. Rebuilding every legacy report is one of the most common ways an ERP programme absorbs effort without creating value.
Where a report exists only because the old system could not answer a question directly, the better outcome is usually a different question.
Data and AI
A connected ERP creates a stronger foundation for automation and intelligence.
Automation, reporting and intelligence become useful once process and data foundations are sound. AI is not the reason to buy Business Central, and predictive models are not native Business Central functionality.
Reliable transactions
The operating core records what actually happened.
Trusted data
Consistent, owned information that people are willing to use.
Automation
Remove manual steps with workflow and Power Automate where value is clear.
Insight
Use reporting and Power BI to explain performance.
Prediction
Apply data and AI capability where the foundations support it.
Action
Change the decision, not just the dashboard.
Power Automate, Power BI, Dataverse, Azure services and Microsoft Copilot capability are Microsoft capabilities, licensed and released by Microsoft. Assessing where they create value, designing them into the operating model and delivering them is InteliSense capability. We keep that distinction explicit.
Microsoft ecosystem
Business Central does not need to operate alone.
Connected capability is valuable where it removes real friction. Not every connection is native or included, and each carries its own licensing and design decisions.
- Microsoft 365
- Outlook
- Teams
- Power Platform
- Power Automate
- Power BI
- Dataverse
- Dynamics 365 Sales
- Dynamics 365 Customer Service
- Dynamics 365 Field Service
- Azure services
- Microsoft Fabric where relevant
Platform fit
The right ERP depends on the business you are becoming.
Platform choice should be made against the future operating model. Company size, turnover and headcount are the least useful inputs available.
Business Central may be a strong fit where
- The organisation wants an integrated finance and operational core.
- Process complexity is manageable and can be standardised where it should be.
- Finance, sales, purchasing, inventory and operations need to connect.
- Microsoft ecosystem alignment matters.
- The business needs more than an accounting package but does not need enterprise architecture it will not use.
- The operating model can be governed by a smaller number of accountable people.
Deeper qualification is needed where there is
- Multiple legal entities with materially different operating models, statutory requirements, controls or processes
- International operation with meaningful statutory localisation
- Routine, high-volume or complex intercompany activity
- Manufacturing models that need capability beyond the selected production model
- Automated or specialist warehouse execution
- Planning requirements beyond connected demand, stock and supply
- Formal enterprise controls and segregation of duties
- Integration landscapes with several business-critical dependencies
- A group or global template that must govern local variation
None of these makes Business Central wrong. Each one means the decision should be made deliberately rather than by default.
Platform decision
Business Central and Finance and Supply Chain Management are not simply small ERP and large ERP.
They are different operating propositions. The comparison should be run against observable characteristics of how the organisation works, not against its size.
Business Central
A highly capable connected operating core where process can remain relatively standard, entity complexity is manageable, and operational dependencies can be controlled without unnecessary enterprise architecture.
- Standardisation is realistic across the group
- Manufacturing and warehouse requirements fit the selected capability model
- Governance requirements are proportionate to the platform
- The business values a simpler Microsoft operating core
Finance and Supply Chain Management
Increasingly relevant as requirements deepen across entities, geography, supply chain execution, control and governance, where the cost of the heavier platform is justified by what the operating model genuinely requires.
- Multiple materially different legal entities, global or regional operating models
- Localisation, intercompany and statutory depth
- Advanced warehouse execution, complex manufacturing, deeper planning
- Enterprise security, advanced controls, complex integration and global templates
Decided against
- Financial complexity
- Legal entities
- Countries and localisation
- Intercompany
- Manufacturing model
- Warehouse model
- Planning requirements
- Security and segregation
- Integration landscape
- Group or global template
- Operational scale and dependency
- Governance
- Growth strategy
- Need for local variation
- Standardisation appetite
We do not reduce this to a score that claims to make the decision for you. The output is an indicative platform view with the reasoning visible, so the leadership team can challenge it.
Explore Finance and Supply Chain ManagementBusiness Central fit assessment
Five questions before the first conversation.
This is a structured pre-qualification, not an automated approval. It gives an honest directional signal, including where another platform or another route is the more responsible answer, and carries your answers through so nothing is retyped.
Indicative signal
Answer the questions and we will show an honest directional signal. This is not an automated platform decision: it makes the first conversation more useful.
Your answers are carried through, so you will not be asked to repeat them. Final qualification is always a conversation.
Delivery routes
The platform decision and the delivery decision are separate.
Once Business Central is the right platform, the next question is which route is responsible for your requirement and your readiness.
Where fit, readiness, standardisation and decision velocity are proven
RAPID 30
An accelerated, qualification-based Business Central route with a controlled first release and its own commercial model. RAPID 30 is a delivery route, not the definition of Business Central.
Explore RAPID 30Where the requirement is clear but does not qualify for acceleration
Conventional implementation
The same disciplines and the same governance, sequenced to the complexity of the operating model rather than to a fixed pace.
Talk to us about implementationWhere the future operating model is still unclear
Transform
Define how the business needs to operate before selecting or committing to a platform, so the ERP decision follows the operating model.
Explore TransformWhere a live system or in-flight programme is unstable
Recover
Establish what is actually true, restore control and then decide what the responsible next step is.
Explore RecoverWhere the platform is live but value has stalled
Optimise
Adoption, process, reporting, workflow and automation usually create more value than starting again.
Explore OptimiseWhere the operating model has outgrown Business Central
Finance and Supply Chain Management
Assess whether the enterprise platform is the more responsible choice before committing to an implementation.
Explore Finance and Supply Chain Management
Implementation
Start with how the business should operate.
The same disciplined route whether the programme is accelerated or conventional.
Understand
Business outcomes, process, complexity and platform fit.
Design
Future operating model, data, integration and controls.
Validate
Representative business processes with real users and realistic data.
Configure
Build the agreed Business Central solution.
Migrate
Prepare, load and reconcile qualified data.
Prove
Test end-to-end business processes and controls.
Cutover
Move the business into the new operating model.
Operate
Stabilise, adopt and improve.
Governance and readiness
Fast implementation still requires fast, accountable business decisions.
Business Central does not need enterprise bureaucracy. It does need named people who can decide, and a clear split of who owns what.
Customer
- Executive sponsor
- Process owners and the finance owner
- Operational subject-matter experts
- Data owners, cleansing and validation
- Key users and testing
- Decisions, cutover ownership and adoption
InteliSense
- Solution guidance and process challenge
- Configuration and technical delivery
- Migration structure and execution
- Integration design
- Testing support
- Cutover planning and implementation governance
Shared
- Design decisions
- Scope
- Risk
- Readiness
- Acceptance
- Go-live decisions
Commercial clarity
A price before qualification is a guess with an invoice attached.
We do not publish a Business Central price or a delivery commitment, because neither is meaningful until the platform and the scope are qualified. This is the sequence we work through.
- Platform fit
- Delivery route
- First-release outcome
- Process scope
- Companies and locations
- Data
- Integrations
- ISVs and extensions
- Customer responsibilities
- Assumptions
- Dependencies
- Agreed commercial commitment
RAPID 30 has its own commercial model where the requirement qualifies for it. Those terms do not transfer automatically to every Business Central implementation. New requirements that appear during delivery are governed and agreed rather than silently absorbed.
Deeper qualification
The detail that decides whether a Business Central programme lands cleanly.
Manufacturing, warehouse, entities, data, integrations, extensions, controls and cutover. Open what is relevant to you.
We can move data. Only the business can confirm whether it is right.
Already running Business Central or Dynamics NAV
You should not have to read an implementation story to find your route.
Most existing customers are in one of five situations. Each has a different responsible next step.
Live and healthy, but underused
Adoption, process, reporting and automation usually create more value than reimplementation.
Explore OptimiseLive but unstable or no longer trusted
Establish what is actually true before deciding whether to fix, re-scope or re-platform.
Explore RecoverImplementation underway but stalled
Recovery re-establishes control, and the delivery decision follows it.
Explore RecoverDynamics NAV or an older estate needing modernisation
Assess the operating model, customisations, integrations and history before choosing a route.
Explore TransformBusiness Central can no longer support the operating model responsibly
Run the platform comparison properly before committing to another implementation.
Explore Finance and Supply Chain Management
After go-live
Go-live establishes the platform. The lifecycle is what creates the return.
Post-go-live adoption, optimisation, automation and better insight can extend the value created by the original implementation.
Operate
Run the business on the new operating model with clear ownership.
Stabilise and support
Resolve what only live operation reveals, and establish dependable support.
Optimise
Adoption, process, workflow, automation and reporting that the first release could not address.
Expand
Additional companies, locations, capability or wider Microsoft applications, decided case by case.
Where organisations commonly go next
- Process optimisation and user adoption
- Workflow and Power Automate
- Reporting and Power BI
- Additional companies and locations
- Additional countries where appropriate
- Dynamics 365 Sales
- Dynamics 365 Customer Service
- Dynamics 365 Field Service
- Ecommerce and integrations
- Data and AI
- Predictive intelligence
- Acquisitions and group standardisation
Not every organisation needs every one of these. Each expansion should be justified on its own merits rather than assumed as the next purchase.
Explore OptimiseEvidence
Long-term Microsoft delivery, in our customers' words.
These are customers describing what it is like to work with InteliSense. They are not presented as Business Central implementation proof, and nothing in them should be read as an indication of Business Central scope, capability or delivery timescale.
Customer voice
What customers say about working with us.
Customer voices
InteliSense customers
Hear our customers talk about InteliSense
How we work
ERP works better when business decisions come before configuration.
Business before software
Understand the operating need first.
Platform fit
Choose Business Central because it fits, not because it is familiar.
Standardise where it makes sense
Avoid rebuilding legacy complexity into a new platform.
Validate early
Expose assumptions before they become expensive.
Data early
Make migration a programme discipline, not a final task.
Commercial discipline
Keep scope, decisions and ownership visible throughout.
Stay beyond go-live
Continue improving after implementation.
Common questions
Questions leaders ask about Business Central.
Is Business Central the right fit?
Start with the business you need to run.
If finance, purchasing, sales, inventory or operational processes are becoming harder to connect, we can help determine whether Business Central is the right platform, whether Finance and Supply Chain Management is more appropriate, and what the first sensible delivery route should be.
Already know the conditions support acceleration? Explore RAPID 30
