Skip to content
SeamSetTalk to us

All guides

NetSuite AI prompts for finance: month-end close examples and how to check the numbers

By Arnaud de Turckheim

Last verified against NetSuite 2026.2

In short

  • A NetSuite AI prompt is a plain-language request to Claude or ChatGPT connected through Oracle’s AI Connector Service. It runs with the NetSuite role you chose when connecting: use a read-only one.
  • The report tools ignore accounting periods, so the AI’s P&L for a month can differ from NetSuite’s report by period.
  • Start each chat with the standing instruction below: read only, reports before SuiteQL, filters stated, computed figures labeled.
  • Use the AI freely for exception lists. Tie every total to a NetSuite report; take final statements from NetSuite.
  • Oracle lists about 100 prompt samples (98 table rows, our count) in its Companion SuiteApp, and publishes a read-only-by-default Finance Analyst skill. Neither removes the period limit.

As of NetSuite 2026.2 (September 2026). These prompts are examples: test each one on a read-only role first.

Who this is for

Controllers, accounts payable (AP) and accounts receivable (AR) teams, financial planning and analysis (FP&A) and operations managers using Claude or ChatGPT on NetSuite at month-end.

What you need

  • An AI client connected through the NetSuite AI Connector Service with the MCP Standard Tools SuiteApp (for Claude, Oracle says Pro plan or higher): setup guide.
  • A read-only role on that connection. The AI acts with the role you pick on NetSuite’s consent screen (the Choose Another Role link). Connected with your own Controller role? Then the AI can do whatever that role can, such as approving journals or paying bills. Role recipe.
  • To switch roles, reconnect. In Claude: Customize > Connectors, select NetSuite, Disconnect, connect again and pick the read-only role. If the tool list shows ns_createRecord or ns_updateRecord, the role has REST Web Services and can write wherever its record permissions allow.

Through MCP (Model Context Protocol), Oracle gives the AI 14 standard tools: reports, saved searches, read-only SuiteQL queries (NetSuite’s SQL dialect), and record reads, creates and updates. Oracle: “Don’t use SuiteQL or build new reports for financial reports.” Details: NetSuite MCP Standard Tools explained.

The #1 limit: the AI’s P&L can differ from NetSuite’s

Oracle’s Report Tools page: “Accounting periods are not supported.” Through the report tools, the AI cannot see your periods, ignores the Report by Period preference, and “may use the calendar year as the fiscal year”.

The tools take date ranges. In NetSuite’s reports, a date range selects by transaction date and a period by posting period. A bill dated June 30 but posted to July would count in June for the AI, in July by period. Oracle does not spell this out for the tools.

Oracle’s Finance Analyst skill does not change this: it calls the same report tools, and its period-over-period query filters on transaction date.

Workarounds, most reliable first:

  1. For figures by period, use a saved search on posting period. Create a transaction saved search (Lists > Search > Saved Search > New). On the Criteria subtab, select Accounting Period Fields in the Filter list; in the popup, pick Period Name and set the month.
  2. Shape it like a statement. Keep posting transactions on income statement account types. On the Results subtab, set Account to Summary Type Group and Amount to Sum. Check it once against NetSuite’s Income Statement by period.
  3. Have the AI run it unchanged. ns_runSavedSearch takes a search ID and a row range, no filters, so the AI cannot change the period: keep one search per month, or edit it at each close. Prompt: “Run saved search [ID] with ns_runSavedSearch, unchanged. Return all rows.”
  4. For report runs, give exact dates and your fiscal year start. Before the run, ask your AI client to open the Report Filters MCP App (ns_report_filters_app) to check the dates, subsidiary and book. It has no period filter either, and whether it displays depends on your client.

Standing instruction for every finance chat

Paste this at the start of each chat, or into your client’s project or custom instructions. It builds on Oracle’s best practices (name the report, give dates, ask for links). It guides the model; the role is the control.

Standing instructions for this chat:
- Read only. Never create, update, approve or delete anything.
- Use a standard report or a saved search before SuiteQL. Never build a financial
  statement with SuiteQL.
- Use the exact dates I give (YYYY-MM-DD). Never assume a period or a fiscal year.
- For every figure, state the tool, report or search, dates, subsidiary ID (consolidated
  or not), book and currency.
