Many organisations operate on a financial year that does not align to the calendar year (for example April–March, July–June, etc.).
Analysis Views currently support date compression options such as Day, Week, Month, Quarter, Period and Year. However, the "Year" compression appears to aggregate data using calendar-year boundaries rather than the company's configured accounting periods or financial year structure. This can lead to discrepancies when reporting over a financial year that spans two calendar years.
Requested Enhancement
Provide one or more of the following options:
- Financial Year Compression
- Compress Analysis View data based on the company's Accounting Period setup rather than calendar years.
- Fiscal Year Date Compression Option
- Add a new date compression type called "Financial Year" or "Fiscal Year".
- Configurable Period Boundaries
- Allow administrators to specify whether Year and Week compression should use:
- Calendar periods; or
- Accounting periods / Financial year definitions.
Business Benefits
- Accurate reporting for organisations whose financial year does not run January–December.
- Reduced need to maintain multiple Analysis Views.
- Improved performance when reporting over large datasets without requiring Day-level compression.
- Easier reconciliation between Analysis Views and General Ledger data.
- Better support for statutory and management reporting requirements across different countries and industries.
Expected Outcome
A Financial Year compressed Analysis View should return the same totals as Day, Month, Quarter and Period compressed Analysis Views when filtered for the same financial-year reporting period, while still providing the performance benefits of pre-aggregated data.