Early bird Book a demo

Guides

How to build a NetSuite board pack in Claude

There are two ways to get from a NetSuite close to a board pack in Claude. You can connect Claude straight to NetSuite, or add a finance layer in between. Here is how each works, where the direct route stops, and a checklist before the board sees it.

By Wouter Born, founder of finstory · Updated 25 September 2026

The short answer

Oracle’s free NetSuite AI Connector Service connects Claude straight to NetSuite. It is quick to set up and good for questions about your numbers. A board pack needs more than that:

  • governed reports;
  • the budget and forecast next to the actuals;
  • a story format that holds from month to month;
  • a way to publish to the board.

You can build that part yourself around the direct connection, or use a finance layer such as finstory between NetSuite and Claude.

Route 1: connect Claude straight to NetSuite

Oracle’s steps, in short:

  1. Prepare NetSuite. Enable Server SuiteScript and REST Web Services, and install Oracle’s standard tools SuiteApp for the AI Connector Service.
  2. Choose the role Claude will use. Give it permission to connect, to use OAuth 2.0 access tokens and to read the File Cabinet. Administrator roles can’t be used, so pick a finance role that sees what the board pack needs, and no more.
  3. Add the connector in Claude. Oracle’s NetSuite connector is listed in Claude’s connector directory. Sign in with the role from step 2.
  4. Add Oracle’s finance instructions (optional). Oracle also publishes a “NetSuite Finance Analyst” plugin for Claude. It is a set of instructions for finance analysis, including a fixed outline for board narratives, with no data or reports of its own.
  5. Ask. For example: “Run last month’s income statement, compare it with the same month last year and draft two paragraphs of commentary.”

Claude can then list and run your NetSuite reports, read saved searches and records, and query data with read-only SuiteQL.

Where the direct route stops for a board pack

The connection is real and useful. For a pack that goes to a board every month, these are the gaps to plan for. Most come from Oracle’s own documentation.

  • Periods. Report filters cover dates and subsidiaries, not accounting periods. An entry dated in one month but posted to another lands in the wrong month, so the numbers can disagree with the close you signed off.
  • Volume. AI clients typically handle about 5,000 rows per call, and token limits and timeouts apply. A full pack becomes many calls that Claude has to stitch together.
  • Budget and forecast. If yours sit in NetSuite, Claude sees them only through the reports and queries you point it to. If they sit in a planning tool or a spreadsheet, it can’t see them at all.
  • Checked numbers. There is no governed report layer in between, so Claude assembles and calculates the figures again for every answer. Oracle lists hallucination among the risks it can’t rule out, so every figure needs checking against the ledger before the pack goes out.
  • Memory and output. Each month starts from zero: Claude doesn’t know how last month’s story went. The result is a chat reply, not a pack you can share with named people, export or update when the numbers change.

Route 2: add a finance layer between NetSuite and Claude

This is what finstory does. It sits between NetSuite and Claude.

  1. Connect your close. NetSuite connects directly: actuals, budgets and forecasts land in one governed model. A budget or forecast kept in a spreadsheet can be loaded next to them, just by asking.
  2. Set up your first reports. In a 60 to 90 minute onboarding call, we connect NetSuite and set up your first reports on your own account structure.
  3. Ask in Claude. Ask “How did May go?” and get the finding in a minute. Every figure comes from those reports and is quoted, never recalculated.
  4. Ask for the board story. Claude drafts it page by page, with a headline, the commentary and the right chart for each part of the pack. It works from your company memory, so it doesn’t start from zero every month.
  5. Add the why. When a number moves and the ledger can’t say why, Claude asks you. Your one-line answer is pinned to the figure it explains.
  6. Publish. Share a secure link with named people, or export to PowerPoint, and see which pages your board actually read.

Most teams are live within two to three business days of the onboarding call.

A checklist before the board sees it

  • Every figure on every page ties back to a report on the ledger, for the right period and entity.
  • Budget and forecast are the versions the board approved, not an older copy.
  • Each headline says what happened and why, in one sentence.
  • Every “why” comes from a person or from the data, never from a guess.
  • Last month’s open questions are answered or carried forward.
  • You know who can see the story, and the link expires when it should.

Sources

Checked on 25 September 2026.

Questions CFOs ask

Which Claude plan do I need?

finstory works on Claude Pro, Max, Team or Enterprise. On Team and Enterprise, an Owner adds finstory as a custom connector once, and each person then connects to it with their own login.

Can Claude read NetSuite without anything in between?

Yes. Oracle's NetSuite AI Connector Service is free. It lets Claude run your NetSuite reports and saved searches, read records and query data read-only. It uses a NetSuite role you choose, and administrator roles can't be used.

Can the board pack show budget against actual?

Only if Claude can read the budget. Some companies keep budgets in NetSuite, but many keep them in a planning tool or a spreadsheet. finstory keeps actuals, budgets and forecasts in one governed model, from NetSuite or from a spreadsheet, so every page can compare them.

Wouter Born founded finstory after more than 20 years in finance software.