Nonprofit Use Restriction Auto-Release in NetSuite

Non-Profit Financial Management version 1.0.2 can automatically create Release from Restriction transactions for eligible use-restricted revenue. A selected saved search supplies candidates, and the Auto Release from Restriction script determines eligible amounts. Run it on demand or on a schedule; time-restriction releases remain a separate manual process.

What Does Automatic Use Restriction Release Change?

The new Auto Release from Restriction script retrieves candidates from a saved search, evaluates eligible amounts, and creates a Release from Restriction transaction for each eligible result. Accounting teams can use automatic processing instead of creating every use-restriction release manually.

A search candidate is not necessarily an eligible release for its entire amount. The script determines eligibility after retrieving candidates, and funding restricted for future use is excluded from the amount currently available for release. Reviewing the search results alone therefore does not establish the amounts that will be released.

Manual transaction creation remains available. Teams can run the script when needed, configure recurring execution, or continue creating transactions manually. The automation adds a processing option rather than replacing the manual workflow.

What Must Be Configured Before the Script Runs?

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

Check that prerequisite before changing search criteria or the deployment schedule to investigate a run that produces no transactions. A suitable candidate search does not replace the account requirement.

Treat account readiness and candidate selection as separate setup checks. The account is a prerequisite for transaction creation; the selected search determines which results the script considers. Neither check, by itself, establishes that a particular amount is eligible for release.

How Does the Saved Search Control Processing?

The script uses the saved search selected in General Preferences. During installation or upgrade, the SuiteApp selects a locked default search. An administrator can retain it or select a compatible customized search with different criteria and supported grouping fields.

The source does not enumerate the supported grouping fields or provide a complete compatibility specification. Do not assume that an existing revenue search is compatible merely because it returns relevant-looking results.

As an implementation review, confirm with the accounting team which revenue the search should submit for consideration. If a customized search is needed, review its criteria and supported grouping before selecting it. Because the script creates transactions for eligible results, this search affects transaction generation rather than serving only as a reporting view.

When an expected release is missing, distinguish two questions:

• Did the selected search return the expected candidate?
• If it did, was the expected amount eligible for release?

These reflect separate stages of the documented workflow. Changing candidate-selection criteria does not remove the script’s eligibility assessment or make funding restricted for future use currently available.

How Do You Run or Schedule the Script?

After installing or upgrading the SuiteApp, go to Customization > Scripting > Script Deployments and open the Auto Release from Restriction deployment. Choose how to run it; the default saved-search selection is separate from configuring execution.

Run on demand

Click Save and Execute. An on-demand run does not require a schedule.

As a recommended validation step, review the transactions from an initial run against the team’s expected eligible use-restricted amounts before adopting recurring processing. This review is operational advice, not an additional documented system requirement.

Run on a schedule

Configure the deployment to run according to the preferred schedule. This option processes eligible releases regularly.

The source does not prescribe a daily, monthly, or other fixed frequency. Choose a cadence that fits the team’s release-review procedures. Before relying on recurring execution, review the qualifying account, selected search, and results of initial processing rather than treating search selection as complete setup.

Which Restrictions Remain Outside Automatic Processing?

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 do not include a Time Restriction value.

Continue using the Release from Time Restriction report and the manual process to release revenue from time restrictions. This feature is not a combined use-and-time restriction release process.

For transaction review, the absence of a Time Restriction value on an automatically created line is documented behavior. It is not, by itself, evidence that the script failed to perform a time release: time releases are outside its scope.

Keep the separate time-restriction review in the accounting workflow when introducing automatic use releases. Reviewing the script’s output does not replace the report and manual processing required for time restrictions.

Who This Affects

• Administrators: Check the qualifying account, review the search selected in General Preferences, and configure on-demand or scheduled execution.
• Nonprofit accountants and finance teams: Review eligible use-restriction releases and continue the separate manual process for time restrictions.
• Saved-search maintainers: Review criteria and supported grouping before selecting a customized search in place of the locked default.
• Financial process owners: Decide when processing should run and where review of created transactions belongs in existing accounting procedures.

These are implementation responsibilities, not a documented permissions matrix. The source does not specify required role permissions or a complete set of customized-search compatibility rules.

Key Takeaways

• Non-Profit Financial Management 1.0.2 adds automatic creation of Release from Restriction transactions for eligible use-restricted revenue.
• Installation or upgrade selects a locked default saved search; administrators can select a compatible customized search.
• Transaction creation requires an active Income or Other Income account with Applies To set to Release from Restriction.
• Use Save and Execute for an on-demand run or configure a schedule for recurring processing. Manual creation remains available.
• Funding restricted for future use is excluded from currently releasable amounts. Time-restriction releases still require the Release from Time Restriction report and manual processing.