Editing and history
How to fix transactions, and how every change is captured in an append-only audit log.
People make mistakes. Bookkeepers fix typos every day. Axerity supports full edit plus a complete audit history so corrections are easy without losing accountability.
Editing a transaction
In Books → Transactions, hover any row. Three icons appear on the
right edge:
- 🕐 History — opens the audit drawer for this entry.
- ✏ Edit — opens the same form you posted with, prefilled.
- 🗑 Delete — confirms and removes.
Click Edit. Change the date, memo, reference, lines, or attachments. Hit Save changes (⌘↵).
Behind the scenes, saving:
- Removes the old lines from the per-account balance cache.
- Replaces every line with what you submitted.
- Re-applies the new lines to the balance cache.
- Writes an audit row capturing the before/after snapshot.
All of that runs in a single database transaction, so a partial failure leaves nothing inconsistent.
Deleting a transaction
Hover row → trash icon → confirm. The entry is removed from the live books, balance cache rolls back, and an audit row is written so the deletion itself is on record.
Audit history
Click the history (🕐) icon on any transaction. A drawer slides in from the right showing every change ever made to this entry, oldest first:
- CREATE — the moment it was posted.
- UPDATE — what fields changed (date, memo, reference, line counts).
- DELETE — when it was removed and by whom.
Each row shows the action, a timestamp, and (for updates) a diff of what moved.
The log is append-only. Rows are never modified or removed. If you
ever delete a transaction, the audit row survives — the entry's
entryId is set to null, but the before-snapshot in the row
preserves everything.
Why this matters
If you ever face a tax audit or a financial dispute, the question is always "what happened on date X, and who did it?" The answer needs to exist regardless of subsequent edits or deletions. Axerity guarantees that — the same way a paper general ledger would, except faster to read.