Health and family

Expense audit logs explained: who, what and when

An audit log lists who made each change to your expense records. See how to read it, with a euro example of a deleted transaction, and what to do next.

Editorial illustration for Expense audit logs explained: who, what and when

Think of an audit log as the minutes of your finances: a dated list of who did what to which record. When a figure looks wrong or a transaction has vanished, it is the first place to look, because it lets you reconstruct events without relying on anyone's memory.

This European-flavoured example centres on a deleted transaction and uses invented euro figures. It is about reading records and building habits and does not address regulation.

A transaction goes missing

A small design agency of four people notices that its October card spending shows €5,418.60, while the card statement totals €5,731.00. The gap is 5,731.00 minus 5,418.60, which is €312.40. Somewhere a line of exactly that size has disappeared. A search by amount finds nothing, because it is no longer in the list. The audit log, however, has a line: deleted, hotel booking for a client workshop, €312.40, by the office manager, October 29.

Now the question is the right one: was that deletion deliberate? Maybe the booking was a duplicate. Maybe it was cancelled and refunded. Maybe it was a mistake. The log tells you who to ask and where to look.

Where do deleted items go?

In many apps a deleted transaction goes to a bin for a while before it is gone for good, which is a safety net. Check your tool's behaviour before you need it: how long does the bin keep things, and who can restore them? If a deleted entry can be restored, restore it first and then decide what to do with it, so the totals are right while you investigate.

What patterns deserve a second look?

  • Deletions of large amounts
  • Edits to old months after reports were sent
  • Many small edits in a short time by one person
  • Changes late at night or on weekends when nobody normally works
  • A category changed on a high-value item

A pattern is not proof of anything. It tells you where to spend your five minutes.

Can the log replace receipts?

No. The log tells you what was done in the app; it does not tell you what happened in the real world. Pair it with receipts, invoices and statements. A good rhythm is to run three checks at month end, as follows.

  1. Statement total equals the app total for each account
  2. Every deletion in the log has a note or an obvious reason
  3. Every edit to an older month has a name and an explanation
CheckResult in OctoberAction
Card statement vs app€5,731.00 vs €5,418.60Gap of €312.40, trace in log
Deleted lines1Ask the office manager
Edited old entries0None

What if your tool lacks a log?

Take a monthly snapshot. Export your transactions to a file, put the date in the file name and keep every month. When a number moves, compare two snapshots. You can see added, removed and changed rows with a simple side-by-side check. It is crude, but it works. SpendixAI, built for India and INR, does keep deleted transactions in a recycle bin for 30 days, which is a useful safety net, though it does not list a full change history in its published features.

What to do this week

  • Find out whether your tool has a history view
  • Test how deleted items behave
  • Agree who may edit old months
  • Start a monthly dated export

A final tip for teams: when you restore or correct something, add a line in the notes explaining the fix, such as restored after checking the supplier's email. A log that shows the delete, the restore and the reason tells the full story in three lines, and it is exactly the kind of record that makes an outside reviewer comfortable with your books.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports