FrontierERP
Sign inTalk to Frontier
Applied guide

Why a saved search won't match NetSuite's P&L

Five documented reasons a saved search, SuiteQL or AI-built P&L differs from NetSuite's income statement, reconciled to zero on one constructed group.

Frontier · November 9, 2026

An applied guide for the controller or FP&A lead who has to make the pull tie.

The short answer. NetSuite's income statement selects lines by posting period, counts posting lines only, translates child subsidiaries at consolidated rates, includes the elimination subsidiary on a consolidated node, and reads one accounting book. A saved search, SuiteQL query or AI-built pull that differs on any of the five returns a different number. The rest of this page shows each rule, in Oracle's words, on a constructed group that reconciles to zero.

The pull looks right. It is a saved search, a SuiteQL query or a P&L that an AI assistant built from your NetSuite account, and it is a few thousand off the income statement the system prints for the same month. Nobody can say which one is wrong, so for now nobody trusts either.

This is the question behind a recent r/Netsuite thread on connecting an AI assistant directly to NetSuite for financial statements: the objections that drew the most agreement were that the tools take dates and subsidiaries rather than accounting periods, and that nothing they produced could be tied out to a NetSuite report. At SuiteWorld in October, Oracle NetSuite introduced more than 45 SuiteSkills, including skills for financial analysis and close that help review reconciliation differences, and said more than 13,000 customers had adopted its AI Connector Service. More pulls are coming from more tools. The tie-out is the same for all of them.

The five rules, in Oracle's words.

NetSuite's income statement is a specific query with five rules. Match all five and the usual causes are gone. Miss one and the numbers won't tie.

  • It selects by posting period, not transaction date. Oracle's reporting documentation: "If you filter by date range, report records are selected by transaction date. If you filter by period, report records are selected by posting period" (How can I filter report results by periods or dates). The two differ whenever a transaction's date and posting period disagree, which the Allow Transaction Date Outside of Posting Period preference permits when set to Warn or Allow.
  • It counts posting lines only. "Those transactions that don't impact the general ledger are called non-posting transactions. Some examples of non-posting transactions are purchase orders, sales orders, and return authorizations" (Working with Transactions). A pull over "all transactions in October" includes them.
  • It translates child subsidiaries at consolidated rates. For a consolidated report "NetSuite uses consolidated rates to convert from child subsidiary base currency to parent subsidiary base currency" (Consolidated Exchange Rates on Reports), and the default rate type for every income-statement account is Average, "the weighted average of the currency exchange rates for all transactions posted during the period" (Consolidated Exchange Rate Types). A pull that translates each line at the rate on its own date will not agree.
  • It includes the elimination subsidiary. "When you select a consolidated node, the data returned is a summary of all transactions associated with the node's child subsidiaries, including elimination subsidiaries" (Subsidiary Context for Reports). A pull filtered to the operating subsidiaries leaves the eliminations out.
  • It reads one accounting book. On a Multi-Book account the report carries an Accounting Book filter, and "the accounting book you select in the filter becomes the default book the next time you run the report" (Reports, KPIs, and Saved Searches in Multi-Book Accounting). Saved searches default to the primary book; a query written directly against the accounting lines reads every book unless it names one, because transactions are book-generic records "created and shared across all accounting books" (Book-Generic and Book-Specific Records).

None of this is a defect. Each rule is the right behaviour for a financial statement. The problem is only that a pull built outside the report has to reproduce all five on purpose.

A group that foots.

The clearest way to see the five is a group small enough to hold in one table, built so that each rule is broken exactly once. Every amount and rate below is constructed for the example and labelled as such; nothing comes from a live account. The figures are generated and re-footed by a script committed beside this page, so the reconciliation is arithmetic, not assertion.

Harbor Inc. is a US parent reporting in US dollars. Harbor GmbH is its German subsidiary, books in euros. Harbor Elimination is the elimination subsidiary. The primary book is US GAAP; an IFRS adjustment-only book sits beside it. The period is October 2026, and the report to match is the Income Statement for Harbor Inc. (Consolidated), period Oct 2026, accounting book Primary.

Subsidiary Line Amount Posts to Oct 2026, primary book?
Harbor Inc. (USD) Customer invoices USD 120,000 yes
Harbor Inc. (USD) Vendor bills USD 70,000 yes
Harbor Inc. (USD) Vendor bill dated 30 Oct, posting period Nov 2026 USD 8,000 no — Nov
Harbor Inc. (USD) Sales order dated 28 Oct USD 15,000 no — non-posting
Harbor Inc. (USD) Intercompany fee invoice to Harbor GmbH, 31 Oct at 1.1000 EUR 10,000 = USD 11,000 yes; eliminated
Harbor GmbH (EUR) Customer invoices, 7 Oct (EUR→USD 1.0800) and 21 Oct (1.1200) EUR 30,000 + 20,000 yes
Harbor GmbH (EUR) Vendor bills, 14 Oct (1.0900) EUR 24,000 yes
Harbor GmbH (EUR) Intercompany fee bill from Harbor Inc., 31 Oct (1.1000) EUR 10,000 yes; eliminated
Harbor Elimination (USD) Elimination journal: Dr fee income, Cr fee expense USD 11,000 yes
Harbor Inc., IFRS book Book-specific journal: Dr depreciation expense, Cr accumulated depreciation USD 5,000 no — secondary book
Average consolidated rate EUR→USD, Oct 2026 1.1000

