Skip to main content

ERP Access

Get Started
NetSuite · Claude

Claude for NetSuite, done safely

Oracle now publishes a NetSuite connector for Claude, so connecting the two is the easy part. The harder parts are doing it safely, knowing what your account actually uses, and pointing Claude at the work your custom scripts and spreadsheets do today. That’s where we come in.

Talk to usNetSuite services
1 · Connect

Connect Claude to NetSuite, safely

Oracle’s connector can read records, run saved searches and SuiteQL, and also create and update records. That last part is why setup matters.

  • A dedicated role for Claude with only the permissions the pilot needs, never an administrator role.
  • Sandbox first, then production for a small group, expanding role by role.
  • Read-only to start. We switch on record changes only for a tested workflow, with a person approving each change.
  • Integration capacity checked. NetSuite shares one web-services concurrency limit across all your integrations, so heavy AI queries and extracts are scheduled so they don’t starve your existing feeds.
  • Health data kept out. Oracle states the connector hasn’t been assessed for HIPAA, so protected health information stays in the upstream systems that are built for it.
  • Release-ready. Roles and connector behavior are re-tested in sandbox before each NetSuite release reaches production.
2 · Assess

Know what your account actually uses

Before a renewal, a rebuild or an AI rollout, we find out what earns the subscription. Read-only throughout, with every action in your account logged.

  • Configuration census: roles, scripts, workflows, custom records and fields, integrations and enabled features.
  • Transaction archaeology with SuiteQL: which transaction types are alive, how volume trends, and which are created by people versus integrations.
  • Saved searches and reports: which still run. We report “no recorded UI execution,” never “unused,” because NetSuite doesn’t stamp searches that scripts or integrations run.
  • Seats and roles: paid seats compared with the people who actually log in, from the login audit trail.
  • A verdict for every area (keep, simplify or drop) with the evidence attached, and an independent review pass before anything reaches your renewal conversation.
3 · Rebuild

Move the custom layer into Claude, keep NetSuite as the ledger

Most mature NetSuite accounts carry a layer of custom scripts, workflows and saved searches that need retesting every release. We move that layer into Claude one capability at a time, and prove each step against your own history before anything changes.

Approvals

Readable approval rules

Approval chains become versioned, human-readable policy. Checked by re-running recent vendor bills and comparing the approvers with what NetSuite actually did.

Close

Close assist

Accruals and allocations computed by code and delivered as a journal import file a person posts. Checked by recomputing last quarter’s journals line by line.

Reporting

A report pack

Department income statements, cost reports and reconciliations built from your ledger data, compared against today’s outputs for several periods.

Messages

Drafted, not sent

Remittance and collection messages are drafted for a person to send. Nothing goes out automatically.

Cutover rule: a step goes live only after parallel runs show no unexplained differences. NetSuite stays the system of record, and real-time posting, payroll tax and statutory filings stay in NetSuite.

What we usually find

From years of NetSuite engagements and a structured review of our own project history.

  • A small core earns the subscription: the ledger, payables and receivables with approvals, the audit trail, and inventory where the business needs it.
  • A ring of outside tools handles expenses, payments, planning, tax and reporting, with NetSuite feeding them through saved searches and CSV files.
  • Licensed or configured but never switched on: features that sat idle for years and hardened into “the system can’t do that.”
  • Document templates such as invoices and order acknowledgements are where change requests pile up.
4 · Protect

Your data, your exit plan

  • You own your data. Oracle’s hosting policy gives a 60-day retrieval window after termination before the data is deleted. Plan extraction before the contract decision, not after.
  • The built-in export isn’t the whole account. Oracle’s documentation says the Full CSV Export doesn’t cover all data: transactions arrive only as a report extract, and File Cabinet attachments aren’t included.
  • We map every route: SuiteAnalytics Connect, SuiteQL and REST, saved-search and report exports, File Cabinet downloads, system notes for the audit trail, and SuiteCloud export for customizations.

NetSuite decommissioning and data archiving →

Our method is open source

The teardown protocol behind this work, SaaS Rebuild, is published under the MIT license, including our documented NetSuite extraction recipe. Read it, run it, or have us run it with you.

SaaS Rebuild on GitHub →

Already on NetSuite and curious about Claude?

Start with a read-only usage teardown or a safe connector pilot. Either one stands on its own.

Talk to us