Automatic Use-Restriction Releases in NetSuite: Setup and Runs

Automatic use-restriction releases in NetSuite let nonprofit finance teams create Release from Restriction transactions for eligible use-restricted revenue without entering every transaction manually. In Non-Profit Financial Management 1.0.2, a selected saved search supplies candidates, and the Auto Release from Restriction script determines eligible amounts.

Configure the qualifying account, review the selected search, and then choose on-demand or scheduled execution. Time-restriction releases remain a separate manual process.

Key takeaways

An active Income or Other Income account must have Applies To set to Release from Restriction. Without a qualifying account, the script creates no transactions.
Installation or upgrade selects a locked default saved search. Administrators can retain it or select a compatible customized search in General Preferences.
Open Customization > Scripting > Script Deployments, then the Auto Release from Restriction deployment. Use Save and Execute for an on-demand run or configure a recurring schedule.
Search candidates are not the same as eligible results: the script determines the amounts available for release.
Future-use funding is excluded from currently releasable amounts. Continue handling time-restriction releases manually.

How automatic use-restriction releases work

The process has three stages: candidate selection, eligibility evaluation, and transaction creation. The saved search defines which candidates reach the script. The Auto Release from Restriction script determines eligible amounts and creates a transaction for each eligible result.

This distinction matters when finance reviews the outcome. Appearing in search results does not establish a candidate's releasable amount. Do not treat the search output as a list of transactions that must be created.

The capability is described in the 2026.2 release material for Non-Profit Financial Management 1.0.2. Manual Release from Restriction transaction creation remains available: automation adds a processing option rather than making every restriction release automatic.

Prerequisites and review responsibilities

Before configuring execution, agree on the intended candidate population and who will review the results. As an implementation recommendation, have an administrator review preferences and deployment setup while a nonprofit accountant reviews candidates and generated transactions. These assignments are suggested responsibilities, not documented permission requirements.

Configuration item	Required condition or behavior
Account status	Active
Account type	Income or Other Income
Applies To	Release from Restriction
Candidate selection	Saved search selected in General Preferences
Initial search selection	Locked default saved search selected during installation or upgrade
Execution setup	On-demand execution or a schedule configured on the script deployment

Confirm locally who can maintain the account, change preferences, and edit the deployment. Do not assume every finance user has that access. The guide to editing custom roles in NetSuite provides related access-management context, not a list of permissions required for this script.

For the first execution, plan to review the selected search results alongside the generated transactions. Retaining those results for comparison is a recommended implementation check, not an additional product requirement.

1. Configure the required account

Start with the account prerequisite rather than the execution schedule. A selected search cannot compensate for the absence of a qualifying account.

Review the account intended for Release from Restriction processing.
Confirm that it is active.
Confirm that its type is Income or Other Income.
Set or verify Applies To as Release from Restriction.

If no account meets these conditions, the script does not create Release from Restriction transactions. Consequently, a run that creates no transactions is not proof that the search found no candidates or that no revenue was eligible.

Check the account before broadening search criteria. Otherwise, the team could change the candidate population without addressing the documented configuration problem.

For broader accounting context, see the overview of NetSuite Accountant module features. For this automation, keep the prerequisite review focused on active status, qualifying account type, and the Applies To value.

2. Review the selected saved search

During installation or upgrade, the SuiteApp selects a locked default saved search. Administrators can retain that search or select a compatible customized search in General Preferences when different criteria are needed.

Use this recommended validation sequence:

Review the default saved search and its returned candidates.
Identify which criteria need to differ, if any.
Confirm compatibility and supported grouping before choosing a customized search.
In General Preferences, retain the default or select the compatible customized search.
Compare the selected search results with the intended candidate population.
After execution, review the created transactions separately from the candidates.

The supplied material identifies General Preferences, but does not establish the precise preference field label or a complete navigation path. Verify the selection control in your account rather than assuming either detail.

Customized searches must use supported grouping fields. An existing revenue search is not necessarily compatible merely because its results look relevant. See custom use restriction search requirements for related reading before replacing the default.

Keep two questions separate: Did the search include the intended candidates? and What amounts did the script determine were eligible? Changing search criteria addresses the first question; it does not establish the answer to the second. The supplied material does not provide the complete eligibility formula or enumerate supported grouping fields.

3. Run the script on demand

