A composite 0-100 index combining batch-error, integration-flow, AR-aging, and inventory-variance signals into one executive pulse on D365 finance and integration health.
At a glance
A single composite score from 0 to 100 that blends several underlying D365 health signals into one number an owner or finance lead can read at a glance. The component signals are batch-job error queue cleanliness, Power Automate / integration flow run health, AR aging staying low, and ERP-vs-ecom inventory variance staying low. A high score means the integration and finance plumbing is healthy; a falling score means something underneath has started to drift before it shows up in the headline financials.
| What it counts | A weighted composite of four health signals: (1) batch-job error queue clean over the last 24 hours, (2) integration flow runs succeeding, (3) AR aging not skewing past due, and (4) ERP-vs-ecom inventory variance staying within tolerance. Each signal is normalised to a 0-100 contribution and combined into the headline index. The exact weighting is tuned per environment during onboarding; the card surfaces the resulting score and the component breakdown, not raw arithmetic. |
| Currency | Not applicable. This is an index score, not a monetary figure. The underlying AR-aging signal is currency-aware, but the headline is a unitless 0-100 number. |
| Time window | RT/7D (real-time score with a 7-day trend line so you can see whether health is improving or degrading) |
| Alert trigger | score < 70. Below 70 means at least one component signal has degraded enough to warrant investigation. The card surfaces which component dragged the score down. |
| Roles | owner, finance, operations |
Calculation
Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A multi-entity Business Central tenant feeding a Shopify Plus storefront, with a Power Automate integration moving orders into BC sales orders and pulling inventory back out. The snapshot is taken at 08:30 on 18 May 26. The owner glances at the gauge before the weekly operations stand-up.| Component signal | Reading | Health contribution | State |
|---|---|---|---|
| Batch-job error queue (24h) | 11 errored jobs | Degraded | Amber |
| Integration flow runs | 2 failed flow runs | Degraded | Amber |
| AR aging low | 9% past 60 days | Healthy | Green |
| Inventory variance low | 1.4% ERP vs ecom | Healthy | Green |
| D365 Finance Health Score (this card) | 66 / 100 | Below 70, alerting |
- The headline is 66, below the 70 threshold, so the card is alerting. Two of four signals are healthy, but the two integration-side signals (batch errors and flow failures) have dragged the composite under the line. The owner does not need to read four cards to know something is wrong; the single gauge told them.
- The score points to the cause, it does not just flag a symptom. The component breakdown shows the batch-job and flow signals are the drag, so the next click is into Batch Job Error Queue (24h) and Power Automate Flow Failures, not into AR or inventory.
- Finance signals are still green. AR aging and inventory variance are within tolerance, so this is an integration-plumbing problem, not a money problem yet. Left unfixed, failed flows often become an AR or inventory problem within days, which is exactly why a leading composite is useful.
- The 7-day trend matters as much as the level. Yesterday the score was 81. A 15-point drop overnight is a sharper signal than the absolute value; it tells the team this is a fresh break, most likely tied to a deployment or a credential expiry, not a slow structural decline.
Sibling cards merchants should reference together
The health score is deliberately a roll-up. When it drops, these are the component cards that tell you why.| Card | Why pair it with D365 Finance Health Score |
|---|---|
| Batch Job Error Queue (24h) | The batch-error component. The first place to look when the integration-side signals drag the score down. |
| Power Automate Flow Failures | The integration-flow component. Failed flows are the most common cause of a sudden score drop. |
| A/R Aging 60+ Days | The AR-aging component. When this degrades, the score reflects a finance problem rather than a plumbing one. |
| ERP vs Ecom Inventory Variance | The inventory-variance component. Rising variance pulls the composite down and signals sync drift. |
| Top Findings Across Companies | The prioritised list of what to fix first across every legal entity, which the score summarises into one number. |
| Ledger Period Close Status | Close health context. A clean close alongside a low score isolates the problem to integration rather than accounting. |
Reconciling against Microsoft Dynamics 365
Where to look in Business Central / Finance & Operations:Business Central: Job Queue Entries (filter Status = Error, for the batch-error component) Power Platform admin centre: Flows > Run history (for the integration-flow component) Business Central: Reports > Finance > Aged Accounts Receivable (for the AR-aging component) Business Central / Finance & Operations: Item availability by location vs the commerce platform’s inventory (for the variance component) Finance & Operations: Batch jobs list page (System administration > Inquiries > Batch jobs, for the F&O batch-error component)There is no single native screen that shows this composite. D365 exposes each underlying signal on a different page, which is the whole reason the card exists. To sanity-check the score, open each of the four sources above and confirm the card’s component breakdown matches what you see. If the card says the batch component is amber, the Job Queue Entries page should show errored jobs; if it says AR is green, the aging report should show a healthy distribution. Why our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| No native equivalent exists | n/a | D365 has no built-in composite health score. The card is a Vortex IQ construct, so there is nothing to tie it to one to one. Reconcile each component separately instead. |
| Weighting is environment-specific | Either | The contribution weights are tuned per environment during onboarding. Two tenants with identical raw signals can show different scores if their weightings differ. |
| Snapshot timing | Either | The score is real time; the underlying D365 pages may have been refreshed at different moments, so a momentary mismatch on a single component is normal. |
| Component normalisation | Either | Each signal is normalised to a 0-100 contribution before blending. A raw count on a native page does not translate linearly into the score’s contribution. |