How does iDBQuery handle a fiscal year or custom business calendar?
iDBQuery can report by your fiscal calendar rather than the standard January–December year once you tell it your fiscal setup — for example a year starting in April, or 4-4-5 periods. Define it in the semantic layer and "Q1" or "this fiscal year" resolves to your periods, with every figure cited to source.
Many organisations don't run on the calendar year, and getting "Q3" wrong by a quarter makes a report useless. iDBQuery adapts to your fiscal setup.
- Your definition. Record your fiscal year start and period structure — a July start, a 4-4-5 retail calendar, custom quarters — in the semantic layer or business glossary.
- Consistent interpretation. From then on, "this quarter", "last fiscal year", or "YTD" map to your periods, not the default calendar, across every question and dashboard.
- Standard calendar by default. Absent a fiscal definition, iDBQuery uses ordinary calendar periods and is explicit about the boundaries it used.
This is essential for finance and FP&A work, where budgets, close, and board reporting all run on the fiscal calendar. Because iDBQuery shows the SQL and cites the exact rows, you can confirm that "Q1 revenue" covers April–June if that's your year — not January–March. Defining the calendar once means the whole team's answers align to the same periods, removing a classic source of reports that don't reconcile.
Updated 2026-06-22