Skip to content
_MULTI-ENTITY ACCOUNTING/

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.

group inflow
attribution
intercompany
roll-up
_THE PROBLEM/

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.

01

Payments default to the wrong entity, and reallocation is a manual journal entry.

02

Restructuring a cost center means re-keying history transaction by transaction.

03

Each acquisition arrives with its own systems, and integration takes quarters.

04

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.

_FLOW OF FUNDS/

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.

entity attribution
group inflowpayment received
attributionentity · cost center
intercompanycross-entity flows
roll-upgroup consolidation
_CAPABILITIES/

The primitives groups need

Built on the open-source Formance ledger.

Dimensional account structures, intercompany flows, and bulk restructuring, composed for multi-entity groups.

_DIMENSIONAL ACCOUNTS/

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

_INTERCOMPANY FLOWS/

Cross-entity movements post both sides atomically, so intercompany balances always net and eliminations are derived, not hunted.

always-balanced IC

_BULK RESTRUCTURING/

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 docs
_ACQUISITION ONBOARDING/

Bring an acquired company's books in through a mapped migration: shadow-run against their system, then cut over with the history intact.

mapped migrations

_BY THE NUMBERS/

Group-grade, by design

entity positionsliveper company · per cost center
intercompany postingsatomicboth sides · always net
restructuring operationsbulkhistory-safe
reporting roll-upanyentity · region · cost center
_NUMSCRIPT/

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.

invoice.num
// Post an invoice with full entity attribution
vars {
  string $customer
  string $company
  string $costcenter
  string $invoice
  monetary $amount
}

send $amount (
  source = @customers:$customer:$company:$costcenter:$invoice
  destination = @platform:ar:$company
)

// Balances now roll up by customer, company,
// cost center, or invoice, same record
_VOICES/

Trusted by builders

LiberisLiberis
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
DoctolibDoctolib
Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.

Healthcare · Financial OS

PayflipPayflip
Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.

Benefits · fintech infrastructure

_TRUST/

Built for regulated money.

Enterprise controls, the certifications auditors ask for, and an immutable record, out of the box.

See our trust center
THE COMPLIANCE STACK
IAM, RBAC & SSO
Non-repudiation
Audit logs
Observability & monitoring
Real-time events
Admin console
_AUDIT-LOG/ NON-REPUDIATION

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

CERTIFICATIONS
AICPA SOC IICERTIFIED
ISO 27001CERTIFIED
DORACOMPLIANT
REGULATORY FRAMEWORKS
EMIFCAMTLNYDFS Trust CharterOCC CharterMiCAGENIUS
_ATTESTED/
FAQ

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.

_GET STARTED/

A group that consolidates itself

See how Formance fits your entity structure: book a demo or start building.