The anatomy of an income statement matrix in Power BI

This video describes the queries behind an intuitive, interactive income statement in Power BI. You can purchase the template and dataset at accountinginsi....
Trade-off between maintainability and performance
The template has a dataset of a little under 50,000 transactions. Organising the queries in the way outlined in this article produces a report that is very flexible and maintainable. Generally, in a situation where measures call other measures (as we have here), performance of the report will drop. Combining the layers of the measures will in many cases improve performance. As a development approach, I would start first by separating the measures along the lines that I have done in this template. It is easier to develop and test the report in this way. If performance is an issue, then I would recombine the layers of measures, testing as I go using the DAX Performance Analyzer.

[@MH001BR]

Hi, I just purchased your template. Can you explain how you treat the relative days in your transaction table to the actual date of the transaction. How is this mapped? Thanks.

[@AccountingInsights]

Hi @MH001BR in reality your transaction table would use the transaction date. In the template, RelativeDay is used merely to keep the demo "current". If you look at the data transformation on the Transactions table, the RelativeDay is converted into Date. In your dataset, you can remove this transformation and use the Date field. If you would like a quick call for assistance, you can book a call with me here calendly.com/hugh-accountinginsights/30min and I would be happy to help. Regards, Hugh

[@AccountingInsights]

You can purchase this template and dataset at accountinginsights.co.uk/product/power-bi-profit-and-loss-template/