Skip to content
CFO Business Breakfast — How to trust AI in financeRequest Invite
Connect every system
Financial Intelligence · Semantic Layer

The business glossary for finance, held in the semantic layer that computes your statements.

Keboola’s business glossary is a governed metric catalog for finance teams: ~197 definitions — formula, source, owner — held in the same semantic layer that computes your P&L and balance sheet. Your dashboards and Kai, Keboola’s AI assistant, read the same definitions. EBITDA means one thing in every report and every AI answer.

Trusted by 1,000+ companies

Apify
Carvago
Česká spořitelna
CreditInfo
DXC
EmbedIT
Firehouse Subs
Groupon
GymBeam
Heureka
HomeCredit
Innogy
ITIS HOLDING
Kofola
P3
Productboard
Rohlík
seznam.cz
ShipMonk
Shoptet
The Evans Network
Apify
Carvago
Česká spořitelna
CreditInfo
DXC
EmbedIT
Firehouse Subs
Groupon
GymBeam
Heureka
HomeCredit
Innogy
ITIS HOLDING
Kofola
P3
Productboard
Rohlík
seznam.cz
ShipMonk
Shoptet
The Evans Network
Apify
Carvago
Česká spořitelna
CreditInfo
DXC
EmbedIT
Firehouse Subs
Groupon
GymBeam
Heureka
HomeCredit
Innogy
ITIS HOLDING
Kofola
P3
Productboard
Rohlík
seznam.cz
ShipMonk
Shoptet
The Evans Network

The Problem

Group EBITDA becomes the sum of four different concepts.

Same metric, three definitions.

EBITDA means one thing in your SAP, another in the FP&A model, and a third in the board deck. Every reconciliation meeting starts by agreeing on which version is correct.

New hires inherit broken logic.

Definitions live in a controller’s head or a stale Confluence page. When that person leaves, the logic leaves with them. Every new analyst reverse-engineers the formula from report output — and gets it slightly wrong.

AI gives confident wrong answers.

When AI queries an undefined metric, it interpolates. In our discovery calls, one multi-entity CFO showed us an AI-generated year-end cash position that was about 30% off. Two analysts ask the same question, get different numbers. Both technically justified. Neither defensible.

Auditors cannot follow the logic.

A metric that cannot be defined unambiguously cannot be audited reliably. The auditor asks for the definition. The answer is a spreadsheet, a long explanation, and a 48-hour wait.

Business Glossary

Defined once. Enforced everywhere.

The semantic layer is the guardrail — every number Kai returns is computed from your definitions, not interpreted from them. When Kai is asked for EBITDA, it executes your definition, not an interpretation of it.

0

Definition per metric — enforced across all systems

0%

AI-query consistency — Kai and your BI read the same definitions

Zero

“What does this mean?” meetings about your own numbers

How it works

Youdonotneedtoagreeinternallybeforeyoustart.

Surface

Connect your data catalog, ERP metadata, and FP&A models. The first step is an inventory — we surface every metric, KPI, and account grouping in active use, including ones nobody knew existed.

01
02

Define

Finance owns each definition — formula, source, owner, approved use. Each one lives in the semantic layer, not in a document. Versioned and change-logged from day one.

Enforce

Definitions are wired into the model itself — the semantic-layer P&L and balance sheet compute from them. Every dashboard, report, and AI query — from Kai or any agent connected over MCP, Copilot, Gemini, or ChatGPT — resolves against the same definition. The definition is the calculation, not a comment on it.

03
04

Monitor

Every definition change lands in a live audit and governance feed — who changed what, when, and why, reconstructable by your auditor. Drift is caught in review, not in the board meeting.

Why Keboola

Most BI tools let you define metrics inside dashboards. That definition lives in the dashboard, not in the data.

When someone builds a second dashboard, they redefine it. Keboola governs the definition at the data layer — every tool that reads from it, including every agent connected via MCP, computes the same governed answer. And each definition is portable SQL your team owns. No black box. No vendor lock-in on your business logic.

Keboola
Surface
Define
Enforce
Monitor

Questions & answers

Frequently Asked Questions

Everything finance, IT, and procurement will want to know — up front.

A business glossary is a governed catalog of every financial metric — formula, source, owner, and approved use — that your reporting and AI tools resolve against. Most glossaries are documentation that drifts from the code within a quarter. In Keboola, the P&L and balance sheet are wired to the same semantic layer that holds ~197 governed metric definitions — the definition drives the calculation, it doesn't document it.
A catalog describes what data exists; a dictionary describes fields. Neither enforces anything — a dashboard can still compute EBITDA its own way. Keboola's glossary sits in the semantic layer, so every dashboard, report, and AI query executes the definition rather than reading a description of it.
Those tools document definitions; they don't compute them. A standalone glossary describes how EBITDA should be calculated — your warehouse and BI tools are free to disagree with it. In Keboola, the definition lives in the semantic layer that computes the statements, so every dashboard and AI query that reads from it executes the same definition. You get the catalog and the enforcement in one layer.
Structurally, not through prompt engineering. Computed answers from Kai or any agent connected over MCP resolve only against your validated metric definitions, with lineage back to source transactions. Every number is in a glass box: definition, formula, and source visible.
Finance owns them — each definition carries a named owner, and changes are versioned and change-logged from day one. Every edit lands in a live audit and governance feed your auditor can reconstruct: who changed what, when, and why. No restatement archaeology.
No — disagreement is the starting input, not a prerequisite. The first step is an inventory: we surface every metric in active use across your ERPs and FP&A models, including ones nobody knew existed. You converge on definitions with the full inventory in front of you, not in a conference room from memory.
No. Keboola builds on the warehouse you already run — Snowflake, BigQuery, Databricks — and feeds your definitions to Power BI, Excel, and your board packs. Nothing is replaced; the glossary becomes the layer those tools read from.
First board-ready output typically lands in 8 weeks, alongside your existing stack — the engagement covers the metric inventory, the definition workshops, and wiring the semantic layer to your warehouse. Creditinfo went live in 2 months and cut month-end close time by 70%. The definitional work is front-loaded — once governed, a definition is maintained, not rebuilt. Manual reconciliation is the opposite: it compounds every close.
Balu Gopakumar|Account Executive
Balu Gopakumar
Martin Lepka|CMO Keboola
Martin Lepka
Giorgio Pontillo|CRO
Giorgio Pontillo

Cannot agree on what revenue means yet? That is exactly where we start.

The 30 minutes is a diagnostic, not a demo. We map your current metric definitions and show you where the gaps are.