The NetSuite AI Connector can now reach your bank reconciliation data

Finance manager reviewing dashboards and a spreadsheet on screen

The NetSuite AI Connector Service can now reach your bank reconciliation data. Oracle has opened up four banking records, so an assistant like Claude or ChatGPT can look at your statement lines and suggested matches, and even accept or reject a suggestion if the role allows it.

This one arrived without fanfare. It turned up in the NetSuite Help Center update of 19 October 2026 rather than in a SuiteWorld keynote, and it’s worth a look, because it moves a connected assistant from simply reading your data to acting on a financial control.

What changed in the October release

Four banking records are now open to SuiteScript and to SuiteTalk REST web services, and you can reach them through the NetSuite AI Connector Service using the Model Context Protocol:

  • Bank Reconciliation Suggestion, along with its record actions
  • Banking Statement
  • Banking Transaction
  • Transaction Match

Oracle’s own wording is refreshingly short: “These record exposures let users use external AI clients to access bank reconciliation data. The record action exposures let users accept or reject suggestions through those clients.”

One detail is easy to miss. The accept and reject part sits in the SuiteScript entry only, so the REST entry covers reading the data rather than acting on it.

What an assistant can do with it

Say you’re part way through a reconciliation. You can now ask a connected assistant to list the statement lines NetSuite hasn’t matched, explain why it suggested a particular match, or group what’s left by type. If the role allows it, the assistant can then accept or reject a suggestion, using the record action tools in the MCP Standard Tools SuiteApp.

Two things are worth being clear about, though. The matching is still NetSuite’s own, so this isn’t a new AI matching engine, and the suggestions come from the same auto-match rules and enriched bank data as before. And nothing happens on its own. The assistant only acts when somebody asks it to, within the permissions of the role it connects under.

What you need for the NetSuite AI Connector

If you’ve already set the connector up for something else, there’s nothing new here:

  • A non-administrator role. Oracle is firm on this one: “For better access control and security, the NetSuite AI Connector service does not support Administrator roles.” Use a custom role, or an existing role that isn’t an administrator.
  • The right permissions. The role needs MCP Server Connection and Log in using OAuth 2.0 Access Tokens. Record tools also need REST Web Services at Full.
  • The MCP Standard Tools SuiteApp. The record action tools, ns_getRecordActionMetadata and ns_executeRecordAction, come from this SuiteApp, and it’s free. We covered it in our round-up of five new SuiteApps.
  • An acknowledgement about data. Oracle asks you to acknowledge the data sharing before NetSuite connects to an outside model. From that point, anything you send is covered by that provider’s privacy policy rather than Oracle’s terms.

There’s no extra licence cost. Oracle says the connector isn’t a paid feature and the MCP Standard Tools SuiteApp is free, and because the model provider runs the request outside NetSuite, the connector doesn’t use up your NetSuite AI Units. Your AI client may still need a paid plan.

Three other banking changes in the same release

The October release brings three smaller banking changes that your finance team will probably notice sooner:

  • Multi-factor authentication now stops imports. Where a bank asks for MFA, NetSuite sends an email and stops trying to import automatically for that account. A banner on the Match Bank Data page lists the accounts affected. So if a feed stops without warning before month end, that’s the first place to look.
  • A count of what reconciled itself. The Bank Reconciliation Summary portlet now shows how many transactions were reconciled automatically in the last 30 days.
  • Better matching on long memos. Customer and vendor matching copes better with punctuation, alphanumeric text and names buried inside longer memo fields.

What to settle before you switch it on

Bank reconciliation is a control rather than just a task, so it’s worth treating an assistant that can accept matches the way you’d treat a new member of staff doing the same job:

  • Decide who owns the decision. Accepting a match is a judgement call, so name the person who signs off the reconciliation, whatever suggested the match.
  • Check the first month by hand. Compare a sample of accepted matches against the statement before anyone leans on the result.
  • Keep the record action tools back at first. Connect the record tools and saved searches, see how the output looks, and add the ability to accept matches once it has earned a bit of trust.

The wider points apply as they would to any AI connection: a dedicated role, approved tools, a person in charge of anything that changes data, and a look at the logs. Our five guardrails post covers those, and setting up NetSuite MCP walks through the set-up itself.

One thing specific to banking is worth adding. Statement lines can carry customer names and payment references, and those leave NetSuite when they go to an outside model, so it’s worth agreeing your data protection position before you start.

If you’d like a hand building the role, or working out which tools to allow, our AI and intelligent automation team would be glad to help.

Sources

Checked against these sources on 9 November 2026. Oracle says features, timing and availability may change.

Frequently asked questions

Can an AI assistant reconcile a bank account in NetSuite?

Not on its own. A connected assistant can read bank reconciliation data and, where the role allows it, accept or reject a match NetSuite has suggested. The matching is still NetSuite’s own, and a person should still own the reconciliation.

Which banking records can the NetSuite AI Connector reach?

Four of them: Bank Reconciliation Suggestion with its record actions, Banking Statement, Banking Transaction and Transaction Match. They’re available through SuiteScript and SuiteTalk REST web services, and through the connector using the Model Context Protocol.

Does this cost extra or use AI Units?

No. Oracle says the AI Connector Service isn’t a paid feature and the MCP Standard Tools SuiteApp is free. It doesn’t use NetSuite AI Units either, because the model provider runs the request outside NetSuite. Your AI client might need a paid plan, though.

How do you stop an assistant changing bank data?

Give it a role with view permissions only, and leave the record action tools out of the connection. Access always follows the permissions of the role the assistant connects under, and administrator roles aren’t supported at all.

Related reading

Author

  • Joanna England, Marketing & Growth Operations Lead at SuiteGeneration

    Joanna England is Marketing & Growth Operations Lead at Suite Generation and an award-winning tech and business journalist with more than 25 years' experience. A former Editor-in-Chief of Insurtech Insights, Fintech Magazine and Insurtech Digital, she was named one of MPVR's Top 30 Journalists in Fintech & Insurtech in 2023.

Follow us on LinkedIn

New NetSuite field notes, UK pricing guidance and implementation practice, as we publish them.

Follow →
Chapter contents:

Netsuite Playbook

From blueprint to go-live, get the play-by-play in our NetSuite Playbook.

Want to be featured on our blog? Get in touch via email hello@suitegeneration.net