Bring comparisons together
Review actuals, budget, forecast and prior year in one financial matrix.
Aivana Financial Reporting · Financial matrix & comments
Financial analysis in Power BI: compare figures and explain variances clearly.
Compare financial results and explain variances. Bring actuals, budget, forecast and prior-year figures together in a structured financial matrix.
For controlling, finance and management.
Package availability, trial duration and licence terms are agreed with Aivana. Validate the visual in your Power BI environment before deployment.
What you can evaluate with your team
Discuss variances
Identify absolute and percentage differences in the report context.
Attach explanations
Link comments to filters and business keys; plan for Fabric SQL when persistence is needed.
What the visual offers
- Actuals, budget, forecast and prior year in one view
- Absolute and percentage variances
- Comments linked to report filters and business keys
- Persistent comments with an additional Fabric SQL integration
Power BI financial matrix with comments: How do I keep the context clear?
Financial Reporting combines financial comparisons and business explanations. Before the first monthly review, define the combination of line item, period and report filters that uniquely identifies a comment.
- Prepare the matrix: compare actuals, budget, forecast and prior year on the same period basis and check the business keys used.
- Check a comment: explain a known variance, change the period or organization filter and verify its business context. An explanation for one month should not be assumed to apply to another.
- Check storage: configure the additional Fabric SQL integration for the next review and test reloading in the same report context. Importing the visual does not automatically configure persistent storage.
From data to a decision
A connected workflow in four steps
- 01
Bring comparison versions together
Map actuals, budget, forecast and prior year to a financial matrix.
Result: A shared starting point for the financial review.
Requirement / boundary: Comparable periods and measures must be available in the model.
- 02
Review a variance
Compare absolute and percentage differences in the selected report context.
Result: The relevant line items can be discussed directly.
Requirement / boundary: A variance does not explain its cause; review the business context.
- 03
Attach an explanation
Comment on the variance in the context of report filters and business keys.
Result: The figure and its explanation share a business context.
Requirement / boundary: Unique keys and appropriate filters are required.
- 04
Use the explanation in the next review
Configure the additional Fabric SQL integration for persistent comments and verify their context.
Result: With the integration configured, explanations can be stored persistently.
Requirement / boundary: Persistence is not automatically included when importing the visual.
Fictional application scenario
How the steps connect in practice
A fictional controlling team reviews a cost line that differs from budget. It compares actuals, forecast and prior year in the same period context and adds a business explanation. The explanation is associated with business keys and filters. To keep it available for the next review, the team configures the additional Fabric SQL integration and verifies storage.
Trial and installation
- Select this product in the trial form and check package availability.
- Once released, request the download link by email and follow the package setup instructions.
- If an approved .pbiviz package is supplied, import it as a custom visual in Power BI Desktop and assign your report fields.
Requirements and boundaries
Supply actual, budget, forecast and prior-year financial measures with consistent periods and business keys. Report filters and keys must identify the business context of comments. Persistent storage requires a separately configured Fabric SQL integration.
Documented V1 scope: financial matrix and comments. Persistent comments require separately configured Fabric SQL. Planning and writeback are extension points; package metadata, certificates and tenant permissions need configuration before deployment.
Validate functionality in the intended Power BI host before deployment. Check your tenant policies, permissions and package instructions before using the visual in your environment.
Frequently asked questions
How do I add Aivana Financial Reporting to Power BI?
When an approved .pbiviz package is available, import it as a custom visual in Power BI Desktop. Follow the package instructions and assign your report fields. Validate functionality in the intended Power BI host before deployment.
What data does the visual use and what are its limitations?
Documented V1 scope: financial matrix and comments. Persistent comments require separately configured Fabric SQL. Planning and writeback are extension points; package metadata, certificates and tenant permissions need configuration before deployment.
How can I get the trial for Aivana Financial Reporting?
Open the trial form with this product preselected. Once the package is approved and available, you can request the download link and setup instructions by email.
What does the visual cost and which licence fits our team?
Contact Aivana for pricing, licence scope, trial duration and package availability. Describe your use case and Power BI environment so we can agree the next steps.
How do I prepare data and setup?
Supply actual, budget, forecast and prior-year financial measures with consistent periods and business keys. Report filters and keys must identify the business context of comments. Persistent storage requires a separately configured Fabric SQL integration.
Explore it with your own data
Request the trial when available. Contact Aivana to discuss your data model, setup support, licence terms and trial duration.