A composite 0-100 score combining several Fusion-integrity signals into one gauge. The single roll-up of whether your Oracle Fusion stack is healthy and your numbers are trustworthy.
At a glance
Oracle Fusion Health Score is a composite 0-100 gauge that blends several Fusion-integrity signals into one number: whether subledger-to-GL posting is running clean, whether intercompany is in balance, whether the integration flows that feed Fusion are healthy, and whether AR aging is under control. It is the single roll-up a finance leader can glance at to answer one question: can I trust the numbers coming out of my Oracle Fusion stack right now? A low score means one or more integrity signals are degraded, and the contributing cards tell you which. Sourced from a blend of Oracle ERP Cloud signals across all in-scope ledgers.
| What it counts | A composite 0-100 score blending several Fusion-integrity inputs, including subledger-to-GL posting cleanliness, intercompany balance, integration-flow health, and AR aging. The exact inputs are described generally; each contributing signal has its own dedicated card. A higher score means a healthier, more trustworthy Fusion stack. |
| Business Unit scope | Respects the dashboard’s selected Business Unit filter. By default rolls up every Business Unit and ledger the connected role can see, so the score reflects the whole in-scope estate. |
| Time window | RT/7D (a real-time score with a 7-day trend), so you see both the current state and whether health is improving or degrading over the week. |
| Alert trigger | Fires when the composite score falls below 70. |
| Roles | owner, finance, operations |
Calculation
Calculated automatically from your Oracle ERP Cloud 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 US Fortune 500 omnichannel speciality retailer running Oracle ERP Cloud across three Business Units under two primary ledgers. The reading is taken live on 22 Jun 26, with the 7-day trend running back to 15 Jun 26. The composite blends several integrity signals; the table below shows the contributing signals in plain terms, not exact weightings.| Contributing signal | State on 22 Jun 26 | Effect on score |
|---|---|---|
| Subledger-to-GL posting clean | 1 failed posting (Receivables) | Drag |
| Intercompany in balance | Balanced | Healthy |
| Integration (OIC) flows healthy | 1 flow failure in last 24h | Drag |
| AR aging under control | 60+ band at 18%, above its threshold | Drag |
| Oracle Fusion Health Score (this card) | 66 / 100 |
- 66 is below the alert threshold of 70, so the Nerve Centre fires. Three of the four signals are dragging at once, which is what pulls the composite under the line. A single weak signal would usually leave the score in the 70s.
- The composite is a roll-up, not the source of truth itself. The score tells you something is wrong; the contributing cards tell you what. Here the drags trace to Subledger to GL Posting: Failed (any source), OIC Integration Flow Failures (24h), and AR Aging 60+ Days.
- The inputs are described generally on purpose. The exact blend and weighting of signals is part of the scoring model and is not exposed as fixed numbers, because the right emphasis varies by estate. What matters operationally is the direction and which signals are dragging.
- The 7-day trend gives the score context. On 15 Jun 26 the score was 81. The slide to 66 over the week shows the degradation is recent and accelerating, not a long-standing baseline. That trend is why this card carries a
RT/7Dwindow rather than a pure snapshot. - Fixing one signal lifts the score. Clearing the failed Receivables posting and resolving the OIC flow failure would likely return the composite to the mid-70s even before the AR aging band recovers, because each resolved signal removes its drag.
Sibling cards merchants should reference together
Oracle Fusion Health Score is the roll-up. Pair it with the contributing cards to find which signal is dragging.| Card | Why pair it with Oracle Fusion Health Score |
|---|---|
| Subledger to GL Posting: Failed (any source) | A core integrity input. Failed postings mean the GL is not capturing all subledger activity, a direct hit to trustworthiness. |
| Intercompany Balance | An out-of-balance intercompany position is a classic integrity red flag the score reflects. |
| OIC Integration Flow Failures (24h) | Failing integration flows mean data may not be reaching Fusion, degrading the health signal. |
| AR Aging 60+ Days | Collections quality is part of the composite. A deteriorating aging band pulls the score down. |
| GL Period Close Status | A close running past deadline is a strong sign the books are not in a trustworthy state. |
| Oracle Fusion REST API Health | Interface errors between subledger and GL feed directly into the posting-cleanliness signal. |
| Top Findings Across Business Units | Surfaces which Business Unit is dragging the composite when the score drops. |
Reconciling against Oracle ERP Cloud
Where to look in Oracle ERP Cloud: There is no single native Oracle screen that produces a composite health score; the score is a Vortex IQ roll-up of signals that Oracle exposes individually. To reconcile it, inspect each contributing signal in its own Oracle home:Navigator → General Accounting → Journals → Manage Journals (unposted and in-error journals, subledger-to-GL posting state) Navigator → General Accounting → Intercompany → Manage Intercompany Transactions / Balances Navigator → General Accounting → Period Close → Close Monitor and Receivables → Reports → Aging (close and AR-aging signals)Each Oracle screen confirms one input. Add them up qualitatively and you can see why the composite sits where it does. For integration-flow health, the Oracle Integration Cloud (OIC) monitoring console shows recent flow runs and failures. Most Fortune 500 teams keep these screens open during close and use the Vortex IQ score as the single pane that tells them which one to look at first. Common mistakes when comparing against Oracle’s own reports:
- Looking for a matching score in Oracle. Oracle does not publish a single health score, so there is no native number to match. Reconcile signal by signal, not score to score.
- Assuming each signal is weighted equally. The composite emphasises signals differently. A clean intercompany position does not fully offset a stack of failed postings, so do not expect a simple average of the inputs.
- Comparing a real-time score against a period-end Oracle snapshot. The score is live with a 7-day trend; a frozen close report reflects a single past moment.
| Reason | Direction | Why |
|---|---|---|
| No native composite exists | n/a | Oracle exposes the inputs, not a single score. Reconcile each contributing signal in its own screen rather than expecting a matching number. |
| Weighting of inputs | Either | The composite emphasises signals by importance, so it is not a flat average. A back-of-envelope average of the inputs will differ from the score. |
| Real-time vs period snapshot | Either | The score is live with a 7-day trend. A period-end Oracle report reflects one frozen moment and can look healthier or worse than the live score. |
| Integration-flow signal source | Either | OIC flow health comes from the integration platform, not the ERP ledgers, so it has no equivalent in a GL or AR report. |
| Business Unit scope | Either | A single-Business-Unit Oracle view will not match a consolidated score that rolls up the whole in-scope estate. |