NetSuite Manual Grants Indirect Cost Allocation: 1.2.0 Upgrade and Run Guide

Move safely to manual grants indirect cost allocation in SuiteApp 1.2.0. Learn what to finish before upgrading, how to generate and review runs, and which historical date ranges can cause duplicates.

·8 min read·By NetSuite Changelog·2 views

NetSuite manual grants indirect cost allocation changes with Indirect Cost Allocation for Grants SuiteApp 1.2.0: users must initiate every run instead of relying on scheduled generation. The transition requires two separate controls—complete pending eligible allocations before upgrading, and avoid selecting date ranges processed under the older version afterward.

Key takeaways

  • Existing accounts are not automatically upgraded to version 1.2.0. Request the upgrade through NetSuite Customer Support.
  • Complete allocations for all pending eligible transactions using the currently installed version before upgrading.
  • Each manual run uses allocation segment selections and required, inclusive Start Date and End Date values.
  • Multiple runs per day and overlapping date ranges are supported, but only one run can be active at a time.
  • The updated workflow excludes already allocated costs, but that is not blanket protection for ranges processed under an older SuiteApp version.

What changes in SuiteApp 1.2.0?

The operational change is ownership of timing: a designated operator must start every allocation run. Manual generation replaces scheduled processing; it is not another launch option alongside an ongoing schedule. Any checklist that assumes allocations will appear automatically needs a new action and a named owner.

Each run also makes scope an explicit decision. The operator chooses allocation segment values and a transaction date range. Multiple daily runs are allowed, but they must happen sequentially because only one allocation run can be active at a time.

The 2026.2 release material describes this change; the SuiteApp version governing this workflow is 1.2.0. For broader grants context, see the grant indirect costs and allocation runs overview.

For finance managers, the practical consequence is a handoff to manage: identify who launches processing, who reviews it, and who takes over when the primary operator is unavailable. These are recommended workflow responsibilities, not assertions about which NetSuite roles have access.

Before upgrading: finish pending allocations and record processed dates

Existing accounts with Indirect Cost Allocation for Grants must request the upgrade through NetSuite Customer Support. Before upgrading, finish allocations for all pending eligible transactions using the currently installed SuiteApp version.

Treat this as a transition boundary, not merely an installation task. The old version’s processed transaction dates matter when choosing dates after the upgrade. Keeping that record is a recommended control, not an additional SuiteApp setup requirement.

Use this transition checklist:

  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.
  6. Verify access for intended operators rather than assuming a particular role can generate allocations.

The distinction between completing the backlog and retaining the date record matters. Finishing pending work satisfies the pre-upgrade allocation requirement; it does not make those historical dates safe to reselect. Selecting date ranges already processed under an older SuiteApp version can generate duplicate allocations.

If your operating notes describe earlier grants behavior, use the earlier grants indirect cost allocation enhancements as background, but update the current checklist for the 1.2.0 manual workflow.

How to generate and review a manual allocation run

Start with the transactions you intend to consider, then translate that scope into both segment selections and dates. Neither control substitutes for the other. Correct dates with an overly broad segment selection can describe a different run than intended; correct segment values with the wrong dates can do the same.

1. Open the generation page and choose segment values

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

Use these controls to define the run:

Field or option Selection or behavior
Allocation Segment Values Choose All Values or Select Values.
All Values Includes all available allocation segment values.
Select Values Includes the specific allocation segment values you choose.
Start Date Required; transactions on this date are included for consideration.
End Date Required; transactions on this date are included for consideration.

For a restricted segment scope:

  1. Choose Select Values.
  2. Click Select Values to open the Select Allocation Segment Values window.
  3. Move the required entries into the Selected Values list.
  4. Click Apply.

Review the selection before proceeding, particularly when different operators handle different allocation scopes. All Values means every available allocation segment value, not merely the subset an operator intended to process.

2. Enter and check both transaction dates

Complete Start Date and End Date. The range is inclusive: transactions dated on either boundary, and dates between those boundaries, are included for consideration.

These are transaction-date filters, not simply a record of when you launch processing. A run performed today can therefore cover a different transaction period.

