All Payments
Route: Finance → All Payments (/bank/entry/list)
This is the ledger of every bank entry across all your accounts — one row per line on your bank statements, income and expense alike. The page is headed Bank statements; the subtitle counts the entries, the accounts they come from, and how many are not fully assigned yet. It is where you reconcile transfers against bookings.
All Payments ledger
| Column | What it shows |
|---|---|
| Date | The value date of the transaction. Click the header to flip the sort order. |
| Bank | The account the entry belongs to (a globe icon marks Wise accounts). Click it to open that account. |
| Purpose | The bank's text for the line, with its reference underneath. |
| Amount | The amount in the entry's currency, with a green arrow for money coming in (Incoming) and a red arrow for money going out (Outgoing). |
| Assignment | The status — Assigned, Partial or Open — with the assigned amount ("… of …" while partial) and a progress bar. |
The link icon on a row opens the entry to match it (next sections); the trash icon deletes a manually created entry after a confirmation — entries imported from a statement or from Wise can't be deleted.
The toolbar filters the list:
- Unassigned only — hides everything already fully assigned.
- Incoming only — hides money going out.
- Bank and Currency — pick one account or one currency; each option shows how many entries it holds.
- Text, reference or amount — searches the purpose, references and amounts.
- Reset clears every filter and the search.
Choose 10, 25 or 50 rows per page at the bottom. If your company has payment-provider import formats configured, an Import statement button in the header imports a provider file here.
Importing a bank statement
Statement files are imported into a bank account. Open the account (from All Banks) and click Import, then choose the file your bank exported. Gurita detects the format automatically — it reads CSV, MT940 (.sta), QIF, OFX and QFX, and CAMT (ISO 20022 .xml). It creates one bank entry per statement line and skips any line it already holds, so re-importing an overlapping statement never doubles up an entry.
To import a statement and reconcile it:
- Go to All Banks and open the account the statement belongs to.
- Click Import and pick the exported file.
- If Gurita cannot recognise a CSV's columns, a mapping step opens. Match each column (date, amount, description, reference) to the field it holds; optionally tick Set account balance manually and enter the opening and closing balances. Click Save.
- The new lines appear in All Payments (and in the account's own Payments list), each marked Open until you match it.
- Match each incoming line to its booking (next section). Expense lines you don't need to match can be left as they are.
- Confirm the account's balance strip shows Matches — see Reconciling an account above.
Tip: import statements regularly (weekly is common). The sooner an entry exists, the sooner you can match it and the more accurate every booking balance stays.
Matching a payment to a booking
This is the core reconciliation step. Open an entry (click the link icon on its row) to see the Assign payment entry dialog.
Assign a bank entry to a booking
The header shows the entry's description and date. Below it, a strip summarises the transaction:
| Field | What it shows |
|---|---|
| Bank account | The account the line was imported into. |
| Booked | The value date. |
| Value | The full amount of the line (negative for money going out). |
| Assigned | The amount matched so far, with a progress bar. The caption reads "… still open on this entry" until every cent is matched, then switches to "Fully assigned". |
The assignments table
Every payment already matched to this entry is listed with its Date, Reference, the Booking / customer it was matched to (or "Without booking"), its Value, and Actions. A green cash icon next to the value means that booking is now fully paid. If an assignment replaced one or more temporary payments, a "Replaced temp" chip appears next to it — hover it to see which ones, with their reference and amount.
Two actions sit in the last column:
- The eye icon opens that booking's payment tab.
- The trash icon removes the assignment. This happens immediately — there is no confirmation step, and it cannot be undone. If the booking is resolved (fully settled and closed), the button is disabled with the note "The booking is resolved — this assignment can no longer be removed."
Warning: removing an assignment does not bring back the temporary payments it replaced. If that money needs to be on the booking again, log a fresh temporary payment or assign a real one.
A note under the table reminds you: "Only the assigned amount is booked as a payment on the booking. The open amount stays on the bank entry and can be assigned to further bookings later."
Adding a new assignment
The New assignment panel sits on the right of the dialog. It is hidden once the entry is fully assigned, and also hidden if you don't have the rights to edit bookings and bank entries.
- Booking — search by invoice number, booking number, guest, or agency name (type at least 3 characters). If the transfer's reference matches an open booking, Gurita lists it under Suggested from the transfer reference with a Match marker — click the chip to pick it without typing. Once picked, the booking's card shows its Agreed, paid, and open amounts.
- Amount — defaults to the entry's remaining open amount. Two quick-fill buttons speed this up: Open fills the full open amount of the bank entry; Booking fills what the selected booking still owes (shown only when that differs from the entry's open amount).
- Asking for more than the entry has open is blocked with "Exceeds the open amount of the bank entry (…)."
- Asking for more than the booking still owes is allowed but warned: "More than this booking still owes (…) — the booking will show the difference as overpaid." When credit is on, you can move the left-over to credit instead — see Bank entries and credit.
- If the booking is billed in a different currency, a note says the amount will be converted, and Gurita asks for an exchange rate before saving (see Different currencies below).
- Reference (optional) — pre-filled with the booking's latest invoice number; overwrite it if you want different wording on the folio.
- Temporary payments on this booking — if any are open, they are listed with a checkbox each, all ticked by default. Only the ticked ones are removed when the assignment is saved — untick any this transfer does not settle.
- Click Assign €….
Tip: you can assign money without picking a booking — useful for income that isn't tied to a reservation. It appears in the table as "Without booking".
Note: on an outgoing (negative) bank entry, the amount you assign is also negative — Gurita keeps the sign of the entry and the payment in step.
Splitting one entry across bookings. A lump-sum transfer often pays several bookings at once. Assign part of it, then repeat the steps — the Open quick-fill always reflects what is left, and the progress bar in the strip fills up as you go.
Unallocated money. If a transfer is larger than the booking it pays, assign only what the booking owes and leave the rest open on the entry for another booking, or move it to the agency's or guest's credit (see Bank entries and credit). Never inflate an amount just to make an entry go green — the surplus belongs somewhere real.
Different currencies. If the booking is billed in a different currency from the bank entry, Gurita opens Exchange rate required before recording the payment, so the booking is credited in its own currency. The same dialog appears when an on-site payment is taken in a currency other than the bill's.
- Enter rate — type the exchange rate. The field is prefilled with the rate Gurita suggests, shown the readable way round (for example
1 EUR = 19.700 IDRrather than1 IDR = 0,0000507614 EUR). The Swap direction button next to the field flips it without changing the rate; the line under the field always shows the reverse reading. - Enter amount — type the amount actually received in the booking's currency instead; Gurita shows the implied rate under the field.
The panel below shows the Payment and what it will be Booked as before you commit. Save rate stays disabled until the field holds a number greater than 0; Enter saves and Esc cancels.
Temporary payments
A temporary payment is money recorded on a booking that isn't a confirmed payment yet — a placeholder for a transfer you expect, so the booking's balance already looks settled and no reminder goes out. It is added on the booking itself.
To resolve a temporary payment: wait for the real money to appear as a bank entry here, open that entry, and pick the same booking in the assign dialog's new-assignment panel. Its open temporary payments are listed under Temporary payments on this booking, all ticked by default — leave the one this transfer settles ticked (untick any that don't apply) and assign the payment. The ticked temporary payments are removed the moment the assignment is saved, so the booking is not credited twice.
Example. An agency tells you a €700 transfer is on its way for booking 12345. You add a €700 temporary payment on that booking. Three days later the transfer lands; you import it, open the entry, pick booking 12345, and assign €700 with the temporary payment left ticked. The temporary line disappears and a real Bank Transfer payment takes its place — the booking was never credited twice.
Warning: temporary payments count towards a booking's paid amount, so a booking can look settled on the strength of money that hasn't truly arrived. Resolve them as soon as the real transfer arrives.
Reconciliation and the locked-month freeze
Reconciling a period means every statement line is imported, every incoming line is matched to a booking, and each account's balance strip shows Matches. A tidy way to close a month:
- Import every account's statements for the month.
- Filter All Payments to Unassigned only and clear the incoming lines one by one.
- When a transfer settles a booking's temporary payment, assign it with that temporary payment ticked (see Temporary payments).
- Confirm each account reconciles on All Banks.
Once a month is closed for reporting, a manager can lock it on the finance report. A locked month freezes that month's profit-and-loss figures — they are reported from a snapshot and stop moving, even if a later edit touches a booking dated in that month. Months lock one asset at a time, oldest month first, and only the most recently locked month can be unlocked. Locking is a reporting control: on its own it does not stop you importing or matching payments — that is what the resolved state on a booking does. See period locking in Reports.
Who can access this: requires the Bank entries permission (view). Adding or removing an assignment also needs the Bookings (edit) and Bank entries (edit) permissions. The eye icon that opens a booking's payment tab needs the Bookings (view) permission. Visible when the Bank module is active.
