Designing a financial dashboard people trust with their money

Financial dashboard design for finance teams and fintech products: the four types, the KPIs each shows, chart and number rules, live data states and two examples.

Summarize with
Line drawing of a bank card, a shield with a tick and a padlock with a green keyhole, standing on one line

A financial dashboard is one screen that shows the state of money and what needs doing about it: how much cash there is, what came in and went out, what is due, and whether the trend is on plan. Good financial dashboard design starts with the type (business, personal, investment or banking), puts only the figures that person decides on in the first view, formats every amount the same way, and says how fresh the data is. Most failures come from those last two, not from the charts.

Search results mix templates for finance teams in BI tools with screens from fintech products; the same rules apply to both. I'm a design engineer: I design products and build them in production code, and finance screens are part of my product design work. For dashboards in general, sorted by the job they do, see my dashboard design examples.

The four types of financial dashboard

TypeWho opens itFirst-screen questionKPIs for the first view
Business (CFO)Founder, finance lead, boardIs there enough cash, and is the business on plan?Cash, net burn, runway, revenue, gross margin, budget against actual
Personal financeOne person or a householdWhere did my money go, and what should I change?Net worth, income against spending, spending by category, bills, goals
InvestmentRetail or professional investorWhat do I own, how is it doing, how is it spread?Total value, return for a stated period, allocation, holdings
Banking and paymentsAccount holder or small businessWhat can I spend, and what is pending?Available balance, pending items, scheduled payments

Business and CFO dashboards are what most search results show, often built in Power BI, Tableau or a spreadsheet. Cash, net burn (cash out minus cash in for the month) and runway (cash divided by net burn, in months) come first, then revenue, gross margin and spending against budget. Profit and loss, receivables ageing and days sales outstanding sit one level down. The trap is variance: spending over budget is bad, revenue over plan is good. If both turn red because the number went up, people stop trusting the colours, so I label variance favourable or unfavourable.

Personal finance dashboards give a verdict and a next step. Net worth and the month's income against spending lead, then categories, upcoming bills and goals.

Investment dashboards answer what someone owns, how it's doing and how it's spread. A return without its period can be read as almost anything, so the period always sits next to it. For past performance and forecast rules, see my notes on fintech app design.

Banking dashboards have two balances people confuse: the current balance and the available balance after pending items. Both need plain labels, and pending transactions must look different from posted ones.

Chart choices for money

A right-aligned table is often the best chart for money. When it isn't:

What you want to showChart I useWhat I avoid
Change over timeLine, or bars starting at zeroA cropped axis on bars
Two measures with different unitsTwo charts on one time axisOne chart with two y-axes
Share of a wholeOne stacked bar, or a small donutA pie with a dozen slices
Where money flowsA flow (Sankey) chartNested tables of sub-totals
Actual against planBars around zero, or a waterfallTwo crossing lines
Exact valuesA right-aligned tableRounded labels on bars

On dual axes I follow the UK Government Analysis Function's guidance on charts, which says it generally does not recommend dual axis charts because readers misread them.

Formatting money: the rules I write into the design system

Most finance dashboard bugs start as a formatting decision nobody wrote down.

  • Tabular figures in every column. The OpenType tnum feature, described in Microsoft's OpenType feature list, gives every digit the same width so columns line up. In CSS it's font-variant-numeric: tabular-nums (MDN). Right-align amounts too.
  • One rule for negatives. A minus sign or brackets, never both. Intl.NumberFormat has a currencySign: "accounting" option that, in many locales, wraps negatives in parentheses, per MDN's reference.
  • Shortened numbers only on overview cards. "1.2M" is fine for a headline; the exact amount appears on hover and in every table, and never shortens where money moves.
  • A currency code when there is more than one currency, with the conversion date beside any converted total.
  • Every period named: calendar month or last 30 days, and the time zone if the business spans several.

Decimals per currency and rounding shares to 100% are in my fintech app design guide.

Colour: never only red and green

Green gains and red losses are fine as long as colour is never the only signal. WCAG 2.2 success criterion 1.4.1, Use of Color, says colour must not be the only visual means of conveying information. So every change carries a sign and an arrow, and a variance carries a word.

Chart lines and bar segments count as graphics. Success criterion 1.4.11, Non-text Contrast, asks for a contrast ratio of at least 3:1 against adjacent colours for graphics needed to understand the content, and pale pastel series on a white card often fail it. I keep one accent for the figure that matters, greys for the rest, and label lines directly.

Real-time data and trust states

A finance dashboard is only trusted if people can tell whether a number is from now or from yesterday. Plaid's Balance documentation says balances from its general accounts endpoint are cached: with Transactions they may update once a day or more, with only Auth every 30 days or less often. Its real-time balance call is slower, around 3 seconds at the median and 11 seconds at the 95th percentile.

The states I design for every finance dashboard:

  1. Fresh: a quiet "Updated 09:42" near the figure, or "As of market close" for prices.
  2. Refreshing: the old value stays visible, with progress shown on that card only.
  3. Stale: the timestamp becomes a warning once data passes the agreed age.
  4. Partial: one account has failed, so the total says "3 of 4 accounts" with a Reconnect button, instead of silently showing a smaller net worth.
  5. Pending: unsettled items look different and are counted separately.
  6. Empty: a new user sees what will appear once an account is connected, not a row of zeros.