An on-demand run is useful for an initial review before adopting recurring execution. No schedule is required, but the account prerequisite and saved-search selection still apply.

After installation or upgrade, go to Customization > Scripting > Script Deployments.
Open the Auto Release from Restriction script deployment.
Confirm that the qualifying account and selected saved search have been reviewed.
Click Save and Execute.
Review the resulting Release from Restriction transactions against the candidate results and intended scope.

Review scenario: candidates appear, but no transactions are created

Suppose the team retains the locked default search and sees candidates before its first on-demand run. After execution, no transactions appear. That observation alone does not show whether the problem is account configuration or whether candidates have eligible amounts.

First, check the qualifying account. A missing active Income or Other Income account with Applies To set to Release from Restriction is a documented reason for transaction creation not to occur.

Next, review the selected search and distinguish its candidates from the script's eligibility evaluation. Do not broaden the search simply to make the output look more like the expected transaction list.

This is a troubleshooting sequence, not an eligibility formula. A useful review records the account conditions, selected search, execution method, and resulting transactions so the administrator and accountant can discuss the same evidence.

4. Configure recurring execution

Selecting the default search during installation or upgrade is separate from configuring a schedule. A selected search does not establish that recurring processing is configured.

Go to Customization > Scripting > Script Deployments.
Open the Auto Release from Restriction script deployment.
Configure the deployment to execute according to your preferred schedule.
Choose timing that fits the team's release-review process.
After execution, review the results using the same checks applied to the initial on-demand run.

The supplied guidance does not prescribe a frequency. Do not assume a daily or period-end default. Scheduling changes when the script runs; it does not replace the account prerequisite, determine the candidate population, or extend processing to time restrictions.

Assign responsibility for reviewing recurring results rather than treating the schedule itself as the completed control. The discussion of accounting task criteria and prerequisite order provides related process context; this recommendation does not imply integration between that framework and the release script.

5. Keep time-restriction releases separate

Automatic processing applies only to use restrictions. Funding restricted for future use is excluded from the amount currently available for release. Automatically created transaction lines also omit a Time Restriction value.

Continue using the Release from Time Restriction report and the manual process for time-restriction releases. A blank Time Restriction value on an automatically created line is documented behavior, not by itself evidence of a configuration failure.

Before recurring execution begins, make the workflow boundary explicit:

Review automatic use-restriction results for eligible amounts and generated transactions.
Check that future-use funding has not been treated as currently releasable.
Keep the separate manual time-restriction review assigned.

Running the script more frequently does not replace the time-restriction workflow. Manual Release from Restriction transaction creation also remains available when needed.

6. Verify configuration and results

Finish implementation by reviewing configuration, candidates, and created transactions—not merely confirming that someone clicked the execution action.

Review question	What to check
Is the account prerequisite satisfied?	Active Income or Other Income account; Applies To set to Release from Restriction
Is the intended search selected?	Selection in General Preferences and the candidates returned
Is a customized search suitable?	Compatibility and supported grouping
How was execution configured?	Save and Execute for an on-demand run, or a recurring deployment schedule
What did processing create?	Release from Restriction transactions for eligible results, reviewed separately from candidates
Is the scope correct?	Future-use funding excluded from currently releasable amounts; manual time-restriction workflow retained

For administrators, the review centers on the account, search selection, and deployment. For accountants, it centers on the candidate population, eligible release amounts, and generated transactions. These are recommended review responsibilities rather than additional product requirements.

If no transactions were created, begin with the qualifying account. Then examine candidate selection and eligibility as separate questions. This avoids changing a correct search to address an unrelated account prerequisite problem.

FAQ

What account is required for automatic use-restriction releases?

An active Income or Other Income account must have Applies To set to Release from Restriction. Without a matching account, the script does not create transactions.

Can I use a customized saved search?

Yes. Administrators can select a compatible customized search in General Preferences. Customized searches must use supported grouping fields; review compatibility before replacing the default.

Does the saved search determine the releasable amount?

No. It supplies candidates. The Auto Release from Restriction script evaluates eligibility and determines the amounts to release.

How do I run the script once?

Open Customization > Scripting > Script Deployments, select Auto Release from Restriction, and click Save and Execute. An on-demand run does not require a schedule.

Does scheduling automate time-restriction releases?

No. Continue the manual workflow using the Release from Time Restriction report. This automation applies only to use restrictions.