Core banking
Cash, liquidity & the ledger
This is the treasurer's home screen: every account, its balance, and the tools to move liquidity to where it is needed. Underneath sits a proper double-entry ledger — the same accounting backbone a core banking system runs on.
Accounts, pooling and sweeps
Accounts are arranged as a pooling tree: physical header accounts with virtual accounts beneath them, so a group can see one notional position while keeping each entity's cash identifiable. A sweep moves surplus cash up the tree — or into a green instrument — on a rule, instead of a person watching balances and wiring manually.
The ledger is the source of truth
Every balance you see is derived from an append-only, double-entry ledger. Each movement posts equal debits and credits, so the books always balance; the "What's real" page runs exactly that check live and shows zero unbalanced journals. Entries can never be edited or deleted — database triggers reject the attempt — so the history is tamper-evident by construction.
You can export any account's activity as a valid ISO 20022 camt.053 statement or a SWIFT MT940, generated from those ledger entries, not from a template.
Good to know
The camt.053 and MT940 buttons on an account produce real, standards-valid files — open one and check it against the schema.
Because balances are ledger-derived, a settled payment and the balance it changed can never fall out of step.