NetSuite Automatic Use Restriction Release Saved Search Checklist

A NetSuite automatic use restriction release saved search must use transaction summary results, preserve the supplied calculation formulas, and retain stable grouping after processing begins. If you need different criteria, copy the locked default search, verify the configuration, and select the copy in Custom Preferences.

The critical safeguard is to finalize supported grouping before the first script run—not merely before saving the search. Changing grouping after processing begins can create duplicate releases, even when the change comes through a replacement search.

Key takeaways

Use a Transaction saved search with summary results and exactly one Formula (Currency) column: Sum, Revenue to be Released, numeric output.
Preserve the supplied calculation formulas and set Posting = Yes, including in a customized copy.
Group only by custom segments, Department, Class, or Location—not Subsidiary or Restriction.
Keep grouping unchanged after processing starts, including when replacing the selected search.
When Classification is selected for grouping, verify that the selected value is available on the parent subsidiary.
Select the copy at Setup > Company > General Preferences, on the Custom Preferences subtab.

When should you copy the locked default search?

The SuiteApp uses a locked default saved search to identify candidates for automatic processing. That search is selected during installation or upgrade. If your organization needs different selection criteria, copy the search and customize the copy rather than attempting to edit the locked original.

Treat the copied search as processing configuration, not simply as an alternate financial report. Its grouping fields define the intended release combinations. A change that looks like a reporting preference can therefore affect how automatic processing relates current results to historical released amounts.

Before customizing, separate three decisions:

Criteria: Which selection criteria need to change?
Grouping: Which supported fields define the intended release combinations?
Timing: Has automatic processing already started?

Before the first run, supported grouping can be finalized. After processing begins, the original grouping must remain unchanged. Make that timing check before reviewing a proposed replacement, rather than discovering a grouping difference at the preference-selection stage.

For context on where this search fits into processing, see the automatic use restriction release workflow. Copying the search does not make every possible alteration safe: the formula, summary, posting, and grouping requirements still apply.

Checklist: required transaction search results and formula settings

Before selecting a customized search, check both its overall structure and its individual formula-column settings. Summary results alone are not sufficient. A search can still fail the requirements by using the wrong custom label or containing more than one Formula (Currency) column.

Requirement	Required configuration
Search type	Transaction saved search
Results	Summary results
Grouping	Fields defining each intended release combination
Currency formula column	Exactly one Formula (Currency) column
Formula summary type	Sum
Formula custom label	Revenue to be Released
Formula output	A numeric amount
Posting criteria	Yes

Review the table as separate acceptance checks. A plausible-looking amount does not establish that the column count, summary type, custom label, and calculation logic are correct.

For example, a copied search with numeric output and the label Revenue to be Released still needs exactly one Formula (Currency) column with summary type Sum. Conversely, matching those column properties does not permit replacing the supplied calculation formula.

For background on column properties, the guide to creating search columns in SuiteScript provides related developer context. It is optional background; the configuration requirements above are the checklist for this process.

Preserve the supplied formulas and Posting = Yes

The Revenue to be Released column has requirements that must hold together: Formula (Currency), Sum, the exact custom label, numeric output, and preserved calculation logic. Numeric output is not permission to replace the supplied formula. A replacement expression that returns a currency amount does not satisfy the requirement to retain the original calculation formulas.

When reviewing the copy, compare its formulas with the supplied baseline rather than judging correctness only from displayed totals. Keep criteria changes separate from formula changes: different selection criteria are the reason to customize the copy, not a reason to rewrite its calculations.

Keep Posting = Yes explicit during customization. It must be set both when working with the saved search and when creating a customized copy. Recheck it before selecting the search for processing rather than assuming the copy still has the correct setting.

A focused formula-and-criteria review should answer:

Are the supplied calculation formulas unchanged?
Is Revenue to be Released still the exact custom label?
Is Posting set to Yes in the customized copy?
Have criteria adjustments been reviewed separately from the required calculation logic?

Teams discussing criteria programmatically can use the search filter creation guide as background. Keep that implementation discussion separate from the release search’s required formula and posting configuration.