Totals must add up, too. If a card and the transactions under it differ by a few cents, the user will notice before you do, so every total links to the rows behind it.

Financial dashboard examples from my work

WealthWise: personal finance

WealthWise is an AI personal finance dashboard for monitoring cash flow, investments and goals in one place. I designed more than 40 web screens, a mobile layout of the home view, and the style guide and design system behind them.

The home overview leads with net worth, with expenses and incomes beneath, each showing its change, and an AI financial health score beside them. The cash flow view is a flow chart: income from salary, freelance and business work runs into food, savings, rent, transport and entertainment, and each band's width shows its size. The budget page opens with monthly budget, actual spending and savings rate, then a budget against actual chart and a zero-based budget builder. The investment page pairs a holdings table, with shares and cost basis, with an allocation card split into stocks, bonds, crypto and cash. Each AI insight sits beside the numbers it comes from, phrased as a plain next step.

Nexfolio: investment

Nexfolio is an AI-powered investment dashboard that brings stocks, crypto and ETFs into one view. I designed the web app on a 12 column grid with a fixed spacing scale, Geist from 14 to 32px, and lime on graphite and white.

The Invest page answers in order: total value, then one bar split by asset with each value and share underneath, then a performance chart that switches between one day, seven days and one month. The AI Insight screen puts portfolio value, AI confidence and market sentiment with a risk assessment on one row, above a forecast chart comparing short, medium and long term outlooks. Transactions carry a Settled, Pending or Failed tag and export to CSV or PDF. The process ran through interactive prototypes, usability testing and accessibility checks before handoff.

Common mistakes in financial dashboard design

  • Totals with no comparison. Show a balance against last month, the budget or the goal.
  • Too many KPIs up front. If nobody can name the decision a card supports, it goes one level down.
  • Undefined metrics, so two screens show two different "revenue" figures.
  • Forecasts drawn like history. A projection needs a dashed line or a range, and a label.
  • AI insights with no visible source. If an insight can't point at its figure, people ignore it.

How I approach a financial dashboard

  1. A free 30 minute intro call: who opens the dashboard, what they decide with it, and where the data comes from.
  2. A written scope and one fixed quote for the whole project. No retainer, nothing billed by the hour.
  3. The KPI sheet: each metric gets a name, formula, source, refresh time and owner, so arguments about numbers happen here, not in review.
  4. Wireframes with awkward data: negative values, long account names, three currencies, a failed connection, an empty account.
  5. Weekly design sprints in Figma, a written update in Slack every 48 hours and a review call each week.
  6. A documented design system with number formats, chart styles and states, named the same in Figma and in code.
  7. The build in React and Next.js. I use AI coding tools where they save time, and a person who knows the design reviews every change.

Frequently asked questions

What should a financial dashboard include?

It depends on the type. Business: cash, burn, runway, revenue, margin and budget against actual. Personal: net worth, income against spending, bills and goals. Investment: total value, return for a stated period and allocation. All of them need a last-updated time and links from each total to its rows.

What KPIs belong on a CFO dashboard?

Cash, net burn and runway show whether the company is safe. Revenue, gross margin and spending against budget show whether it's on plan. Receivables ageing and days sales outstanding show whether cash is coming in. The rest usually belongs one level down.

Should a financial dashboard use red and green?

Yes, if colour isn't the only signal. Add a sign and an arrow, label variances favourable or unfavourable, and check chart parts reach 3:1 contrast, as WCAG 2.2 asks.

Can I use Power BI instead of designing a financial dashboard?

For an internal finance team, often yes, and the rules above still apply to its layout and formatting. When the dashboard sits inside your product for your customers, it needs product design: states, onboarding, mobile and a design system shared with the code.

Can you design and build a financial dashboard?

Yes. I design the product and build the front end in React and Next.js from a documented design system, so the build matches the screens.

Sources and method

I read every source on 10 November 2026. Before writing, I studied the pages ranking for "financial dashboard" and "financial dashboard examples": most are template galleries for finance teams, and few cover number formatting, accessibility or data freshness, so this guide adds them. I give no market size figures, because the ones I found came from vendors' sales pages.

  • UK Government Analysis Function, Data visualisation: charts, date read 10 November 2026: analysisfunction.civilservice.gov.uk
  • Microsoft, OpenType feature list (tnum), date read 10 November 2026: learn.microsoft.com
  • MDN, font-variant-numeric, date read 10 November 2026: developer.mozilla.org
  • MDN, Intl.NumberFormat() constructor, date read 10 November 2026: developer.mozilla.org
  • W3C, Understanding SC 1.4.1 Use of Color, date read 10 November 2026: w3.org
  • W3C, Understanding SC 1.4.11 Non-text Contrast, date read 10 November 2026: w3.org
  • Plaid, Balance documentation, date read 10 November 2026: plaid.com

If you're planning a financial dashboard, for your finance team or inside your product, and want it designed and built as one piece of work, book a free 30 minute intro call. After it, you get a written scope and one fixed quote.

Tags: Financial dashboard, Dashboard design, Fintech, Data visualisation, Product design

Keep reading

Let’s look at your product.

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call