Watch AP and cash application run themselves in NetSuite
Follow a real-looking invoice or customer payment step by step: Claude reads it, checks NetSuite through Oracle’s MCP connector, applies your rules, and prepares the record. Your team still approves every one.
Sample dataEvery document in the journeys belongs to Ridgeline Industrial Supply Co., a fictional distributor.
MCP is a standard, secure plug between Claude and NetSuite
Oracle’s NetSuite AI Connector gives Claude a fixed menu of tools under a login you control. No exports, no middleware, no copy of your data.
Claude
Reads the documents, applies your rules, decides what to look up or create.
MCP connector
Oracle’s free connector. Checks Claude’s login and runs only standard tools.
NetSuite
Your data stays here. Every action runs under Claude’s own role and is logged.
A fixed menu
About 20 standard tools: get a record, run a read-only query, create a record, attach a file.
Its own login
OAuth sign-in to a non-administrator role you define. Claude can only do what that role allows.
Live data
Claude reads current POs and open invoices at the moment it needs them.
Logged
Every call appears in NetSuite’s execution log.
Pick a document and walk it through, one step at a time
Each journey shows the same six steps across four lanes: your team, Claude, the MCP connector and NetSuite. Choose a scenario and click through.
From inbox to approved Vendor Bill
- The invoice arrives
- Claude reads every field and line
- Claude checks open POs and duplicates in NetSuite, read-only
- Claude applies your rules: capitalization, prepaids, location
- Claude creates the bill with the PDF attached
- Your approver approves, as today
From bank file to posted Customer Payment
- The day’s bank files land
- Claude reads remittances, checks and stubs
- Claude finds the customer and its open invoices, read-only
- Claude works out discounts, short pays and overpayments
- Your team approves one batch that ties to the bank
- Claude posts the payments
People approve. Claude prepares.
Least privilege
Claude uses its own NetSuite role, limited to the records each process touches.
Human approval
Bills go through your approval workflow. Cash batches post only after a person approves. Claude can’t pay anyone.
Traceable
Every record carries its source document and a note on how it was matched. Duplicates are blocked before they exist.
Minimal data
Only vendor or customer, amount and coding cross the MCP link.
Claude licensing from about $1,200 a year
For five users covering both processes. The NetSuite AI Connector is free. Sequente’s project fees are quoted separately.
| Option, 5 users | Annual cost | Fits when |
|---|---|---|
| Claude Team | $1,200 – $2,160 | Most AP and AR teams |
| Claude Enterprise | $5,900 – $7,700 | Regulated data that needs a BAA, or more admin control |
| NetSuite AI Connector and MCP tools | $0 | Needed with either plan |
Prices as of October 2026 from claude.com/pricing. Enterprise includes a 20-seat minimum plus usage; usage estimate assumes about 500 invoices a month.
What finance teams ask first
Can Claude approve or pay anything?
No. Claude prepares Vendor Bills in your existing approval workflow and posts cash only after a person approves the batch. Its NetSuite role can’t approve or create payments.
What happens when Claude isn’t sure?
It stops and says why. The item goes on a short exception list with a suggestion; everything else keeps moving. When your team decides, Claude adds the answer to the rules so it doesn’t ask again.
Is our data used to train models?
On Claude’s business plans, Anthropic does not train models on your data by default. NetSuite data stays in NetSuite; Claude reads what it needs through the connector.
We’re in healthcare. Does this work with patient data?
Anthropic offers a BAA on Claude Enterprise, but MCP connector traffic isn’t covered by it, and Oracle hasn’t assessed the NetSuite AI Connector for HIPAA. The design keeps protected details off the records and out of the MCP link.
How long does a project take?
About one week of design and sandbox setup, three to four weeks of build and a parallel run beside your team, then go-live with two weeks of support.
What do you need from us?
Sandbox access, an AP or AR lead, 30 to 50 sample invoices or a few days of bank files, your written rules, and a decision on the Claude plan.
Run it on your own documents
Send 30 to 50 invoices or two or three days of bank files. We run them through the same journey and walk your team through the result.