Which grouping fields are supported?

Group only by custom segments, Department, Class, or Location. Do not group by Subsidiary or Restriction. The script uses consolidated parent results and assigns restriction values when creating each transaction.

Field or field category	Grouping decision
Custom segments	Supported
Department	Supported
Class	Supported
Location	Supported
Subsidiary	Do not group
Restriction	Do not group

Do not add Subsidiary or Restriction as extra grouping dimensions for reporting convenience. The grouping defines intended release combinations; it is not simply a way to rearrange the report.

The choice of field is only the first check. The second is whether the grouping structure remains consistent with the one used when processing began.

How do you avoid duplicate releases when switching searches?

Finalize grouping before the first script run. After automatic releases begin, historical released amounts are calculated using the original grouping. Changing that structure can create duplicate releases, including when switching to another saved search.

For an existing process, compare the proposed replacement’s grouping directly with the original before switching. Selecting another search does not remove the requirement to preserve the original grouping.

For example, suppose the original search groups by Department and Location. A proposed replacement groups only by Department. Although both fields are supported individually, the replacement changes the original structure. Do not treat it as safe merely because it uses allowed fields or returns a similar overall amount.

Use this review sequence:

Identify the original grouping. Record the fields used when processing started so later comparisons have a clear baseline.
Compare the replacement’s grouping. Check the structure, not just whether each field appears on the supported list.
Preserve the original structure. A different search name is not a new grouping baseline.
Review the remaining requirements. Matching grouping does not replace the formula, summary, posting, or applicable classification checks.

This distinction is particularly important during handoffs: “supported fields” and “unchanged grouping” are two separate acceptance criteria.

Check parent-subsidiary availability when grouping by Classification

When Classification is selected as a grouping field, the selected classification value must be available on the parent subsidiary. The Release from Restriction transaction is created at that parent-subsidiary level.

Do not limit the review to the classification value associated with the source activity. Include availability where the release transaction is created.

This is a useful point for administrator and accounting review to meet. As a review assignment, the administrator can check classification availability while the accountant reviews the intended release combinations. Neither review replaces the supported-grouping and unchanged-grouping checks.

Identify whether Classification is selected for grouping. Check the actual customized search rather than an assumed design.
Check the selected value’s availability on the parent subsidiary. This is the level where the Release from Restriction transaction is created.
Include the check when reviewing a replacement search. Preserve the original grouping and confirm the applicable classification availability before selecting the replacement.

Do not try to address this requirement by grouping by Subsidiary. That field remains prohibited for grouping; parent-subsidiary classification availability is a separate condition.

How do you select the customized search and open its report?

Complete the configuration review before changing the selected search. For a first implementation, finalize supported grouping before processing begins. For an existing process, compare the replacement with the original grouping and retain that structure.

Before the handoff, confirm:

Transaction saved search with summary results.
Exactly one Formula (Currency) column, with Sum, Revenue to be Released, numeric output, and unchanged supplied calculation formulas.
Posting = Yes.
Supported grouping, unchanged from the original if processing has started.
Parent-subsidiary availability for the selected classification value, when Classification is used for grouping.

Then select the search:

Go to Setup > Company > General Preferences.
Open the Custom Preferences subtab.
Select the customized search in Release from Use Restriction Saved Search.

To open its report, go to NFP Financial Center > Financial. The selected saved search’s label appears as a center label. Select its name to view the release from restriction report.

Use the report review to confirm that you are viewing the intended selected search and its release combinations. Opening the report is not a substitute for inspecting formula settings, posting criteria, and grouping configuration.

FAQ

Can I edit the locked default saved search?

No. Copy the locked default search to change criteria, preserving the supplied calculation formulas and required summary structure.

Is numeric formula output enough?

No. The search needs exactly one Formula (Currency) column with summary type Sum and custom label Revenue to be Released. Its output must be numeric, and the supplied calculation formulas must remain unchanged.

Can grouping change when I switch to another saved search?

Not after automatic releases begin. Historical released amounts use the original grouping, so changing it—even through a replacement search—can create duplicate releases.