NetSuite Saved Searches: Build KPI Dashboards and Custom Reports Step by Step

NetSuite saved searches are the most-used analytical tool in the platform, yet most teams use only a fraction of what they can do. A saved search can filter records, calculate formulas, group results by any field, send scheduled email exports, and feed live data directly into dashboard portlets, all without writing a single line of SQL. For finance teams tracking AR aging, operations managers watching open purchase orders, and NetSuite admins building role-specific dashboards, getting fluent with saved searches removes a significant bottleneck between data and decisions. This guide covers the full workflow: how saved searches differ from native reports and SuiteAnalytics workbooks, how to build one from scratch, the advanced features most users skip, and how to wire results into a NetSuite reporting and dashboards setup your team will actually use.

Saved Searches, Reports, and Workbooks: What Each One Does

NetSuite gives you three analytical layers, and choosing the wrong one costs time. Understanding the boundary between them matters before building anything.

Saved Searches query a single record type (transactions, items, contacts, etc.) and return a flat or summarized result set. They are real-time: they query live data every time they run. They support formula columns using NetSuite’s expression syntax, conditional highlighting, and scheduled email delivery. They can be embedded in dashboard portlets as reminders, KPI tiles, or full data grids. The result is always tabular.

Standard Reports (under Reports in the navigation) use a pre-defined data model with preset columns and groupings. They are slower to customize, but they support multi-level subtotaling and period comparisons that saved searches cannot replicate natively. Financial statements, P&L, balance sheet, trial balance, live here, not in saved searches.

SuiteAnalytics Workbooks are the most capable layer. They support joins across multiple record types, pivot tables, chart visualizations, and ad hoc exploration without saving a permanent query. NetSuite SuiteAnalytics workbooks and queries are the right tool when you need cross-record analysis, for example, correlating sales orders with fulfillment times and customer segments in one view. The trade-off is that workbooks cannot feed dashboard portlets directly and require the SuiteAnalytics permission bundle.

The practical rule: use a saved search when you need a live, embeddable, schedulable result set against one record type. Use a report for financial statements and period-based subtotals. Use a workbook for exploratory multi-record analysis.

How to Build a NetSuite Saved Search: Step by Step

Navigate to Reports > Saved Searches > All Saved Searches > New, then select your record type. The four tabs, Criteria, Results, Sorting, and Email, control everything.

Criteria tab

Criteria filter which records appear. Each filter has three parts: the field, the operator (is, is not, contains, greater than, between, etc.), and the value. For date fields, use dynamic values like “within the last 30 days” or “this fiscal quarter” rather than hard-coded dates so the search stays useful over time. The Filter checkbox on any criterion makes it an interactive filter bar that appears above results: useful for letting end users narrow results without editing the search definition.

Results tab

Results columns define what data appears for each matching record. Every column has a Function dropdown: leave it blank for a raw field value, or choose Sum, Count, Average, Maximum, Minimum, or Group to aggregate. When at least one column uses a summary function, the search returns grouped totals instead of row-level records: this is the switch that turns a flat list into a summary view.

Add a Formula (Text), Formula (Numeric), or Formula (Date) column to calculate values not stored as native fields. Example: a formula column of NVL({amountremaining},0) / DECODE(NVL({amount},0),0,1,{amount}) calculates the outstanding balance as a percentage of invoice total, inline in results.

Highlighting tab

Highlighting applies background colors to rows that meet a condition. For an overdue invoice search, rows where {daysoverdue} > 30 can appear yellow, and rows where {daysoverdue} > 60 appear red. This requires no additional setup from the user viewing the search: the color is baked in.

Email tab

Schedule the search to deliver results as an email attachment (CSV or PDF) on a daily, weekly, or monthly schedule. You can specify recipients by role or by individual user. This is how finance teams get an automatic Monday morning aging report without anyone having to log in and run it manually.

Advanced Saved Search Techniques

Joined searches

Many record types expose joined fields from related records. On a Transaction saved search, you can pull in fields from the associated customer, subsidiary, sales rep, or item record without building a separate search. Look for the join prefix in the field picker, for example, “Customer: Category” or “Item: Cost Accounting”. This extends the reach of a single-record-type search significantly.

Summary types and grouped results

Grouping by two or three fields and summing a numeric column produces a pivot-like table inside a saved search. A common pattern: group by Customer and Month/Year of Close Date, then sum Amount: this gives a monthly revenue-by-customer matrix that can feed a dashboard portlet. The key constraint is that every column must either be a Group column or use a summary function; you cannot mix raw row data with aggregations in the same search.

