NetSuite Grants Allocations Require Manual Runs

Grants SuiteApp 1.2.0 replaces scheduled allocations with manual runs. Review date selection, duplicate risks, and the support-requested upgrade.

·5 min read·12 views·NetSuite 2026.2·View Oracle Docs

Indirect Cost Allocation for Grants SuiteApp version 1.2.0 replaces scheduled generation with manual runs, including multiple runs per day. Users select allocation segment values and transaction dates for each run. Existing accounts must request the upgrade through NetSuite Customer Support and complete pending eligible allocations before upgrading.

What Changes in Indirect Cost Allocation Generation?

SuiteApp version 1.2.0 changes who controls allocation timing: a user must initiate every run. Instead of waiting for scheduled processing, accounting teams can start a run when they are ready to calculate indirect costs. The SuiteApp no longer generates these allocations automatically or on a schedule.

Each run lets you choose all available allocation segment values or specific values and enter a transaction date range. Only transactions within that range are considered for allocation.

You can generate allocations multiple times per day, including for overlapping date ranges. However, only one allocation run can be active at a time. Multiple daily runs are supported; concurrent runs are not.

For teams already using the SuiteApp, this replaces scheduled processing rather than adding another way to launch it. Review any operating procedure that assumes allocations will appear without someone initiating a run. For related grants functionality, see indirect cost allocation enhancements for grants.

What Must You Do Before Upgrading?

Existing accounts with Indirect Cost Allocation for Grants are not automatically upgraded to version 1.2.0. Contact NetSuite Customer Support to request the upgrade. Before upgrading, use the currently installed version to complete indirect cost allocations for all pending eligible transactions.

A practical transition checklist is:

  1. Identify pending eligible transactions that still require allocation.
  2. Complete their allocations using the existing SuiteApp version.
  3. Retain a record of the transaction date ranges processed before the upgrade.
  4. Coordinate the upgrade request with NetSuite Customer Support.
  5. Assign responsibility for starting and reviewing manual runs after the upgrade.

Keeping a record of previously processed dates is a recommended control, not an additional SuiteApp setup requirement. It addresses a specific warning in the generation instructions: do not select date ranges already processed using an older SuiteApp version, because this can generate duplicate allocations.

Plan the transition around both requirements: finish pending eligible allocations in the current version, then avoid reselecting the older version's processed date ranges after upgrading.

How Do You Generate Indirect Cost Allocations?

Go to Indirect Cost Allocations > Generate Indirect Cost Allocations. This page is both the starting point for a run and the place to review processing status and results.

1. Choose the segment scope and dates

Use these controls to define which source transactions the run considers:

Field or optionSupported selection or behavior
Allocation Segment ValuesChoose All Values or Select Values.
All ValuesIncludes all available allocation segment values.
Select ValuesIncludes the specific allocation segment values you choose.
Start DateRequired; transactions on this date are included for consideration.
End DateRequired; transactions on this date are included for consideration.

If you choose Select Values, click Select Values to open the Select Allocation Segment Values window. Move the required entries into the Selected Values list, then click Apply.

Before proceeding, review whether the run should cover every available segment value or only the selected entries. This check is particularly useful when different operators are responsible for different allocation scopes.

2. Check the transaction date range

Complete both Start Date and End Date. The range is inclusive: transactions dated on either boundary, as well as dates between them, are included for consideration.

These fields filter transaction dates, not simply the day you launch processing. Verify that the range matches the transactions you intend to allocate and does not include dates already processed under an older SuiteApp version.

Segment selection and date selection work together to define the run's scope. Reviewing only the selected segment values is not enough if the transaction period is wrong; likewise, the intended dates do not replace checking the segment selection.

3. Start processing

Click Generate. The SuiteApp starts processing source transactions matching your selections and excludes costs that already have an indirect cost allocation.

Wait until that run finishes before starting another. If several team members generate allocations, coordinate responsibility for the next run so everyone works within the single-active-run limit.

4. Review status and results

Review each run's processing status on the same page. In the Results column, click View to inspect the results for that run.

As a recommended control, compare the results with the intended segment scope and transaction period before treating the allocation task as complete. Include both starting the run and reviewing its outcome in the team's allocation checklist.

What Should You Check Before Using Overlapping Dates?

The updated SuiteApp permits overlapping date ranges and excludes costs that already have an indirect cost allocation when processing matching source transactions. A subsequent run therefore does not have to use an entirely separate date window.

Do not treat that exclusion as blanket protection across the upgrade. Oracle explicitly warns that selecting ranges processed using an older SuiteApp version can generate duplicate allocations. Keep the distinction between overlapping runs in the updated workflow and reprocessing historical ranges from the older version.

For example, before another run covers part of an earlier period, establish whether that period was processed before or after upgrading. Consult retained processing records rather than assuming all historical allocations receive the same duplicate protection.

Who This Affects

  • Grants accountants and allocation operators: Must initiate runs, choose segment values and dates, and review processing results rather than wait for scheduled generation.
  • NetSuite administrators: Should coordinate the support-requested SuiteApp upgrade and ensure the team completes pending eligible allocations beforehand.
  • Accounting managers and reviewers: Should update allocation checklists to identify who launches each run, who reviews it, and how previously processed date ranges are tracked.

These are suggested workflow responsibilities, not a list of NetSuite roles granted access to the feature. The source does not specify exact permissions or permission changes; verify access for intended operators rather than assuming a particular role can generate allocations.

Key Takeaways

  • SuiteApp version 1.2.0 replaces scheduled generation with user-initiated runs, including multiple runs per day.
  • Each run uses allocation segment selections and requires an inclusive start and end date; only one run can be active at a time.
  • Existing accounts must request the upgrade through NetSuite Customer Support and complete pending eligible allocations first.
  • Overlapping ranges are supported, but ranges processed under an older SuiteApp version can produce duplicates.
  • Review processing status and click View in the Results column on the generation page to inspect each run.

Frequently Asked Questions (4)

Can Indirect Cost Allocation for Grants run automatically after upgrading to version 1.2.0?
No. Version 1.2.0 replaces scheduled generation with runs that a user must initiate. Users can start multiple runs per day, but only one run can be active at a time.
What should existing users complete before requesting the SuiteApp 1.2.0 upgrade?
Complete allocations for all pending eligible transactions using the currently installed version before upgrading. Keep a record of the transaction date ranges processed, then request the upgrade through NetSuite Customer Support.
Can I run allocations for overlapping transaction date ranges?
Yes. The updated SuiteApp supports overlapping ranges and excludes source costs that already have an indirect cost allocation. However, selecting ranges processed with an older SuiteApp version can generate duplicate allocations, so check your processing records before choosing dates.
Which segment values and dates can I include in an allocation run?
Choose either All Values or Select Values for the allocation segments, and enter both a required Start Date and End Date. The date range is inclusive, and only transactions within that range are considered. After clicking Generate, review the run status and use View in the Results column to inspect its outcome.

Weekly Update History (1)

Accounting SuiteAppsadded

Added an entry for Changes to Indirect Cost Allocation Generation.

View Oracle Docs
Source: Changes to Indirect Cost Allocation Generation — 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 →