Almadar A dashboard built for a finance team in Al Olaya looks fine until someone in a KAFD board meeting asks a question the underlying model was never designed to answer.
The visible part of Power BI, the charts and dashboards, is the smallest part of the work. The data model underneath, how tables relate, how measures are defined, how time intelligence handles Hijri and Gregorian calendars side by side, determines whether the numbers a board sees are trustworthy. We build the model first and treat visualization as the final, relatively quick step.
Connecting to Saudi financial systems
Power BI connects to most ERP platforms, SAP, Oracle, Dynamics, Odoo, either directly or through a data warehouse layer. For Riyadh businesses the practical question is usually how to bring in Arabic-labeled master data cleanly and how to handle multi-entity consolidation where entities report in different currencies or on different chart of accounts structures, which is a design decision made once and then relied upon by every report built afterward.
Measures, not just visuals
A well-built model defines business logic once, in DAX measures, so that gross margin means the same thing on the CFO's dashboard and in the sales report. Where measures are instead recalculated inconsistently report by report, numbers quietly disagree, and the resulting loss of trust in the reporting is far more damaging than any missing visual would be.
Governance and workspace structure
As Power BI usage grows past a handful of reports, workspace structure, access permissions and a naming convention stop being administrative details and start determining whether people can find and trust the right report. We set this up deliberately from the start rather than letting it accumulate organically into the sprawl we are frequently called in to untangle.
A common Saudi scenario
A Riyadh group has forty disconnected Power BI reports built by different people over three years, several answering the same question with different numbers because each was built on its own disconnected extract. We consolidate onto a single governed data model with one definition of revenue, one of margin, and retire the reports that duplicated it, cutting confusion rather than the number of dashboards.
Bilingual reporting
Power BI supports Arabic labels, right-to-left layout and dual-language reports from the same model, which matters directly for boards and staff who work primarily in Arabic. This is a deliberate build decision, not a default, and it connects to the same underlying discipline as Arabic financial statement configuration.
Row-level security for sensitive figures
Not every user should see every entity's margin or every region's headcount. Power BI supports row-level security that filters what each user sees from the same report, which matters directly for a Riyadh group where a regional manager should see their own performance without seeing a competitor entity's, or where salary-linked figures need restricting to HR and finance leadership only. This is a design decision made during modeling, and it connects to the same access discipline as data governance more broadly.
Businesses already standardized on Microsoft 365 get the fastest and cheapest path to Power BI given licensing overlap, while those on Google Workspace or a mixed technology stack should weigh Power BI against Tableau on platform fit rather than defaulting.