AND/OR logic in criteria

By default, all criteria are AND conditions. To add OR logic, check the Use Expressions checkbox on the Criteria tab. This reveals a logic expression builder where you can write conditions like (A AND B) OR C using row numbers as variables. This is essential for searches that need to catch records matching any of several states, for example, invoices that are either overdue or on credit hold.

Wiring Saved Searches into KPI Dashboard Portlets

NetSuite dashboards are built from portlets, modular widgets arranged on a role’s home page. Four portlet types consume saved searches directly.

Saved Search portlet

Displays the full result table of a saved search, paginated. Add it via Personalize Dashboard > Add Content > Saved Search. Once placed, click the pencil icon to select which saved search to display. The portlet refreshes its data each time the dashboard loads. This is the right portlet for lists: open POs, unassigned leads, items below reorder point.

KPI Scorecard portlet

Shows a grid of named KPIs, each sourced from a saved search that returns exactly one numeric value. The portlet can show current period vs prior period with a trend arrow. To wire a saved search to a KPI tile, the search must return a single-row, single-column summary result, typically a Count or Sum with no grouping. Build the search first, confirm it returns one value, then create the KPI scorecard portlet and assign the search to a metric row.

Reminder portlet

Shows a count of records matching a saved search, with a drillthrough link to the full list. Reminders are configured at the role level (Setup > Company > Reminders) and appear automatically on the dashboard for all users in that role. A reminder for “Invoices overdue > 30 days” showing a count of 14 in red is more effective than a report buried in a menu.

Key Performance Indicators portlet

Similar to the KPI Scorecard but uses NetSuite’s built-in KPI definitions (revenue, gross profit, open orders, etc.) combined with custom saved-search KPIs. The portlet supports period selectors, so users can switch between this week, this month, and this quarter without editing anything.

Role-Based Dashboard Setup and Publishing

Every NetSuite role has its own default dashboard layout. Admins can configure a dashboard for a role and then publish it to all users in that role, overriding their personal layouts. The process is:

1. Log in as a user with the target role (or use Setup > User Management > Roles to access role settings).
2. Arrange the dashboard portlets, saved search tables, KPI scorecards, reminders, activity feeds, as you want users to see them.
3. Go to Home > Settings portlet > Publish Dashboard (or the equivalent under the role’s dashboard settings). Select the role and confirm.
4. Optionally, check “Lock” to prevent users from personalizing the layout. Leave it unlocked if you want users to be able to add personal portlets while keeping your defaults.

A well-structured role dashboard for a finance manager might include: an AR aging reminder portlet, a KPI scorecard with monthly billed revenue and collection rate, a saved search table of invoices due this week, and a NetSuite financial reporting shortcut to the P&L. None of that requires custom development; it is entirely configuration.

Six Saved Search Use Cases Worth Building Today

• Overdue invoices by aging bucket: Transaction search, type = Invoice, status = Open, criteria on days overdue. Group by customer, sum amount remaining. Add highlighting for 30/60/90 day thresholds. Wire to a reminder portlet.
• Sales pipeline by stage: Opportunity search, status = In Progress. Group by sales stage and assigned rep, sum weighted amount. Display in a saved search portlet on the sales manager dashboard.
• Inventory reorder alert: Item search, criteria: quantity on hand less than reorder point. Results: item name, current quantity, reorder point, preferred vendor. Schedule to email the purchasing team every Monday at 7am.
• Open purchase orders by vendor: Transaction search, type = Purchase Order, status = Pending Receipt or Partially Received. Group by vendor, sum amount remaining. Use a reminder portlet so the AP team sees the count on login.
• Customer credit exposure: Customer search. Results columns: balance, credit limit, a formula column calculating balance/credit limit as a percentage. Highlight rows where the ratio exceeds 80%. Share with the credit manager role.
• Employee expense reports pending approval: Transaction search, type = Expense Report, status = Pending Approval. Results: employee, submission date, amount, approver. Wire to a reminder portlet on manager dashboards so nothing sits in limbo.

If your team is building these for the first time, Aaxonix’s NetSuite consulting services can help configure saved searches, dashboards, and role-based publishing across your entire organisation.

Saved Search vs Report vs Workbook: A Decision Framework

The fastest path to better reporting in NetSuite is not a new module or a custom script; it is getting more out of the saved search engine you already have. Start with one of the six use cases above, build the search, wire it to a portlet, and publish the dashboard to the relevant role. That single workflow, repeated across your team’s top reporting needs, produces a measurable improvement in how quickly your team can see and act on operational data.