An audit trail turns the question of who changed this transaction from a guess into a lookup. It is a time-ordered record of edits, additions and deletions, each stamped with a person and a moment, so you can see the history of any number in your books.
The example is a flat-share household with a shared bills tracker, plus a note on small businesses. Everything is in pounds and invented, and it covers records and habits rather than compliance.
The shared-bills mystery
Three housemates log shared costs in one tracker. On the 1st the electricity bill sat at £96.40. On the 8th it says £69.40 and the monthly split looks lighter. Nobody remembers touching it. With only three people, the temptation is to start an argument. An audit trail replaces that with a quick look: it shows the amount was changed from £96.40 to £69.40 on the 4th by one housemate, perhaps while fixing a typo. Dispute over, and the figure goes back.
What do you read in each line?
- The person, so you know whom to ask
- The date and time, so you can match it to events
- The field that changed, such as amount, category, date or note
- The old and new values
- The action: created, edited or deleted
Read them top to bottom, newest first, and look for patterns: the same person editing amounts repeatedly, or several deletions in a row.
How much does a slip cost?
Work out the effect so you know whether it matters. Electricity £96.40 recorded as £69.40 is a gap of £27.00. Split three ways, each housemate underpays by 27 divided by 3, which is £9.00. For a business, the same slip on a supplier invoice flows into totals, categories and every report built on them, so a quick check of the log saves a bigger tidy-up.
| Month | Recorded | Actual | Gap | Per person (3) |
|---|---|---|---|---|
| Electricity | £69.40 | £96.40 | £27.00 | £9.00 |
| Broadband | £32.00 | £32.00 | £0.00 | £0.00 |
Should everyone be able to edit everything?
In a shared household, the honest answer is usually yes for the current month and no for past months. For small businesses, give the person entering receipts the right to add, and keep editing and deleting for someone who checks the work. Roles are your first line of control; the log is your second, showing what happened despite the roles.
What if your app has no log?
Not every tracker records who changed what. In that case, build your own trail. Save a copy of the data at the end of every month, name the file with the date, and compare the two when something looks off. Add a notes column where each person writes initials and a reason whenever they change something. It takes a few seconds and answers most questions later. SpendixAI does not list an audit log among its documented features, so for personal use there, a dated export once a month does the same job.
A monthly routine in five minutes
- Open the history, filter to the last month
- Look for edits to entries older than a month
- Look for deletions, and check the recycle bin if there is one
- Ask about anything unexplained
- Save a dated export
Housemates who do this once a month find that the tracker stops being a source of friction. People behave more carefully when they know changes are visible, and nobody has to play detective when a figure looks odd. The same routine works for a two-person business: the five minutes cost almost nothing, and the first time it spares you a row or a wrongly reported total, it has paid for itself.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

