Skip to main content
Vortex IQ Nerve Centre tracks 60 KPI pulses for Sage stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves. Sage Intacct is the system of record for US mid-market commerce finance. Specifically Sage Intacct, the cloud-native dimensional financials product, not Sage 50, Sage 100, or Sage 200 (which are SMB desktop / hybrid lineage products) and not Sage X3 (which is a separate mid-market manufacturing ERP). Vortex IQ’s Sage connector targets Sage Intacct exclusively because that is the product where mid-market US ecommerce, B2B distribution, services, and SaaS-subscription businesses (10Mto10M to 150M revenue) actually run their books. The defining feature of Sage Intacct, the single thing that distinguishes it from every other mid-market financial system, is its dimensional accounting model: every transaction line carries Department, Location, Project, Item, Class, Customer, Vendor, and Employee tags by default. Those eight first-class dimensions are not bolt-ons or custom records, they are queryable structures inside the GL Detail itself. That fact alone rewires how a Controller, a VP Finance, or an Implementation Partner works the numbers on a Monday morning. The persona running this dashboard is the Finance Controller, the Bookkeeper, or the VP Finance / VP Operations at a US mid-market business, often paired with a Sage Intacct-certified Implementation Partner (an accounting firm or VAR who owns the Chart of Accounts mapping, the dimension structure, and the monthly board pack). They open Intacct at 9am every Monday for cash-flow telemetry: how much GL revenue did we book by Department, by Class, by Project; which Customers are aged into 60+ days; what the Multi-Entity Console roll-up looks like across the US, Canadian, and APAC entities. Sage Intacct has the data and the dimensions; what Sage Intacct does not have is a single screen that surfaces the killer cross-stack findings every Controller actually wants to see, namely the gap between commerce-platform revenue and Intacct GL-booked revenue, decomposed by both reason and dimension. The first killer finding is the revenue gap reconciliation, dimensionally decomposed. Commerce platforms (Shopify, BigCommerce, Adobe Commerce) report gross order totals that always exceed Intacct GL-booked revenue, often by 1.5 to 5% in any 30-day window. Other ERP gap cards decompose the gap by reason (Pending Billing, Credit Memos, unmapped orders); the Sage Intacct version decomposes by reason AND by Intacct dimension simultaneously. A merchant whose unmapped-orders cause concentrates in one Customer cohort (a B2B portal with broken Customer-dimension links), one Item launch (a new SKU launched on commerce before its Intacct Item record was created), or one Project (an Implementation Services workflow with dimensional drift) sees the cause and the fix in one read. This is the structural advantage of running Sage Intacct as the financial spine plus Vortex IQ as the cross-stack telemetry. Most US mid-market Controllers see this view for the first time and identify 50Kto50K to 400K of trapped working capital that nobody had previously surfaced. The second killer finding is the dead-stock-with-active-ad-spend kill shot. Intacct shows Item-tagged sales velocity (a single GL Detail query); Google Ads, Amazon Ads, and Meta Ads show campaign spend by SKU. Cross-tabulating reveals Items that have not sold in 90+ days but are still receiving thousands of dollars per month in paid traffic. For a Sage Intacct merchant in the 20Mto20M to 100M band running 100Kto100K to 400K of monthly ad spend, this typically surfaces 30Kto30K to 150K of recoverable annual budget, often more. Sage Intacct’s dimensional Item read is structurally cleaner than NetSuite’s or Acumatica’s for this join, which makes the card uniquely accurate on Intacct. The third killer finding is margin erosion at the Item dimension level, often layered with the Project or Customer dimension for services-heavy businesses. A 2 percentage point drop in headline gross margin almost always traces to a small set of Items with 20 to 35 percentage point drops, plus (on services merchants) a small set of Projects whose billable utilisation collapsed. Intacct tracks the data dimensionally; surfacing the per-Item per-Project drift requires a comparison ICR that most Implementation Partners do not maintain. The Margin Erosion Alerts card runs that comparison continuously. Beyond the three killer findings, Sage Intacct’s data shape is unique on the Nerve Centre because it is dimensional-first, multi-entity (via Multi-Entity Console with intercompany eliminations), and Implementation-Partner-mediated. Multi-Entity Console accounts route the 60 cards through a per-entity scope, an FX translation layer that respects per-entity cadence configuration, and an elimination convention. Single-entity accounts collapse the same logic to a single bar. The Implementation Partner relationship means most accounts have a curated Chart of Accounts and dimension hygiene; Vortex IQ’s field map aligns with the Partner’s mapping so this card catalogue and the Partner’s monthly pack speak the same language. The integration is built on Sage Intacct’s REST API and the long-standing XML API (Web Services API), with Web Services User authentication. The XML API is faster for bulk GL Detail reads (the workhorse for the cross-channel reconciliation cards); REST is used for incremental change-event delivery and for transactional create/update operations. Refresh cadence is 15 minutes for posted GL data and real-time for status flags (credit holds, OOS alerts) on workspaces with webhook notifications enabled. Vortex IQ Nerve Centre keeps Sage Intacct as the source of truth for everything financial, every dimensional cut, and every audit-grade reconciliation; commerce platforms remain the source of truth for everything customer-facing. The AI OS positioning anchor: Sage Intacct’s dimensional accounting is brilliant inside finance. Vortex IQ extends those dimensions across your live commerce, ads, payment, and monitoring surfaces, joined to the live customer-cohort data your finance team cannot see in Intacct alone. Sage Intacct tells you what the GL knows, dimensionally. Vortex IQ tells you the truth across the whole stack, dimensionally.
CardClassTierCategoryChart
Days Sales Outstanding (DSO)🦸 HeroheroReceivables & Cashgauge
Dead Stock Value🦸 HeroheroInventory & Itemskpi
Gross Margin Percentage🦸 HeroheroMargin & Cost Intelligencegauge
Inventory Aging🦸 HeroheroInventory & Itemsbar
Margin Erosion Alerts🦸 HeroheroMargin & Cost Intelligencealert_table
Open Order Value🦸 HeroheroExecutive Command Centrekpi
Orders Blocked on Inventory or Credit🦸 HeroheroExecutive Command Centrealert_table
Revenue Booked into GL🦸 HeroheroExecutive Command Centrekpi
Revenue Gap vs Commerce🦸 HeroheroExecutive Command Centrekpi
Total Inventory Value🦸 HeroheroInventory & Itemskpi
Commerce Orders Without Sage Intacct Order🔗 Cross-Channel-Cross-Channel: Revenue Reconciliationalert_table
Dead Stock with Active Ad Spend🔗 Cross-ChannelheroCross-Channel: Revenue Reconciliationalert_table
Inventory Sync Drift🔗 Cross-Channel-Cross-Channel: Revenue Reconciliationalert_table
OOS with Open Order Demand🔗 Cross-ChannelheroCross-Channel: Revenue Reconciliationalert_table
Revenue Gap, Detailed Breakdown🔗 Cross-ChannelheroCross-Channel: Revenue Reconciliationtable
A/R Aging DetailNon-Hero-Receivables & Cashbar
Active CustomersNon-Hero-Customers & B2Bkpi
Average Landed Cost per UnitNon-Hero-Inventory & Itemskpi
Average Order ValueNon-Hero-Revenue & Sales Performancekpi
B2B Payment Terms MixNon-Hero-Customers & B2Bpie
Cash Application RateNon-Hero-Receivables & Cashgauge
Cash Applied TodayNon-Hero-Executive Command Centrekpi
Cash CollectedNon-Hero-Revenue & Sales Performancekpi
Consolidated Revenue TrendNon-Hero-Multi-Entity Dashboardarea
Credit Hold SpikeNon-Hero-Alerts & Anomaliesalert_table
Credit Memo ValueNon-Hero-Order Operationskpi
Customer Churn SignalsNon-Hero-Customers & B2Balert_table
Customer Credit UtilisationNon-Hero-Customers & B2Bgauge
Dead Stock Threshold BreachNon-Hero-Alerts & Anomaliesalert_table
DSO Increase AlertNon-Hero-Alerts & Anomaliesalert_table
Entity Health Roll-upNon-Hero-Multi-Entity Dashboardtable
Entity PerformanceNon-Hero-Multi-Entity & Multi-Currencytable
FX Currency ExposureNon-Hero-Multi-Entity & Multi-Currencybar
High-Value Overdue InvoicesNon-Hero-Alerts & Anomaliesalert_table
Intercompany BalanceNon-Hero-Multi-Entity & Multi-Currencykpi
Inventory Carrying CostNon-Hero-Inventory & Itemskpi
Inventory Turnover RatioNon-Hero-Inventory & Itemsgauge
Invoice Aging SummaryNon-Hero-Executive Command Centrebar
Invoiced RevenueNon-Hero-Revenue & Sales Performancekpi
Landed Cost Variance vs StandardNon-Hero-Margin & Cost Intelligencebar
Low Stock AlertsNon-Hero-Inventory & Itemsalert_table
Margin by SKUNon-Hero-Margin & Cost Intelligencebar_horizontal
Margin CompressionNon-Hero-Alerts & Anomaliesalert_table
Open OrdersNon-Hero-Order Operationskpi
Order State BreakdownNon-Hero-Order Operationspie
Order to Invoice Lead TimeNon-Hero-Order Operationsgauge
Orders on Credit HoldNon-Hero-Receivables & Cashalert_table
Overdue Invoice ValueNon-Hero-Receivables & Cashkpi
Returns CountNon-Hero-Order Operationskpi
Revenue Booked Over TimeNon-Hero-Revenue & Sales Performancearea
Revenue by CurrencyNon-Hero-Revenue & Sales Performancebar
Revenue by EntityNon-Hero-Revenue & Sales Performancebar
Revenue by SegmentNon-Hero-Revenue & Sales Performancebar
Revenue Gap SpikeNon-Hero-Alerts & Anomaliesalert_table
Top B2B Accounts by RevenueNon-Hero-Customers & B2Bbar_horizontal
Top Customers by RevenueNon-Hero-Revenue & Sales Performancebar_horizontal
Top Findings Across EntitysNon-Hero-Multi-Entity Dashboardalert_table
Top SKUs by Inventory ValueNon-Hero-Inventory & Itemsbar_horizontal
Total COGSNon-Hero-Margin & Cost Intelligencekpi
Unpaid Invoice CountNon-Hero-Receivables & Cashkpi

