How Cube Connects to NetSuite

Cube connects to NetSuite through a native, Cube-built connector. This is a direct, read-only API connection: Cube pulls your financial data from NetSuite on demand, and nothing is ever written back to your ERP. There is no middleware to install and no agent running in your environment.

This article explains how the connection works, what data Cube pulls, what's required from your team, and how long setup takes.

Connection at a Glance

How It Works

1. Authentication via NetSuite access tokens. Your NetSuite administrator creates an integration record and generates access tokens using NetSuite's Token-Based Authentication. This means Cube never stores a NetSuite username or password, and access can be revoked by your admin at any time, instantly, from within NetSuite.

2. Data is pulled through Saved Searches. Cube reads your general ledger data through NetSuite Saved Searches. This gives you full control and transparency: the Saved Search defines exactly which accounts, transactions, and dimensions Cube can see, and your team can review it before the connection goes live. Nothing outside the search definition is accessible.

3. Your NetSuite structure maps directly into Cube. Cube pulls your chart of accounts as-is and maps each NetSuite subsidiary to a Cube entity, so multi-entity organizations see the same structure in Cube that they manage in NetSuite. Standard NetSuite dimensions come along with the data, including:

• Subsidiary
• Department
• Class
• Location
• Customer and Vendor
• Custom segments (enabled by your admin in the Saved Search)

4. Refresh on your terms. Once connected, you can pull updated data from NetSuite whenever you need it, so your actuals in Cube stay current without a heavy data engineering lift.

What About Multi-Entity and Multi-Currency?

Cube supports multi-subsidiary NetSuite environments, including organizations with multiple currencies. Each subsidiary maps to its own entity in Cube, and consolidation, FX handling, and roll-up structures are configured during implementation to match how your team reports today.

What About Messy Data?

Real-world GL data is rarely perfect. Cube's semantic layer and mapping rules handle the most common NetSuite data quality patterns, such as inconsistent naming across transactions or historical postings to the wrong cost center, without requiring you to clean up your ERP first. Where issues do exist at the source, Cube surfaces them clearly so your team can correct them over time.

What's Required From Your Team

The main resource on your side is your NetSuite administrator. During setup, your admin will:

1. Enable Token-Based Authentication (usually already on)
2. Create an integration record and a read-only role for Cube
3. Generate the access tokens
4. Review and approve the Saved Search that defines the data Cube pulls

Cube's implementation team guides your admin through each step in a structured walkthrough, so no prior integration experience is needed on your side.

What Does Implementation Look Like?

For a proof of concept or trial, the focus is connecting your chart of accounts and entity structure so you can see your live data in Cube. A full production implementation adds custom roll-up views, mapping rules, and connections to adjacent systems like your CRM or HRIS, following Cube's standard activation process. Your Cube team will scope the specifics with you based on your environment.

Security Summary

• Read-only access. Cube cannot create, modify, or delete anything in NetSuite.
• No stored credentials. Authentication uses revocable access tokens, not passwords.
• Scoped data access. Cube sees only what the Saved Search defines, and your team approves it.
• No installed software. The connection is API-based; nothing runs inside your environment.

Questions about connecting your NetSuite instance? Reach out to your Cube account team or contact support@cubesoftware.com.