Grant Management 1.0.1 Automates Restriction Releases

Grant Management SuiteApp 1.0.1 creates restriction-release transactions from eligible saved search rows, on demand or on a schedule.

·3 min read·18 views·NetSuite 2026.2·View Oracle Docs

Grant Management SuiteApp version 1.0.1 can automatically create Release from Restriction transactions for eligible use-restricted grant amounts. A script evaluates saved search results and creates a separate balanced transaction for each eligible row. Processing can run on demand or on a schedule, and manual transaction creation remains available.

What Changes for Grant Restriction Releases?

Grant funding can be restricted to a particular purpose. A Release from Restriction transaction records the accounting change when an amount meets the conditions for release. The automation reduces repetitive transaction entry for organizations regularly processing releases across multiple grants or programs.

This is an additional processing option, not a replacement for manual releases. For grant-accounting teams, the practical preparation shifts toward selecting the amounts to evaluate, checking the release-account prerequisite, and reviewing the resulting transactions.

Related reading: indirect cost allocation enhancements for grants.

How Does Automatic Processing Select Grant Amounts?

On every run, the script uses the saved search selected in General Preferences. The default saved search is selected during installation or upgrade. Each result row identifies a grant amount for evaluation; appearing in the results does not, by itself, establish eligibility for release.

An amount qualifies only when both conditions are met:

  • It satisfies the use restriction rule.
  • Its amount is greater than zero.

If your organization needs different selection criteria, copy the default saved search and update the copy’s criteria. Select a compatible customized search in General Preferences. The selected search determines which grant amounts enter evaluation, while the eligibility check determines which rows produce transactions.

Treat these as separate checks during rollout: does the search return the intended candidates, and do those candidates satisfy the release conditions? A returned row with a zero amount does not qualify, even if it falls within the intended grant-processing scope.

What Account and Transaction Behavior Should You Verify?

Before automatic processing begins, configure a valid, active account for Release from Restriction. If no matching account is available, the script does not create Release from Restriction transactions. The script uses the first valid, active account configured for this purpose.

For every eligible result row, the script creates one separate, balanced transaction. Both lines use the same account and release amount:

Transaction LineRestriction Classification
DebitWith Sponsor Restrictions
CreditWithout Sponsor Restrictions

For rollout validation, check the configured account, confirm that the selected search returns the intended candidates, and review the resulting debit and credit classifications. Because transaction creation is per eligible row, review the search at the row level rather than assuming that all results for a grant become one transaction.

Who This Affects

  • Administrators: Prepare the selected search, configure the schedule during script deployment, and verify the active account prerequisite. Processing can also run on demand.
  • Grant accountants: Review release eligibility and generated transactions, while retaining manual creation when needed.
  • Grant and program teams: Coordinate which grant amounts should enter automated evaluation by reviewing the intended search scope with the people configuring processing.

Related reading: NetSuite SuiteApps enhancements overview.

Key Takeaways

  • Grant Management SuiteApp 1.0.1 adds automatic Release from Restriction transaction creation.
  • The selected saved search supplies candidates; eligibility requires a satisfied use restriction rule and a positive amount.
  • A valid, active release account is a prerequisite for transaction creation.
  • Each eligible row produces a separate balanced transaction; manual creation remains available.

Frequently Asked Questions (4)

How does Grant Management decide which saved search results qualify for an automatic restriction release?
The script evaluates results from the saved search selected in General Preferences. A row qualifies only if it satisfies the use restriction rule and its amount is greater than zero; appearing in the search results alone is not enough.
Can I change which grant amounts the automation evaluates?
Yes. Copy the default saved search, update the copy’s criteria, and select the customized search in General Preferences. The search determines which amounts are evaluated, while the eligibility rules determine which rows generate transactions.
What account must be configured before automatic Release from Restriction transactions can be created?
A valid, active account for Release from Restriction must be configured. If no matching account is available, the script creates no transactions; when multiple accounts are configured, it uses the first valid, active account.
Does the automation combine eligible grant amounts into one transaction, and can releases still be entered manually?
The script creates one separate, balanced transaction for each eligible search result row. Each transaction debits the account with Sponsor Restrictions and credits the same account without Sponsor Restrictions, using the release amount. Manual transaction creation remains available.

Weekly Update History (1)

Accounting SuiteAppsadded

Added an entry for Grant Management Enhancements.

View Oracle Docs
Source: Grant Management Enhancements — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Accounting

View all Accounting articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →