Audit log

The audit log is your organisation's record of record-keeping: every change to your books and settings, who made it, and what the data looked like before and after. It is what lets you hand write access to a colleague — or an AI assistant — and still be able to answer "who changed this, and when?".

Where to find it

Go to Settings → Audit Log. The log is visible to owners, admins and accountants. Ordinary members cannot read it — it spans everybody's activity, and a read-only accountant who could not see who changed what would have little reason to trust the books they are signing off. See Team & roles.

What is recorded

Each entry answers four questions:

• Who. A person working in the web app appears by name. A connected AI assistant appears as the member it acted for, with a badge naming the client it acted through — an agent's work is never mistakable for a human's. Scheduled runs and system activity are labelled as such.
• What. The action and the record it touched. The record types covered include:
  • invoices and invoice payments
  • bills and bill payments
  • journal entries
  • period locks and year-end closes
  • bank accounts
  • organisation settings and ledger accounts
• When. Every entry is timestamped, and the list runs newest first.
• Before and after. Expand an entry to see exactly which fields changed, old value struck through beside the new one. Sensitive values are masked before they are stored, so the log never becomes a place to read secrets.

Reading an entry

Each entry carries a one-line summary of what happened, so most questions are answered from the list alone. Expanding it shows the field-level detail: only the fields that actually changed are listed — unchanged ones are hidden so the change stands out — and an event with no field-level detail says so explicitly rather than showing an empty diff.

Entries are shown newest first, with a Load more button to page further back.

Filtering

Two filters narrow the list:

• Filter by who — everyone, people in the web app, agents acting over MCP, scheduled runs, or the system.
• Filter by record type — just invoices, just journal entries, just organisation settings, and so on.

The combination answers the questions you actually ask: "show me everything the assistant did this week", or "who touched the bank account details?".

What it is for

• Reviewing an assistant's work. If you connect an AI assistant with write access, the log is where you check what it actually did — every action it takes is attributed to it, by client name. See Connect your AI assistant.
• Accountant sign-off. A read-only accountant can trace any figure back to the change that produced it before signing anything.
• Payment questions. Invoice and bill payments are record types in their own right, so "when was this actually recorded as paid, and by whom" is a filter away.
• Sensitive changes. Period locks, year-end closes and settings changes are exactly the events you want a trail for. See Period close.

The log is read-only for everyone — there is no way to edit or delete an entry from the app. That is the point of it.