Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings Vortex IQ Nerve Centre tracks 60 KPI pulses for Microsoft Dynamics 365 stores. Each metric has its own page: definition, calculation, why it matters, and what to do when it moves. Microsoft Dynamics 365 Business Central (formerly Dynamics NAV) is Microsoft’s mid-market cloud ERP for commerce, manufacturing, and service businesses. Business Central sits at the heart of Microsoft-shop mid-market operations: deep Microsoft 365 integration, Power BI dashboards out of the box, AL Extensions for safe customisation, native Common Data Service sharing with Dynamics 365 Sales (CRM). The persona is the VP Finance or Controller running a 30Mto30M to 150M commerce or manufacturing business who wants Microsoft-native UX without the implementation weight of SAP S/4HANA or the platform breadth of NetSuite. Vortex IQ tracks 60 KPI pulses for Business Central, every one mapped to merchant decisions a Controller actually makes at 9am Monday. Three of those pulses are the killer findings any mid-market commerce business on Business Central feels immediately:
  1. Revenue Gap vs Commerce. The dollar value of commerce-platform orders (Shopify, BigCommerce, Adobe Commerce) that have not yet hit the BC General Ledger, broken down by reason: Released-Not-Invoiced, Sales Credit Memo Refund, Unmapped Marketplace, Period Boundary Timing. Most BC merchants run an 8 to 15% gap on a 30-day window. The card surfaces every dollar with the originating order ID.
  2. Dead Stock with Active Ad Spend. SKUs that are dead in BC (zero sales in 90+ days, ageing inventory) but still receiving Google Ads, Amazon Ads, or Meta Ads spend. The cross-platform join only Vortex IQ delivers: BC knows velocity, ad platforms know spend, neither sees the intersection. Typical recovery: £30K to £120K of annualised wasted ad spend for £2M to £20M revenue merchants.
  3. DSO and Sales Orders Blocked. The classic working-capital pair. DSO at terms + 5 to 15 days is healthy; beyond that signals collection drift. Sales Orders Blocked surfaces stuck SOs with reason (Credit Hold, Inventory Shortage, Pending Approval >72hrs) so the Controller’s morning unblocking queue is one click away.
Business Central versus NetSuite. Same arithmetic on hero KPIs: revenue, COGS, margin, AR. The difference is the surrounding ecosystem. BC is Microsoft-native: Office 365 UX feels familiar, Teams notifications work without integration plumbing, Power Automate triggers on document events come for free, Power BI dashboards are first-class. NetSuite delivers a broader pre-built marketplace and quarterly release cadence (BC ships major releases twice a year), and scales further into the 150Mto150M to 500M revenue range. For Microsoft-shop mid-market merchants, BC’s stack integration is the differentiator. Business Central versus SAP S/4HANA. S/4HANA is enterprise-tier with deeper manufacturing-cost, treasury, and tax-jurisdiction tooling, but implementation cost is typically 5 to 10x BC. For mid-market commerce + light manufacturing, BC’s AL Extensions handle 80% of customisation needs without the SAP weight. The AI OS positioning anchor: Vortex IQ joins your Business Central General Ledger to your live commerce, ads, payment, and monitoring surfaces. Power BI shows one ERP at a time, one Company at a time. Vortex IQ surfaces the gap between Business Central and Shopify the moment it appears. That is what makes the difference between a Controller who reacts to month-end surprises and a Controller who walks into board meetings already knowing the answer. Cross-connector reconciliation guidance. The single most-asked question in any BC merchant onboarding is “where did the £531K go?” The answer lives on the Revenue Gap, Detailed Breakdown card: every commerce order that has not yet generated a Posted Sales Invoice in BC, with reason code and originating order ID. The Controller exports the table at 8am Monday, sorts by gap descending, and assigns rows by reason: Released-Not-Invoiced to the AR clerk, Unmapped Customer to the BC Functional Consultant, Credit Hold to the CFO conversation queue. Steady-state target is a small structural gap (Net-30 ship-to-bill lag plus Sales Credit Memos), with the Unknown bucket near zero. API freshness. Vortex IQ pulls BC data via the OData v2.0 REST API at businesscentral.dynamics.com. Auth is OAuth2 via Azure AD. Most KPIs use a 15-minute cache; real-time cards (Open Sales Orders, Sales Orders Blocked, Cash Applied Today) refresh every 5 minutes. Posted documents appear via OData immediately on posting (no batch lag). This is materially fresher than Power BI’s standard scheduled-refresh cadence (once or twice a day on the BC content pack). Power BI complementarity. Power BI’s Finance Performance, Sales Insights, Inventory Performance, and Cash Flow content packs cover the BC-internal slice well at single-Company scope. Where Power BI cannot reach without custom DAX or Premium-tier work: multi-Company consolidation, cross-connector reconciliation (commerce vs BC), cross-platform kill-shots (dead stock with active ad spend, OOS with SO demand). Vortex IQ delivers those out of the box. The two tools coexist on the merchant’s desktop: Power BI for one-Company deep-dives, Vortex IQ for the consolidated AI OS view. Multi-Company aggregation FAQ. BC’s multi-Company model puts each Company in a separate database table set within a single tenant. The OData API exposes /companies({companyId})/... per Company; Vortex IQ enumerates connected Companies and aggregates server-side, applying FX translation to the configured Reporting Currency via the Adjust Exchange Rates batch convention. Eliminations apply when the user selects the Consolidation Company; per-Company filters are available throughout. Common Data Service / Dataverse FAQ. CDS is the Microsoft integration layer between Dynamics 365 Sales (CRM) and Business Central. Vortex IQ reads BC’s General Ledger, Customer Ledger, Item Ledger, and Sales Header tables directly via OData; CDS is not on the read path. If your tenant uses Dynamics 365 Sales as the customer master and BC as the financial sub-ledger, Customer mapping happens in CDS but the revenue and AR numbers Vortex IQ surfaces are the BC-side truth. Refund vs Sales Credit Memo terminology FAQ. In Business Central a “refund” can mean two different things. A Sales Credit Memo reverses a posted Sales Invoice (or part of it), creating a negative G/L entry on revenue and a Customer Ledger Entry the customer can apply against the original Invoice. A Refund in the Cash Receipt Journal is the actual money going out (bank account credit, customer balance debit). Vortex IQ uses Sales Credit Memo posting (the revenue reversal) for revenue-related cards because the question is “what hit the Income Statement”, not “what left the bank”. Cash Receipt Refunds appear on Cash Collected and Cash Applied Today. AL Extensions FAQ. AL Extensions are Microsoft’s safe customisation framework for BC. They add fields, validations, and workflow without modifying the standard chart of accounts or core posting logic. Vortex IQ works identically across vanilla BC and BC with AL Extensions. Custom revenue accounts, custom Customer Posting Groups, and custom approval states are mapped via the field map at onboarding.