--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Fiscal calendar support for targets # Fiscal calendar support for targets {#ariaid-title1} Release version: Australia Updated October 28, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Fiscal calendar support for targets This feature enables targets in ServiceNow to align their check-in frequencies with the fiscal calendar periods of your organization rather than the standard Gregorian calendar. The fiscal calendar mode affects how targets break down their values and how check-in frequencies are presented and managed system-wide. Show full answer Show less ## Key Features * **Calendar Mode Configuration:** The calendar mode is configured via the `sngfa.calendartype` system property, which can be set to *gregorian* or *fiscal*. If unset, Gregorian is the default. * **Fiscal Calendar Types Supported:** Includes standard fiscal calendars, 13-period calendars, and 4-4-5 calendars, each supporting different check-in frequencies. * **Check-in Frequencies in Fiscal Mode:** * Yearly aligns to the fiscal year. * Quarterly aligns to fiscal quarters or 4-4-5 quarters. * Monthly aligns to fiscal months. * Period aligns to quad weeks (13-period) or 4-4-5 periods. * Weekly appears if the fiscal calendar generates weeks. * **Default Frequencies:** * In fiscal mode, new targets default to the most detailed supported frequency (e.g., monthly for standard fiscal, period for 13-period or 4-4-5). * In Gregorian mode, new targets do not default to any frequency. * **Handling Stale Targets:** Changing calendar modes can cause targets with existing breakdowns to become stale if breakdowns no longer match the calendar. Stale targets can be recovered by resetting or duplicating them (duplication excludes remarks, work notes, and history). * **Validation and Restrictions:** Targets cannot be saved and breakdowns cannot be generated if the fiscal calendar has gaps, overlaps, or missing parent periods within the target's date range for the selected frequency. Users receive clear messages guiding them to resolve these issues by adjusting frequencies, dates, or contacting administrators. ## Practical Implications for ServiceNow Customers By enabling fiscal calendar support, customers can synchronize target tracking and performance measurement with their organization's financial periods, providing more relevant insights and reporting aligned to business cycles. This capability requires system-wide configuration and careful management of calendar data to ensure accuracy and prevent stale targets. Understanding the supported check-in frequencies and calendar types is essential for setting up targets effectively. With fiscal calendar support, the check-in frequency of a target follows the fiscal periods of your organization instead of the Gregorian calendar. Targets can break down their values by Gregorian periods or by the periods of a fiscal calendar. The calendar mode is set for the whole instance. When the mode is fiscal, the form displays the check-in frequencies that the calendar type supports, and the breakdowns that a target generates follow the fiscal periods. ## How the calendar mode is set {#fiscal-calendar-support-targets__how-the-calendar-mode-is-set} The calendar mode is stored in the sn_gfa.calendar_type system property. The value is `gregorian` or `fiscal`. If the property is not set, the mode is Gregorian. The sn_gfa.calendar_type system property is separate from the older sn_gf.goal_calendar_type system property. Changing the calendar mode can make targets with breakdowns stale when their stored breakdowns no longer match the calendar, even when their check-in frequency is supported by both calendars. A stale target can be recovered by running the reset job or by duplicating the target. The copy doesn't include the remarks, work notes, or history of the stale target. For more information, see [Stale targets](https://www.servicenow.com/docs/wx6aJLRs94klEzcw85xI9w "A target with breakdowns becomes stale when its stored breakdowns no longer match the goal calendar. A stale target can't be changed until its check-in frequency is cleared."). ## Check-in frequencies in fiscal mode {#fiscal-calendar-support-targets__check-in-frequencies-in-fiscal-mode} In fiscal mode, the form displays only the check-in frequencies that the fiscal calendar type supports. Each frequency maps to a fiscal period type: * Yearly maps to the fiscal year. * Quarterly maps to a fiscal quarter. In a 4-4-5 calendar, it maps to the 4-4-5 quarter. * Monthly maps to a fiscal month. * Period maps to a quad week in a 13-period calendar, or to a 4-4-5 period in a 4-4-5 calendar. The calendar type decides which frequencies are displayed: * A standard fiscal calendar displays yearly, quarterly, and monthly. * A 13-period calendar displays yearly and period. * A 4-4-5 calendar displays yearly, quarterly, and period. Weekly is displayed for any fiscal calendar that generates weeks. In fiscal mode, a new target defaults to the most detailed check-in frequency that the fiscal calendar provides, excluding weekly. For a standard fiscal calendar, the default is monthly. For a 13-period or 4-4-5 calendar, the default is period. In Gregorian mode, a new target has no default frequency. ## When saving and breakdown generation are blocked {#fiscal-calendar-support-targets__when-saving-and-breakdown-generation-are-blocked} All check-in frequencies that the calendar type supports are always displayed. The fiscal calendar must fully cover the start and end dates of the target at every level of the selected frequency. If the calendar has a gap or an overlap in the target's date range, or if a parent period is missing, the target can't be saved with that frequency, and its breakdowns aren't generated. When a save is blocked, the user sees a message that explains the cause. Depending on the cause, the message asks the user to choose a different frequency, to adjust the target dates, or to contact the administrator. **Related concepts** * [Managing stale targets](https://www.servicenow.com/docs/93uzOU87kotKRDG9_c6Zww "Understand which targets become stale after a goal calendar change, and how to recover them.") * [Setting a goal calendar](https://www.servicenow.com/docs/8AlajWPKuv1qUBY~LJAInQ "The goal calendar decides which periods your targets use for their check-in frequency and breakdowns. You can use the Gregorian calendar or a fiscal calendar.") **Related tasks** * [Duplicate a goal or target](https://www.servicenow.com/docs/m1j62Y8O_Z4aNH0cW7JnUg "Create a copy of an existing goal or target to align goals with your organizational strategic priorities. If the goal or target you want to create is similar to an existing one, duplicating the existing record saves your time.") **Related reference** * [Check-in frequency values](https://www.servicenow.com/docs/8iwKOqJJGyFTGgBnECz6VA "The check-in frequency of a target sets how often its actual value must be updated. This reference lists each value and when it is displayed on the target form.")