Banking¶
4 screens.
Bank Accounts¶
Banking → Bank Accounts
The accounts themselves. The account number is always shown masked.
What you see¶
The list of accounts, then a form below it to add one.
Fields¶
| Field | What goes in it |
|---|---|
| Name, Subsidiary, GL account | All three required. |
| Bank, branch, account number, currency | Optional. The number you type is stored securely and only ever shown masked. |
Buttons¶
| Button | When you can use it | What it does |
|---|---|---|
| Create | Once the required fields are filled in. | Adds the account. |
Rules this screen enforces¶
- Choosing the ledger account matters more than it looks: it is what every future reconciliation of this bank account is proved against. That is why adding a bank account needs setup rights rather than ordinary transaction rights.
Statements & Matching¶
Banking → Statements & Matching
Importing a bank statement and matching its lines to the documents they settle.
What you see¶
The list of statements already imported, and a button to import another.
On the import form, three chips above the paste box tell you what the system made of your paste as you type: how many lines it could read, what they add up to, and whether that agrees with the opening and closing balances you typed. The third turns green when they agree.
Opening a statement shows its lines with what each is matched to, and the buttons to match the rest.
Fields¶
| Field | What goes in it |
|---|---|
| Bank account | Required. |
| Period start / Period end | Required. |
| Opening balance / Closing balance | Required — copied from the statement. |
| The paste box | One movement per line, comma or tab separated, in the order date, amount, description, reference. A heading row is skipped. The amount is signed: positive is money in. |
Buttons¶
| Button | When you can use it | What it does |
|---|---|---|
| Import a statement | Always. Reads Close import once open. | Opens the import form. |
| Check without importing | Always. | Tests the paste and reports what it found. Nothing is saved. |
| Import | Only once the pasted lines add up from the opening balance to the closing balance. | Imports the statement. Any line it could not read is listed with the reason and left out. |
| Open | On any statement. | Opens it for matching. |
| Preview auto-match | On an open statement. | Shows what it would match. Nothing is saved. |
| Apply auto-match | On an open statement. | Asks first, then writes the matches. Lines with more than one candidate are left alone. |
| Match… | On an unmatched line. | Opens a search for the document. |
| Match | On a candidate document in that search. | Matches the line to it, recorded against your name. |
| Bank item | On an unmatched line. | Records it as the bank's own charge or interest — ours to record, not to match. |
| Unmatch | On a matched line. | Reverses the match. |
| Undo | On a line marked as a bank item. | Reverses that. |
| Cancel | In the match search. | Closes it without matching. |
| Close | On the open statement. | Goes back to the list. |
Rules this screen enforces¶
- Import is greyed until the pasted lines foot. That is not fussiness: a statement that does not add up from opening to closing has a movement missing, and importing it would put a gap into the reconciliation that nobody could later explain.
- The matcher never guesses between two documents of the same amount. Those are reported as ambiguous and left for you. A wrong match is harder to find later than no match, because the reconciliation still ties.
- A match you make by hand is recorded against your name, so the audit trail can tell it apart from one the matcher made.
- A bank item stays on the statement and still counts towards the total — it is recorded, not dismissed.
Reconcile¶
Banking → Reconcile
Proving the bank statement and our own records agree, laid out as a sum you can follow.
What you see¶
Choose the account and the date and the proof appears immediately: the ledger balance, less payments not yet on the statement, plus receipts not yet on it, plus the bank's own items not yet recorded, giving the expected statement balance — then the actual one, and the difference.
Underneath, the lists behind each line, so a difference can be worked rather than guessed at.
One list is worth understanding: Matched, but posted somewhere else — statement lines matched to a document whose entry went to a different bank account. The match is right and the posting is wrong, and until they agree the difference cannot close.
Fields¶
| Field | What goes in it |
|---|---|
| Bank account, As at | Which account, and the date to prove it at. |
Buttons¶
| Button | When you can use it | What it does |
|---|---|---|
| Refresh | Always. | Recalculates. |
| Show | On each supporting list. | Expands it. |
| Record reconciliation | Always — including when it does not balance. | Strikes the reconciliation and stores the difference and the date. |
Rules this screen enforces¶
- You can record a reconciliation that does not balance, and the button is not taken away. Refusing would not make the difference go away; it would make it undocumented. The stored record keeps the gap and the date, which is what makes next month's gap explainable.
- If it does not come to nil the screen says so and lists what to work through: an unmatched statement line, a payment posted to the wrong bank account, or a bank charge nobody has recorded.
Bill Settlements¶
Banking → Bill Settlements
Not a list of payments made here — a log of observations: supplier bills the daily sync reports as more paid than they were yesterday.
What you see¶
Every row is labelled, and the two kinds are kept visibly apart.
inferred means it was worked out from the bill's balance changing. For anything after the changeover this is the only evidence the system has that a supplier was paid, because the connection cannot read the old system's payment documents.
document means a real payment with its own number and entries.
A reversal — a bill that went backwards — is shown in bold red rather than hidden.
Rules this screen enforces¶
- Merging the two kinds into one list would present a deduction as a document. Keeping them apart on every row means nobody has to remember the difference.