Tag not monitored by Microsoft.
The error indicates that the dates in the deferral schedule do not fit within the accounting/accrual periods that are set up for the company. To resolve this, the setup of periods must be corrected so that the full range of dates used by the deferral schedule is covered.
Use the following checks and corrections (adapted from similar accrual/deferral period issues):
- Verify accounting/accrual periods cover all needed years
- Open the setup page where accounting or accrual periods are defined for the company (for example, fiscal periods, accrual periods, or deferral periods depending on the module being used).
- Ensure that at least the previous year, current year, and upcoming year are fully defined.
- Confirm that the deferral start and end dates for the transaction fall within one of these defined periods.
- Check for missing, overlapping, or duplicated dates in period setup
- For each period definition, verify that:
- There are no gaps between period end and the next period start.
- No dates are skipped within the year (for example, the last period must run through the final day of the year, such as December 31).
- No dates appear in more than one period.
- Correct any missing, overlapping, or duplicated dates and save the setup.
- For each period definition, verify that:
- Confirm all period types are set up, even if not used
- If the system supports multiple period frequencies (weekly, biweekly, semimonthly, monthly, etc.), ensure that all relevant period types are fully set up for the entire year.
- Even if only one frequency is actively used, incomplete setup in other period types can still cause errors in some configurations.
- Re-check the deferral schedule dates
- Open the specific deferral schedule that is failing.
- Confirm that the schedule’s start date and end date are within the defined accounting/accrual periods.
- If necessary, adjust the deferral start date or template so that the calculated schedule does not extend beyond the last defined period.
- Retry the operation
- After correcting the period setup and/or deferral schedule dates, run the same action again (for example, transforming the invoice or validating the deferral code) and confirm that the error no longer occurs.
If the deferral schedule still fails after these checks, review any customizations (such as the iSAMS-related tables and pages in the call stack) to ensure they are not generating deferral dates outside the configured periods.
References: