The go-live has already been postponed once
And the second postponement is visibly in the room.
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, UAT and cutover support, localisation, hypercare, project recovery and partner takeover. We deliberately do not currently offer full greenfield F&O implementations — there are firms whose core business is exactly that.
The starting point
“Almost every F&O problem that reaches us is described as a system problem. In the majority of cases it is a decision or process problem that becomes visible in the system.”
Microsoft Business Unit · Tech IQ 365 GmbH
Overview
Dynamics 365 F&O is powerful — and one of the least forgiving stacks to operate.
F&O carries enterprise complexity: multiple entities, multiple countries, deep supply chain, manufacturing, statutory variety. That power is precisely why wrong decisions in the design stay invisible for so long — and then become visible all at once: at the close, in reporting, after the next update.
We usually arrive when the system is already live. So our work does not start with a platform debate but with a sober question: what is actually causing it — configuration, process, data, an integration, a customisation, reporting, governance, the test and cutover approach, or simply missing capacity?
- 01
Finance & reporting
General ledger, financial dimensions, posting profiles, fixed assets, banking, tax, intercompany, consolidation and close.
- 02
Stabilisation
An unstable production system, breaking integrations, numbers nobody trusts, performance and error handling.
- 03
Optimisation
Closing process and system gaps without restarting the programme.
- 04
Rollout & localisation
Further entities and countries on a controlled template rather than as individual projects.
- 05
UAT, testing & cutover
Test coverage along the critical process chains, cutover planning, opening balances and hypercare.
- 06
Recovery & partner takeover
Programmes off track, partner exit, re-baseline and taking over architecture ownership.
Lead product
The Dynamics 365 F&O Health Check.
You do not have to commission a transformation programme to find out why one part of Dynamics 365 F&O is not working. The Health Check is a deliberately focused, senior-led diagnostic entry point: Start focused. Diagnose what matters. Then decide what to fix next.
Choose your business area. Choose your depth.
- 01
Choose the area
Eight business areas — from finance through order-to-cash, procure-to-pay, inventory and manufacturing to reporting, integration and rollout. You pick the area that is not delivering what it should. Multiple selection is possible where the symptoms visibly connect — and the Health Check will tell you when that turns into a programme rather than a diagnosis.
- 02
Choose the depth
System Only reviews the F&O environment and its technical and functional setup. System & Operations additionally reviews the end-to-end process and the operating model around it.
- 03
Qualify the environment
Entities, countries, version and environment structure, symptoms, urgency, programme phase and partner situation — proportionate, not sprawling.
- 04
Receive the evaluation
Per review dimension a status and a root-cause level, plus the sensible next steps. No overall score, but a statement you can work with.
Findings first, scope second
A Health Check starts in one business area and grows only where the findings justify it. A finance Health Check whose cause sits in an integration expands into Integration & Platform. A manufacturing Health Check that finds a costing problem expands into Inventory & Costing or Finance. An order-to-cash Health Check that runs into a collections process expands into the System & Operations depth. That is evidence-driven expansion — not forced scope.
Business areas
Eight business areas. You pick the one that hurts.
Each area has its own review catalogue in both depths. The list below shows the focus — the concrete scope is sharpened against your environment, not read off a standard form.
Business area 01
Finance
System Only. General ledger, financial dimensions, posting profiles, accounts payable, accounts receivable, fixed assets, banking, tax and statutory configuration, intercompany, financial reporting, period close and reconciliation setup.
System & Operations. Additionally: month-end close and close calendar, responsibilities, reconciliation and intercompany process, manual journals and workarounds, finance controls, reporting process, auditability, governance and key-person dependency.
Health Check for this area →
Business area 02
Order-to-Cash
System Only. Sales order, customer setup, pricing and discounts, credit management, picking and delivery, billing, accounts receivable, collections configuration, intercompany O2C, integrations and workflows.
System & Operations. Additionally: order ownership, pricing governance, credit decision process, fulfilment handoffs, billing ownership, dispute handling, collections process, exception management, KPIs and process governance.
Health Check for this area →
Business area 03
Procure-to-Pay
System Only. Vendor setup, procurement, purchase requisitions, purchase orders, goods receipt, invoice matching, accounts payable, payment preparation, workflows, posting logic and integrations.
System & Operations. Additionally: procurement governance, approval responsibilities, purchasing controls, receiving process, invoice exception handling, supplier communication, AP process ownership, payment readiness, segregation of duties and process KPIs.
Health Check for this area →
Business area 04
Inventory & costing
System Only. Inventory models, item model groups, inventory dimensions, posting, valuation, costing, inventory close, cost adjustments, variances, reconciliation and the warehouse-to-finance connection.
System & Operations. Additionally: inventory ownership, physical versus financial process, inventory accuracy, reconciliation process, costing governance, close responsibilities, exception and adjustment process, operational controls and KPI ownership.
Health Check for this area →
Business area 05
Manufacturing
System Only. Production control, bills of material, formulas, routes, resources and work centres, production orders, planning, WIP, costing, production posting, shop-floor related setup, quality-related setup and integrations.
System & Operations. Additionally: plan-to-produce process, production planning and release, material issue, shop-floor execution and feedback, WIP ownership, costing responsibility, variance review, production close, handoffs between operations and finance, and process controls.
Health Check for this area →
Business area 06
Reporting & controls
System Only. Financial reporting, financial dimensions, reporting architecture including Power BI, data sources, reconciliation logic, security, report distribution, management reporting setup and auditability.
System & Operations. Additionally: reporting ownership, management information requirements, reporting calendar, manual reporting routes, Excel dependencies, reconciliation ownership, KPI governance, management sign-off, control framework and decision process.
Health Check for this area →
Business area 07
Integration & platform
System Only. Interfaces, APIs, data management, batch jobs, extensions, custom code, ISV solutions, monitoring, performance, error handling, upgrade resilience, environment structure and deployment dependencies.
System & Operations. Additionally: integration ownership, support model, incident management, monitoring responsibilities, escalation routes, release governance, vendor dependencies, operational continuity, key-person risk and change management.
Health Check for this area →
Business area 08
Rollout & cutover
System Only. Localisation, configuration readiness, migration, master data, opening balances, interfaces, UAT, test coverage, cutover scripts, deployment and hypercare readiness.
System & Operations. Additionally: local business readiness, process ownership, training, decision governance, cutover ownership, business sign-off, support model, hypercare organisation, escalation routes, and the split between local and global responsibility.
Health Check for this area →
Review depth
The system — or the system and the organisation around it.
The second decision is the more important one. It settles whether we review the application or the complete business process in which the application is only one part.
System Only — is Dynamics 365 F&O configured and operating correctly?
The focus is the application and its technical and functional setup: configuration, parameters, posting setup, master data, financial dimensions, workflows, security and roles, extensions and customisations, integrations, batch jobs, data management, reporting setup, performance, error handling, upgrade resilience, system controls and the relevant statutory configuration. The faster, narrower depth — right for anyone who already suspects the origin sits in the F&O environment itself.
System & Operations — is the complete business process working?
Everything from System Only, plus the actual operating model: end-to-end process design, process ownership, roles and responsibilities, handovers, controls, approvals, reconciliations, manual workarounds and Excel shadow processes, exception handling, governance, how the system is actually used, process KPIs, management reporting, the close and operational calendar, process-system gaps, capacity constraints and organisational dependencies.
Why the second depth is the real difference
Many Dynamics specialists can review configuration. The difference comes where system, process, finance and operating model are assessed together — by people who can read all four. Every operational finding stays tied to the F&O-enabled business process it belongs to. This is explicitly not generic management consulting.
Deliverable
One standardised deliverable — whichever business area you choose.
Every Health Check variant produces the same deliverable structure. That makes findings comparable across areas and lets you attach a second area later without switching methodology.
- 01
Executive summary
- 02
Scope reviewed
- 03
Environment and process context
- 04
Assessment by dimension
- 05
Findings
- 06
Root causes
- 07
Quick wins
- 08
Structural issues
- 09
Risks
- 10
Dependencies
- 11
Prioritised remediation roadmap
- 12
Recommended next step
- 13
Process and operating model findings
- 14
Roles and responsibility findings
- 15
Manual workarounds and shadow processes
- 16
Governance and control findings
Additionally with System & Operations: Process and operating model findings, Roles and responsibility findings, Manual workarounds and shadow processes, Governance and control findings.
How we assess — and what we deliberately do not do
There is no overall 0–100 score. A single number covering an F&O environment is either trivial or misleading. Instead every review dimension gets a status and, where it helps, a root-cause level.
- 01
Healthy
Carries at the depth reviewed. No action needed.
- 02
Needs attention
Works, but with visible risk or friction.
- 03
Structural issue
A design or process problem that cannot be solved by adjustment.
- 04
Critical
Puts numbers, deadlines or operations at risk. Belongs at the front.
- 05
Not assessed
Outside the chosen depth or business area — deliberately declared rather than implied.
Root-cause levels: Configuration · Process · Data · Integration · Customisation · Reporting · Governance · Testing / cutover · Capacity.
On duration, fixed price, package combinations, additional business areas, workshops or crediting back against later remediation we deliberately state nothing here while they are not released. The product is built so they can be added without redesigning the page or the product.
Choose your business area. Choose your depth.
Start the F&O Health Check
Rollout & cutover
When the next entity, the next country or the go-live is coming up.
A substantial part of the F&O work is not diagnosis but delivery support inside a running programme: another country entity, a localisation, a UAT round that will not converge, a cutover weekend with too many open items.
- 01
Rollout on a template
Further entities and countries on a controlled template rather than as a project each.
- 02
Localisation
Statutory and tax requirements per country — and the question of what stays global and what belongs locally.
- 03
UAT & test management
Test coverage along the critical process chains rather than along the module list. Clear acceptance criteria.
- 04
Cutover
Cutover plan, opening balances, reconciliation against the legacy system, a fallback point and a defined abort point.
- 05
Hypercare
Support beyond the first close, with handover into an operating model that holds.
Recovery
When the programme has already gone off track.
Not every situation needs a diagnosis first. If the go-live has already been postponed, the budget is well beyond baseline, the partner is underperforming, or the steering committee has lost confidence in the delivery plan, this is no longer a Health Check case. Then we talk directly.
The budget is at a multiple of the baseline
With no credible end in sight.
The close takes longer after F&O than before
A classic sign of an architecture rather than a system problem.
Reporting and consolidation figures are not trusted
And are reconstructed alongside.
Integrations break after every update or ISV release
The extension landscape has grown without a rulebook.
The current partner rotates consultants or goes quiet
Subject-matter continuity is not a comfort but a precondition.
The steering committee no longer believes the plan
The most expensive state of all, because from here every decision gets deferred.
- 01
Senior only
The takeover is led by senior architects and finance leads — no junior staffing.
- 02
Architecture first
We repair the target model before touching the next configuration.
- 03
Governance-led
A clear re-baseline, a clear decision line, a clear stabilisation plan.
- 04
Handover-capable
We hand back a system you can steer — not a permanent dependency.
A recovery conversation is non-binding and usually takes half an hour: where things stand, the red flags, the realistic options. A clear second opinion from a senior partner — with no assessment in front of it.
Evidence
What is evidenced for this practice.
We show no F&O customer figures here, because we have no released, attributable F&O reference. Passing off results from mandates on other platforms as F&O evidence would be the easier route — and the wrong one.
Substance in the open
Our position on F&O financial reporting, financial dimensions and dual GAAP is published as an article anyone can read.
Five-level diagnostics
Operating model, finance architecture, master data, system landscape and governance — the method the Health Check grew out of.
Senior-led
Diagnosis and takeover are led by senior architecture and finance leads, not by a delivery queue.
German finance depth
HGB and IFRS in parallel, statutory requirements, VAT, group accounts and consolidation as a core competence.
Capacity from the group
Where a finding calls for capacity rather than configuration, BPO by JPS-iQ is a unit that explicitly supports Dynamics 365 F&O as a target system.
Platform-neutral
We have no interest in making an F&O problem bigger than it is — the group does not earn from your platform choice.
As soon as an F&O reference is released — client, starting position, outcome and timeframe, anonymised if necessary — it goes exactly here.
Good fit
Does this match your situation?
Good fit
- You run Dynamics 365 F&O in production and one business area is not delivering what it should.
- You want to know what is causing it before you commission a fix.
- You need support in a running rollout, in UAT or ahead of a cutover.
- Your programme is off track and you are looking for a senior second opinion or a partner change.
- You expect an assessment that also names what is healthy — not only what can be sold.
Weaker fit
- You want a full greenfield Dynamics 365 F&O implementation — we deliberately do not offer that at present.
- You are looking for pure development capacity for an implementation that is already decided.
- You expect an assessment without access to the environment, the process or the people involved.
- You are looking for a justification for a decision that has already been made.
- You are evaluating F&O for the first time — then the real question is whether Business Central or another group platform fits.
Common questions
What usually gets asked before a Health Check.
How long does a Health Check take?
That depends on the chosen business area, the review depth and the size of your environment. System Only in one area is considerably shorter than System & Operations across a multi-country rollout. We name duration and scope after qualification — not before, because any figure earlier would be a guess.
What does it cost?
On prices and package cuts we deliberately state nothing here while they are not released. The Health Check is structured so that duration, fixed scope and package combinations can be added once they are settled. Until then we agree it in conversation.
What is the difference between System Only and System & Operations?
System Only answers: is Dynamics 365 F&O configured and operating correctly? The focus is the application. System & Operations answers: is the complete business process working — in the system and in the organisation? It additionally reviews process design, responsibilities, handovers, controls, manual workarounds, governance and capacity.
Can we start with one area and expand later?
Yes, and that is the normal case. The Health Check is built exactly for that: start focused and expand only where the findings point to an adjacent area. A finance finding whose cause sits in an interface leads into Integration & Platform — not the other way round.
We have an acute problem. Do we still have to do the Health Check first?
No. If the go-live is wobbling, the close is due or a partner change is coming, talk to us directly. The Health Check is the structured entry point for anyone who has time for a clean diagnosis — not a mandatory station in front of an urgent conversation.
Do you also implement Dynamics 365 F&O from scratch?
Not at present. Our F&O motion is aimed at existing environments. If you are facing a first-time ERP decision, the more honest question is whether Business Central or another group platform fits your structure — the Business Central Fit Assessment exists for that, and OPCON provides a platform-neutral entry point.
Do you take on the remediation as well?
In the areas where we can evidence delivery: finance and reporting, stabilisation, optimisation, rollout and cutover support, recovery and partner takeover. Where a finding mainly calls for capacity, BPO by JPS-iQ is the better-suited unit — Dynamics 365 F&O is explicitly supported there as a target system. And where we are not the right people, we say so.
Contact · Dynamics 365 F&O
Have an area reviewed — or pull a programme back?
If you want to know what is causing it, start with the Health Check: choose the area, choose the depth, receive the evaluation. If your programme is already under deadline pressure, skip the Health Check and talk to us directly.