- Label any figure you computed yourself: sums, differences, percentages, rankings.
- Say if a result may be cut off by a row limit.
- Link every record and report you cite.

The prompts below write dates as YYYY-MM-DD: 07/08/2026 reads as July 8 in the US and 7 August elsewhere.

NetSuite AI prompts for month-end close

Use Examples Rule
Exception lists Pending approvals, duplicate bills, aging outliers, unbilled orders Use freely; open each linked record
Totals and variances Income statement, balance sheet changes, aging totals Use, then tie out to a NetSuite report
Final figures Statements for the CFO or board; any posting Run and export by period from NetSuite; attach the export for commentary

Names in quotes are Oracle’s samples, from its Companion library (next section).

1. Close blockers

List journal entries, vendor bills and expense reports dated 2026-08-01 to 2026-08-31
in [subsidiary] that are still awaiting approval: type, document number (linked), date,
amount, memo, creator. Group by type.

Check period status yourself at Setup > Accounting > Manage G/L > Manage Accounting Periods (locks and the Period Close column). The Finance Analyst skill reads it from the accountingperiod table, which its own files say may not be queryable through the MCP endpoint.

Natively, the Intelligent Close Manager portlet lists close tasks and exceptions by period and subsidiary, linking to open items. Enable it at Setup > Company > Enable Features, Accounting subtab, Advanced Features (OneKloudX demo). Users need the Manage Accounting Periods permission at View or Full.

2. AP: duplicate bills

List vendor bills dated 2026-07-25 to 2026-09-07 in [subsidiary], excluding voided bills,
where one vendor has two or more bills of the same amount within 7 days: document number
(linked), vendor, date, reference number, amount, status.

The extra week on each side catches duplicates across month boundaries. Oracle’s “Vendor Bill Fraud Detection” also flags round amounts and bills just under approval thresholds.

3. AR: aging and unapplied cash

Run the A/R Aging Summary report as of 2026-08-31 for [subsidiary]. List the 10 customers
with the largest balance over 60 days past due, each linked. Then list customer payments
and credit memos not fully applied as of 2026-08-31, with customer and open amount.

For a cash view, add the A/P Aging Summary as of the same date and call it an aging view, not a forecast. Oracle samples: “A/R Analysis - Days to Pay”; “Working Capital Analysis”, whose days-outstanding figures come from SuiteQL and are estimates.

Naming the report is not enough. Asked to “run an AR aging report”, Claude gave a Luxent senior consultant an aging that took her over an hour to correct, foreign-currency amounts included (Luxent, MCP Connector webinar). Check that the tool call is ns_runReport on the A/R Aging Summary, then tie out.

4. Cut-off and accruals

List sales orders dated on or before 2026-08-31 with a status of Pending Billing (document
number linked, customer, date, amount), largest first. Then list purchase order lines
received on or before 2026-08-31 and not yet billed (vendor, order linked, item, amount).

5. Balance sheet changes

Run the Balance Sheet for [subsidiary], consolidated, as of 2026-08-31, then as of
2026-07-31, as two report runs. By account, show both balances and the change, largest
change first.

6. Income statement against last year

Adapted from Oracle’s “Period-over-period Comparison” sample:

Run the Income Statement for [subsidiary], consolidated, for 2026-08-01 to 2026-08-31,
then for 2025-08-01 to 2025-08-31. Show each run's parameters first. Then revenue, gross
profit, operating expenses and net income side by side, with the change. Last line: net
income per run, for my tie-out.

These are date-range runs: compare them with NetSuite’s reports by period before using the change. Where an Oracle sample says “[current period]”, put dates.

Ask for both runs. In the same webinar, asked to “review my income statement for this year compared to last year”, Claude did not find NetSuite’s Comparative Income Statement report and wrote its own code instead of running a report (watch).

Oracle’s prompt library: the Companion SuiteApp

Read a sample before running it: “Create Journal Entry”, “Monitor & Approve Journal Entries”, “Monitor and Approve Bills” and “Pay Bill(s) via ACH” create or approve records. A sample also fails if your role lacks the tools or data it uses.