Constructed figures; rates are illustrative. The example's average rate is set by hand on the Consolidated Exchange Rates page rather than calculated: Oracle lets you edit direct rates "for periods that aren't closed" (Editing Consolidated Exchange Rates). Calculated from these four euro lines by Oracle's amount-weighted method it would be about 1.0948, and the fee would then leave a small elimination residual; 1.1000 keeps each break to one line.

The naive pull is the one most people write first: every transaction line dated 1 to 31 October, for Harbor Inc. and Harbor GmbH, with euro lines translated at the EUR→USD exchange rate on each transaction's date, and no accounting-book filter. Here is how each rule bites it.

1 · Posting period. The USD 8,000 bill is dated 30 October but was saved with a posting period of November, which the Allow Transaction Date Outside of Posting Period preference permits (General Accounting Preferences: Disallow, Warn or Allow). A date filter catches it; the October income statement does not. The pull overstates expenses by 8,000.

2 · Non-posting lines. The USD 15,000 sales order has a date, an amount and an income account on its line, and no general-ledger impact. The pull counts it as revenue. The income statement never sees it.

3 · Rate. Harbor GmbH's EUR 50,000 of revenue is worth USD 54,800 at the rates on the invoice dates and USD 55,000 at the period's average consolidated rate; its EUR 24,000 of bills are USD 26,160 one way and USD 26,400 the other. The fee bill happens to carry the same rate as the average, so it moves nothing. The net effect on this group is USD 40, small by construction, but Oracle's own note on the mechanism is the one to keep in mind: a search translated at a consolidated rate "may not match the general ledger impact of these same transactions", because the ledger "is posted using the currency exchange rate at the time of the transaction" (Consolidated Exchange Rates on Reports). In a saved search, the rate is the Consolidated Exchange Rate field on the Results subtab: Average, Current, Historical, Per-Account (the default, which uses each account's own rate type) or None, which "uses the transaction subsidiary's base currency. No consolidation occurs" (Consolidated Exchange Rate Types for Transaction Searches).

4 · The elimination subsidiary. Harbor Inc. charges Harbor GmbH a EUR 10,000 management fee. In the parent it is USD 11,000 of intercompany income; in the subsidiary, translated at the average rate, USD 11,000 of intercompany expense; in Harbor Elimination, after Eliminate Intercompany Transactions has run, a journal that reverses both. The two sides agree only because the average rate was set to the fee's own rate; see the caption above. The pull was filtered to the two operating subsidiaries, so it carries USD 11,000 of revenue and USD 11,000 of expense the consolidated report does not. Net income is unaffected. Revenue is wrong by 11,000, and revenue is usually the line someone is looking at. When the two sides of an intercompany pair translate at rates that do not agree, the elimination leaves a residual as well; NetSuite intercompany eliminations: what breaks works through that case.

5 · The accounting book. At period end the controller posts one book-specific journal, USD 5,000 of additional depreciation, to the IFRS book (fixed-asset depreciation is one of the processes Oracle lists as book-specific). Oracle's design for an adjustment-only book is that day-to-day transactions post "only to the base book" and book-specific journal entries go to the adjustment-only book at period end, with results "calculated at the report level by combining data from both" (Adjustment-Only Books Overview). A pull over the accounting lines with no book filter reads both books at once and lands the IFRS adjustment in a US GAAP P&L. With a full secondary book rather than an adjustment-only one, the same mistake is larger: every book-generic posting is "created and shared across all accounting books" (Book-Generic and Book-Specific Records), so an unconstrained query counts each of them once per book.

Put the five together and the reconciliation closes.

Revenue Expenses Net income
The naive pull 200,800 120,160 80,640
1 · Posting period: a bill dated 30 Oct, posted to Nov — (8,000) 8,000
2 · Non-posting: a sales-order line (15,000) — (15,000)
3 · Rate: EUR lines at the average consolidated rate, not the transaction-date rate 200 240 (40)
4 · Elimination subsidiary: the intercompany fee, both sides (11,000) (11,000) —
5 · Accounting book: the IFRS adjustment-only journal — (5,000) 5,000
Reconciled 175,000 96,400 78,600
NetSuite, Harbor Inc. (Consolidated), Oct 2026, primary book 175,000 96,400 78,600
Difference 0 0 0

USD. Constructed figures; generated and re-footed by the packet script.

Two things in that table are worth a second look. The net income gap, USD 2,040, is small enough to be waved through as "timing", and it is made of five errors that partly cancel. And the largest single error, the elimination, does not show in net income at all; it shows in revenue and in expenses, which is where a board pack reads.

Check before you trust the number.

