NetSuite Saved Searches: How to Create, Customize & Schedule Reports
NetSuite saved searches are one of the most useful no-code reporting tools in NetSuite. They let you pull real-time data from transactions, customers, items, vendors, employees, and custom records using filters, result columns, formulas, and scheduled delivery. A well-built saved search can replace recurring manual reporting, support workflows, and surface live operational data on dashboards. If standard NetSuite reports do not give you the exact view you need, saved searches usually fill the gap. You can build searches for overdue invoices, inactive customers, inventory below reorder point, purchase orders past due, pending approvals, and many other use cases without writing code. This guide explains how to create a NetSuite saved search, customize it with formulas and joins, schedule it for email delivery, add it to a dashboard, and avoid common performance and configuration mistakes.
Date
September 17, 2026
Read
17 min
Key Takeaways
Navigation can vary by account and role. In many accounts, go to Reports > Saved Searches > All Saved Searches > New. In some older setups, it appears under Lists > Searches > Saved Searches.
Always check “Summarize Scheduled Emails.” If you leave it unchecked, NetSuite can send one email per result row instead of one summarized message.
Use indexed fields when possible. Filtering on fields like Internal ID, Entity ID, Item ID, or Transaction Number is usually faster than filtering on name or description text fields.
Match the formula type to the output. Date calculations should use Formula (Date), text output should use Formula (Text), and numeric calculations should use Formula (Numeric).
Saved searches can support automation. They can be emailed on a schedule, used on dashboards, saved to the File Cabinet, and referenced in workflows.
Use SuiteAnalytics Workbooks when complexity grows. If your reporting needs involve deeper joins, larger datasets, or visualizations, Workbooks may be a better fit.
A NetSuite saved search is a reusable query that pulls records based on criteria you define and displays them in a custom result layout. You choose the record type, apply filters, select result columns, and optionally add sorting, grouping, summary logic, formulas, scheduled email delivery, or dashboard visibility.
Unlike many standard reports, saved searches are highly flexible. They are commonly used for operational reporting because they return live data and can be adapted quickly to changing business needs.
Typical use cases include:
Open invoices past due
Vendor bills due soon
Customers with no activity in 90 days
Inventory below reorder point
Pending expense approvals
Open opportunities by expected close date
Saved searches can also be shared, scheduled, pinned to dashboards, or used alongside NetSuite workflows to support process automation.
NetSuite Saved Searches vs. Reports
Use a saved search when you need flexible, real-time data with custom criteria. Use a standard report when presentation and formatting matter more than configuration flexibility.
Feature
Saved Search
Standard Report
Real-time data
Yes
Yes
Custom formula fields
Yes
Limited
Schedule for email delivery
Yes
Yes
Trigger workflow automation
Yes
No
Access custom record types
Yes
No
Native charts/visualizations
No
Yes
Executive-ready formatting
No
Yes
Dashboard portlet integration
Yes
Limited
A practical way to choose:
Use saved searches for daily operational monitoring and exception reporting.
Use reports or SuiteAnalytics Workbooks for polished executive output, charts, and broader analytics.
Permissions You Need
Before creating or editing a saved search, confirm your role has the right permissions.
Saved Searches: Required to create, edit, or delete saved searches
Publish Search: Required to share a search or make it public
Record type access: You can only search record types your role can view
Send Email: Required to configure scheduled email delivery
Admins can review these permissions under Setup > Users/Roles > Manage Roles. Sharing issues often come from role restrictions or Audience settings rather than the saved search itself.
How to Create a Saved Search in NetSuite
Step 1: Open the Saved Search Menu
Go to Reports > Saved Searches > All Saved Searches, then click New.
In some accounts, the path may be Lists > Searches > Saved Searches > New.
If you do not see either option, your role may be missing saved search permissions. In that case, contact your administrator or a NetSuite consulting partner.
Step 2: Choose the Record Type
NetSuite will ask which record type you want to search. This choice determines the core dataset the search can access.
Choose the record type that contains the main records you want to analyze. You can pull related fields later through joins, but the base record type shapes the search.
Step 3: Add Criteria and Filters
The Criteria tab determines which records are included.
Each filter has three parts:
Field
Operator
Value
For example, a customer inactivity search might use:
Status \= Active
Date of Last Transaction \= before 90 days ago
A transaction-based overdue invoice search might use:
Type \= Invoice
Status \= Open
Days Overdue > 0
Use multiple filters together to narrow the result set to the records that matter.
Step 4: Configure the Results
The Results tab controls what appears in the output.
Here you can:
Add columns
Rename labels
Sort ascending or descending
Group by a field
Apply summary types such as Sum, Count, Max, Min, or Average
For example, you might show:
Customer Name
Invoice Number
Transaction Date
Due Date
Days Overdue
Amount Remaining
If you are creating a summary search, make sure summary types are configured consistently. Mixed summary and non-summary columns can cause errors if not set correctly.
Step 5: Add Formula Fields
Formula fields let you calculate, classify, or reformat data directly in the search.
Available types typically include:
Formula (Text)
Formula (Numeric)
Formula (Date)
Formula (Percent)
Formula (Currency)
Formula (HTML) where supported
Choose the formula type that matches the kind of value you want to return.
Examples:
Date formula{trandate} + 90
Use this in a Formula (Date) field to calculate a date 90 days after the transaction date.
Text formula{companyname} || ' - ' || {accountnumber}
Use this in a Formula (Text) field to combine multiple text values.
Overdue status formulaCASE WHEN {daysoverdue} > 0 THEN 'Overdue' ELSE 'Current' END
This is useful in a Formula (Text) result column to classify records clearly.
Use a numeric or percent formula to show transaction margin.
Formula fields are often the difference between a basic data pull and a business-ready report.
If you are also exploring newer NetSuite AI capabilities, formula strategy becomes even more important as reporting features continue to evolve.
Step 6: Preview, Save, and Name the Search
Before saving, preview the search and make sure:
The right records are returned
The column layout is clear
Sorting and formulas work as expected
The result count looks reasonable
Then:
Enter a descriptive Title
Choose whether the search is Public or Private
Mark it as available for dashboard use if needed
Save the search
A clear title helps other users understand the purpose immediately, such as:
AR – Overdue Invoices 30+ Days
Inventory – Below Reorder Point by Location
Sales – Open Opportunities by Close Date
How to Customize a Saved Search
Once the search works, customization makes it more useful for the team that will rely on it.
Add Formula-Based Insights
Formula fields can help turn raw data into action-ready information.
Examples include:
Aging buckets using CASE logic
Status flags such as Overdue, Current, or On Hold
Concatenated identifiers for easier reading
Calculated due dates or SLA targets
Gross margin or utilization calculations
Instead of forcing users to interpret raw columns manually, formulas let the search explain the result.
Use Joins to Pull Related Data
You can include fields from related records by selecting joined fields in the Results tab.
Examples from a Transaction search might include:
Customer: Phone
Customer: Terms
Sales Rep: Email
Item: Preferred Stock Level
This is useful when the base record type does not contain all the context you need.
As a rule, joins are fine for simple related fields. If your search becomes too dependent on multiple layered joins, performance may suffer. That is often the point where SuiteAnalytics Workbooks become the better reporting option.
Sort, Group, and Summarize
Sorting helps users prioritize records quickly. For example:
Sort overdue invoices by highest days overdue
Sort opportunities by expected close date
Sort low-stock items by location
Grouping and summarizing are useful for management-level reporting. You might:
Group invoices by customer and sum open balance
Group items by location and count below-reorder products
Group projects by manager and summarize budget vs. actual
Be explicit with summary settings to avoid result configuration errors.
Control Access Through Audience Settings
The Audience tab determines who can access the saved search.
You can share by:
Role
Employee
Group
Public visibility
Use this carefully. Searches that expose margin data, compensation-related records, or vendor pricing should be restricted to the right audience. Public searches should be reviewed regularly.
How to Schedule a Saved Search
Scheduling turns a saved search into an automated report.
Open the Email Tab
After saving the search, open it again and go to the Email tab. Then enable Send Emails According to Schedule.
Choose Recipients and Frequency
You can typically send results to:
Internal NetSuite users
External email addresses
Then choose a cadence such as:
Daily
Weekly
Monthly
Common patterns:
Daily for exception monitoring
Weekly for team reviews
Monthly for slower-moving activity reports
Select an Output Format
Depending on the audience, you may choose:
HTML email: good for quick reading
CSV attachment: useful for further analysis
Excel/XLS attachment: often preferred by finance teams
PDF: useful for archival or locked formatting
Choose the format based on how the recipients actually use the report.
Always Check “Summarize Scheduled Emails”
This setting is critical.
If Summarize Scheduled Emails is unchecked, NetSuite may send one email per returned record instead of one consolidated email. That can create a flood of messages for every recipient.
For most reporting use cases, this box should be checked.
If you need help cleaning up a misconfigured scheduled search, a NetSuite support services team can usually help resolve the issue quickly.
Save a Copy to the File Cabinet
If needed, you can also save each scheduled run to the NetSuite File Cabinet. This is useful for:
Audit trails
Timestamped report archives
Compliance documentation
Historical reference copies
How to Add a Saved Search to a Dashboard
To show a saved search on a NetSuite dashboard:
Go to the Home dashboard
Click Personalize
Find the Saved Search portlet
Drag it onto the dashboard
Open the portlet settings and choose your saved search
Dashboard portlets are especially useful for live operational monitoring. Teams can use them to track:
Open POs past due
Invoices overdue today
Inventory below reorder point
Records awaiting approval
Because the data is live, users get instant visibility without running the full search manually.
9 Common Saved Search Examples
Below are practical saved search examples by function.
Finance & Accounts Receivable
1. Overdue Invoice Search Transaction search filtered to open invoices with days overdue greater than zero. Best for a daily AR review.
2. Vendor Bills Due in 7 Days Transaction search filtered to open vendor bills due within the next seven days. Useful for AP planning.
3. Customer No-Activity Report Customer search filtered to active customers with no recent transaction activity. Often used by sales or account management teams.
Operations & Inventory
4. Inventory Below Reorder Point Item search comparing quantity on hand to preferred stock level, often grouped by location.
5. Open Purchase Orders Past Expected Receipt Date Transaction search filtered to purchase orders pending receipt where the expected receipt date has passed.
6. Items With No Sales in 180 Days Inventory or transaction-based search to identify slow-moving or dead stock.
Sales, HR, and Projects
7. Expense Reports Awaiting Approval Search filtered to expense reports still pending supervisor or manager approval.
8. Open Sales Opportunities by Close Date Opportunity search showing active deals ordered by expected close date.
9. Project Budget vs. Actual by Project Manager Project search summarized by manager with budget and actuals shown side by side.
Common Mistakes to Avoid
1. Forgetting to Summarize Scheduled Emails
This is one of the most damaging avoidable mistakes. Always verify the summarize setting before turning on delivery.
2. Filtering First on Non-Indexed Fields
Name and description fields are often slower than IDs, numbers, and standard date fields. Lead with indexed fields when possible.
3. Using the Wrong Formula Type
If the output is a date, use Formula (Date). If it is text, use Formula (Text). Type mismatches can cause vague errors.
4. Overusing Joins
Too many joins increase complexity and execution time, especially on dashboard searches or frequently run reports.
5. Making Sensitive Searches Public
Public saved searches should be reviewed for exposed financial or personnel data. Use the Audience tab carefully.
Performance Tips for Faster Saved Searches
Saved searches can affect the user experience if they are poorly designed, especially when they run on dashboards or are shared broadly.
Use these best practices:
Filter on indexed fields first: Internal ID, Entity ID, Item ID, Transaction Number, and date fields are typically more efficient.
Avoid broad wildcard logic: “Contains” filters and loose text matching are more expensive than exact matching.
Keep formula logic out of Criteria when possible: Formula filters may be evaluated row by row before filtering is applied.
Limit result volume: If the search supports a dashboard portlet, do not return thousands of rows when only a few are displayed.
Review and archive old searches: Unused public searches add clutter and may still affect users indirectly.
If a search is slow, simplify the criteria, reduce joins, tighten the date range, and confirm it is not doing unnecessary work. For broader tuning strategies, review these NetSuite optimization best practices.
When to Use SuiteAnalytics Workbooks Instead
Saved searches are excellent for operational reporting, but they are not always the right long-term solution.
Consider SuiteAnalytics Workbooks when you need:
More complex joins across multiple record types
Larger datasets
Better cross-functional analysis
Pivot-style reporting
Native charts and visualizations
More advanced analytics logic
Saved searches are best when you need quick, focused, real-time operational output. Workbooks are better when the question is broader, more analytical, or more visual.
You may also want to review NetSuite’s SuiteQL documentation if your team is moving beyond standard saved search capabilities. If you need help deciding which reporting layer fits your use case, working with a NetSuite consultant can speed up that decision.
Helpful NetSuite Resources
If you need implementation, optimization, or troubleshooting support for your NetSuite environment, there are several helpful resources available that can guide you through best practices and expert solutions. You can start by exploring the NetSuite platform overview to understand the full capabilities of the system and how it supports business operations. For more hands-on expertise, consider leveraging NetSuite consulting services or ongoing assistance through NetSuite support services. To enhance system performance and efficiency, review ERP optimization best practices, which provide actionable strategies for improvement.
If you're looking for specialized expertise, the NetSuite consultant resources page offers valuable insights, while a broader range of solutions can be found under NetSuite services. For quick productivity gains, check out the NetSuite Keyboard Shortcuts reference. You can also stay ahead with innovation by exploring NetSuite AI and Generative AI capabilities.
NetSuite saved searches are one of the fastest ways to improve visibility and reduce manual reporting inside NetSuite. Once your team knows how to build them correctly, they can support recurring operational reporting, automate scheduled delivery, and surface live exception data where people actually work.
Start with one high-value use case, such as:
Overdue invoices
Inventory below reorder point
Open approvals
Inactive customers
Build the search, test the filters, verify the output, then schedule or publish it only after reviewing the audience and email settings carefully.
If you need help building or refining more advanced reporting, NetSuite services can help support more complex saved search and analytics work.
Frequently Asked Questions
What is a NetSuite saved search?
A NetSuite saved search is a reusable query that pulls records based on criteria you define, displays them in a customizable format, and can be shared, scheduled, or used for automation.
How do I create a saved search in NetSuite?
Go to Reports > Saved Searches > All Saved Searches > New, choose a record type, add Criteria filters, define the Results columns, then save the search.
How do I schedule a saved search email?
Open the saved search, go to the Email tab, enable scheduled delivery, set recipients and frequency, choose the output format, and check Summarize Scheduled Emails.
What is the difference between a saved search and a report?
Saved searches are more flexible for operational reporting and formulas. Reports are better for formatted presentation output.
Why is my saved search slow?
Common causes include non-indexed filters, too many joins, complex criteria formulas, wildcard searches, and oversized result sets.
Can saved searches trigger workflows?
Yes. NetSuite workflows can use saved searches to target records for automated actions.
When should I use SuiteAnalytics Workbooks instead?
Use Workbooks when you need more complex joins, larger datasets, visualizations, or broader analytical reporting.
Disclaimer: This content is for general informational purposes only and may not reflect current updates or your specific configuration—please confirm details with your Anchor Group consultant.
A NetSuite implementation usually takes 4–6 months for a mid-market company. Most projects move through six core phases: Discovery, Configuration, Data Migration, UAT, Cutover, and Hypercare. Oracle’s SuiteSuccess methodology can shorten that to 90–120 days for companies adopting standard best-practice workflows, while complex multi-entity or highly customized deployments may take 9–18 months. This guide explains the full timeline from kickoff to go-live, including realistic phase durations, cost ranges, internal bandwidth requirements, common delay risks, and how to choose between SuiteSuccess and a custom implementation path.
A complete NetSuite implementation checklist covers six phases: discovery and planning, design and configuration, data migration, testing and UAT, go-live cutover, and post-go-live hypercare. For most mid-market companies, the full implementation runs 4–6 months from kickoff to go-live, followed by a structured 30–90 day stabilization period. This guide gives you a phase-by-phase checklist for planning, building, launching, and stabilizing NetSuite in 2026. It is designed to help teams avoid the most common causes of implementation failure: weak discovery, late data cleanup, inadequate testing, poor cutover planning, and underfunded hypercare. Whether you are leading the project internally or working with a NetSuite implementation partner, use this as a practical guide from kickoff through the 90-day post-launch review.
A NetSuite implementation project plan is the operating guide for deploying NetSuite across finance, operations, inventory, procurement, and reporting. It defines scope, milestones, owners, risks, data migration, testing, and go-live readiness. Without that structure, ERP projects drift quickly. Research consistently shows that ERP implementations often run over budget, miss timelines, or fail to meet objectives, largely because teams underestimate scope, delay data cleanup, and treat go-live as the finish line rather than the beginning of adoption.
NetSuite rescue is a structured guide for diagnosing, stabilizing, and remediating a failed or stalled ERP implementation without starting over. In most mid-market cases, a rescue engagement is faster, less disruptive, and less expensive than a full re-implementation because it preserves usable configuration, existing data, and the company’s NetSuite license investment.