Wallets

The Wallets page is a ledger of every credit and debit that has affected a client's prepaid wallet balance in your organisation. Client wallets hold prepaid credit that clients can spend when booking and paying online. Almost every entry is created automatically by the system as clients top up, pay, are refunded, or redeem vouchers.

Administrator-level operators can additionally post a manual wallet adjustment — a credit to add funds or a debit to remove them — from this page (see below). Ordinary operators see the ledger read-only and cannot add, edit, or remove entries here; only tags and internal notes can be changed.

Overview

Wallet entries are shown in a paged table of 25 rows, newest first, with sorting handled server-side. Each row is one transaction. The page does not show running balances — a client's current balance appears in the Wallet balance column on the Clients page.

Columns

• Date — the date and time of the entry.
• Client — the client whose wallet was affected.
• Credit — the amount added to the wallet, formatted in your currency and right-aligned.
• Debit — the amount taken from the wallet, formatted in your currency and right-aligned.
• Event type — a colour-coded chip describing what caused the entry (see below).

A trailing cell shows a small tag icon when the row has tags and a note icon when it has internal notes.

Event types

Each entry carries one of these colour-coded event types:

• Top-up (green) — credit added to the wallet.
• Payment (blue) — wallet credit applied to a purchase at checkout.
• Refund (orange) — credit returned to the wallet by a refund.
• Voucher (purple) — credit from a voucher redemption.
• Expiry (red) — credit removed because it expired.
• Migration (grey) — an entry created during a data migration.
• Adjustment (teal) — a manual credit or debit posted by an administrator.

Adjusting a wallet manually

If you have the administrator role (configuration.write), an Adjust wallet button appears above the table. It opens a small dialog where you:

1. pick the client,
2. choose Credit (add funds) or Debit (remove funds),
3. enter the amount, and
4. give a reason (required — it is stored on the transaction and printed on the accounting document).

Saving the adjustment posts the wallet entry and creates a backing accounting order with a receipt PDF, exactly like an automatic movement, so the ledger stays audit-complete. The adjustment appears immediately in the list as an Adjustment entry. Operators without the administrator role do not see this button.

Searching and filtering

Use the search field ("Find wallet entry") to narrow the list; the search runs automatically a moment after you stop typing.

Next to it, the month/year picker restricts the list to a single calendar month. You can pick any month within the last five years up to the current month.

Expanding a row (tags & notes)

Every row can be expanded to reveal a tags and internal notes panel. You can add tags and post timestamped internal notes (each note records who wrote it and when). Nothing is stored until you press the panel's Save button, which stays disabled until you have actually changed something. These tags and notes are the only data you can change on this page.

Exporting to Excel

The Excel button above the table exports the rows currently shown — date, client, credit, debit and event type. The button is disabled while the list is empty.

Online requirement

The ledger is loaded live from the server and is never cached locally, so this page needs an internet connection: when you are offline it shows a message that you need to be online instead of the table. The list reloads automatically when you switch organisation.