Gregorian Year
Gregorian Year is the standard calendar year as defined by the Gregorian calendar, the civil calendar used worldwide since 1582 and the default fiscal-year basis for any Salesforce organization that has not configured a Custom Fiscal Year.
Definition
Gregorian Year is the standard calendar year as defined by the Gregorian calendar, the civil calendar used worldwide since 1582 and the default fiscal-year basis for any Salesforce organization that has not configured a Custom Fiscal Year. In Salesforce, a Gregorian-year-based fiscal year runs January 1 through December 31, with quarters Q1 (Jan-Mar), Q2 (Apr-Jun), Q3 (Jul-Sep), and Q4 (Oct-Dec). Date math inside formulas, reports, forecasts, and dashboards all default to Gregorian year arithmetic.
Salesforce explicitly calls out Gregorian Year as the alternative to Standard Fiscal Year (which uses a customizable start month while still aligning to four-quarter calendar weeks) and Custom Fiscal Year (which lets admins define arbitrary period structures). When an org uses a Gregorian fiscal year, the YEAR() formula function, the THIS_FISCAL_YEAR report filter, and the Collaborative Forecasts period grid all snap to January 1 as the first day of the year. Switching from Gregorian to a custom fiscal year is a one-way change with significant downstream impact and is rarely undertaken lightly.
Why Salesforce treats Gregorian Year as the baseline
Default behavior in a fresh org
A new Salesforce organization starts with the fiscal year set to Gregorian Year. This means the fiscal year begins January 1, ends December 31, and the four quarters fall on the natural calendar boundaries. Reports filtered by THIS_FISCAL_YEAR return the same records as filtered by CALENDAR_YEAR(Today). Most B2C and small-business orgs never change this setting.
How Gregorian differs from Standard Fiscal Year
Standard Fiscal Year lets the admin pick a start month other than January while still using calendar-aligned weeks and 4-4-5 or 5-4-4 period structures. The fiscal year still has 12 months and 4 quarters, but they no longer align with Gregorian boundaries. For example, a Standard Fiscal Year starting February 1 has Q1 spanning Feb-Mar-Apr. Forecast periods, fiscal-year report filters, and dashboards all use this non-Gregorian schedule once the setting is changed.
Custom Fiscal Year and retail calendars
Custom Fiscal Year lets admins define arbitrary periods, including 13-period years used in retail (the 4-4-5, 4-5-4, or 5-4-4 patterns), 52-or-53-week years, and other irregular structures. Custom Fiscal Year requires explicit period-by-period configuration in Setup. Once enabled, the standard Gregorian arithmetic in formulas still works (YEAR(CloseDate) returns the calendar year), but Salesforce''s built-in fiscal report filters use the custom periods.
Formula functions and Gregorian assumptions
Most Salesforce formula functions assume Gregorian arithmetic regardless of fiscal-year settings. YEAR(date) returns the four-digit Gregorian year. MONTH(date) returns 1-12. DATE(year, month, day) constructs a date in the Gregorian calendar. The functions do not care about the org''s fiscal-year configuration; they always speak Gregorian. Mixing fiscal-year report filters with formula functions that use Gregorian math is a common source of misaligned reporting.
Forecasts and the period boundary
Collaborative Forecasts uses the org''s fiscal-year settings to decide period boundaries. With Gregorian Year, the forecast grid shows months that match calendar months. Switching to a Standard or Custom Fiscal Year recomputes every period boundary immediately and can move opportunities from one period to another mid-quarter. Plan any fiscal-year change for a clean break (start of a new year) to avoid this kind of disruption.
One-way settings change
Switching from Gregorian Year to a non-Gregorian fiscal year is supported under Setup, Fiscal Year. The reverse (going back to Gregorian Year after enabling Custom Fiscal Year) is also supported but more disruptive: existing custom-period definitions are deleted and any custom-period-aware reports break. Document the change before flipping the switch.
International alignment
The Gregorian calendar is the international civil calendar standard. Customer-facing communication, contract dates, and most accounting integrations expect Gregorian semantics. Salesforce stores Date and Datetime values in Gregorian terms in the database regardless of the org''s fiscal-year setting, so the term Gregorian Year shows up most often as a clarification that the org is using the platform''s default behavior.
Confirm or change the fiscal year setting
The fiscal-year setting is one of the platform''s most under-discussed configuration choices. Verifying the current setting takes 30 seconds.
- Open Setup, Fiscal Year
Setup, Quick Find, type Fiscal Year, click the result. The page shows the current fiscal-year structure.
- Confirm the setting
Gregorian Year is the default. The page shows the current setting at the top with a Change link next to it.
- Decide whether a change is needed
Most orgs leave it on Gregorian Year. Change only when finance or operations require a non-calendar fiscal year, such as a February-start corporate calendar.
- Plan the change for January 1
Pick a date that aligns with a fresh fiscal period start. Mid-quarter changes cause downstream report and forecast disruption.
- Run regression tests
After changing, verify standard reports (THIS_FISCAL_YEAR filters), forecast grids, and any custom Apex that references fiscal-year functions still return expected values.
- Formula functions ignore the fiscal-year setting. YEAR(date) always returns the Gregorian year regardless of the org configuration.
- Switching from Gregorian to Custom Fiscal Year is supported but rare; document the rationale before flipping the switch.
- Reverting from Custom Fiscal Year to Gregorian deletes the custom period definitions and breaks any reports that referenced them.
- Collaborative Forecasts immediately recomputes period boundaries when fiscal-year settings change. Plan the change for January 1 to avoid mid-quarter chaos.
Trust & references
Cross-checked against the following references.
- About Fiscal YearsSalesforce Help
- Fiscal Year OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Gregorian Year.
- Set the Fiscal YearSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Gregorian Year in Salesforce?
Q2. When should you use Gregorian Year?
Q3. What's the alternative for non-January fiscal years?
Discussion
Loading discussion…