Validating Tax Automation Forms
- Number of Periods - Annualize/De-Annualize can be used only with
Annualize/De-Annualize logic
In the below example, form save fails as Number of Periods - Annualize/De-Annualize is used with Pull logic:

- For Move and Prior Year logic, the Source Year must be prior to the target Year,
unless a different Source Scenario is configured
In the below example, form save fails as Source Year is not prior to the target year for the Movement Logic:

Current/Future year can be configured as Source Year only if a different Source Scenario is configured.

Note:
Ensure that the Source Scenario configured is already consolidated. - For Pull, Squeeze, Annualize, De-Annualize, National Adjustment the combination
of Source Year and/or Source Period must be prior/equal to the target Year and
Period, unless a different Source Scenario is configured
In the below example, form save fails as the combination of Source Year and Source period (FY28, P1) is not prior/equal to the combination of target year and period (FY27, P2):

Combination of Source Year and Source Period configured can be greater than the combination of target and period only when a Source Scenario is configured.

Note:
Ensure that the Source Scenario configured is already consolidated. - For Pull, Squeeze, Movement, Annualize, De-Annualize rules, if Source Account is
Tax Account, then the Source Year, or Source Period, or Source Scenario must be
different
In the below example, the form save fails because the Source Account is configured as a Tax Account, while the Source Year, Source Period, and Source Scenario are all the same as the target.

Note:
The above validations are also added as a part of data load.