BI financial analysis best practices: Use finance-approved figures with defined periods and data cutoffs; Break variances into groups like product, customer type or location; Check refresh paths and storage modes in Power BI (Import, DirectQuery, etc.)
Image: Business Insight Stack

Dashboard Design

Financial performance analysis in BI

Structure finance BI views around approved figures, comparable periods, explainable variances and visible reporting limits.

Financial performance analysis in business intelligence (BI) should explain a result and indicate what to investigate next. Start with finance-approved figures, a defined period and a visible data cutoff. Compare like with like, then trace material differences back to the records.

Establish the comparison

Name the decision the report supports. A finance lead reviewing a closed month may need to explain revenue against budget and identify where margin changed. A manager reviewing weekly trading may need a narrower view. Related data can serve both decisions, but periods and measures must be labelled for each.

For every measure, state the entity, population, accounting period, currency, calculation and owner. Name the reference used for comparison: budget, an earlier period or another approved figure. Show underlying amounts beside percentage movements, particularly when the base is small.

ViewQuestion it answersQualification to show
RevenueWhere did the recognised amount change?Revenue basis, period and close status
MarginDid revenue or the defined cost base drive the change?Included costs and treatment of shared costs
ExpensesWhich categories changed against the reference?Reclassifications and accruals affecting comparability
Cash receiptsDoes collection timing need attention?Receipt definition and cutoff

Label recognised revenue and cash receipts separately. For contracts within AASB 15, revenue is recognised when or as the relevant performance obligation is satisfied; payment alone does not set its period. Finance must approve the treatment of the transactions being reported.

Key Financial Metrics: Revenue vs. Margin vs. Expenses

Revenue
Recognised when performance obligations are satisfied under AASB 15
Margin
Driven by revenue or cost base; shared costs must be clearly treated
Expenses
Reclassifications and accruals affect comparability; must be disclosed

Explain a variance

Begin with a total that agrees with an approved finance reference for the same entity, period and currency. Break a material movement into useful groups, such as product, customer type or location. Show each group's amount and contribution to the movement. A matching total can conceal offsetting errors, so inspect the groups and relevant underlying records.

Treat possible drivers as questions until the data supports them. A revenue increase might reflect quantity, price, product mix or a correction posted after the earlier extract. Attributing the movement requires comparable inputs across periods. If those inputs are absent, describe the movement without assigning a cause.

Match the boundaries of budgets and actuals. A monthly budget by business unit cannot be compared fairly with daily actuals by product unless an allocation rule has been approved. Keep an unallocated line when the source does not support a finer breakdown.

Make specialised views clear

A segment view needs a membership rule, a defined margin and visible shared or unallocated costs. Reconcile its groups to the whole-business figure. An internal product or regional group is not automatically an operating segment under AASB 8, which has specific criteria and a defined reporting scope.

A recurring-versus-one-off view classifies recognised revenue under an agreed management rule. Keep ambiguous items visible and reconcile the categories to total revenue. A recurring label for a past amount is not a forecast.

For a multi-currency view, distinguish original-currency amounts, management conversions and finance-ledger amounts. Record the rate source, date, quote direction and correction rule. AASB 121 distinguishes transaction-date recognition, period-end treatment of monetary items and presentation-currency translation; one unexplained rate cannot represent every purpose.

Financial Reporting Compliance Requirements

  • 15AASB - Revenue Recognition — Performance obligation satisfaction determines recognition timing
  • 121AASB - Foreign Currency Translation — Distinguishes transaction-date, period-end and presentation-currency treatment
  • 8AASB - Operating Segments — Specific criteria required for segment reporting beyond internal groupings

Check the refresh path

A Power BI refresh can involve querying underlying data sources. It can load source data into a semantic model and update the report visuals that depend on that model. Treat these as separate checkpoints. A successful refresh at one stage does not, by itself, confirm that every stage has completed.

The storage mode changes what a refresh means. Import mode stores copied data in the semantic model and requires a source-data refresh to bring in changes. DirectQuery, Direct Lake and live connection models query the underlying source rather than importing data, so they do not use the same source-refresh process.

Before releasing a review, identify the model's storage mode and check freshness at the relevant point in its data path. If a figure is stale, establish whether the delay is in the source, the model update or the dependent visuals. Then decide whether to hold the figure or publish it with a clear limitation.

A refresh process should be checked against the report's stated cutoff, not just its completion status. The review should make clear which period and data state the released figures represent, so readers do not mistake a newer source extract for an updated result.

Pre-Release Checklist for Finance BI Reports

  • Verify data freshness at each stage of the pathSource → Semantic model → Visuals
  • Confirm storage mode and its impact on refreshImport mode requires re-import; DirectQuery queries live
  • Check that the reported cutoff matches the stated periodAvoid confusion between source extract and report update
  • Document any unallocated or ambiguous itemsEnsure transparency in reconciliation
  • Define and maintain consistent calculation rulesEnable reliable variance analysis over time

Release a usable figure

Show the latest complete period and the source and model cutoffs. In Power BI Import mode, the semantic model contains copied data until it is refreshed; a newer upstream extract alone does not update that copy. Other storage modes behave differently.

For a recurring finance review, check expected source deliveries, selected totals and breakdowns against the approved reference, and material unmatched records. Record known close adjustments.

Give each unresolved difference an owner and a reporting treatment: hold the affected figure, show a clearly limited view or retain the last accepted result with its earlier cutoff. Keep the definition used for each released period so readers can distinguish business movement from a changed calculation.

Power BI supports Import, DirectQuery, Direct Lake, live connection and push storage modes, with different data-access and refresh requirements. A refresh check should therefore follow the mode in use rather than assume every model needs data re-imported.

Steps to Release a Usable Financial Figure in Power BI

  1. Confirm latest complete period and cutoff datesVerify source and model refresh status
  2. Check storage mode (Import, DirectQuery, etc.)Adjust refresh expectations based on mode
  3. Validate against approved finance referenceMatch budgets, actuals and calculation rules
  4. Record known close adjustments and unresolved differencesAssign owners and define reporting treatment
  5. Publish with clear limitations if data is staleAvoid misleading interpretations

In this guide

  1. Tracing revenue discrepancies through BI data transformationsFind where a BI revenue difference begins by comparing an approved finance amount and contributing records at each transformation boundary.
  2. Reporting margin by a clearly defined business segmentDefine segment membership, margin costs and shared-cost treatment before comparing segment results in a finance BI report.
  3. Separating recurring and one-off revenue in a reportClassify recognised revenue under an approved recurring and one-off rule, keep ambiguous lines visible and reconcile the split to total revenue.
  4. Documenting currency conversion assumptionsRecord currency pair, rate source, date, direction and missing-rate treatment so converted BI figures can be reproduced and reconciled.

More from Dashboard Design

Dashboard Design

Comparing self-service BI with centrally managed reporting

Compare who builds reports, owns shared measures and approves distribution when selecting a BI reporting model.