Choose, implement and operate the right Microsoft architecture.
JPS-iQ helps organisations choose, build and run the Microsoft business architecture that fits their structure. Dynamics 365 Business Central is our primary implementation practice — from selection through architecture, implementation and migration to optimisation and senior support. For existing Dynamics 365 F&O environments we deliver Health Check, stabilisation, rollout support and project recovery. And with JPS FinanceOS we bring our own, ERP-neutral Finance Operations Platform.
“The right Microsoft stack is not the biggest one. It is the ERP that matches the size of the business — and the finance architecture inside it that makes the first quarter-end unremarkable.“
Microsoft Business Unit · Tech IQ 365 GmbHTell us what is on the table — we will show you the path that fits it.
Seven situations we keep seeing in Microsoft programmes. Each one leads to a real next step, not to a general contact form.
We are evaluating a new ERP
Business Central is on the shortlist, but finance requirements are under-represented in the selection process. You want to know what your structure actually forces.
- Result immediately, no contact details
- Also says so when Business Central does not fit
We want to implement Business Central
The platform is decided, the route there is not: scope, finance foundation, migration, integrations, cutover — and who owns the architecture.
- Finance architecture before the first module
- One owner through to hypercare
We already run Business Central
The system runs, but reporting, extensions or support are not good enough. You are looking for a more senior partner, not another ticket queue.
- Optimisation instead of a restart
- Senior support & application management
We are planning NAV → Business Central
The end of NAV is in sight. The real question is not the tool but this: lift-and-shift or redesign — and what happens to the customisations that have grown over the years.
- The migration decision before the migration project
- Carry the legacy deliberately, or set it down
Our Dynamics 365 F&O is not delivering
One area is not working — finance, O2C, P2P, inventory, production, reporting, integration or a rollout. You want to know what is causing it before you commission anything.
- Choose the area and the depth
- The system — or the system and the process
Our F&O programme has gone off track
Go-live postponed, budget overrun, partner underperforming, steering committee losing confidence. That is no longer a diagnostic case, that is a conversation.
- Straight to the conversation, no assessment first
- Senior architecture and finance ownership
Our finance function runs on Excel, bank portals and email
The ERP is implemented and correctly configured. Controls, approvals, payments and exceptions still run beside it. That is not an ERP defect — a layer is missing.
- System of control above the ERP
- ERP-neutral, not a Business Central add-on
We need operational finance capacity
The system is fine — the hands are missing. Bookkeeping, reconciliations and the close need capacity, not another project.
- Executed inside your own system
- Dynamics 365 F&O is explicitly supported there
Business Central: our Microsoft ERP practice — from selection to running operations.
Business Central is the Microsoft ERP we actively sell, advise on, architect, implement and support long term. It is built for mid-market organisations that want a clean, scalable core — with finance discipline from day one rather than as rework in year two.
We cover the full lifecycle. As a Microsoft Cloud Solution Provider we can also handle licensing and subscription — as part of the lifecycle, not as the business model. The advisory work remains architecture, finance and delivery.
Where the natural limit sits — and what happens then
Business Central has a limit. It does not run along a revenue figure but along manufacturing depth, warehouse and planning complexity, statutory variety across many countries, and the question of how much extension a standard core can still carry. If your structure crosses that line we say so — and assess group-wide which architecture holds: NetSuite, SAP, another group platform, or Dynamics 365 F&O where it genuinely fits. That is structurally deliverable in this group because the alternatives exist as sister business units.
- 01
Evaluate
Does Business Central fit your legal, process and finance structure — and where does it get demanding? The output is a read, not a buying recommendation.
- 02
Architect
Chart of accounts, dimensions, multi-entity, intercompany, tax and the reporting model are designed before the first module is configured.
- 03
License & subscription
As a Microsoft Cloud Solution Provider we can take on licensing and subscription. You can also source them elsewhere — it changes nothing about the architecture work.
- 04
Implement
Process design, configuration, extensions through AL and vetted ISV apps, integrations, testing, cutover and hypercare under one line of responsibility.
- 05
Migrate
NAV or another mid-market ERP as the starting point: data decisions, grown customisations, opening balances, and the lift-and-shift versus redesign question.
- 06
Optimise
Existing Business Central environments: reporting, close, the extension landscape, permissions, process gaps and performance.
- 07
Senior support & application management
Ongoing operations with senior counterparts: incidents, releases, change and functional development. We deliberately do not build the practice as an implementation business that leaves after go-live.
Book an architecture call
Book an architecture callJPS FinanceOS: the layer that is missing once the ERP already runs correctly.
A common finding after a clean ERP implementation: the system posts correctly — and the finance organisation still runs on Excel, bank portals, email approvals, manual controls and separate reporting. That is not an ERP defect. A layer is missing.
FinanceOS is our own product and built ERP-neutral: one core with a canonical finance data model and provider adapters, not one product per ERP. Microsoft technology is an enabler here — Entra for identity and access, Azure as the operating layer. FinanceOS is explicitly not a Microsoft product, not a Business Central add-on and not a Power BI front end.
Maturity, stated plainly
FinanceOS is in Early Access — the first 100 finance organisations, onboarding through the end of 2026. NetSuite is today the first and deepest ERP path. Business Central is the next strategic path and is on the roadmap: not available, and we do not present it as a feature you can buy today.
- Business Central
System of record
posts the transaction
- JPS FinanceOS
System of control + system of action
runs the finance organisation
You already run Dynamics 365 F&O. We make sure it delivers.
For Finance & Operations our commercial focus is the existing environment: Health Check, finance and reporting, stabilisation, rollout and cutover support, localisation, hypercare, project recovery and partner takeover. We deliberately do not currently offer full greenfield F&O implementations.
The Dynamics 365 F&O Health Check
Choose the area that is not delivering what it should — several are possible where the symptoms connect. Then choose how deep we go: System Only reviews the F&O environment, its configuration and the technical and functional setup. System & Operations additionally reviews the end-to-end process and the operating model around it — responsibilities, handovers, controls, manual workarounds and governance.
So you do not have to commission a transformation programme to find out why one part of Dynamics 365 F&O is not working. Start focused, diagnose what matters, then decide what to fix next.
- 01
Finance
- 02
Order-to-Cash
- 03
Procure-to-Pay
- 04
Inventory & costing
- 05
Manufacturing
- 06
Reporting & controls
- 07
Integration & platform
- 08
Rollout & cutover
Four reasons Microsoft programmes run differently with us.
A clear commercial focus
Business Central is our primary practice for selection, implementation and operations. Finance & Operations is existing-environment work — Health Check, stabilisation, rollout support and recovery. No margin-driven platform push.
A finance-first foundation
Chart of accounts, multi-entity, intercompany, tax and reporting are defensible from day one rather than built afterwards. The first quarter-end stays unremarkable because the numbers logic already sits in the target model.
Architecture ownership
One business unit owns architecture, finance, design and delivery, led at senior level. No strategy-to-delivery gap: whoever owns the target model stays in the programme through hypercare.
An ERP-agnostic group
We are part of the JPS-iQ Solutions Group and say no to Microsoft when another system fits better. That is not a promise but daily practice — the neighbouring business units deliver exactly those alternatives.
A four-step method that survives the step from design to go-live.
Every Microsoft programme runs through the same method: architecture-led, finance-first, governance-aware — so that the target model from day one is also the target model the organisation ends up operating.
Finance & target architecture
Numbers logic, operating model, reporting structure and the platform decision are settled up front.
Process, data & integration model
End-to-end processes, data model, roles and the integration map — aligned to the finance foundation.
Build, test & controlled rollout
Configuration, extensions, integrations, data migration and rollout under governance and decision discipline.
Operations, evolution & ownership
Ownership transfer, controlled development, extension rules and a support model that carries beyond go-live.
What we can evidence — and what we deliberately do not claim.
We show no Microsoft customer figures here, because we have no released, attributable Business Central or F&O reference. Passing off results from mandates on other platforms as Microsoft evidence would be the easier route — and the wrong one. What stands here is evidenced:
As soon as a Microsoft reference is released — client, starting position, outcome and timeframe, anonymised if necessary — it goes exactly here. Until then it stays empty rather than filled.
The Microsoft platform underneath — as a foundation, not a product catalogue.
Azure, Entra, Microsoft 365, SharePoint, Teams, Power Platform and Power BI are enablers in our programmes: identity, operations, collaboration, automation and analysis around the ERP. We do not run them as standalone practices and we do not build product pillars out of them.
- 01
Azure
The operating and data platform beneath ERP and analytics.
- 02
Entra
One identity and permission layer instead of parallel rights silos.
- 03
Microsoft 365 · SharePoint · Teams
Documents, collaboration and process communication on the same identity as the ERP.
- 04
Power Platform
Automation and companion apps along the ERP processes — under controlled extension rules.
- 05
Power BI
Analysis on the ERP data model. Useful — but no substitute for a sound reporting foundation inside the ERP itself.
The substance, before you talk to us.
Business Central for growth companies: where the platform's strengths play out
Where Business Central structurally carries, where the natural limit sits — and when a remediation conversation starts instead.
Read the article →Dynamics 365 F&O financial reporting: what HGB and IFRS preparers need to know
Financial dimensions, legal entities, consolidation, and why dual GAAP has to be designed before go-live.
Read the article →ERP selection without vendor bias: how a platform-neutral evaluation actually works
The methodology behind our claim that we also say no to Microsoft.
Read the article →Recovering a stalled multi-entity finance close — without restarting the ERP
A group case: 14 entities, seven countries, close from 22 to 8 working days. Platform-anonymised — not Microsoft evidence, but our diagnostic method in full.
Read the article →What you want to know before the first call.
What exactly does Microsoft — JPS-iQ do?
We are the Dynamics 365 business unit of the JPS-iQ Solutions Group. Business Central is our primary practice: selection, architecture, implementation, migration, optimisation and senior support. For existing Dynamics 365 F&O environments we deliver the Health Check, stabilisation, rollout and cutover support, and project recovery. JPS FinanceOS is our own product: an ERP-neutral Finance Operations Platform above the ERP.
You are a Microsoft Cloud Solution Provider — does that make you a licence reseller?
No. CSP status means we can handle licensing and subscription within the customer lifecycle if you want us to. The business is architecture, finance and delivery. You can also source your licences elsewhere — it changes nothing about our work.
Do you also implement Dynamics 365 F&O from scratch?
Not at present. Our F&O motion is aimed at existing environments: Health Check, finance and reporting, stabilisation, rollout and cutover support, localisation, hypercare, recovery and partner takeover. If Business Central is too small for your structure we assess group-wide which architecture holds — and tell you honestly where we are not the right delivery partner ourselves.
When Business Central — and when not?
Business Central plays to its strengths in mid-market organisations that want a clean, scalable core with a sound finance basis — product and distribution businesses, services and project work, light manufacturing, multi-entity. The limit sits at deep manufacturing and planning complexity, very broad statutory variety, and an extension need that overstretches the standard core. The Business Central Fit Assessment tells you where your structure sits in that picture.
What does a Business Central project cost?
That depends on legal structure, process complexity, migration load and integration scope — and any figure before that is settled would be a guess. The usual entry point is the Fit & Architecture Assessment: it shows which architecture decisions your structure forces. After that a scope can be quantified that holds.
How does an engagement start?
For Business Central: the Fit & Architecture Assessment, then an architecture conversation about the target model and the rollout window. For an existing F&O environment: the Health Check with your chosen area and depth, then a conversation about findings and sequence. For a programme that is acutely off track: straight to the recovery conversation — no assessment in front of it.
Who is a weaker fit?
For a standard Business Central implementation in a single entity without finance depth there are cheaper partners, and we say so. And if you are looking for a pure licence source with no advisory content, we are the wrong firm.
Planning Business Central, reviewing an F&O area — or pulling a programme back?
Bring whatever is actually on the table: the ERP decision coming up, the area in F&O that is not delivering, or the milestone about to slip. We listen before we recommend.