The NetSuite AI Connector Service Companion is a managed SuiteApp of prompt samples for MCP Standard Tools. Ask your administrator to install it from the SuiteApps tab (search NetSuite AI Connector Service Companion, then Install).

  • Where: Setup > AI Companion Tools > AI Companion Library, searchable by category, role and industry. Copy, Use Prompt (opens it in a supported AI client) or Customize a sample.
  • Roles: optional AI Companion Controller and AI Companion View Only (read-only). Check their permissions before assigning them.
  • Size: 98 samples in the Help Center’s tables (our count; 97 distinct titles), 37 of them Financial; Oracle’s March 2026 announcement says “more than 100”. 23 languages.

In the chat, ask your client to open the Prompt Library MCP App (ns_prompt_library_app) to pick a sample.

Oracle’s Finance Analyst and AI Companion plug-ins

Oracle publishes two business skills on GitHub under an open license, also packaged as plug-ins:

  • NetSuite Finance Analyst (netsuite-finance-analyst): statements, variance, aging, close, reconciliation, cash and board narratives.
  • NetSuite AI Companion (netsuite-ai-companion): the netsuite-ai-connector-instructions skill, which sets a tool order (reports, saved searches, then SuiteQL) and SuiteQL rules, including a 1,000-row cap on every query.

The Finance Analyst skill, per its files:

  • Read-only by default. It writes only when you ask and confirm the record, period, subsidiary and accounting impact. Journal entries, reclasses and accruals are “high-risk actions”.
  • Onboarding. A 10- to 15-minute conversation runs 11 probes, shows a Profile Card you validate, and re-runs after 90 days. Check the fiscal year on the card: without the period table, the skill infers it from transaction volume.
  • Materiality. Defaults of 5% or $50,000 (financial statements) and 3% or $25,000 (operating), for about $10 million to $100 million in revenue; onboarding adjusts them. In an audit or SOX context it defers to your auditor’s thresholds: give them.

Install. Both need the AI Connector. In Claude chat and Cowork, install the NetSuite Finance Analyst plug-in, or upload netsuite-finance-analyst.zip from the GitHub release “SuiteCloud Agent Skills 1.0” as a skill (code execution must be on). ChatGPT takes the same ZIP as a skill. Steps for each client, Claude Code and Codex included: install Oracle’s plug-ins and skills.

Seen in practice: finance prompts in partner demos

Runs by NetSuite partners and consultants, on demo accounts; each link opens at that moment.

Demo Asked What came back Checked on screen
JR Tallman, Companion SuiteApp Oracle’s “Current Period Financial Overview”, “current period” replaced by January to December 2025 The standard Income Statement on subsidiary ID -1 (consolidated) Yes: net income matched NetSuite’s Income Statement for the same dates
Sarah Muha (RSM), fraud detection Oracle’s “Vendor Bill Fraud Detection”, sent from the Companion library Questions on subsidiaries and period, then almost 20% of bills flagged (duplicate payments, round numbers, timing) No. Open each flagged bill
Rand Group, MCP webinar “How much is intercompany versus trade payables?” A split no saved search provided: 99.6% trade No. Tie the total to the A/P Aging Summary
DataAnts, setup and demo “Top invoices for the last six months” Sales orders The presenter noticed. Name the transaction type
Annexa, Claude demo An expense dashboard “across these different periods” Spending flagged as unusual against “actual market data” (the presenter’s words) No. Market data does not come from NetSuite: ask Claude for its source
JR Tallman, Companion SuiteApp Oracle’s “Create Journal Entry”, subsidiary “parent company consolidated” The entry posted to the parent company; Claude said so afterward Yes, in NetSuite. But the role could post, and Claude changed the subsidiary without asking (What never to do)

Wrong answers looked as finished as right ones: check the record type and the source of each figure.

Checking the numbers

Tie out to a standard report

  1. Read the tool call itself. Oracle’s best practices say to check the tool requests and responses, because models “may sometimes make up information”. Open the tool call and note reportId, dateFrom, dateTo, subsidiaryId and book. A figure with no tool call behind it is not data.
  2. Check subsidiaryId. Oracle: negative IDs are consolidated or context subsidiaries, positive IDs single ones. A positive ID on a “consolidated” request means one subsidiary only. Currency follows the subsidiary.
  3. Run the same report in NetSuite with those filters. If the AI used ns_runReport, totals should match; if it used SuiteQL or added up rows, expect gaps. Recompute every figure the AI labeled as its own.
  4. Run the report by period. The remaining gap is date versus posting period: list it with your posting-period saved search, or with the query below.
