Transaction search
Search the deposits ledger by date range on the value date and on the entry date, by amount range in integer cents, by transaction type, by direction, by derived status and by counterparty account — alone or in any combination. Each row is one customer leg of a balanced double entry; open its reference to read the full posting set together with any compensating entry correcting it.
Every customer account in the ledger. Add an account, a customer or a counterparty to narrow the search.
Pending is judged as at 2026-08-18 05:37:33 UTC. Statuses are derived, never stored: an entry whose value date has not arrived is pending; one with a compensating entry against it is reversed or adjusted; and a compensating entry says so itself. Nothing in this ledger is ever edited or deleted, so a correction always appears as a second, linked entry.
Any holder of an account may view that account's transactions. Add ?customerId=… — or open a customer and follow their account — to run the search on a party's behalf, scoped to exactly the accounts they hold.
Results (0)
Nothing matches these filters.
- Matching lines
- 0
- across the whole match, not just this page
- Credits
- 0.00
- 0 cents in
- Debits
- 0.00
- 0 cents out
- Net effect
- +0.00
- credits minus debits, in integer cents
No transaction matches these filters. No filters: every transaction in scope, newest by value date first. Widen a date or amount range, untick a type or a status, or clear the filters to start again.
A resulting balance is only meaningful within one account, so the column is not shown for a multi-account search. Narrow the search to one account to see it. Each row is one CUSTOMER leg of a balanced double entry; open the transaction reference to see the full posting set, both sides, any compensating entry linked to it and the supervisor authorisation behind a back-dated value date. Amounts are integer cents throughout — the positive amount is on the row and the debit/credit direction carries the sign.
The same filters are available over the API at /api/transactions, which takes the identical query string and returns the same rows, totals and scope as JSON.