Classic register totals and analysis (the figures shown before this dashboard, unchanged)
These tiles and charts are computed exactly as before, from the register rows the slicers select, before approved balance adjustments. The dashboard above is the authoritative view.
Register totals
Recovery & legal position
Counted by case, not by row, wherever one case consolidates several cheques.
Outstanding by principal
Balance still unrecovered on each principal's behalf.
Analysis
Every panel follows the slicers above, and every chart has its figures in text.
Aging profile
Outstanding balance by aging bucket
Monthly due, paid and outstanding timeline
Show the figures as a table
| Month | Due | Paid | Outstanding |
|---|
Top 10 customers by outstanding balance
Court diary · next 30 days
Court outcomes
Priority legal milestone alerts and next actions
Outstanding balance by company
Outstanding balance by branch
Recovered by payment mode
Loading the register…
How exports and shared copies work
Dates are shown and exported as dd/mm/yyyy. The downloaded Excel file carries dropdown lists on Company, Branch, Mode of payment and the yes/no/status columns, so edits stay valid when you re-upload it.
Records live on the shared server, so every signed-in user works from the same register. Save dashboard copy bundles the current data into a standalone read-only HTML file that still displays when you send it on — re-run it whenever you want to share a fresh copy.
One alert per case — the latest actionable stage, with earlier stages suppressed once the matter has moved on. Principal, company, branch and aging follow the slicers; narrow further by priority or stage here.
Changes are not written to the live register until an administrator approves them. Each request shows exactly which fields move, and from what to what. Every decision is kept permanently in the audit history.
A permanent record of every approval decision, account request, account change, register replacement, backup and restore. It cannot be edited or deleted from the dashboard.
| When | Decision | Change | Requested by | Decided by | Details |
|---|
Backups are consistent copies of the whole database taken with SQLite's online backup, stored on the server outside the web folder. One is also taken automatically before every register replacement, clear and restore.
Backup files
Verify checks a file's integrity without touching the live data.
| File | Created | Size | Result | Actions |
|---|
How restore works
Restoring replaces the register, the user accounts, the approval queue and pending account requests with the contents of the chosen backup. First the file is validated, then a fresh pre-restore backup of the current data is taken, then the swap happens in a single transaction. The audit history is never rolled back. Anyone whose account does not exist in the backup is signed out.
To restore a file brought from elsewhere, copy it into the server's backups folder with a name of the form ledger-YYYYMMDD-HHMMSS-note.db; it then appears in this list.
Accounts
Click any permission chip to grant or remove it instantly.
| Username | Role | Access | Permissions | Actions |
|---|
Add user
Add an account, reset a password, or change several permissions at once.
An account counts as an administrator while it holds Manage users & permissions; the dashboard keeps at least one administrator at all times.
Your access
What this account is allowed to see.
Appearance
Remembered on this device only.
Alert thresholds and rules
Administrators only. Changes apply at once and are kept in the audit history.
Change password
Updating signs out every other device holding the old password.