NetSuite reporting guide

NetSuite Reporting and Saved Searches

How to turn NetSuite records into answers: when to use a report, when to use a saved search, and how to build both so they stay fast, accurate and easy to share.

NetSuite holds the operational data that finance, sales, inventory and support teams depend on every day. Getting value from that data usually comes down to two tools that look similar but solve different problems: reports and saved searches. This guide to NetSuite Reporting and Saved Searches explains how they work, how to build them well, and how to choose between them.

Why reporting matters in NetSuite

NetSuite is a shared system of record. A sales order, a journal entry, a purchase order and a support case all live in the same database, which means a single well built search or report can answer questions that would otherwise take hours of manual work. The challenge is not a lack of data. The challenge is asking for the right slice of it, in the right shape, at the right time.

Different teams need different views of the same records. Finance needs totals and audit friendly detail. Sales needs pipeline and quota visibility. Operations needs stock levels and fulfilment status. A reporting approach that works for one team may be far too heavy, or far too shallow, for another. Reports and saved searches let each team shape the data without changing the underlying records.

Reports and saved searches: two tools, one data model

A report is a presentation layer. It arranges data into a structured output such as a profit and loss statement, an aged receivables summary or a sales by customer breakdown. Reports are designed to be read, printed and compared over time.

A saved search is a stored query. It finds records that match conditions you define, shows the columns you choose, and can be reused, filtered, exported, scheduled or displayed on a dashboard. Saved searches are designed to be live and flexible.

Both draw on the same records. You can often build a report that mirrors a saved search, and you can use saved searches to feed dashboards and exports that reports do not cover. The practical question is not which tool is better. It is which tool matches the job in front of you.

What a saved search actually is

A saved search is a reusable definition with four moving parts:

A saved search is not a snapshot. It runs against current data each time it is opened, which makes it ideal for operational lists that need to stay current. When you need a fixed point in time, export the results or schedule a copy to be sent to a recipient.

Quick rule: if the question starts with "which records" or "show me everything where", a saved search is usually the faster place to start. If the question starts with "how much" or "compare this period with last period", a report or a workbook is often the better fit.

Building a saved search step by step

Menu paths vary by role and edition, but the flow is consistent. Most saved searches can be created from the search menu for the record type, or from a list view where you apply filters and then choose to save the search.

  1. Choose the record type. Start from the record that holds the answer. If you need transaction lines, search transactions. If you need one row per customer, search customers.
  2. Set criteria. Add the conditions that narrow the list. Start broad, confirm the record count, then tighten the filters until the results match the question.
  3. Pick results columns. Add only the fields the audience needs. Fewer columns are easier to read and faster to run.
  4. Add grouping and summaries. Use group and summary options when you need totals, counts or averages rather than individual rows.
  5. Set the audience. Decide whether the search is private or shared, and which roles or departments should see it.
  6. Save and, if needed, schedule. Give it a clear name, then use the email options to send it on a schedule when the audience should receive it automatically.

Criteria: deciding what the search returns

Criteria are where most saved searches succeed or fail. A search with no criteria returns everything, which is slow and rarely useful. A search with criteria that are too tight hides records that should have appeared.

Simple filters cover most needs: status, date range, subsidiary, location, customer or item. When the logic becomes more complex, expression based criteria let you combine conditions with AND and OR logic in a single line. Expressions are powerful, but they are also harder to read later, so name the search clearly and keep a short note about what the logic is meant to do.

Date filters deserve special attention. Relative dates such as this month, last month or this fiscal quarter keep a search useful over time. Hard coded dates are appropriate for a one time review, but they quietly turn a reusable search into a stale one.

Results: deciding what the search shows

The results tab controls what the audience actually sees. A few habits make results much easier to use:

Sharing and scheduling saved searches

A saved search becomes far more valuable when it is shared in the right way. The audience settings control who can open the search, while permissions control who can edit or publish it. Agree on a naming convention early so that shared searches remain discoverable as the number of searches grows.

Saved searches can also be delivered rather than opened. Scheduling sends the results to named recipients on a cadence you choose, which is useful for daily operational lists and weekly management summaries. The same search can usually be exported to a spreadsheet for further analysis or handed to a script for automation.

Common reuse patterns include:

Saved search or report? A practical comparison

Choosing between a saved search and a report
NeedSaved searchReport or workbook
Show a live list of records that match conditionsStrong fitPossible, but less flexible
Produce a formatted financial statementNot the right toolStrong fit
Export rows for spreadsheet analysisStrong fitSometimes available
Compare periods with totals and subtotalsPossible with summariesStrong fit
Email a recurring list to a teamStrong fitAvailable for some reports
Build charts, pivots and key indicatorsLimitedStrong fit in a workbook
Drive a mass update or a scriptStrong fitNot the right tool

In practice, many teams use both. A saved search identifies the records and keeps the detail current, while a report or workbook turns that detail into a view that managers can read at a glance.

SuiteAnalytics Workbook and modern reporting

NetSuite also provides a workbook style analysis tool that works from datasets rather than from a single record type. Workbooks are well suited to exploration: you can pivot data, build charts, define key indicators and compare segments without rebuilding each view from scratch.

Think of the workbook as the place for analysis and presentation, and the saved search as the place for precise record selection and delivery. When a workbook needs a specific population of records, a saved search can often define that population more clearly than a set of ad hoc filters.

Performance and governance

Saved searches are easy to create, which is exactly why they can get out of hand. A large library of overlapping searches slows everyone down and makes the right answer harder to find. A little discipline goes a long way:

Common mistakes to avoid

Conclusion

NetSuite reporting works best when reports and saved searches are treated as complements rather than competitors. Saved searches answer the operational question: which records match, and what should we do with them. Reports and workbooks answer the management question: what does the shape of the business look like, and how is it changing.

Start with the question, choose the tool that matches it, and build once so the answer can be reused. A small number of well named, well scoped searches and reports will almost always outperform a large collection of overlapping ones, and it will make the next question much easier to answer.

Teams that want a broader learning path can explore net-suite-training for additional NetSuite guidance.

Further reading