Power BI guide
If your Power BI YTD sales or fiscal year-to-date figures restart in January, the measure is using calendar-year logic. The fix is a marked Date table plus a YTD measure that passes the correct fiscal year-end date.
Updated June 2026 by Matty Hatton, founder of Digital Adaption.
For fiscal YTD Power BI measures, use TOTALYTD or DATESYTD with the fiscal year-end argument. October-September years use "09-30". April-March UK financial years use "03-31". The Date table must also have matching fiscal year and fiscal month fields.
Start with a base measure, then wrap it in TOTALYTD with the right year-end date.
Sales Amount =
SUM('Sales'[SalesAmount])
Fiscal YTD Sales =
TOTALYTD(
[Sales Amount],
'Date'[Date],
"09-30"
)That example is for an October-September financial year. For an April-March UK fiscal year, change the third argument to "03-31".
Most broken fiscal YTD reports have one of these problems:
| Financial year | Power BI year-end argument | Common use |
|---|---|---|
| October to September | "09-30" | Education, charities, public-sector reporting |
| April to March | "03-31" | UK financial-year reporting |
| July to June | "06-30" | Some global and academic reporting cycles |
| January to December | omit the argument | Calendar-year reporting only |
For more control, use CALCULATE with DATESYTD. This makes the filter behaviour easier to extend for prior-year, variance, and rolling-period measures.
Fiscal YTD Sales =
CALCULATE(
[Sales Amount],
DATESYTD('Date'[Date], "09-30")
)If the fiscal YTD measure is right but the visual still looks wrong, fix Power BI month sorting. If the Date table itself is missing fiscal columns, start with the full fiscal year Power BI guide. If the issue comes from inconsistent transaction dates, old ERP extracts or fields that changed during a system move, review post ERP go-live reporting rescue, data management support and the ERP Data Migration Readiness Review before adding more report logic.
Fiscal YTD means year-to-date based on the organisation's financial year, not the calendar year. For an October-September year, the YTD period starts on 1 October and resets after 30 September.
The common cause is a TOTALYTD measure with no fiscal year-end argument. Power BI then assumes a calendar year and restarts the calculation in January.
Yes. Use TOTALYTD([Measure], 'Date'[Date], "03-31") for an April-March UK financial year, supported by a proper Date table.
If TOTALYTD uses the right fiscal year-end but finance, ERP and Power BI totals still disagree, the DAX is probably exposing a source-data, ownership or reconciliation problem. Use post ERP go-live reporting rescue to trace the mismatch before adding more measures.
Digital Adaption reviews Power BI models for UK SMEs, including fiscal calendars, YTD measures, month sorting, and dashboard trust issues. When the YTD issue is caused by bad source dates, weak master data or a system change, the next step is a data management review or migration readiness check.
Book a Power BI reviewA fiscal YTD measure is only the visible symptom. If finance, ERP extracts and Power BI disagree after go-live, use the reporting rescue route. If the mismatch is appearing before an ERP or finance-system migration, use the readiness review before cutover.
View reporting rescue Check migration readiness
If the DAX pattern is only one symptom and the real issue is reporting trust, start with a Power BI Reporting Trust Review. I trace the model, source data, fiscal logic and reconciliation checks before rebuilding dashboards.
View Power BI consultant UK View reporting rescue
Matty Hatton is the founder of Digital Adaption, an ERP and data consultancy based on the Wirral. He has spent 15 years delivering ERP transformations for manufacturers, including leading the data migration on a £4.5m consolidation of four legacy systems onto a single Infor LN cloud instance for a 220-user group. He holds an MSc in Digital Transformation and IT Strategy from Manchester Metropolitan University and is Microsoft PL-200 certified.
Start with a 30-minute data risk call