Skip to content
_LEDGER MODERNIZATION/

Retire the legacy ledger without betting the close

Move off Great Plains-era systems onto a programmable, API-first ledger: shadow-run both, prove they agree, then cut over with history intact.

legacy GL
mapping
shadow ledger
cutover
_THE PROBLEM/

The ERP ledger was built for batches, not products

Rigid GL strings cannot power modern finance operations.

The legacy GL runs on rigid account strings, nightly batches, and screens your team works around. Every new workflow (a portal, an automation, real-time reporting) fights the system it depends on, and replacing it feels like open-heart surgery.

01

Rigid GL strings encode the org chart of a decade ago, and every change is a project.

02

The ledger is batch-based, so balances are yesterday's truth at best.

03

Building modern tools (portals, automations, dashboards) against the old ERP means screen-scraping and CSV exports.

04

Migration risk is existential: get it wrong and you cannot close the quarter.

_PROOF/ Enterprises replace legacy AR ledgers with Formance as the system of record, keeping the ERP for what it is good at.

_FLOW OF FUNDS/

Shadow first, then cut over

Both ledgers run until they agree; then the old one retires.

Live events stream into Formance while history migrates through a mapped bulk import. The shadow ledger reconciles against the legacy system until both agree on every balance; then you cut over, with the ERP consuming roll-ups downstream.

shadow reconciliation
legacy GLsystem of record today
mappingCoA translation
shadow ledgerboth run, reconciled
cutoverFormance is the record
_CAPABILITIES/

The primitives modernization needs

Built on the open-source Formance ledger.

A programmable chart of accounts, bulk migration tooling, and an API-first surface, composed for replacing legacy ledgers safely.

_FLEXIBLE CHART OF ACCOUNTS/

Replace rigid GL strings with a dimensional account structure designed around how the business works now, and change it when the business changes.

designed with you

_BULK MIGRATION/

History migrates through bulk endpoints at balance or transaction level, through an explicit mapping from the old chart to the new.

mapped, repeatable

Read the docs
_SHADOW RECONCILIATION/

Run Formance alongside the legacy ledger and reconcile them continuously: cut over only when both agree on everything.

prove before cutover

_API-FIRST SURFACE/

Every balance and posting available over API and events in real time: build the portals and automations the ERP never allowed.

build on top

_BY THE NUMBERS/

Modernization without the cliff

big-bang cutovers0shadow-run · then switch
history preserved100%balance or transaction level
balancesreal-timeAPI-first · event-driven
to first shadow runweeksmapped migration
_NUMSCRIPT/

The new ledger speaks your dimensions

GL strings become structured accounts you can query.

A legacy GL string like 100-B0313-AR becomes a structured, queryable account path: same meaning, real structure, and every roll-up derived instead of report-coded.

migrate.num
// Legacy GL string → structured account
// "100-B0313-AR"  becomes:
//   @platform:ar:company100:B0313

vars {
  monetary $opening_balance
}

// Opening balance posted from migration
send $opening_balance (
  source = @migration:gp-cutover
  destination = @platform:ar:company100:B0313
)
_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

Modernization, answered

01 / DO WE REPLACE THE ERP ENTIRELY?

No: Formance becomes the operational system of record for money movement; the ERP keeps consuming roll-ups for statutory accounting. Each system does what it is good at.

02 / HOW DOES THE MIGRATION ACTUALLY RUN?

Chart of accounts first, then a mapping from the old structure, then bulk import, at balance level or full transaction history, while live events stream in parallel.

03 / WHAT IF THE TWO LEDGERS DISAGREE?

That is the point of the shadow run: continuous reconciliation surfaces every difference before cutover, so the switch happens on proof, not hope.

04 / CAN WE BUILD OUR OWN TOOLS ON TOP?

Yes: everything is API-first with real-time events, so AR portals, approval workflows, and dashboards build against the ledger directly.

_GET STARTED/

Modernize on proof, not hope

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