Fiscal-year vs calendar-year date attributes (CY/FY) in Allocadia

Allocadia exposes both fiscal-year and calendar-year date attributes so reports can slice by whichever matches your reporting cadence.

Why both exist

Many organizations plan on a fiscal year that doesn't align with the calendar year — e.g. February–January, July–June. Finance and marketing teams often need to report in both cadences:

• CY (calendar year) — Jan–Dec. Used for calendar-aligned reporting, external benchmarks, and some tax/finance views.
• FY (fiscal year) — your organization's custom fiscal year. Used for internal plan vs actual, budget cycles, and most Allocadia operational reporting.

Allocadia exposes both so you can filter or group reports by whichever is relevant for the audience.

Where CY/FY attributes live

The fydate dataset in GoodData is the primary date dimension. It exposes year, quarter, and month at both CY and FY levels:

• CY Year, CY Quarter, CY Month
• FY Year, FY Quarter, FY Month

Similar CY/FY attributes exist on other date dimensions — PO Line End Date, Transfer Decision Date (V8+), and others.

Choosing which to use

• Grouping a report by FY Year = your fiscal year total.
• Grouping by CY Year = calendar-year total.
• Filtering FY = This Year or CY = This Year scopes the report to the current fiscal or calendar year.

For most Allocadia operational reporting (plan vs actual, variance), FY is the right choice. CY is useful for external-facing reporting or when stakeholders expect calendar months.

Fiscal-year start month

Your fiscal year's start month is configured at the account level. All FY attributes derive from that setting — if your account rolls over in February, FY1 is February and FY12 is January.

Related articles

• The GoodData data table — attributes and facts available in Allocadia
• Custom reports and MAQL basics in Allocadia
• What changes during a fiscal-year rollover in Allocadia, and what doesn't?
• Fiscal-year rollovers in Allocadia — what's included and what's not