Skip to content
CFO Business Breakfast — How to trust AI in financeRequest Invite
Connect SAP, NetSuite, Xero, Dynamics
Unified Chart of Accounts

One chart of accounts.
Every entity you own.

Keboola maintains your group chart of accounts as a governed single source of truth. Every entity’s accounts — SAP, NetSuite, Xero, Dynamics — map into one structure you bulk-edit across entities, with a changelog on every mapping change and lineage back to the source account. You do not need to fix your ERPs first.

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

Mapping tables work at 2 entities. At 10, they go stale.

Every ERP names accounts differently.

SAP GL 4000 is NetSuite ‘Sales Revenue’ is a Xero custom code. Reconciling them is a monthly manual project owned by whoever knows both systems — and it leaves when they do.

Every acquisition arrives with its own chart.

A new entity brings its own ERP and 1,200 accounts shaped by ten years of someone else’s decisions. Months of mapping later, the logic lives in a workbook tab — and the next deal starts the work over.

The CFO and the controller report different revenue.

Same period, same group — different account groupings, different totals. The discrepancy is explainable. Explaining it is what costs you the board’s confidence.

The mapping table has no audit trail.

Nobody can say who moved an account, when, or why. When a number is questioned — or restated — the answer lives in file versions and memory. An auditor cannot reconstruct that. Neither can you.

Unified Chart of Accounts

The group chart of accounts stops being a spreadsheet someone maintains.

Multi-entity bulk edits, a changelog on every mapping change, and an audit trail your auditor can follow on their own.

0wks

New entity onboarded — vs 6–9 months of manual mapping

0%

Traceable to source — from group P&L line to entity account

Zero

Manual mapping at close — rules re-apply every period

How it works

YoudonotneedtofixyourERPsfirst.

Connect

Pull account structures from every connected ERP at source — SAP, NetSuite, Xero, Dynamics. No manual exports. No uploads. Hours to connect, not weeks.

01
02

Map

Each entity’s accounts map into one group chart. Your controller defines and approves every match once; the mapping holds from then on. Need to reclass an account group-wide? One bulk edit applies across every entity.

Govern

Every mapping change lands in the changelog — who, when, what, why — and surfaces in a live audit feed. The trail runs from consolidated P&L line back to the source account. Your auditor can reconstruct any number without asking.

03
04

Propagate

Harmonized accounts feed the consolidation layer directly — mapping rules re-apply automatically every period. New entities onboard in 8 weeks, not 6–9 months.

Why Keboola

Manual mapping in Excel has no audit trail, breaks on every acquisition, and lives in one person’s head.

Planning and consolidation tools connect above the chart of accounts and model whatever they find. Keboola fixes the layer they assume — a versioned, change-logged mapping in 8 weeks, alongside the ERPs you already run.

Keboola
Connect
Map
Govern
Propagate

Questions & answers

Frequently Asked Questions

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

It ingests each entity's account structure at source — SAP, NetSuite, Xero, Dynamics — and maps it into one governed group chart. Your controller defines and approves every match once; the rules then re-apply every period. Mappings are stored as governed, versioned rules with a named owner. Group-wide reclasses are bulk edits applied across every entity at once.
No. Each entity keeps its ERP and its local chart; Keboola is the mapping layer between your ledgers and your reporting — we add on top of what you run, we don't replace it. Home Credit runs nine country operations through one structure on top of its local systems.
The new entity's accounts map into the existing structure — the target chart, mapping rules, and approval workflow already exist, so onboarding repeats them. Expect about 8 weeks to fold in a new entity, versus the 6–9 months a manual remapping typically takes; Creditinfo's implementation went live in 2 months. Every mapping decision lands in the changelog.
A spreadsheet mapping has no version history, no enforced owner, and no link to the source ledgers — it goes stale the moment entities, standards, or staff change. In Keboola, every mapping is a versioned rule with a changelog (who, when, what, why) and lineage from the consolidated line to the entity account. Mapping tables work at 2 entities; at 10 entities with M&A, they do not.
Yes — auditability of the mapping is the point. Every change is logged and surfaces in a live audit feed, so an auditor can reconstruct how any group number was assembled from the changelog and lineage, instead of from file versions and your team's memory. The trail runs from consolidated P&L line back to the source account.
First board-ready output in about 8 weeks. Creditinfo went live in 2 months and cut month-end close time by 70%; one structure now serves its 30+ markets. Weeks 1–2 are the heaviest — but that work ends, while manual remapping compounds with every new entity.
No. Keboola sits underneath and feeds harmonized, traceable accounts to whatever you run on top — consolidated financial reporting, EPM, BI, or Excel. Those tools assume a clean chart of accounts when they connect; Keboola is what makes that assumption true. Agreeing on what each consolidated line means — revenue, EBITDA — is the adjacent job, covered by a shared business glossary.
It is scoped per engagement, and two variables drive it: how many entities you consolidate and how many different ERPs they run. Four entities on two ERPs is a smaller scope than twelve entities on six. The comparison that matters is against the status quo — a manual remapping consumes 6–9 months of controller time and repeats with every acquisition, while the mapping layer is built once and re-applied. The 30-minute mapping review is where we scope it: bring your entity list and ERP mix.
Balu Gopakumar|Account Executive
Balu Gopakumar
Martin Lepka|CMO Keboola
Martin Lepka
Giorgio Pontillo|CRO
Giorgio Pontillo

Your mapping workbook has one owner and no version history. Bring it to the call.

30 minutes. We walk through how your entities map today, where the gaps are, and what one chart changes at your next close.