PRODUCT · LEDGER

Accounting-grade positions, as an API.

Ledger is a double-entry positions engine. Every movement is recorded as balanced debit and credit entries, so balances are always provable and every state reconstructs from its history. Use it standalone, or reach it through the One API.

Start in sandbox Read the docs →

Double-entry by construction

Every transaction balances debits against credits, enforced by the engine. It never commits a half-posting, so your books are always provably consistent.

Hierarchical accounts

Model accounts with classes, multiple currencies, liquidity policy, and overdraft limits. Roll balances up a subtree, or read entry history per account.

Holds and reversals

Reserve available balance with a hold, then release it in whole or part. Reverse a transaction with inverse entries — the original is never mutated.

Audit-grade export

Stream your full history as NDJSON. Replaying the entries reconstructs live balances exactly, and two exports of one state are byte-identical.

Enforced idempotency

Every post carries an idempotency key the engine enforces structurally. Retries are safe; a conflicting reuse is rejected, never double-applied.

Tenant isolation

The tenant is resolved from the verified credential, never from input. A caller can only ever reach its own tenant's data.

Let's talk integration.

Building something on Posteering, or weighing a fit? Send a note and the team will get back to you.