Every entity, every cost center, one ledger
Attribute every dollar to the right company and cost center across a growing group, and keep it right through acquisitions, restructures, and consolidation.
The org chart moves faster than the GL
Acquisitions and restructures break entity-level accounting.
Money arrives addressed to the group and must land in the right subsidiary, business unit, and cost center. Every acquisition adds entities, every restructure re-keys cost centers, and the GL absorbs it in batches, months behind reality.
Payments default to the wrong entity, and reallocation is a manual journal entry.
Restructuring a cost center means re-keying history transaction by transaction.
Each acquisition arrives with its own systems, and integration takes quarters.
Roll-up reporting across entities and cost centers is a spreadsheet exercise, not a query.
_PROOF/ A serial acquirer runs entity and cost-center attribution on Formance across dozens of operating companies.
Group money, entity truth
Attributed at posting, not reallocated at close.
Every transaction posts with its customer, company, and cost-center dimensions from day one, so entity positions, intercompany balances, and group roll-ups are derived live, not assembled at month-end.
The primitives groups need
Built on the open-source Formance ledger.
Dimensional account structures, intercompany flows, and bulk restructuring, composed for multi-entity groups.
Accounts structured by customer, company, and cost center: every posting carries its dimensions, every balance rolls up along any of them.
roll-up any axis
Cross-entity movements post both sides atomically, so intercompany balances always net and eliminations are derived, not hunted.
always-balanced IC
Re-key cost centers and merge entities with bulk operations across committed history: a restructure is a mapping, not a re-keying project.
history-safe re-keys
Read the docsBring an acquired company's books in through a mapped migration: shadow-run against their system, then cut over with the history intact.
mapped migrations
Group-grade, by design
Attribution happens at posting
Customer, company, and cost center, in the account itself.
The account structure carries the dimensions: one posting records which customer owes which company for work done by which cost center, and every roll-up follows.
Trusted by builders
“Formance enabled us to ship new lending products faster by providing a customizable foundation that let us reliably express the complexities of our flow of funds.”
Embedded finance · reconciliation across 14 countries
See customer story“Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.”
Healthcare · Financial OS
“Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.”
Benefits · fintech infrastructure
Built for regulated money.
Enterprise controls, the certifications auditors ask for, and an immutable record, out of the box.
09:41:07Z AUDIT gateway POST /api/ledger/v2/main/transactions 200 sub:ops@acme.io
09:41:09Z LOG id:4093 NEW_TRANSACTION ledger:main
09:41:12Z LOG id:4094 SET_METADATA ledger:main
09:41:15Z LOG id:4095 REVERTED_TRANSACTION ledger:main
09:41:18Z AUDIT gateway GET /api/ledger/v2/main/logs 200 sub:audit@acme.io
Keep going
Everything you need to evaluate and build on Formance.
Multi-entity accounting, answered
01 / HOW DO COST-CENTER RESTRUCTURES WORK?
As bulk operations: a mapping (say B.0313 → B.0314) applies across accounts and metadata without hand-editing history, and the change itself is auditable.
02 / HOW FAST CAN AN ACQUISITION BE ONBOARDED?
Once the chart of accounts mapping is defined, the acquired books migrate through bulk endpoints: shadow-run alongside their system, then cut over. Weeks, not quarters.
03 / DO INTERCOMPANY BALANCES ALWAYS NET?
Yes: cross-entity flows post both legs in one atomic transaction, so intercompany positions are equal and opposite by construction, and eliminations are a query.
04 / CAN REPORTING ROLL UP ACROSS DIMENSIONS?
Yes. Balances derive along any dimension in the account structure: one customer across all entities, one entity across all customers, one cost center across everything.
A group that consolidates itself
See how Formance fits your entity structure: book a demo or start building.





