Yes. Oracle's SuiteAnalytics Connect is read-only by design, and NetSuite's REST interface answers SuiteQL queries under a role your administrator sets up; either way, NetSuite applies that role's permissions to everything the warehouse asks for. Each night, transactions, customers, items and classifications load beside your other systems, AI checks them against the rules agreed in the audit, and the morning's figures are ready on one screen. Connect is an add-on module bought separately, so the audit checks what your account already has first.
What NetSuite's own reporting covers, and what it cannot see
Saved searches, SuiteAnalytics Workbook and the financial statements cover orders, stock, invoices and the ledger, and OneWorld consolidates subsidiaries in the parent's base currency, with intercompany transactions eliminated as the last task on the period close checklist.
What it cannot see is activity that never passes through it. Ad spend sits in the ad platforms, tickets and return reasons in a support desk, people costs with the payroll provider, and in many groups at least one company keeps its books in another system. Each of those knows the same customers under identifiers of its own.
There is a narrower gap inside NetSuite too. Budgets can be set up by custom segment, yet custom segments are not among the columns of the Budget vs. Actual report, which Oracle lists as including period, class, department, location and subsidiary. A business managed by a custom segment, a brand or a sales channel for instance, often compares budget with actual outside NetSuite.
The routes Oracle provides for reading NetSuite
From Oracle's NetSuite documentation. Which one fits depends on what your account includes, so the audit checks it before anything is quoted.
SuiteAnalytics Connect
Oracle's read-only service, with ODBC, JDBC and ADO.NET drivers, reading the NetSuite2.com data source. It is an add-on module bought through your NetSuite account manager, and Oracle does not offer it on Small Business accounts.
REST web services with SuiteQL
Queries in SuiteQL, NetSuite's SQL-based query language, sent through the REST interface under an integration record and a role. Oracle caps each query at 100,000 results and points larger reads to Connect.
Saved searches
Exported to CSV or Excel, or emailed on a schedule. A scheduled email stops at 10,000 rows and is cut off past 5 MB, so this suits a short list rather than the ledger.
The role under every route
NetSuite applies a role's permissions to every query. Oracle names a Data Warehouse Integrator role as its preferred option for moving data to a warehouse; a custom role limited to what the reports need is the alternative, agreed with your administrator.
Questions NetSuite cannot answer from inside
Each one needs NetSuite and at least one system beside it. The audit picks the ones your board asks first.
What a customer cost to win, by channel
Spend from the ad platforms set against the customers NetSuite actually invoiced, channel by channel.
Margin after returns and service
Credits from NetSuite joined to tickets and return reasons from the support desk, product by product.
Cost per order, people included
Pay totals for the fulfilment and service teams set against the orders NetSuite shipped in the same month.
Budget against actual by custom segment
The budget already held in NetSuite by brand or channel, compared every morning with actuals on that same segment.
One group view, whichever system
NetSuite subsidiaries and the companies outside NetSuite reported under one set of lines, each still visible on its own.
How the warehouse reads NetSuite, and checks what it reads
Whichever route the audit settles on, the warehouse reads NetSuite under a role created for it, never an administrator's login; Oracle itself does not recommend the Administrator role for REST integrations, for security reasons. NetSuite then applies that role's permissions to every query, so the warehouse sees only the records and fields the role allows.
Custom fields and custom records come across with the standard ones. Through NetSuite2.com they are queried by their IDs, so renaming a field's label in NetSuite does not break the load. A new field the reports should use is added to the mapping, with your partner telling us what it means.
Every load is then checked by AI against the matching rules below before the figures reach a report: an order with no channel recorded, a shop customer that matches no NetSuite customer, a new custom segment value with no report line. Each goes to the person who owns it, to fix in NetSuite or in the shop, and the 110 Command Centre opens each morning on figures that have passed those checks.
On the REST route, Oracle governs at account level how many web services and RESTlet requests run at once, counted together, so the allowance is shared with your other integrations. The loads are scheduled overnight and kept inside it, with the timing agreed with your partner where other integrations also run at night. If a night's load fails, the person named for it is told, while NetSuite carries on regardless.
What NetSuite holds for reporting, and what usually sits beside it
The middle column is NetSuite's, from Oracle's documentation. The right column is what a warehouse adds from the systems around it.
| Held in NetSuite | Beside NetSuite, joined in the warehouse | |
|---|---|---|
| Customers and orders | Customer records, sales orders, invoices and credits | Shop accounts and the campaign that brought each order |
| Costs | Purchases, expenses and the ledger | Pay totals by department from the payroll provider |
| After the sale | Credits and returns as posted | Tickets and their reasons from the support desk |
| The group | OneWorld subsidiaries, consolidated in the parent's currency | Companies that keep their books in another system |
| Classification | Departments, classes, locations and custom segments | The same labels mapped to the board's report lines |
| Change history | System notes: who changed which field, when, from what to what | A dated copy of every night's read, kept for trends |
An online and trade seller with one company outside NetSuite
A Maltese company sells through its own online shop and to trade buyers, with two subsidiaries in NetSuite OneWorld and a third company, bought last year, still on another accounting system. Advertising runs on two ad platforms, customer service works in a support desk, and payroll is run by a provider that sends a file each month.
- Marketing reports clicks and conversions, finance reports invoiced revenue, and the two never share a page.
- Returns are logged in the support desk and credited in NetSuite, with no link to the product or the campaign.
- The group pack is put together from exports each month, because the newest company is not in NetSuite.
- Budget against actual by brand lives in a spreadsheet, because brand is a custom segment.
- NetSuite, read through Connect under a role made for the warehouse, loads overnight with the shop, both ad platforms, the support desk and the payroll file.
- Each channel shows spend, customers won, repeat orders and returns on one screen, and orders with no channel are flagged for the shop team.
- The newest company's ledger sits beside the two NetSuite subsidiaries under one set of report lines.
- Budget against actual by brand refreshes every morning from the budget already kept in NetSuite.
Nobody changed how they work in NetSuite, and the partner's plans for it stayed as they were. Marketing, finance and the group board now start the day from the same figures.
Matching rules to settle before NetSuite meets the other systems
Customer
NetSuite's customer ID carried into the shop, or the email address both hold, agreed as the key. Customers that match on neither are listed, never guessed.
Item
The shop's product code and NetSuite's item record agreed as one key, with bundles and variants decided up front.
Channel
Which field on the order records where it came from, and how each ad campaign maps to it. Without that field, cost per customer by channel cannot be worked out.
Subsidiary and currency
Which figures stay in each subsidiary's own currency and which are shown in the parent's, at the rates finance chooses.
Classifications to report lines
Departments, classes, locations and custom segments mapped once to the lines the board reads.
What we do not do
- We do not sell, license, implement or support NetSuite. Your NetSuite partner keeps doing that.
- We do not add scripts, customisations or workflows to NetSuite, and nothing is written back to it.
- We do not connect your shop to NetSuite so that orders flow between them. That integration work stays with your partner or integrator.
- NetSuite data is copied into a warehouse in your own cloud account.
How it works
- A strategy callThirty minutes with Glen, free, with no pitch deck. Bring the systems you run and the question none of them answers on its own. You leave knowing whether joining them is worth doing, and where to start.
- The data auditAbout three hours with your team, mapping where each figure comes from, which system holds it and which steps are done by hand. The audit confirms how each system can be read, and it ends with a quote.
- The buildThree to four weeks from an accepted quote to a live dashboard. Implementation is the first month. Your team agrees the definitions with us; we do the building.
- The fractional teamAn ongoing senior team keeps the loads running, follows changes made to your systems and connects the next source when the business needs it.
Glen Sultana founded 110 Analytics after a career built where the numbers move daily. Our people have run analytics for tier-one companies, S&P 500 firms and high-growth technology businesses. Glen is the person on the first call, and he runs every data audit himself.
- Built in your environment, under your account
- Every connection approved by you first
- Based in Malta
Straight answers
Does NetSuite stay as it is?
Yes. Your teams keep working in NetSuite, and its saved searches and financial statements carry on as they are. Alongside it, the warehouse keeps its own copy of the records your reports use, together with the systems NetSuite never sees.
Will this affect our NetSuite partner or licence?
Whoever supports NetSuite for you keeps doing so, and NetSuite is left as it is. If the audit recommends SuiteAnalytics Connect and your account does not have it, Oracle sells it as an add-on through your account manager, and you hear that before any quote, as you do for anything the warehouse's user needs licensed. The role it uses is created by your administrator or partner.
How do you connect to NetSuite?
Through SuiteAnalytics Connect, Oracle's read-only service, or through NetSuite's REST interface with SuiteQL queries, under a role your administrator creates for the warehouse. Saved search exports are kept for short lists. The audit confirms which suits your account.
Is SuiteAnalytics Connect really read-only?
Yes. Oracle describes Connect as a read-only way of obtaining NetSuite data and states that it cannot be used to update NetSuite. On the REST route, the role decides what is possible, so it is limited to what the reports need to see.
Oracle sells NetSuite Analytics Warehouse. How is this different?
NetSuite Analytics Warehouse is Oracle's own: a warehouse service Oracle manages, with ready-made NetSuite KPIs, dashboards and reports, sold by subscription. What we build sits in your own cloud account and is designed around the systems beside NetSuite as much as NetSuite itself. If nearly everything you report on lives in NetSuite, Oracle's product may suit you better.
We use OneWorld. Does that change anything?
It helps. Subsidiaries, their currencies and the consolidated exchange rates are read with everything else, so each subsidiary can be shown in its own currency and the group in the parent's, with companies outside NetSuite added to the same view.
What does a NetSuite connection cost?
Our price follows the data audit, as a quote. It rests mainly on how many systems join NetSuite and how much matching they need; any NetSuite add-on stays between you and Oracle.
Terms on this page
- NetSuite2.com
- The data source SuiteAnalytics Connect reads. From NetSuite 2026.1 the older NetSuite.com source is no longer available, so it is the only one Connect offers.
- SuiteQL
- NetSuite's query language, based on SQL. It respects the same role-based access as SuiteAnalytics Workbook.
- Subsidiary
- A legal entity in NetSuite OneWorld, with its own base currency.
- Custom segment
- A classification your business adds, alongside department, class and location, such as brand or channel.
Where the product facts come from
Every product fact on this page comes from the vendor's own documentation, read on 22 October 2026. Vendors change their products, so the audit checks the version you run.
- Oracle NetSuite Help: SuiteAnalytics Connect (read-only; ODBC, JDBC, ADO.NET)
- Oracle NetSuite Help: SuiteAnalytics Connect FAQ (add-on module; Small Business accounts)
- Oracle NetSuite Help: the NetSuite.com data source is no longer available
- Oracle NetSuite Help: role and permission considerations for NetSuite2.com (Data Warehouse Integrator role)
- Oracle NetSuite Help: the analytics data source and SuiteAnalytics Connect
- Oracle NetSuite Help: SuiteQL
- Oracle NetSuite Help: executing SuiteQL queries through REST web services (100,000 results)
- Oracle NetSuite Help: prerequisites and setup for REST web services
- Oracle NetSuite Help: record types and fields (custom fields and records in NetSuite2.com)
- Oracle NetSuite Help: exporting search results
- Oracle NetSuite Help: saved search email (10,000 rows, 5 MB)
- Oracle NetSuite Help: consolidated reporting in OneWorld
- Oracle NetSuite Help: intercompany elimination overview
- Oracle NetSuite Help: classifications overview
- Oracle NetSuite Help: custom segments overview
- Oracle NetSuite Help: setting up a budget
- Oracle NetSuite Help: budget-related reports (Budget vs. Actual)
- Oracle NetSuite Help: system notes overview
- Oracle NetSuite Help: web services and RESTlet concurrency governance
- Oracle: about NetSuite Analytics Warehouse
