Tokens are a currency. Give them a ledger.
Post every billable event atomically (customer balance, revenue, and cost of serving together) and know your margin per model, per customer, per dimension, in real time.
Your billing platform meters revenue. It cannot see cost.
Consumption AI breaks the traditional billing stack.
The effective price of a token spreads ~50x across model, cache state, batch, mode, region, and channel, and the cost of serving moves just as fast. Billing platforms meter what you charge; the question that decides pricing ("what did we make on this customer, this hour, on this model?") has no system of record.
Effective token pricing spans model, cache state, batch, mode, region, and channel, and margin per customer is a quarterly estimate, not a number.
Billing tools track what you charge, never what it cost to serve: the dual balance does not exist anywhere.
Cloud marketplace remittances arrive as aggregated wholesale sums that someone reconciles back to per-token usage by hand.
Prepaid commits with real-time drawdown and monthly true-ups are bent into subscription billers that cannot express them.
_PROOF/ Formance runs event-level consumption ledgers in production: hundreds of thousands of monthly events, zero reconciliation errors across 18 months.
Every billable event, fully posted
One event updates balance, revenue, and cost, atomically.
A token event draws down the customer's prepaid balance, recognizes revenue on its exact dimensions, and accrues the cost of serving: one atomic transaction, billions of times, so margin is a query instead of a month-end model.
The primitives consumption AI needs
Built on the open-source Formance ledger.
Event-level posting, dual-balance margin, native commit drawdown, and channel reconciliation, composed for businesses that bill by the token.
Every billable event posts atomically across customer, model, and channel accounts: thousands per second sustained, exactly-once, replay-safe.
atomic at token scale
Revenue and cost of serving accounted side by side on the same dimensions: margin per customer, model, or region is a real-time query, not a data project.
cost beside revenue
Prepaid commits as wallet balances with real-time drawdown and monthly true-up to the floor: native, not bent into a subscription object.
native drawdown
Read the Numscript docsAggregated marketplace remittances matched back to per-event usage per channel, so wholesale revenue is as auditable as direct.
wholesale to per-event
Consumption-scale accounting
One event, three postings, zero drift
Drawdown, revenue, and cost: one atomic transaction.
A single Numscript transaction draws down the prepaid commit, recognizes revenue on the event's exact dimensions, and accrues the cost of serving: the three balances can never disagree.
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.
Token accounting, answered
01 / IS THIS A BILLING SYSTEM?
No: it is the substrate underneath one. Keep your payment provider and biller for invoicing and collection; the ledger holds the event-level state of record they all read from.
02 / CAN IT HANDLE BILLIONS OF EVENTS?
The ledger sustains thousands of transactions per second per ledger and scales horizontally. Aggregation across dimensions derives from the log, not from a warehouse recomputation.
03 / HOW DO MARKETPLACE CHANNELS RECONCILE?
Wholesale remittances arrive aggregated; the ledger already holds per-event usage per channel, so matching them is a reconciliation policy, not a quarterly data project.
04 / DOES IT SURVIVE AN AUDIT?
Yes: an append-only, immutable event history with per-dimension revenue states gives finance an ASC 606 basis and auditors direct evidence, at consumption scale.
Know your margin while the tokens are still flowing
See how Formance fits your consumption stack: book a demo or start building.