What NetSuite gives through its API
Control.dev reads NetSuite through its REST API with a dedicated integration role, never an Administrator role. Each Control.dev entity connects to one NetSuite subsidiary and its primary accounting book. Control.dev only reads NetSuite, never writes to it, and NetSuite stays the book of record.
- Posted general ledger entries in the subsidiary’s base currency
- The chart of accounts and the counterparties on the postings
- Departments, classes and locations
What an AI client gets from NetSuite alone today
Oracle’s NetSuite AI Connector Service lets an external AI client work with NetSuite data over MCP, with Oracle’s MCP Standard Tools SuiteApp or tools a customer builds1. The SuiteApp covers records, reports, saved searches and SuiteQL queries, with the same access controls as the NetSuite user interface2.
Some of its tools create and update records, so Oracle suggests a separate role with only the permissions users should have through the AI client3. The service is not a paid feature, the SuiteApp is free, and the client connects to an address built from your NetSuite account ID4.
What Control.dev’s MCP adds above NetSuite
Control.dev reads NetSuite and every other ledger the group runs, then gives the whole group to the same AI client over MCP.
- Every entity on one group chart Each entity’s accounts are mapped to one group chart of accounts, and the eliminations, currency translation and CTA are done before the client reads. The eliminations sit in a column of their own.
- Statements first, not a raw export The client starts from the statements and the group structure, not a raw export of the general ledger. It finds what needs attention there and traces it to the entries.
- Every figure opens to its entries Every actual opens to the transactions behind it, and every row stays connected to its source system and legal entity.
- Your role decides what it sees Over MCP the client gets at most the access your role allows in Control.dev, and a read-only session rejects write tools.
- A plan with a reason on every cell The client can also draft budget values over MCP, and every value it writes carries its reason. The budget version keeps its change history, so a later variance analysis compares the actuals with the assumptions.
- Other MCP servers in the same conversation The client can use its other MCP servers in the same conversation, a CRM for example, and bring that data into a plan or an analysis next to the group’s actuals.
How each AI client connects is on the Control.dev MCP server, every tool it exposes on MCP tools and reusable instructions on finance skills, every integration and what comes in from it on the integrations page, and how the group view is built on multi-entity consolidation.
Already connected Claude to NetSuite yourself? Control.dev vs building it yourself with Claude compares what you build and keep alive, what the client reads, who may change what, and what it costs.
NetSuite MCP in three steps
Our team sets up the integration with you. Most companies have live data in under two hours from the first call, a larger group takes days, the hardest a few weeks, and there is no setup fee.
- 01Create the NetSuite integration A NetSuite administrator creates an integration record with OAuth 2.0 client credentials, a dedicated role for the subsidiary and a certificate mapping. You then enter the account, subsidiary and accounting book IDs in Control.dev. The steps are in the NetSuite integration guide.
- 02Copy the server URL and the client ID into your client In Control.dev, open Data outputs and then MCP Server. Add the server URL and the client ID from the MCP Server page to Claude, ChatGPT or Codex as a remote MCP server, then sign in with your Control.dev login. If the page shows no client ID yet, ask us: registering your client is part of setup.
- 03Ask something you already know One company, one month, one figure. Check it against the same view in Control.dev, then ask the bigger questions.
Questions
How many integrations does a NetSuite group need, and what does it cost?
Each Control.dev entity connects to one NetSuite subsidiary, and one integration is one connected accounting system, such as one entity’s ledger. Control.dev publishes its monthly prices, excluding VAT: EUR 249 for one entity and one integration, EUR 499 for consolidation with three integrations and EUR 999 with five, where a Stripe connection counts as one integration, with no implementation fee, no multi-year contract and a notice period from one month. Larger groups are priced on request: book a demo.
Does Control.dev write to NetSuite?
No. Control.dev sends only read requests to NetSuite, so nothing it does changes NetSuite. Eliminations and group entries stay in Control.dev.
Where does the AI process our data?
Control.dev’s own AI features process data in the EU, and Control.dev’s data is hosted on Google Cloud in Hamina, Finland, encrypted in transit and at rest. What your AI client reads is processed under your agreement with its provider, so where that data goes is your decision.
How fast does a correction in NetSuite reach the group view?
Scheduled syncs run at least daily, and you can trigger a refresh on demand. Backdated entries and corrections are synced again automatically, so the next sync carries a correction into the group view and into what the client reads.
What does Oracle’s NetSuite AI Connector do, and when do you use both?
It gives an AI client tools for the records, reports, saved searches and SuiteQL queries of your NetSuite account, within your NetSuite role2, and some of them create and update records3. Use it for work inside NetSuite. Use Control.dev for the group: entities on NetSuite and on other ledgers on one group chart of accounts, with the eliminations done. One AI client can use both servers in the same conversation.