Restriction and Automation Rules Governing Accounting Period Changes
When you add, delete, or modify accounting periods, NetSuite attempts to adjust the rollup hierarchy across all fiscal calendars and prevent creating standalone periods. Restriction and automation rules run in the background to simplify managing accounting periods though preserving the integrity of the accounting period structure.
Modifying an accounting period is generally prohibited if doing so removes an existing parent/child without reestablishing a new one.
When you create, update, or delete base or aggregate periods, NetSuite automatically attempts to find the logical parent for a period in the accounting period rollup and across all existing fiscal calendars to prevent creating a standalone period.
-
If one or more aggregate periods exist for the date range, NetSuite assigns the new period to the lowest level aggregate period available, unless you specify a parent.
-
You can make changes in a hierarchy such deleting a period, as long as a suitable parent exists for all periods in the hierarchy. If no logical parent exists, you cannot make the change.
You are restricted from making a change if the change disrupts the accounting period rollup. The general rules that affect rollups are:
-
A base period must have at least one aggregate level period or parent
-
Aggregate periods are the parents for subperiods
-
A base period has multiple parents, one in each fiscal calendar context
-
A subperiod can be a base period or another aggregate period
-
All base periods must have at least one parent
-
Parent and child periods roll up into fiscal years for each fiscal calendar