Skip to main content

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.

Connecting NetSuite brings your ERP and general ledger data into Vortex IQ. Vortex Mind uses NetSuite to run the Daily Revenue Leakage report—reconciling gross ecommerce revenue (from Shopify, BigCommerce, or another commerce platform) against your NetSuite GL booking to identify where revenue is lost to fees, refunds, disputes, or timing gaps. Finance teams can then query this data directly through Ask Viq using a Finance Profile.

​
What Vortex IQ reads from NetSuite

Data typeUsed by
General ledger entriesVortex Mind — Daily Revenue Leakage
Sales orders and invoicesVortex Mind — Payment Performance Intelligence, Daily Revenue Leakage
Customer recordsVortex Mind — Customer Recovery Opportunity
Refund and credit memo recordsVortex Mind — Daily Revenue Leakage, Decline Recovery Intelligence

​
How to connect

NetSuite uses token-based authentication (TBA). You will need to create an integration record and generate access tokens inside NetSuite before connecting.
1

Create a NetSuite Integration Record

In NetSuite, go to Setup → Integrations → Manage Integrations → New. Name it “Vortex IQ”, enable Token-Based Authentication, and save. Note the Consumer Key and Consumer Secret.
2

Create an Access Token

Go to Setup → Users/Roles → Access Tokens → New. Select the Integration you just created, select a user with the appropriate role, and save. Note the Token ID and Token Secret.
3

Open Connected Sources in Vortex IQ

Navigate to Settings → Connected Sources, click Add Source, and select NetSuite.
4

Enter credentials

Enter your NetSuite Account ID, Consumer Key, Consumer Secret, Token ID, and Token Secret, then click Save.
5

Verify

Vortex IQ runs a connection test. A successful test confirms credentials are valid and pulls begin.
The NetSuite user associated with the access token must have read access to Transactions, Customers, and General Ledger records. Missing role permissions cause partial or failed data pulls.

​
Troubleshooting

Double-check that TBA is enabled on the integration record in NetSuite, and that the Token ID/Secret match the token created for that integration (not a different one).
The NetSuite user’s role must include read access to the Transaction and Accounting Period record types. Ask your NetSuite admin to verify role permissions.
NetSuite imposes concurrent API connection limits. If other integrations are polling heavily at the same time, Vortex IQ may hit rate limits. Use Settings → Data Refresh to stagger the NetSuite refresh cadence to off-peak hours.