Settlement engine · hosted or licensed
Settlement to journal, as an engine you can license.
LedgerBridge is the engine we run behind our own books, packaged for firms and platforms that want the settlement logic rather than another app. Ingest the payouts, classify every fee, emit journals that tie to the bank — inside your own product.
Self-hosted, single container, licensed per installation. No endpoint of ours sits in your client's data path.
01
Every firm building this starts from zero.
A payout file is not a transaction list. Splitting it by month, classifying fees, keeping per-channel clearing accounts and proving the journal ties to the bank is weeks of unglamorous work that every team rewrites from scratch.
Payout formats are hostile
Each channel ships a different shape, changes it without notice, and calls the same fee three things.
Fee mapping is the real work
Unknown fee types must stop the journal. A pipeline that silently absorbs them produces books nobody can defend.
Audit proof is not optional
The output has to show that the components equal the payout, line by line, months after the fact.
02
How it runs
Deterministic, idempotent, and allowed to fail. A run either produces a balanced journal or tells you precisely where it refused.
Ingest the settlement
Channel adapters read the payout from the source the client actually has, and re-runs do not double-post.
Classify every fee line
Mapped fees post to their own accounts. An unmapped fee enters the mapping queue and stops the journal.
Emit the journal
Split by transaction month, cash on the deposit date, per-channel clearing, exported in the target ledger's format.
03
What is in the box
Multi-channel ingestion
Amazon, Shopify, WooCommerce, Authorize.net and Etsy adapters behind one interface.
Fee mapping queue
The unglamorous part, already built: classify once, reuse across settlements, block when unknown.
Balanced journal output
Per-channel clearing accounts, month split by transaction date, cash on the deposit date.
Restatement handling
A restated settlement adjusts the prior journal instead of double-booking the month.
Deterministic and idempotent
Same input, same journal. Re-runs are safe, which is what makes automation defensible.
Security suite
103 attack assertions sit alongside the functional ones, so hardening is tested rather than assumed.
04
Licence model
Licensed per installation, quoted with the engagement. You get the engine, the mapping library and the deployment, and your clients' data never passes through us.
Enterprise licensing
Quoted per installation and scope. Firms embed it in their own product; we do not compete with the product it powers.
The engine, not the app
You bring the UI and the client relationship. LedgerBridge does the settlement arithmetic underneath.
Deployment and handover
Container, Caddy, licence file, runbook and the mapping library — installed, then yours to run.
Not hosting it yourself? The same engine runs as a hosted app — $19/month for one store, $49/month multi-channel, $99 one-time setup. No licence file needed.
05
Questions, answered.
What exactly am I licensing?
The settlement engine: ingestion adapters, fee mapping, journal generation and the licence enforcement. Not our sales site, not the hosted interface we run in-house.
Is it a hosted API?
No. It is self-hosted in one container on your infrastructure, which is the point — client data does not leave the box.
How is the licence enforced?
A signed Ed25519 licence file verified locally, so it works without a call home and without our availability in your path.
Which channels are supported?
Amazon, Shopify, WooCommerce, Authorize.net and Etsy adapters, with the mapping library covering the fee types seen in practice.
Can we extend the fee mapping ourselves?
Yes. The mapping library is data, not hard-coded logic, and additions are testable against the suite.
Bring a settlement file. We will run it in front of you.
A technical walkthrough with your own payout file: ingestion, fee mapping, journal, and the cases where it refuses to post.