-- Illustrative, not tested. August 2026: change the three dates for another month.
-- Posted lines dated outside their posting period, on either side of the month.
SELECT t.tranid,
       BUILTIN.DF(t.type) AS type,
       t.trandate,
       BUILTIN.DF(t.postingperiod) AS posting_period,
       BUILTIN.DF(tal.account) AS account,
       tal.amount
FROM transaction t
JOIN transactionaccountingline tal ON tal.transaction = t.id
JOIN accountingperiod ap ON ap.id = t.postingperiod
WHERE t.posting = 'T'
  AND (t.trandate < ap.startdate OR t.trandate > ap.enddate)
  AND (ap.startdate = TO_DATE('08/01/2026', 'MM/DD/YYYY')
       OR t.trandate BETWEEN TO_DATE('08/01/2026', 'MM/DD/YYYY')
                         AND TO_DATE('08/31/2026', 'MM/DD/YYYY'))
  AND ROWNUM <= 1000

Paste it into the chat with: “Run this with ns_runCustomSuiteQL, unchanged. If it fails, show me the error.” Compare the amounts account by account with the gap. If exactly 1,000 lines come back, the list is cut: narrow it by account.

Oracle’s Finance Analyst skill says the accountingperiod table may not be queryable through the MCP endpoint (one of its files says it is not), so this query may fail: the saved search is the reliable path.

Field names follow Oracle’s SuiteQL examples, sample MCP tools and Finance Analyst skill. With Multi-Book Accounting, also filter tal.accountingbook on your primary book. Finding field names: Map and document a NetSuite account with AI.

Reuse what ties out. Anchor Group suggests having the AI draft a SuiteQL query, checking what it includes and excludes, then rerunning it unchanged (Sonar webinar). Do this only for lists and checks like the one above: Oracle says not to use SuiteQL for financial reports. The posting-period saved search works the same way.

A five-number test

Run it after connecting, after any change to the AI’s role or model, and before the AI’s first close. It condenses Nuage NetSuite Consultants’ public “Connection Check” prompt. Write down your own definition and figure for each number first.

For revenue, settle more than the date field: which transaction types count, account type or a chosen list of accounts, and custom fields that exclude lines.

The list comes from an analytics vendor pitching his own product in a Nuage session (May 2025, before Oracle’s connector). Asked for total revenue, a generic AI’s formula was “something like sum all the invoices for these transaction dates”, he says.

Read only. Compute these five numbers for [subsidiary] without asking me to clarify:
open AR, revenue for 2026-08-01 to 2026-08-31, open sales order backlog, inventory value
on hand, active customer count. For each, give the figure, the definition you chose (date
field, statuses, entities included) and the exact tool call or query you ran.

Classify each gap as a match, a timing difference (as-of date, posting period, open period) or a material difference (two defensible definitions). Nuage treats material gaps as definitions to settle, not tool defects.

Watch it: Louis Balla (Nuage) runs the test on a demo account, with definitions left vague on purpose (Nuage, validating Claude’s results). Only inventory value matched; Claude counted 116 active customers against his 420. He concludes that two of the three outcome types are “findings about your configuration,” not about the AI (results).

What never to do

  • Never give the AI a role that can post or approve. A read-only role cannot create journal entries. If you deliberately let the AI draft entries, keep Journal Approval off its role: holders can approve their own entries.
  • Never turn on journal approval for the AI alone. Require Approvals on Journal Entries (Setup > Accounting > Accounting Preferences, General subtab) gates every journal entry from every user and integration. Decide it for the whole team. With SuiteFlow approval routing, the workflow decides who approves.
  • Never run approval or payment samples on a role that can approve or pay. “Monitor & Approve Journal Entries” approves through ns_updateRecord; “Pay Bill(s) via ACH” creates payments.
  • Never auto-approve write tools. In Claude: Customize > Connectors, select NetSuite, and under Tool permissions set create and update tools to Needs approval or Blocked. Organization-wide settings and audit: Governing AI access to NetSuite.
  • Never retry a failed create blindly. Oracle advises setting externalId on every created record to prevent duplicates.
  • Never present open-period numbers as final.

Ask Oracle or an external assistant

