I connected Claude to a NetSuite demo account with read-only access. The first thing I asked for was a transaction count.
Claude told me the transaction table did not exist.
That answer makes it easy to assume the connector failed. The connector worked exactly as configured. The role I had selected could not see transactions, and the response came back as “record not found.”
Same words. Different problem.
After three permission changes, I ran the same query again. This time, it returned 8,669 transactions. Nothing about the AI tool had changed. I finally understood what I had given it permission to see.
That distinction matters every time you connect an AI tool to NetSuite. Watch our full NetSuite AI Connector video below.
The disagreement was already there
When an AI-generated number does not match a report, the tool may have made a mistake. Start by checking something more common: the tool and the report may be answering different versions of the same question.
One saved search may define open accounts receivable using a particular date, posting period, transaction type, and subsidiary. A new query may use a different combination. Both outputs can be defensible. They still disagree.
In Nuage’s delivery data, 200 of 296 reporting issues resolved around configuration. Someone had made a decision about filters, periods, or definitions, and over time the reason behind that decision disappeared.
The ambiguity was already there. AI made it visible sooner.
For a finance leader, that can be useful. You would rather find two definitions during a controlled test than during a board meeting, audit, or month-end close.
Decide the boundary before you trust the output
Before we test a number, we answer three scope questions. These decisions belong to the business and system owners. A software vendor cannot make them for you.
1) Can the connection write?
This is the first decision because it sets the potential impact of a bad result.
For an initial connection, I want read-only access. I also want evidence. Saying a connection is read-only is different from opening the role’s permission list and confirming that Create, Edit, and Full are absent.
The claim is useful. The permission list is what your auditor will want to see.
2) Whose eyes does it use?
The tool does not arrive with its own view of NetSuite. It reads through the role assigned to the connection.
That role carries its subsidiary scope, department and class restrictions, field-level restrictions, and record permissions. If the role can see something, the connection may be able to see it. If the role cannot see it, the AI may report that the record does not exist.
An administrator role can expose far more than the test requires. Check the selected role’s actual permissions and scope before connecting it.
3) Which records are in scope?
“NetSuite” is not a useful answer.
Name the record types. Transactions may be in scope. Customers may be in scope. Employee records may stay out. The scope also limits what a wrong answer can cover. After a matched test, expand one record type at a time.
Write those decisions on one page: the environment, role name and internal ID, approved record types, write access, subsidiary scope, authentication method, owner, and review date. Give it one business owner and one system owner.
That page turns a conversation into an audit trail.
Run the five-number test
Companies often evaluate AI by asking it a question nobody in the room can answer. If the result looks plausible, they call the test successful.
I use the opposite approach.
Pick five numbers you already know cold. These should be figures you would defend in a board meeting. In the video, I used open A/R, revenue for the last closed month, open sales-order backlog, inventory on hand, and active customer count.
Write down the trusted results first. Then state the definitions behind them. After that, let the AI query NetSuite and place its answers next to yours.
One of my five matched. Several differed because of timing or filters. One was materially different. That gave us three possible outcomes.
1) The numbers match
The definition and query agree. Document the result. If there is a business reason to expand access, widen the scope gradually and test again.
2) The difference comes from timing
Check the as-of date, posting period, open periods, and transaction status. Refine the question and rerun it. You may need to fix the query rather than change NetSuite.
3) The difference is material
Two definitions may be active inside the business, each with real users and a valid history. Assign an owner, choose the approved definition, and document it in the scope record.
That is a finding, not a bug.
One timeline worth planning around
The authentication changes are easier to understand when you separate new integrations from existing ones.
Under Oracle’s current authentication guidance, NetSuite 2027.1 will prevent the creation of new integrations that use token-based authentication, or TBA. Existing TBA integrations can continue until final support ends, which Oracle currently describes as tentatively planned for NetSuite 2028.1.
That makes 2027.1 a design constraint for a new connection, rather than a date when every existing TBA integration suddenly stops.
There is a separate integration deadline to track. Oracle says SOAP web services will no longer be available with NetSuite 2028.2. If an important connection still relies on SOAP, treat that as its own migration conversation.
Two things to do this afternoon
- Inventory the connections you already have. Review integration records, assigned users and roles, authentication methods, and access tokens. You need the actual account state, not a plan someone wrote two years ago.
- Ask each connector vendor one direct question: Which OAuth 2.0 grant type do you support today? If the capability is still on the roadmap, ask for the date.
Then run the Connection Check against numbers your business already trusts. The prompt interviews you about scope, queries the account, compares the output, and produces the one-page record you can keep.
Copy the Connection Check prompt
AI output should not earn trust because it sounds confident. It earns trust when you can explain what the connection saw, which definition it used, who approved the boundary, and how the result reconciles to the business.
Louis Balla
CRO & Partner, Nuage
Speak to a NetSuite expert today
