
13 Jan The major drawbacks of Power BI
The big drawbacks of Power BI in financial modeling (and why it’s not a user problem).
There is a phrase that is repeated a lot in the BI world:
“With Power BI you can do it all.”
The statement is formally true, but operationally misleading, especially when we enter the realm of advanced financial modeling.
I say this because of a real and recent case: trying to build a dynamic financial matrix, with simultaneous row and column logic, context-dependent measures, and typical management calculations such as PY / CY / YTD / differences / percentage changes. In other words, exactly the kind of report that a CFO or a controller uses on a daily basis.
The result was clear: Power BI wastes far more time than necessary. And not because it is done badly, but because the tabular model is not designed for this type of hybrid reports, which are so common in finance.
Power BI is not designed for financial reporting, but for generalist analysis.
Here is the first key point.
Tools such as Mercur natively understand concepts such as:
- Accounting hierarchies
- Row templates
- Column templates
- PY / CY / YTD Logic
- Financial aggregations
- Matrix structures
- Management reports
- In Power BI, none of this exists naturally.
Everything has to be reconstructed manually: auxiliary tables, measures, relations, filters, formats, sorting and behavior of the matrix.
2. The big pain: dynamic rows + columns at the same time
In Mercur, combining row and column templates simultaneously is trivial.
In Power BI, the experience is usually this:
- A disconnected board → works
- Two tables disconnected → stops working
- One connected + one disconnected → chaos
- SWITCH within SWITCH → explosion of complexity
- Calculation Groups + multilevel matrices → resource errors
And here it should be made clear:
👉 it is not the user’s fault.
👉 is a limitation of the engine.
3. Power BI does not have a financial engine (and it shows).
In Mercur, concepts such as:
- Month
- Accumulated
- PY
- CY
- Difference
- % difference
are native concepts of the system.
In Power BI, all of these are:
- Manual measurements
- Written in DAX
- Context-dependent
- Sensitive to relationships and filters
- With ambiguous results if something changes
- Each new combination can break the pattern.
4. In Power BI you build what other tools have already done.
At Mercur, everything is integrated:
- Row templates
- Column templates
- Financial formulas
- Hierarchies
- Totals and subtotals
- Consistent drill-down
In Power BI, the user has to:
- Create auxiliary tables
- Create physical measurements
- Relationship management
- Avoiding context conflicts
- Controlling the order
- Control the format
- Controlling the behavior of the matrix
The result is not only technical: it is frustrating.
Conclusion
Power BI is not a natural substitute for a tool designed for complex financial reporting.
Can it be done? Yes.
Is it intuitive? No.
Is it fast? No.
Is it elegant? No, it isn’t.
Power BI understands tables and context.
Tools like Mercur understand finance, structure and business.
And that difference, for a CFO, is not minor.
You may be interested in
AMSO Consulting
Pioneers in providing innovative solutions for 30 years, we are specialists in Corporate Performance Management and in particular in everything related to budgeting and forcasting processes. We have worked in several sectors, such as Retail, Fashion, Services, Hospitality, and Healthcare. In our projects, we always optimize processes that allow clients to prepare budgets, rolling forecasts, and financial plans easily and with minimal effort. Everything updated at the same time.
We are the specialists and integrators of Mercur Business Control in Spain, France, Andorra and Portugal.