Compare the proposed dates with the retained pre-upgrade processing record. If the window includes dates processed under the older version, do not assume the updated workflow’s duplicate exclusion will protect the run. Check the entire range, not just its starting date or its most recent portion.

3. Generate the run and wait for completion

Before submitting:

  1. Confirm that another allocation run is not active.
  2. Recheck Allocation Segment Values, Start Date, and End Date against the intended scope.
  3. Click Generate.
  4. Wait for the run to finish before starting another.

The SuiteApp processes matching source transactions and excludes costs that already have an indirect cost allocation. Keep the separate warning about older-version date ranges in view when applying that behavior.

Multiple runs per day do not mean concurrent processing. If two accountants share the work, agree who owns the next run rather than having each person independently start processing. A recommended handoff includes the intended segment scope and transaction dates so the next operator knows what was submitted.

4. Review status and results

Submitting a run is not the same as confirming its outcome. Include review as an explicit final step:

  1. Review the run’s processing status on Indirect Cost Allocations > Generate Indirect Cost Allocations.
  2. In the Results column, click View for the relevant run.
  3. Compare the outcome with the intended segment scope and transaction period.
  4. As a recommended control, retain the reviewed date range and identify whether it was processed before or after the upgrade.

Do not treat every source transaction within the chosen dates as a promise of a new allocation. The dates determine which transactions are considered, while updated processing excludes costs that already have an indirect cost allocation.

Teams revising older operating procedures can also use the manual indirect cost allocations overview for background, while keeping the steps and upgrade boundary explicit in the current checklist.

Worked example: the first post-upgrade run

This hypothetical example illustrates a date-boundary check; it is not an additional SuiteApp requirement. Assume the retained record shows that the older version processed transactions through September 30, 2026, and the intended new run covers October 2026.

Checklist item Example selection or action
Legacy processing record Older SuiteApp version processed transactions through September 30, 2026.
Allocation Segment Values All Values, assuming that matches the intended scope.
Start Date October 1, 2026.
End Date October 31, 2026.
Before generation Confirm the range excludes legacy dates and no run is active.
Start processing Click Generate and wait for completion.
Review Check status, then click View in the Results column.

Compare the results with the intended segment scope and October transaction period before considering the task complete.

This example deliberately starts after the recorded legacy period. It does not imply that every run in the updated workflow must use a completely separate date window. The important distinction is whether the earlier processing occurred under the older or updated version.

Can overlapping date ranges cause duplicate allocations?

The answer depends on which version processed the earlier range. In the updated workflow, overlapping date ranges are supported, and costs that already have an indirect cost allocation are excluded. A subsequent run therefore does not have to use an entirely separate transaction-date window.

Do not extend that behavior into a blanket assumption about historical processing. Selecting ranges processed using an older SuiteApp version can generate duplicate allocations.

Proposed date selection Documented behavior or warning Recommended check
Range not previously processed Only matching transactions are considered. Confirm segment scope and transaction dates.
Range overlapping a run in the updated workflow Overlap is supported; already allocated costs are excluded. Review the earlier run and the new intended scope.
Range processed under an older SuiteApp version Duplicate allocations can be generated. Avoid reselecting legacy dates; check retained processing records.

Expanding the worked example’s October range backward into September would cross its recorded legacy boundary. The October portion does not make the combined range safe. Review both inclusive boundaries and all dates between them before generating.

A useful operating record therefore distinguishes legacy processing from updated-version processing. A list of dates without that distinction loses the context needed to apply the duplicate warning correctly.

FAQ

Can allocations still run on a schedule in SuiteApp 1.2.0?

No. Version 1.2.0 replaces scheduled generation with user-initiated manual runs. Multiple runs per day are supported, but only one can be active at a time.

Are Start Date and End Date inclusive?

Yes. Both fields are required. Transactions dated on either boundary, as well as dates between them, are included for consideration.

Does completing the pre-upgrade backlog prevent historical duplicates?

No. Completing pending eligible allocations is required before upgrading, but selecting ranges processed under the older version afterward can still generate duplicates. Retain those processed ranges as a recommended control and avoid reselecting them.

Related reading