> ## 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. # NetSuite ERP on Vortex IQ > Monitor NetSuite ERP performance signals, run automated checks, and prepare approved work through Vortex IQ. Monitor NetSuite ERP performance signals, run automated checks, and prepare approved work through Vortex IQ. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/netsuite) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=netsuite) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Monitor orders, fulfilment, delivery and settlement. Improve discovery, conversion, campaigns and repeat purchase. Keep tracking, access and change under governed control. Find failures, leaks and risks before they cost sales. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 27 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **AP Aging - 60+ Days** | Alert band 10 / 30 | Description pending editorial review; the signal is live. | | **AR Aging - 60+ Days** | Alert band 5 / 15 | Description pending editorial review; the signal is live. | | **AR Aging Buckets** | Watch only | AR Aging Buckets, compared across items. | | **AR Balance (live, by Subsidiary)** | Watch only | Description pending editorial review; the signal is live. | | **Accounting Period Close Past Deadline** | Alert band 0 / 5 | Alerts for Accounting Period Close Past Deadline. | | **Accounting Period Close Status** | Alert band 0 / 5 | Description pending editorial review; the signal is live. | | **Accrual Reversals (last close)** | Merchant rule | Description pending editorial review; the signal is live. | | **Active Vendors** | Watch only | Description pending editorial review; the signal is live. | | **Customers on Credit Hold (onCreditHold=ON or AUTO)** | Merchant rule | Description pending editorial review; the signal is live. | | **Days Sales Outstanding (DSO)** | Alert band 30 / 60 | Description pending editorial review; the signal is live. | | **ERP-vs-Ecom Inventory Variance %** | Alert band 1 / 5 | Compares NetSuite location on-hand to a separate storefront's availability; dormant for NetSuite-as-store merchants (no external storefront to compare | | **Ecom Customers Absent from NetSuite** | Alert band 0 / 10 | Buyers on a separate storefront with no NetSuite customer record; dormant for NetSuite-as-store merchants. | | **Inventory Item On-Hand Went Negative (any Location)** | Merchant rule | Alerts for Inventory Item On-Hand Went Negative (any Location). | | **Items Below Reorder Point** | Merchant rule | Description pending editorial review; the signal is live. | | **Manual Journal Entries as % of Total** | Merchant rule | Description pending editorial review; the signal is live. | | **New Customers (30d)** | Watch only | Description pending editorial review; the signal is live. | | **On-Hand Inventory Value (by Location)** | Watch only | Description pending editorial review; the signal is live. | | **Transactions by Type** | Watch only | CashSale/CustInvc/VendBill/JournalEntry split. CashSale spike = ecom integration scaling; JE spike = manual override creep. | | **Vendor Payment On-Time Rate** | Merchant rule | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | ------------------------------------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **AR Aging on Customers with Active Ecom Orders** | Alert band 1000 / 10000 | Should auto-flag onCreditHold=ON via SuiteScript. Manual review needed when this fires. | | **Ecom Customers Absent from NetSuite Customer Record** | Alert band 0 / 10 | Ecom buyers without NetSuite Customer = Cash Sale / Invoice can't post under correct entity; revenue recognition rules don't apply. | | **Ecom Orders Missing Matching NetSuite Cash Sale / Invoice** | Merchant rule | Ecom orders the merchant fulfilled but NetSuite never billed for. Common cause: SuiteScript order-import script failing silently. | | **SKUs with NetSuite-vs-Ecom Inventory Drift >5%** | Alert band 1 / 5 | Location-level NetSuite available vs ecom availability. Drives overselling on multi-channel SKUs. | | Signal | Alert behaviour | What it tracks | | ----------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- | | **NetSuite Health Score** | Merchant rule | Composite: integration-error-free x saved-search-fast x AR-aging-low x inventory-variance-low. | | **OneWorld Customers Missing Subsidiary** | Merchant rule | OneWorld-account customer records without Subsidiary assignment break intercompany flows + revenue rule application. | | Signal | Alert behaviour | What it tracks | | ----------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------- | | **Open Transactions (Pending Approval / Error)** | Alert band 0 / 50 | Transactions in PENDING\_APPROVAL or REJECTED status. Spike = SuiteScript integration error or approval-routing rule broken. | | **Transactions Failing to Save (SuiteScript errors)** | Alert band 0 / 5 | SuiteScript record-save failures block transactions. P1 because they often happen silently inside background scripts. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** critical · **Outcome** Protect revenue · **Fix status** Report only An entry where debits and credits do not match cannot post to a correct ledger; if it exists at all, it means something upstream (an import, an integration, a manual entry) produced a genuinely broken transaction that accounting will have to find and fix by hand before the books balance. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `ERP-GL-002` **Severity** high · **Outcome** Run operations · **Fix status** Report only More than 15% of receivables are sitting in the 60+ day bucket. The longer an invoice goes unpaid, the less likely it is ever collected in full, so this is not just a cash-flow timing issue, a growing 60+ day bucket is a leading indicator of bad debt building up. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `ERP-FIN-001` **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation Stock levels disagree between the ERP and the storefront by more than 5% on SKUs that currently have active orders. That gap risks selling inventory that is not really there (an oversell) or holding stock back that is actually available, on exactly the products customers are ordering right now. A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided. Reference: `ERP-INV-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only The accounting period is more than 5 days past its close deadline and still open. Every day it stays open is another day transactions can still be edited or added to a period that reporting, tax filing and any lender or investor reporting expects to be final. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `ERP-CLOSE-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only More than 50 journal entries are sitting unposted. Every report pulled from the general ledger while this backlog exists, profitability, cash position, tax figures, is working from incomplete books, and the larger the backlog grows the harder it gets to reconcile at period close. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `ERP-GL-001` **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation Customers who ordered over a week ago still are not in the ERP's customer master. Anything downstream that depends on that record, invoicing, tax reporting, credit terms, customer-level reporting, is working with an incomplete customer base until this syncs. A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided. Reference: `ERP-CUST-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **5 read** and **2 write** operations across serviceauthoauth2tokens, servicequerysuiteqls, servicerecordaccounts, servicerecordcustomers, servicerecordinventoryitems, servicerecordtransactions on NetSuite ERP. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=netsuite) #### Ready to build your first NetSuite ERP workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | --------------------------- | --------------- | ---------------- | | serviceauthoauth2tokens | 0 | 1 | | servicequerysuiteqls | 0 | 1 | | servicerecordaccounts | 1 | 0 | | servicerecordcustomers | 1 | 0 | | servicerecordinventoryitems | 1 | 0 | | servicerecordtransactions | 1 | 0 | | servicerecordvendors | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.