Guarantees, not features
The properties the system of record is built on. Every one is a property of the ledger, not application code you maintain.
A financial database is only as good as what it makes impossible. These primitives are why books on Formance cannot drift, cannot lie about the past, and cannot be spent into states that never happened. They come from the demo slide used with every technical evaluator, organized in four groups.
Correctness & integrity · Never wrong
Every posting balances by construction.
All legs commit, or none do.
Safe replays via idempotency keys.
Correct under high parallelism.
Reads reflect every committed posting.
Preserve each unit's identity in a pool.
Structure & modeling · Model any book
Colon-delimited paths model your whole book.
Roll up at any segment in constant time.
Any currency or unit on the same account.
Cumulative inflow and outflow, per asset.
No floating-point drift, ever.
Computed from the log, never stored.
History & time · Provable past
Tamper-evident append-only log.
Effective time and record time, both.
Reconstruct any balance, any date.
Effective-dated logic changes.
Compensating entries, not deletes.
Control & governance · In your hands
Bounded or unbounded, per account.
Every change attributable to an actor.
Queryable context on every entity.
Reject undefined or malformed accounts.
Isolated books within one deployment.
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.
Build on guarantees, not conventions
See the primitives in your own flows: start building or book a demo.