> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Sage Health Score, Sage > Sage Health Score. A single 0-100 composite of ledger health, blending VAT-code completeness, smart-coding queue, bank-recon freshness and AR aging. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > A single 0-100 composite of ledger health: VAT-code completeness times smart-coding-queue cleanliness times bank-recon freshness times AR-aging. One executive number that says whether the books are in good shape. ## At a glance > One number, 0 to 100, that answers the question a finance director asks first: are the books healthy right now? It is a composite of the factors that most reliably indicate whether a Sage Intacct ledger is clean and current: VAT-code completeness (are revenue lines compliant), smart-coding queue cleanliness (is the coding backlog under control), bank-reconciliation freshness (when was the last reconciliation), and AR aging (is the receivables book current or drifting overdue). No single sub-card tells the whole story; this card multiplies them into one read that drops fast when any factor degrades. It is the card you put on the executive overview so a problem in any corner of the ledger surfaces as a falling score before it becomes a board conversation. | | | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | A weighted composite scored 0-100 from four factor groups: VAT-code completeness, smart-coding queue depth, bank-reconciliation recency, and AR-aging health. Each factor is normalised to a 0-100 sub-score and combined; the headline is the blended result. | | **VAT-coded-complete factor** | Driven by the count of revenue lines missing a VAT code in the current MTD period. The more uncoded lines, the lower this factor. Pulls from the same data as [Revenue Lines Missing VAT Code (MTD)](/nerve-centre/kpi-cards/sage/revenue-lines-missing-vat-code-mtd). | | **Smart-coding-queue-clean factor** | Driven by the smart-coding queue depth over the last 24 hours. A deep, aging queue means transactions are not being coded promptly, which lowers this factor. Pulls from [Smart Coding Queue Depth (24h)](/nerve-centre/kpi-cards/sage/smart-coding-queue-depth-24h). | | **Bank-recon-fresh factor** | Driven by days since the last bank reconciliation. The longer since the last rec, the lower this factor, because an unreconciled ledger is an untrusted ledger. Pulls from [Days Since Last Bank Reconciliation](/nerve-centre/kpi-cards/sage/days-since-last-bank-reconciliation). | | **AR-aging-low factor** | Driven by the proportion of AR sitting in overdue buckets. A receivables book skewing to 60+ days lowers this factor. Pulls from the AR-aging family. | | **Why multiply, not average** | A weak factor should drag the whole score, not be hidden by strong ones. A ledger that is VAT-clean and well-coded but has not been bank-reconciled in 90 days is not healthy, and a multiplicative blend reflects that more honestly than a simple average. | | **Currency** | The score is unitless (0-100). The underlying factors that carry currency (AR aging) are computed per entity in base currency and rolled up. | | **Entity scope** | Card respects the dashboard entity filter; a per-entity score is the most actionable read in a multi-entity group. | | **Time window** | `RT/7D` | | **Alert trigger** | `<70`. A score below 70 means at least one factor has degraded enough to warrant attention. Configurable per workspace. | | **Roles** | owner, finance, operations | ## Calculation Calculated automatically from your Sage 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 UK mid-market business on Sage Intacct, VAT registered, selling DTC through Shopify Plus and B2B through BigCommerce B2B, with AR running on Net-30 wholesale terms. Snapshot 23 Jun 26. Reporting currency GBP. Alert at 70. The four factors and their contribution: | Factor | Sub-score (0-100) | What is driving it | Pulling the headline | | ------------------------ | ----------------- | ---------------------------------------- | ----------------------- | | VAT-code completeness | 88 | 12 revenue lines uncoded this MTD period | Slight drag | | Smart-coding queue clean | 95 | Queue shallow, cleared within the day | Healthy | | Bank-recon freshness | 55 | Last reconciliation 38 days ago | Major drag | | AR-aging health | 72 | 18 percent of AR in 60+ buckets | Moderate drag | | **Sage Health Score** | **68** | | **Below 70, alert lit** | Five things to notice: 1. **The headline is 68 and the single reason is bank-recon freshness at 55, which is exactly what a composite score is for.** Three of the four factors are healthy or close to it, but a 38-day-old bank reconciliation drags the blended score below the 70 alert line. A simple average might have let the three strong factors paper over the weak one; the multiplicative blend does not, because an unreconciled ledger genuinely undermines confidence in every other number. The card's value is that it told the finance director "something is wrong" with one glance, and the factor breakdown told them exactly what, without a single report being run. 2. **Read the factor breakdown, not just the headline, because the breakdown is the to-do list.** The score going to 68 is the alarm; the breakdown saying "bank recon: 55, last rec 38 days ago" is the instruction. The fix is concrete and owned: run the bank reconciliation, and watch the bank-recon factor jump from 55 toward 95, which alone would lift the headline back above 70. The card is designed so that the number tells you to look and the components tell you where. Pair with [Days Since Last Bank Reconciliation](/nerve-centre/kpi-cards/sage/days-since-last-bank-reconciliation) to action the specific blocker. 3. **The AR-aging factor at 72 is the slow-burn one to watch even though it is not the alarm today.** Eighteen percent of receivables in the 60+ bucket is a moderate drag, not a crisis, but it is the kind of factor that erodes quietly over a quarter as collection discipline slips. If next month the bank rec is fixed (lifting the headline) but AR aging deteriorates to 30 percent overdue, the headline could stay flat while the underlying health shifts from a recon problem to a collections problem. Reading the factor trend over the 7-day window, not just the daily snapshot, is how you catch that rotation. Pair with [AR Aging 60+ Days](/nerve-centre/kpi-cards/sage/ar-aging-60-days) and [Days Sales Outstanding](/nerve-centre/kpi-cards/sage/days-sales-outstanding). 4. **The twelve uncoded VAT lines barely move the score today but are a compliance time bomb the score will amplify near the deadline.** At 88, VAT-code completeness is only a slight drag mid-period, which is correct: twelve uncoded lines with two weeks of runway is manageable. But the same twelve lines unfixed on the eve of the MTD deadline are a different risk entirely, and a well-tuned health score weights VAT completeness more heavily as the filing deadline approaches, so the factor that is a gentle drag today becomes a sharp one if it is still there in two weeks. This is the score reflecting that the cost of a problem depends on timing, not just size. Pair with [Current VAT Return Status (MTD)](/nerve-centre/kpi-cards/sage/current-vat-return-status-mtd). 5. **This is the executive overview card, and its job is to compress four diagnostic cards into one glance for someone who will not open four cards.** A finance director or owner does not want to scan VAT, coding, recon, and AR every morning; they want one number that turns red when any of those needs attention, with a breakdown one click away when it does. That is the entire design intent: a single trustworthy proxy for "are the books in good shape" that fails loudly and points at the cause. When the score is green, the detailed cards can stay closed; when it is below 70, the breakdown tells you which detailed card to open. Pair with [Sage Health Score](/nerve-centre/kpi-cards/sage/sage-health-score) component siblings listed below for the deep dives. ## Sibling cards merchants should reference together | Card | Why pair it with Sage Health Score | | ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | [Revenue Lines Missing VAT Code (MTD)](/nerve-centre/kpi-cards/sage/revenue-lines-missing-vat-code-mtd) | The VAT-completeness factor. Drill here when that component drags the score. | | [Smart Coding Queue Depth (24h)](/nerve-centre/kpi-cards/sage/smart-coding-queue-depth-24h) | The smart-coding factor. A deep queue pulls the score down. | | [Days Since Last Bank Reconciliation](/nerve-centre/kpi-cards/sage/days-since-last-bank-reconciliation) | The bank-recon factor. A stale rec is the single most common drag. | | [AR Aging 60+ Days](/nerve-centre/kpi-cards/sage/ar-aging-60-days) | The AR-aging factor. A receivables book skewing overdue lowers the score. | | [Current VAT Return Status (MTD)](/nerve-centre/kpi-cards/sage/current-vat-return-status-mtd) | VAT status sharpens the VAT factor's weight near the deadline. | | [Open (Pending) Transactions](/nerve-centre/kpi-cards/sage/open-pending-transactions) | A pending backlog signals coding and approval problems the score reflects. | | [Transaction Imbalances](/nerve-centre/kpi-cards/sage/transaction-imbalances) | Unbalanced journals undermine ledger trust the score is meant to capture. | | [Period Close On-Time Rate (12 months)](/nerve-centre/kpi-cards/sage/period-close-on-time-rate-12mo) | The structural-discipline trend that correlates with a healthy score. | ## Reconciling against Sage **Where to look in Sage Intacct:** The Sage Health Score has no single native equivalent, because Sage Intacct does not ship a composite ledger-health number. Instead, reconcile each factor against its native source: > **Applications → Tax → VAT Detail Report** for the VAT-code completeness factor (uncoded revenue lines). > **Platform Services → Smart Coding queue / review** for the smart-coding-queue factor (queue depth and age). > **Applications → Cash Management → Bank Reconciliation** for the bank-recon-freshness factor (date of last completed reconciliation). > **Reports → Accounts Receivable → AR Aging** for the AR-aging factor (overdue bucket proportions). > **Interactive Custom Reports (ICRs)** on each underlying data source to reproduce the inputs the score blends. For Multi-Entity Console accounts, compute each factor per entity, because a single bad subsidiary should be visible as a low per-entity score rather than diluted in a group average. Common reconciliation pitfalls: * **There is no native score to match.** Do not expect Sage to show 68; Sage shows the four underlying datasets. Reconcile the inputs, not the headline. If the inputs match and the blend formula is understood, the score is correct by construction. * **Weighting and normalisation are Vortex IQ choices.** How each factor maps to a 0-100 sub-score, and how the four combine, is the card's model. Two reasonable people could weight bank-recon vs AR-aging differently; the card exposes the weights so you can align them to your priorities. * **Factor freshness differs.** VAT completeness is current-period; bank-recon freshness is days-since; smart-coding is a 24-hour window; AR-aging is a point-in-time snapshot. The blended score is only as fresh as its slowest input, so a recon completed an hour ago may not lift the score until the next refresh. **Why our number may legitimately differ from what you would compute by hand:** | Reason | Direction | Why | | ----------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | **No native baseline** | n/a | Sage has no composite to compare against; the score is a Vortex IQ model over Sage inputs. | | **Weighting** | Either | Reweighting the four factors changes the headline without any input changing. Weights are configurable. | | **Normalisation curve** | Either | How a raw input (for example 38 days since recon) maps to a sub-score is a curve choice; a linear vs stepped curve gives different sub-scores. | | **Multiplicative vs average** | Either | The blend multiplies so a weak factor drags hard; a hand-computed average would read higher. | | **Factor scope** | Either | Which AR buckets count as overdue, or how the smart-coding window is defined, shifts a factor and therefore the headline. | | **Entity rollup** | Either | A per-entity score versus a group blend can differ when one subsidiary is much weaker than the others. | **Cross-connector reconciliation:** | Card | Expected relationship | What the comparison reveals | | ------------------------------------------------------------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------- | | [Revenue Lines Missing VAT Code (MTD)](/nerve-centre/kpi-cards/sage/revenue-lines-missing-vat-code-mtd) | Direct input | When the score's VAT factor drops, this is the card that explains why. | | [Days Since Last Bank Reconciliation](/nerve-centre/kpi-cards/sage/days-since-last-bank-reconciliation) | Direct input | The single most common reason the score dips below 70. | | [Smart Coding Queue Depth (24h)](/nerve-centre/kpi-cards/sage/smart-coding-queue-depth-24h) | Direct input | A coding backlog is both a score drag and a leading indicator of downstream errors. | | [AR Aging 60+ Days](/nerve-centre/kpi-cards/sage/ar-aging-60-days) | Direct input | A slow-burn factor that erodes the score over a quarter as collections slip. | | [Revenue Gap vs Commerce](/nerve-centre/kpi-cards/sage/revenue-gap-vs-commerce) | Correlated | A widening commerce-to-GL gap usually shows up first as coding and validation drags the score reflects. | The cross-connector point is that ledger health is multi-dimensional and no single number from any one system captures it, which is exactly why this card multiplies four independent signals into one. A commerce platform can tell you sales are strong while the ledger behind them is unreconciled, uncoded, and aging; a healthy revenue chart says nothing about whether the books supporting it can be trusted or filed. Sage Intacct holds all four health dimensions in one place, so it is the only place this composite can be built honestly. The card is the executive proxy that turns four diagnostic feeds into one watched number, and the factor breakdown is the thread back to the specific card that needs action. It is the first card to glance at and the last one you want to see red. ## Known limitations / merchant FAQs **What are the four factors and why these four?** VAT-code completeness, smart-coding queue cleanliness, bank-reconciliation freshness, and AR-aging health. They were chosen because they are the factors that most reliably indicate whether a Sage Intacct ledger is clean, current, and trustworthy: compliance (VAT), coding hygiene (smart coding), reconciliation (bank recon), and collections (AR aging). Together they span the main ways a ledger goes wrong, and each has a clear owner and a clear fix. **Why multiply the factors instead of averaging them?** Because a weak factor should drag the whole score rather than be hidden by strong ones. A ledger that is VAT-clean and well-coded but has not been bank-reconciled in three months is not healthy, and an average would let the strong factors mask that. Multiplication (or a similarly penalising blend) ensures any one degraded factor pulls the headline down, which is the honest read for an executive proxy. **What does a score of 70 actually mean?** Seventy is the alert line, the point below which at least one factor has degraded enough to warrant attention. It is not a pass/fail boundary in any accounting sense; it is a tuned threshold where the composite suggests something needs looking at. Above 70, the ledger is broadly healthy; below 70, open the factor breakdown and action the weakest one. The threshold is configurable per workspace. **Can I change the weights?** Yes. The weighting of the four factors is configurable, because different businesses prioritise differently: a B2B distributor with large receivables may weight AR-aging more heavily, while a UK retailer near a VAT deadline may weight VAT completeness more. The card exposes the weights so you can align the score to what "healthy" means for your operation. Changing weights changes the headline without any underlying data changing, which is expected. **Why did my score drop when no individual card looks alarming?** Because the composite catches degradation across multiple factors before any single one crosses its own alarm. Each factor can be in mildly-amber territory, none individually alarming, yet the blend drops below 70 because the combined picture is weaker. This is a feature: the score is meant to be more sensitive than any single sub-card, surfacing a broad softening before it becomes a specific crisis. Read the breakdown to see the contributing factors. **Does VAT completeness weigh more near the filing deadline?** In a well-tuned configuration, yes. The cost of uncoded VAT lines depends heavily on timing: twelve uncoded lines mid-period is manageable, the same twelve on the eve of the MTD deadline is a real compliance risk. A health score that weights VAT completeness more heavily as the deadline approaches reflects that the same data carries more risk closer to the line. Whether this dynamic weighting is on is configurable. **How fresh is the score?** It is only as fresh as its slowest input. VAT completeness and smart-coding are near real-time; bank-recon freshness updates when a reconciliation completes; AR-aging is a point-in-time snapshot on the standard refresh. So a bank reconciliation you finished an hour ago may not lift the score until the next refresh cycle picks it up. The 7-day window also lets you read the factor trend rather than just today's snapshot, which is the better way to spot a slow-burn factor like AR aging. **Should I put this on the executive dashboard?** Yes, that is its design intent. The Sage Health Score exists so a finance director or owner can glance at one number each morning instead of scanning four diagnostic cards. When it is green, the detailed cards can stay closed; when it drops below 70, the factor breakdown tells you exactly which card to open. It is the compression layer that makes the detailed cards optional reading on a good day. **How does it behave in a Multi-Entity Console group?** The most actionable read is per entity, because a single weak subsidiary should show as a low per-entity score rather than being diluted in a group average where three healthy entities mask one unhealthy one. The card respects the dashboard entity filter, so you can view the group blend or drill to a specific entity. For multi-entity operations, watching the per-entity scores catches the quiet subsidiary that a group number would hide. **What is the fastest way to lift a low score?** Open the factor breakdown and action the lowest sub-score first, because the multiplicative blend means the weakest factor is dragging hardest. In practice the fastest single win is usually running an overdue bank reconciliation, since bank-recon freshness is both the most common drag and the most binary to fix. After that, clearing uncoded VAT lines and the smart-coding queue tends to give the next quickest lifts. AR aging is the slowest to move because it depends on collections. **Is the score a substitute for actually reviewing the books?** No. It is a proxy and an early-warning system, not an audit. A green score means the four tracked factors are healthy, which is a strong signal but not a guarantee that every number is correct; problems outside the four factors will not show up here. Use it to know where and when to look, then use the detailed cards and your normal review process to confirm. The score's value is direction and timing, not certification. *** ### Tracked live in Vortex IQ Nerve Centre *Sage Health Score* is one of hundreds of KPI pulses Vortex IQ tracks across Sage and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.