​
Cross-connector reconciliation: how Sage Intacct fits into the Vortex IQ stack

Sage Intacct is the system of record for revenue, AR, inventory, and dimensional reporting at US mid-market commerce, B2B distribution, services, and SaaS-subscription businesses. It rarely operates alone: the typical Vortex IQ Sage Intacct tenant runs alongside one or more commerce platforms (Shopify Plus, BigCommerce B2B Edition, Adobe Commerce), at least one payment connector (Stripe, PayPal, sometimes Authorize.Net for older accounts), and often ad platforms (Google Ads, Amazon Ads, Meta) for the Retail D2C Class. The cross-connector value of Sage Intacct is the same fact: every other connector tracks ONE LENS on the customer; Intacct is the only system that records the GL-level truth dimensionally, so every other lens must reconcile against the dimensional Intacct read. The reconciliation patterns in priority order: (1) commerce orders to Sage Intacct Orders via Commerce Orders Without Sage Intacct Order, the largest revenue-leakage detector for merchants migrating onto integrated stacks; expect 1.5 to 5% of commerce revenue to be missing in Intacct books on first connection, with the dimensional decomposition revealing whether the cause is Customer-mapping, Item-mapping, Class-routing, or Project-tag drift; (2) commerce inventory to Intacct Item.qty_on_hand by Location via Inventory Sync Drift, the operational-risk twin of the revenue gap with the unique Sage Intacct value of per-Location dimensional decomposition; (3) Intacct Credit Memos to gateway refund value via Credit Memo Value plus the corresponding stripe.stripe_refund_value or paypal.pp_refund_value cards, the GL-vs-bank reconciliation; (4) Intacct dead stock to ad-platform spend via Dead Stock with Active Ad Spend, the kill shot for ad-spend recovery, joining Item-tagged sales velocity from Intacct’s GL Detail to spend from Google Ads, Amazon Ads, and Meta Ads. The dimensional read on Intacct makes (4) cleaner than the equivalent finding on NetSuite or Acumatica.

