Cash & bank reconciliation¶
Your bank accounts, the receipts and payments through them, and matching them to the bank's own statement.
Where: /cash, with three tabs: Bank accounts, Movements, Reconciliation.
Bank accounts¶
Open a bank account with its code, name, bank and SWIFT, branch, account type, number or IBAN, currency, and a GL role (resolved to a chart code at posting time, defaulting to a bank-control role). The balance shown is deliberately the book balance, what your ledger says, not the bank's.
Using a role rather than a fixed chart code means several bank accounts can report through one cash line in the statements.
Recording money¶
| Action | What it does | Debit | Credit |
|---|---|---|---|
| Record receipt | Money in (optionally settling a specific customer invoice) | Bank | Receivables control |
| Record payment | Money out (clearing supplier invoices) | Payables control | Bank |
Amounts are always positive: the direction (receipt or payment) carries the sign.
Reconciliation¶
On the Reconciliation tab, import a bank statement (its lines and closing balance) and auto-match each statement line to an unreconciled book movement by amount and direction (and reference). Matched movements are cleared. You are left looking at the two unmatched sides (a deposit the bank has not shown yet, a bank charge your books do not have) and the book-minus-statement difference.
Two things to keep in mind:
- Matching posts nothing. It clears a reconciled flag on movements that already posted.
- Missing entries are posted separately. A bank charge or interest the reconciliation surfaces is recorded as an ordinary cash movement, which does post.
Zero-touch when the other side is also Cortex
When a payment's counterparty is itself on Cortex, reconciliation can match deterministically on the payment's correlation id, no guessing. Statement-file parsing (MT940 / CAMT / CSV) and fuzzy matching are deferred; the reconciliation API takes structured lines for now.
Permissions: cash:read, cash:manage, cash:reconcile.