Integrations

One card per source category, data flows in from anywhere.

View all integrations →

The Agentic Layer

The governed foundation — platform capabilities.

Reporting & Analysis

Business performance tracking, variance, and analytical insight.

See all →

Planning & Modeling

A comprehensive look at forward-looking corporate financial strategy.

See all →

Consolidation & Close

The entire financial close and data management cycle, at a high level.

See all →
BI Tools

BI dashboards and board decks that finally agree.

Sync finance data that ties to the board deck into Power BI, Tableau, and Looker. Cube ships one governed model through exports and the API, mapped once, so every dashboard reads from the same numbers finance reports from. And it works both ways: operational data in your BI tools can flow back into Cube.

CubeGoverned modelSynced
Revenue · Q3$4.82M
4000 · RevenueAll entitiesTraces to 1,284 GL lines
Power BIPower BI
Revenue · Q3
$4.82M
TableauTableau
Revenue · Q3
$4.82M
LookerLooker
Revenue · Q3
$4.82M
Product 46%Services 32%
Same number in every dashboard and the board deck
Before Cube

The dashboard says one number. The deck says another.

Every finance leader knows the meeting where the BI dashboard and the deck disagree, and the room stops trusting both. They were built from different pulls, so finance spends the meeting explaining which one to believe.

Stacked outdated glass panels representing stale numbersrevenue_export_v3.csvCOA_mapping_FINAL.xlsxWhich revenue is right?
Different BI pulls

The dashboard and the deck come from separate extracts, so they drift apart.

CSVs that drift

An analyst pulls a CSV, applies their own mapping, and the file drifts the moment anything changes.

Rebuilt from memory

The data team re-creates your chart of accounts, and every rebuild is a fresh chance to diverge.

No way to trace it

When a director asks which number is right, nobody can trace it to the transaction.

See your own dashboards tie to the deck.Try it freeGet a demo
The solution

Dashboards in Cube, or in the BI tool you already use.

Build dashboards right in Cube, or send the same governed numbers to Power BI, Tableau, Looker, or any BI platform. Either way, every chart ties to the board deck.

Cube Web
Built in

Cube dashboards

Dashboards and reports in Cube Web, built by finance with no BI team or data model to maintain.

  • KPIs, budget vs. actual, and variance views on live data
  • Drill from any chart to the GL transactions behind it
  • Share with leaders, with Cube permissions on every view
Power BITableauLooker+ any
Connected

Any BI platform

Keep the dashboards your company already runs on, fed from the same governed model finance reports from.

  • Power BI, Tableau, Looker, and other BI tools
  • Structured exports and API feeds, mapped once
  • Same accounts, rollups, and totals as the deck
Why Cube

One governed model behind every dashboard.

Power BI, Tableau, and Looker are great at showing data, but none of them knows your chart of accounts. Cube maps every account once and ships that model out, so what lands in BI ties to every other surface.

A glass panel refreshing with live numbers
Export by dimension

Pick the options for each dimension, preview the shape, and export a structured CSV.

One glass source feeding many panels
Data in both directions

Send a file or API feed to your BI tools, and sync operational data from them back into Cube.

A glass AI spark over live numbers
Same rollups as the board deck

Every account is mapped once, so the file carries the same rollups finance reports from.

Branching glass panels representing scenarios
Change the rollup, keep the model

Change the dimension and keep the model: same accounts, new rollup, same totals.

A glass line tracing a number to its source
Every dashboard figure traces back

Inside Cube, each figure drills to the GL transactions behind it.

A glass lock representing secure access
Only what you’re allowed to see

Exports and the API respect Cube permissions, so people only get the data they’re allowed to see.

How it works

Context in. Decisions out. Every change written back.

Cube Operating Intelligence™ unifies your business data, applies your rules and calculations, and serves the result to your BI tools and every other surface, so every leader decides on the same numbers. Edits flow back to the same governed source.

Your business data
ERP & accountingGL, AP, AR
CRMPipeline, bookings
HRIS & payrollHeadcount, comp
Data warehouseCompany-wide data
SpreadsheetsExcel, Google Sheets
CubeOI™ Operating Intelligence
Four glass layers, unified data, business logic, security, and agents, with business context flowing through them and edits flowing back
Unified data
Business logic
Security & controls
Agents & automation
Unified data Business logic Security & controls Agents & automation
Where your team works
Cube WebPlan, report, and model
Excel & SheetsWork
PowerPoint & SlidesPresent
Slack & TeamsDecide
AI assistantsClaude, ChatGPT, Copilot
Security & governance

Board-ready means audit-ready.

Delivering numbers everywhere only works if access travels with them. In Cube it does, enforced in the layer rather than in each tool.

Security & compliance
Every export, governed.

Every AI feature respects your permissions, and every edit, sync, and publish lands in one audit trail.

SOC 1 & 2
Type 2
Certified
HIPAA
Compliant
Certified
Every edit
Tracked
To the source
Role-based access
CFO, VP and auditor views from one source.
CFO
VP Sales
Permissions on every view
User-level access wherever your numbers show up.
Viewing as David
Marketing$1.24M
Sales
Full audit trail
Who, what, when, before and after.
Maya edited Q3 rent2:14 PM
David approved forecast2:31 PM
SSO
Okta, Microsoft Entra, Google.
Single sign-on enabled

One number on every dashboard.

On the demo, we build a dimension-by-dimension export from a model like yours and preview the file before it ships.

FAQs

Questions data and finance teams ask.

Which BI tools does Cube work with?

Cube works with Power BI, Tableau, and Looker, plus any tool that reads a CSV or an API feed. You can also load the data into the warehouse that serves your BI tools.

How do we get Cube data into BI?

Cube data gets into BI through a structured CSV export or the Cube API. Pick the dimensions you want, preview the shape, and export a structured CSV, or connect through the Cube API for a recurring feed.

How do you connect FP&A data to Power BI or Tableau?

Sync governed finance data from your FP&A platform into the BI tool, rather than rebuilding finance logic in BI. Cube syncs actuals, plans, and forecasts into Power BI, Tableau, and Looker, so BI dashboards match the board deck.

What is the difference between FP&A software and BI tools?

BI tools visualize data across the business; FP&A software owns planning, forecasting, and the financial rules behind the numbers. Cube handles the finance side and syncs the results into your BI tools, so both show the same figures. 

Will the numbers match our board deck?

Yes. The dashboard, the deck, and the spreadsheet all read from the same Cube model, with every account mapped once, so the totals tie on every surface.

Does Cube have its own dashboards?

Yes. For finance-owned dashboards, Cube BI and Cube Boards are built in and run live on the same governed model.

Can our BI tools feed Cube too?

Yes. Sync operational data from tools like Power BI into Cube and tie it to your budgets and forecasts. Cube also reads from hundreds of source systems, your warehouse included.

Still have questions?
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. 1.
    Unify the sources. Connect the GL, CRM, HRIS, and billing systems into Cube.
  2. 2.
    Map once. Define accounts, rollups, entities, and dimensions in one model.
  3. 3.
    Choose the shape. Pick the dimensions and options for each export and preview the output.
  4. 4.
    Connect BI. Send structured exports or API feeds to Power BI, Tableau, Looker, or another BI tool.
  5. 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