Ask Oracle is NetSuite’s own assistant, in NetSuite Next (Oracle’s redesigned, AI-centered NetSuite, released in phases) and as a companion in the current interface.

Criterion Ask Oracle Claude or ChatGPT via the AI Connector
Cost Included with the NetSuite license; consumes AI Units (Oracle estimates 10 to 200 per question; 1,000 per General Access user per month, pooled) Connector not a paid feature, no AI Units; you pay your AI plan
Regions United States and Canada first, in phases No regional restriction in Oracle’s docs
Access No role by default; an administrator grants it at Setup > Company > AI > Ask Oracle Access Non-Administrator role with connector permissions
Writes May pause “protected actions” (those that can change data) for your approval Your role, plus your client’s tool approvals
Reports by accounting period Oracle does not say No, per Oracle’s Report Tools page

Oracle ships Ask Oracle’s core skills as read-only skills: you use them as provided and cannot edit them. They run only inside Ask Oracle and, per Oracle, are designed for NetSuite Next. Most analyze data, such as “Period close readiness review”, but “Workflow manipulation” drafts SuiteFlow workflows.

For AR in NetSuite Next: run Narrative Insights on the A/R Aging Summary, paste the insight into a new Ask Oracle chat and ask how to address the key risks (Verde demo). Both steps draw AI Units.

Before acting, check the insight against the report itself, as the presenter advises, and save a copy: Oracle says its content “may differ each time you generate an insight, even when viewing the same data.”

Recommendation: choose by where your team works and by cost, and tie out either way. Claude or ChatGPT also combine NetSuite data with your other tools and skills. Details: Every AI feature in NetSuite 2026.2.

Common problems

Symptom Cause Fix
Total differs from NetSuite’s report for the same dates The AI used SuiteQL or added up rows Ask for the report or a saved search
Month P&L differs from NetSuite’s report by period Report tools ignore accounting periods Posting-period saved search; list the gap
Wrong fiscal year or quarter Calendar year assumed (Oracle) State your fiscal year start and exact dates
“Consolidated” total too low, or other subsidiaries missing Positive subsidiaryId, or a role limited to some subsidiaries (Prolecto demo: a vendor lookup silently limited to the role’s one subsidiary) Check the ID is negative and the role’s Subsidiary Restrictions
Total of a long list too low AI clients “usually support up to ~5,000 rows per call” (Oracle); Oracle’s AI Companion skill caps every SuiteQL query at 1,000 rows, sums included Totals from a report or summary saved search (row limits)
Unexpected currency Reports use the selected subsidiary’s currency Check subsidiaryId
Null values from a custom report Custom segments used for column segmentation Standard report or saved search
Period query fails accountingperiod may not be queryable through MCP Posting-period saved search

More: NetSuite AI Connector (MCP) errors.

FAQ

Why doesn’t the AI’s P&L match NetSuite’s?

Usually because Oracle’s report tools ignore accounting periods: they work from date ranges, which in NetSuite’s reports select by transaction date. Other causes: a calendar fiscal year, another subsidiary, a row limit, or SuiteQL instead of the report. A saved search on posting period is the closest route.

Can I give these numbers to the CFO or the board?

Not as they come. Tie each total to a NetSuite report run by period. For board packs, export the statements from NetSuite and have the AI comment on the export.

Can it run our customized financial reports?

Often. Oracle says the report tools support custom reports and “most of the standard reports”. Custom reports using custom segments for column segmentation may return null values, and custom filters are not supported.

Does it cut month-end close work?

It depends on your data and your checks. At Oracle’s SuiteWorld 2025, Media Manager’s COO said one prompt now aggregates the saved searches and manual checks of their close; they compare its output with those searches and are “still very much in the testing and validation phase” (his claim, NetSuite keynote). On r/Netsuite, one finance team asked for higher usage limits after adding Oracle’s Finance Analyst skill; another user called gross profit answers “wildly inaccurate”. Plan tie-outs into the close calendar.

Does our financial data go to Anthropic or OpenAI?

What the AI reads goes to the model provider, and Oracle’s FAQ says it then follows that provider’s privacy policy. Anthropic’s commercial plans and OpenAI’s business plans do not train on your data by default; on Claude’s consumer plans, Pro included, each user chooses. Details: Governing AI access to NetSuite.

Sources

Oracle Help Center

Oracle, other

Third party