How to Build a CFO Dashboard in Power BI: Metrics, Structure, and What Actually Gets Used

Most CFO dashboards fail before they’re ever used. Not because of the tool, not because of the data — because whoever built the dashboard tried to show everything. Every line item, every sub-category, every variance down to the department level, all on one screen.

The result is a wall of numbers that requires 30 minutes to interpret and gets opened once a month, usually by the analyst who built it.

A functional CFO dashboard is a decision support tool. It answers the 6-8 questions leadership checks weekly and nothing else. Build around that constraint and you’ll build something people actually use.

What a CFO Dashboard Should Actually Do

A CFO dashboard is not a financial report. It’s not a replacement for your accounting system. It’s a real-time signal that tells you, in under five minutes, whether the business is operating within expected parameters.

Three questions it should answer every morning:

1. Are we profitable this month, and how does it compare to budget?
2. What is our cash position and how long does it last at current burn?
3. Where are we against revenue and expense targets — and what’s the variance?

If the dashboard can’t answer those three questions in a single view, it’s not doing its job. Everything else — drill-down by region, department-level P&L, project-level costs — belongs on supporting pages, not the executive summary.

The target interaction: CFO opens the dashboard, reviews the summary in under five minutes, identifies anything that needs attention, and goes to the detail only if something is off.

The Core Metrics for a CFO Dashboard

These are the metrics that belong on the primary view:

Revenue: Actual vs. forecast, ideally broken down by product line, region, or channel. The number itself matters less than the variance indicator — is this above, on, or below where it should be?

Gross margin: By segment if your business sells meaningfully different products or services. Margin erosion often shows up here before it shows up in net income.

Operating expenses: Actual vs. budget, with a trend line. A single month of elevated OpEx is noise. Three consecutive months is a problem.

Cash position and burn rate: Cash on hand today, average monthly burn, and implied runway. For any business that isn’t cash-flow positive every month, this is a non-negotiable primary metric.

Accounts receivable aging: Total AR is less useful than the aging breakdown — how much is current, 30-60 days, 60-90 days, 90+ days. Deteriorating AR aging is an early warning sign of collection problems.

Payroll and headcount costs: Payroll is typically the largest operating expense. Tracking it against budget and headcount against plan catches overruns early.

MRR/ARR (for SaaS businesses): Monthly recurring revenue, churn, and net revenue retention belong on any SaaS metrics dashboard at the CFO level. For non-SaaS businesses, replace with the equivalent recurring revenue indicator.

Connecting Your Data Sources in Power BI

Power BI supports direct connections, scheduled imports, and live queries. For a CFO dashboard, scheduled refresh (daily or more frequent) covers most needs.

QuickBooks / Xero: Both have Power BI connectors. For QuickBooks Desktop, you’ll need the Power BI Desktop connector or an intermediary like a scheduled CSV export. QuickBooks Online connects via API. Xero has an official Power BI connector with OAuth.

Bank data: Most banks don’t offer direct Power BI connections. Options include a treasury management system that exports to a format Power BI can read, or manual CSV import on a defined schedule. Real-time bank balance tracking typically requires a fintech intermediary (Plaid, MX) feeding a database that Power BI queries.

CRM pipeline data: HubSpot and Salesforce both have native Power BI connectors. CRM pipeline visibility — deals in stages, weighted pipeline, expected close dates — belongs on the CFO dashboard when pipeline is a leading indicator of revenue.

Payroll (Gusto, ADP): Gusto has limited direct integrations; ADP has more robust API options for larger implementations. For many businesses, a scheduled export from payroll to a shared location that Power BI reads is the practical approach.

Licensing note: Power BI Pro runs $10/user/month; Power BI Premium Per User is $20/user/month. Sharing reports with users who aren’t building dashboards requires at minimum a Power BI Pro license on the sharing end, and either Pro or Premium for viewers. For on-premise data sources (databases running in your own servers), the Power BI On-premises Data Gateway is required.

