Two books. One chain behind both
Sub-ledger detail and general ledger state, linked to the work behind them.
| Account | Debit | Credit |
|---|---|---|
| 6100 | $100,000.00 | — |
| 2000 | — | $100,000.00 |
- Entity
- Acme US
- Period
- 2026-09
- Posted
- 20 Sept 2026 · 17:20 UTC
- Description
- Payment settled — Cobalt Logistics Group INV-18377
- Caused by
- pay-ap-0002
- Recognised in
- SL-US-310002
- Evidence
- ev-ap-0002
The account-level state the finance team reports from. It rolls up the detail on the left; it does not replace it, and the detail is what an auditor asks for.
Not one “ledger”. Two responsibilities that need each other.
Merging them is the clearest sign a product was built by someone who has never closed a period. A controller will check the difference inside the first minute.
Sub-ledger
The detailed accounting record of financial activity: each transaction posted as balanced double-entry lines in exact minor units, with the balances they produce and the operational record they came from still attached.
Double-entry lines
Activity posted as balanced entries, in exact minor units. No floating-point value touches an amount.
Transaction-level detail
The accounting representation of a transaction, with the operational record it came from attached.
Sub-ledger balances
Balances that agree with the detail behind them rather than being asserted separately.
Roll-up to the General Ledger
Detail summarised into the accounts the General Ledger carries, traceable in both directions.
General Ledger
Accounts, journal entries, balances and the financial state a finance team reports from — with an audit trail that leads back through the Sub-ledger to the reconciliation, the execution, the approval and the source record.
Chart of accounts
The accounts financial state is reported against.
Journal entries
Entries carrying the activity, the accounts and the reason they were posted.
Balances and financial state
The position a finance team reports from, agreeing with the sub-ledger detail beneath it.
Audit trail
Every posting attributable and in order, traceable to the evidence behind it.
Every entry names the event that caused it.
An accounting record nobody can walk back to the operational event behind it is an assertion, not a record. Both books carry the source, the dimensions the event had and the evidence reference — so the question “why is this number here?” has an answer that does not involve anyone’s memory.
Dimensions carried on this entry: entity ACME-US · costCenter CC-1200 Manufacturing · vendor Cobalt Logistics Group · period 2026-09.
| Entry | Entity | Caused by | Lines | State |
|---|---|---|---|---|
| SL-AE-310001 | Acme UAE | inv-18492 | 3 | POSTED |
| SL-US-310002 | Acme US | inv-18377 | 2 | POSTED |
| SL-AE-310003 | Acme UAE | inv-ap-0003 | 3 | POSTED |
| SL-DE-310004 | Acme DE | inv-ap-0004 | 3 | POSTED |
| SL-UK-310005 | Acme UK | inv-ap-0005 | 3 | POSTED |
| SL-SG-310006 | Acme Asia | inv-ap-0006 | 3 | POSTED |
Bring your financial operations into one intelligent system.
Connect the ERPs, banks and providers you already run, establish one view of financial reality across them, and govern, reconcile and prove the work on top.
Onboarding is sales-led with company verification — there is no anonymous signup.