​
Sage Intacct API freshness

Sage Intacct exposes data through two complementary APIs: the long-standing XML API (also called the Web Services API), and the newer REST API. Vortex IQ uses the XML API for bulk GL Detail extraction (the workhorse for revenue cards and dimensional cuts; faster for large reads of joined revenue and COGS lines) and the REST API for incremental refreshes and webhook-style change-event delivery where supported. Authentication uses a dedicated Web Services User per workspace (the Sage Intacct security model expects API access via a separate user record from the human Controller’s login). Refresh cadence is typically 15 minutes for posted GL data on standard workspaces, and real-time for status flags (credit holds, OOS alerts, Order Entry state changes) where webhook notifications are enabled. The XML API has historically been more dimension-aware than the REST API; for any card that requires dimensional decomposition, Vortex IQ defaults to the XML API source.

​
Sage Intacct Implementation Partner complementarity

Most Sage Intacct merchants are paired with an Intacct-certified Implementation Partner: an accounting firm or VAR who owns the Chart of Accounts setup, the dimension structure, and typically the monthly board pack. The Partner’s role is structural (they designed the Chart and the dimension hygiene rules) and ongoing (they run the close and produce the management accounts). Vortex IQ does not replace the Partner relationship; it complements it. The Partner sees what is inside Intacct cleanly; Vortex IQ sees what arrives at Intacct from the rest of the stack and reconciles it dimensionally. Most Partners welcome Vortex IQ because it answers questions their pack cannot (“where did the $208K go between Shopify and Intacct?”, “which Customer dimension link is broken?”, “is this Project’s revenue recognition lagging?”) without requiring them to build new ICRs. Aligning Vortex IQ’s field map to the Partner’s Chart of Accounts mapping is the onboarding step that locks both views into the same vocabulary.