Five rows, one per rule. Each names the setting or field that decides it. Run them against the pull before you reconcile anything.

  1. Period. Is the filter on posting period, or on transaction date? For a report, the Report by Period preference (Home > Set Preferences > Reporting/Search) has three values: All Reports, Financials Only and Never (Oracle). For a search or query, look for a posting-period field, not a date range. And check Allow Transaction Date Outside of Posting Period under Setup > Accounting > Accounting Preferences: on Warn or Allow, the two can differ.
  2. Posting. Does the pull restrict itself to posting transactions? If sales orders, purchase orders or return authorizations can appear, it does not.
  3. Rate. On a saved search, read the Consolidated Exchange Rate field on the Results subtab; Per-Account matches the report's translation for income-statement accounts, None does not consolidate at all. On a query, ask which rate table it joined and on what date.
  4. Subsidiary. Is the context the consolidated node, or a list of operating subsidiaries? Only the node includes the elimination subsidiary.
  5. Book. Which Accounting Book did the report last run in, since the selection sticks to the next run? A saved search reads the primary book by default; a query against the accounting lines reads every book unless told otherwise.

A pull that passes all five and still differs has a sixth cause, and that one is worth a ticket. A pull that fails one of them has its answer.

What this means for an AI-built P&L.

The same five rules apply to a P&L that an assistant builds from your account, whatever the tool. The difference is how easily you can check them. Frontier's income statement is one of nine standard statements: it takes a fiscal year start, a period end date, optionally a subsidiary and an accounting book, and returns the query and the rows beside the number. Left without a subsidiary, it is consolidated. Rule 1 applies to it as to any other pull: read the period filter off the attached query. It defaults to the primary book, book 1, because an unconstrained query over the accounting lines "counts every posting once per book". The nine were validated against a real NetSuite instance before they shipped; a question outside them is answered with a generated query, which has not been, and the docs say to read it before relying on the figure.

That is the point of the attached query. The five checks above are a reading exercise, and a pull that shows its own query lets you do them in a minute rather than reverse-engineer them from the total.

On access: Frontier reads your NetSuite through one integration role that you create and can revoke at any time: web-services only, view-level record permissions. Every answer carries the query and the rows behind it, so your team can check any figure against the ledger.

One next step: take the pull you have, the income statement for the same period and subsidiary context, and walk the five rows above in order. Write down which rule each difference belongs to. The list you end up with is the reconciliation, and it is usually shorter than it looked.

Sources and limits.

Every figure in this guide is constructed to show the mechanism; none comes from a customer account, and no query here has been run against a live NetSuite instance. Statements about NetSuite's behaviour are quoted from Oracle's documentation, linked where they appear: period and date filtering, General Accounting Preferences, posting and non-posting transactions, consolidated exchange rate types for searches, consolidated exchange rate types, consolidated exchange rates on reports, subsidiary context for reports, reports and saved searches in Multi-Book Accounting, adjustment-only books, editing consolidated exchange rates, Accounting Preferences and book-generic and book-specific records. The forum thread is paraphrased, not quoted. Your account's preferences, rate types and books decide which of the five apply to you; the checklist is how to find out.

The balance sheet adds three equity lines that NetSuite computes and, by default, doesn't post, so no sum of balance-sheet postings reaches them: Why a saved search won't match the balance sheet reconciles the same Harbor group at 31 October. Net income is also the first line of NetSuite's cash flow statement: Why the cash flow won't tie to the balance sheet starts from this October's 78,600 and foots it to the change in Bank.

Questions this raises

Why doesn't my NetSuite saved search match the income statement?
Because the income statement selects lines by posting period, counts posting lines only, translates child subsidiaries at consolidated rates, includes the elimination subsidiary when run on a consolidated node, and reads one accounting book. A saved search, SuiteQL query or AI-built pull that differs on any of those five returns a different number. Oracle documents each behaviour; the page reconciles all five on one constructed group.
Should a NetSuite saved search filter on transaction date or posting period?
On posting period, if it is meant to match a financial report. Oracle's documentation says that when a report is filtered by date range its records are selected by transaction date, and when it is filtered by period they are selected by posting period. A transaction can carry a date in one period and a posting period in the next when the Allow Transaction Date Outside of Posting Period preference is set to Warn or Allow.
Which consolidated exchange rate does a saved search use?
Whichever is set in the Consolidated Exchange Rate field on the search's Results subtab: Average, Current, Historical, Per-Account or None. Per-Account is the default and uses each account's own rate type, which for income-statement accounts is Average by default, the same rate the consolidated income statement uses. Oracle notes that a search translated at a consolidated rate may not match the general ledger impact, which is posted at the transaction's own exchange rate.
Does a saved search read every accounting book?
No. Oracle's documentation says that by default all saved searches search the primary book, and that a Multi-Book Accounting Transaction search type exists for searching across books. A query written directly against the accounting lines has no such default and must name a book, or it counts every posting once per book.

← All notes

Push the Frontier

Work alongside our team to establish your first operational capabilities, built around the problems that matter most to your business.

Explore the platformTalk to Frontier
FrontierERP

Set a new standard for how businesses operate.

Platform
Solutions
Resources
Company
© 2026 Frontier ERP, Inc.PrivacyTerms