Start here
What is BI for finance?
BI for finance means using business intelligence tools such as Power BI, Tableau, and Looker to report on financial data: revenue, margins, spend, headcount cost, and budget vs. actual. Finance teams use BI to put live numbers in front of leaders without building every view by hand.
The hard part is the data, not the dashboard. BI tools show whatever they are given. When finance data reaches BI through separate extracts and ad hoc mappings, dashboards stop matching the board deck. Finance-ready BI starts with one governed model that every tool reads from.
Model
One governed model
Accounts, entities, and dimensions mapped once in Cube, so every dashboard uses the same structure finance reports from.
Deliver
Exports and API feeds
Structured CSV exports and API connections send finance data to Power BI, Tableau, Looker, and other BI tools.
Govern
Permissions on every feed
Exports and the API respect Cube roles, so each person only receives the data they are allowed to see.
Return
Data in both directions
Operational data from BI and warehouse sources can sync back into Cube for planning and forecasting.
Why finance-ready BI matters
When the dashboard and the board deck disagree, leaders stop trusting both, and finance spends the meeting reconciling numbers instead of discussing them. Feeding BI from the same governed model as finance reporting removes the disagreement at the source. Leaders get self-serve dashboards, and finance gets one number to stand behind.
How to connect finance data to BI
A typical rollout with Cube follows five steps.
-
1.
Unify the sources. Connect the GL, CRM, HRIS, and billing systems into Cube.
-
2.
Map once. Define accounts, rollups, entities, and dimensions in one model.
-
3.
Choose the shape. Pick the dimensions and options for each export and preview the output.
-
4.
Connect BI. Send structured exports or API feeds to Power BI, Tableau, Looker, or another BI tool.
-
5.
Use Cube dashboards where they fit. Build finance dashboards directly in Cube Web, with drill-down to the GL transactions.
Key terms
- Governed financial model
- A single, reconciled structure of accounts, entities, and dimensions with agreed business rules and permissions.
- Chart of accounts mapping
- Assigning each source account to a standard reporting account so rollups match across every report.
- Rollup
- How detailed accounts or departments aggregate into totals, such as Opex or Gross margin.
- Dimension
- An attribute used to slice financial data, such as department, entity, region, product, or scenario.
- Single source of truth
- One governed dataset that every report, dashboard, and deck reads from, so figures match everywhere.
- Drill-down
- Clicking a summary figure to see the detail behind it, down to individual GL transactions.
BI on raw extracts vs. BI fed by Cube
|
Raw extracts in BI |
BI fed by Cube |
| Mapping |
Rebuilt by the data team in each tool |
Mapped once in Cube and reused everywhere |
| Consistency |
Dashboards drift from the board deck |
Same rollups and totals as the deck |
| Freshness |
Manual pulls on a schedule |
Scheduled exports and API feeds |
| Permissions |
Set separately in every tool |
Cube roles applied to every export |
| Traceability |
Hard to tie back to the GL |
Figures trace to GL transactions in Cube |
| Dashboards |
BI tool only |
BI tools or Cube dashboards, from one model |