Power BI compatibility

The engine calculates. Power BI renders. The numbers always agree.

One set of numbers, not two. The engine is the single calculation authority; it builds the Power BI dataset from the same figures shown on screen, so the board report cannot drift from the engine.

One calculation authority

A report is only as trustworthy as the calculation behind it. Here the calculation happens once, in the engine; Power BI is the surface it is drawn on. The dataset is generated from that same output, so the two cannot disagree by being computed twice.

What the export gives your team

  • A Power BI-ready dataset: dimension tables for people, organisation and period, and fact tables for the measures, with a metric dimension that carries each metric’s definition.
  • Measures that match the engine: the DAX in the supplied template reads the engine’s figures, it does not recalculate them independently.
  • Your own pages on top: analysts can extend the report with their own visuals and slicers without changing the underlying numbers.

It stays yours

The export is a file. Nothing leaves this site. Your team opens it in Power BI Desktop, or publishes it to your own workspace, on your own controls.

Absence days per employee, by departmentMeridian Bank - demo data036912org avg 7.49.2Retail7.8Ops5.1Finance4.6Tech6.3HR11.4ContactContact Centre: 2.5x the Finance rate
Absence days by department
Absence rate (%), rolling 12 monthsMeridian Bank - demo data0%2%4%6%8%target 5%JFMAMJJASOND6.4% peak
Twelve-month absence trend
Workforce by contract typeMeridian Bank - demo data1,284peoplePermanent78%Fixed-term12%Contractor6%Casual4%Stable core: 78% permanent
Workforce by contract type
Attrition (bars) vs headcount (line)Meridian Bank - demo dataattr %HC
Attrition against headcount

Rendered in the site theme; figures are synthetic Meridian Bank demo data. Real Power BI captures are being re-taken in the report theme.