Revenue Restriction Management SuiteApp Now Automates Release from Use Restriction via Scheduled Script

What changed

The Revenue Restriction Management SuiteApp now includes an Auto Release from Restriction script deployment that programmatically creates Release from Restriction transactions for use-restricted revenue. Previously this was a manual process; the new script automates candidate identification and transaction creation.

How the script works

• A saved search (Transaction type, summary mode) identifies candidates by grouping posted financial activity by custom segment groupings.
• The script calculates eligibility using: Funding, Expenses, Amounts already released, and Funding restricted for future use. A candidate qualifies when Revenue to be Released > 0.
• For each eligible candidate, one balanced Release from Restriction transaction is created:
  • Debit line — With Donor Restrictions
  • Credit line — Without Donor Restrictions
• Both lines use the same active Income or Other Income account whose Applies To field is set to Release from Restriction.
• The script copies Program, Grant, Region, Department, Class, and Location values to transaction lines—but only when those fields appear as Group columns under the saved search Results tab. Adding them only as filters does not propagate values.
• Subsequent runs factor in previously released amounts to prevent duplicate transactions.
• If one candidate fails, the script skips it and continues with the rest.

Scope limitation

Automatic processing applies only to use restrictions. Time-restriction releases remain manual via the Release from Time Restriction report.

Saved search requirements for customization

The SuiteApp ships a locked default saved search selected on install/upgrade. To customize, copy the default and modify the copy. The custom search must meet all of these criteria:

1. Transaction saved search with Use Summary Results enabled.
2. Must include the grouping fields that define each intended release combination.
3. Exactly one Formula (Currency) column: Summary Type = Sum, Custom Label = Revenue to be Released, returning a numeric amount.
4. Group only by custom segments, Department, Class, or Location. Do not group by Subsidiary or Restriction.
5. Posting criteria must be set to Yes.
6. Do not alter the supplied calculation formulas.
7. When Classification is a grouping field, the selected value must be available on the parent subsidiary because transactions are created at the parent-subsidiary level.

Critical: Finalize grouping fields before the first script run. Changing grouping fields after releases have been created—or when switching saved searches—can produce duplicate release transactions because historical amounts are calculated using the original grouping.

What to do

1. Verify the GL account: Confirm an active Income or Other Income account exists with Applies To = Release from Restriction. Without this, the script silently creates nothing.
2. Open the script deployment: Navigate to Customization > Scripting > Script Deployments and locate the Auto Release from Restriction deployment.
3. Choose a run mode:
   • On demand — Click Save and Execute (no schedule needed).
   • Scheduled — Configure a recurring schedule on the deployment record.
4. Review or customize the saved search: If the default search criteria are insufficient, copy the locked default, modify per the requirements above, then set your custom search at Setup > Company > General Preferences > Custom Preferences > Release from Use Restriction Saved Search.
5. Lock down grouping fields: Finalize all grouping columns before the first scheduled run. Document the chosen groupings for your team.
6. Review results: After each run, check the Release from Use Restriction report (accessible via NFP Financial Center > Financial) to verify totals for funding, restricted amounts, released amounts, expenses, and remaining revenue to release.
7. Coordinate manual releases: Before creating any manual Release from Restriction transaction, review the report to avoid duplicating an automatic release.

Open questions

Oracle's documentation does not specify the script type (Scheduled Script vs. Map/Reduce), the script's internal ID, or governance-unit consumption. Administrators should inspect the deployment record to confirm the script type and plan execution windows accordingly, especially in accounts with heavy scheduled-script queues.