​
FAQ-style notes

When does Sage Intacct data refresh? XML API bulk reads on the workspace’s configured cadence; cards typically reflect transactions within 15 minutes for posted GL data, real-time for webhook-driven status events. Real-time RT cards (Open Orders, Customer Credit Utilisation, OOS-with-Open-Order-Demand) re-query on dashboard load. Sage Intacct vs NetSuite, when to choose which? Sage Intacct for 10Mto10M to 150M revenue businesses where dimensional accounting is operationally important (services, agencies, project-based commerce, multi-Class hybrid B2B + Retail D2C, Multi-Entity Console with light intercompany). NetSuite for similar revenue bands but where deeper transactional commerce, native PSA, native CRM, and tighter Suite integration are higher priority. Both are Oracle-owned (Sage Intacct is Sage Group, not Oracle, but they compete in the same mid-market segment). Implementation cost and time-to-value are typically lighter on Intacct (~3 to 6 months) than on NetSuite (~6 to 12 months); the trade-off is that Intacct does less out of the box on the operational side. Vortex IQ supports both connectors with the same KPI catalogue framing, easing the choice. Multi-Entity Console aggregation, how does it affect Vortex IQ cards? Top Level entity views with eliminations enabled apply intercompany cancellations automatically; per-entity views show raw inter-co revenue. The dashboard filter respects the chosen scope. The most common Multi-Entity Console pattern on Sage Intacct is a US parent entity plus one or two foreign subs (Canada, UK, or APAC); the cards collapse cleanly to single-entity views on accounts that have not yet adopted Multi-Entity Console. REST vs XML API freshness, which does Vortex IQ use? Both. XML API for bulk GL Detail reads (revenue, COGS, Item-tagged transactions, dimensional cuts); REST for incremental change events and transactional create/update. The number on any card reflects the GL state as of the last sync window. For real-time intraday checks, the native Intacct UI is always live; the card refreshes on the workspace’s configured cadence. Sage Intacct Contracts and Revenue Management module, what cards does it affect? Revenue Booked into GL, Invoiced Revenue, and any Item-velocity-driven card (including Dead Stock with Active Ad Spend) read recognised revenue rather than billed revenue when the Contracts module is enabled. SaaS-adjacent and subscription-bundled businesses see materially different per-period numbers under Contracts than they would under invoice-on-billing accounting. Sage Analytics or Intacct Custom Reports complementarity? Sage Intacct’s native Custom Reports and Interactive Custom Reports (ICRs) are excellent for dimensional cuts inside Intacct’s data. Use them for in-Intacct financial dashboards, period-close reports, and dimension-pivot views. Use Vortex IQ for the cross-stack views Intacct’s reporting fundamentally cannot show because the underlying data lives outside Intacct (Shopify orders, Google Ads spend, Stripe refunds). Both layers running side-by-side is the typical Sage Intacct mid-market pattern. Implementation Partner alignment on the field map? Critical. The Partner’s Chart of Accounts and dimension structure define what the cards consider revenue, COGS, shipping, and contra-revenue. Confirm during onboarding: revenue account range (typically 4000-4999), COGS range (typically 5000-5999), shipping treatment (revenue vs contra-cost), Multi-Entity elimination convention, and any custom dimension structures. Vortex IQ’s field map captures these and ensures the cards match the Partner’s monthly pack.