Structuring the Dashboard — Layout Best Practices

Structure determines whether a dashboard gets used daily or opened once and forgotten.

Page 1: Executive summary. This is the only page the CFO should need to review on a normal day. Design it for a single screen — no scrolling.

• Top row: 3-4 KPI cards — Revenue MTD, Gross Margin %, Cash Position, Variance to Budget. Each card shows the current value and the trend/variance indicator (up/down arrow, green/yellow/red).
• Middle section: a 12-month trend chart showing revenue and total operating expenses on the same axis. Seasonality, growth trajectory, and cost acceleration all show up here.
• Bottom section: AR aging table (bucketed by 0-30, 31-60, 61-90, 90+ days) and an expense breakdown by major category.

Pages 2+: Department drill-downs. Revenue by product/region, detailed expense by category, headcount by department. These exist for when something on the executive summary needs investigation — not for daily review.

Color coding: Variance indicators should use green/yellow/red relative to budget or target — not relative to the prior period, which can obscure whether the business is on plan.

Avoid dual axes. Charts with two y-axes are difficult to read quickly. If you need to show two metrics together, use a combo chart with clear labels or separate panels.

Common Mistakes to Avoid

Too many pages. A 12-tab Power BI dashboard is a sign that nobody made hard decisions about what matters. CFOs don’t click through 8 pages. If something needs its own page, it should be accessed by drilling down from a KPI on the summary — not navigating a tab bar.

Manual data refresh. If someone has to manually trigger a data refresh, open a file, or paste from a spreadsheet to keep the dashboard current, it will fall out of date within weeks. Automatic scheduled refresh is non-negotiable for a dashboard that’s supposed to drive daily decisions.

Numbers without context. Displaying “$1.2M revenue” without context — compared to what? budget? last month? last year? — provides zero decision support. Every KPI on an executive dashboard needs a benchmark built in.

Mixing strategic and operational metrics. The executive summary is not the place for invoice-level transaction data or line-item expense detail. Keep the summary strategic, and put operational detail on drill-down pages.

Missing variance columns. An AR aging table that shows totals without showing movement from the prior month misses the most important information: is the situation improving or deteriorating?

When Power BI Is the Right Choice (and When It Isn’t)

Power BI is a strong fit when your business is already in the Microsoft ecosystem — Azure, Microsoft 365, Teams. The integration with Azure data services is mature, the licensing is bundled in many M365 enterprise plans, and your IT team likely already has operational knowledge of the platform.

The $10-20/user/month licensing is manageable for small finance teams but scales up meaningfully when you need to share dashboards with department heads, regional managers, or the full leadership team.

For businesses that prefer open-source or self-hosted options, Metabase is a strong alternative — particularly for organizations where data should not leave internal servers. Apache Superset is another option for high data volume environments.

For CFO dashboards that need to connect non-standard sources — a proprietary ERP, a legacy accounting system, a combination of internal databases and external APIs — the connectors available in standard Power BI often fall short. Custom CFO dashboard development handles those cases with a purpose-built data pipeline rather than workarounds.

Getting Started

The fastest path to a CFO dashboard that gets used:

Define the 6-8 metrics first. Before opening Power BI, write down the questions leadership checks weekly. These become the metrics on the executive summary. Build those first; expand later.

Connect one data source at a time. Validate accuracy against your source system before connecting the next one. Data quality issues are significantly harder to debug across five connected sources than across one.

Schedule automatic refresh from day one. Don’t build a dashboard that requires manual updates. Set up the refresh schedule before you share it with anyone. A stale dashboard is worse than no dashboard.

Start narrow and earn trust. A dashboard that answers three questions accurately and refreshes daily gets trusted and used. A dashboard that tries to answer everything but has two metrics that are occasionally wrong gets abandoned.

If you’re looking to build a CFO dashboard with non-standard data sources or more complex financial modeling requirements, reach out to discuss what you’re building. We scope and build custom CFO dashboards for businesses that have outgrown the out-of-the-box connector approach.