The Second Copy: What the Audit Log Keeps When the AI Edits Your Invoice

Editing an invoice feels like tidying a desk: a date is wrong, a customer name carries a typo, a note no longer makes sense. You change it and move on. The consequences arrive later — when the monthly chart looks different from last week, or when the bookkeeper asks why March closed with a number nobody remembers entering. In Firmspace the edit takes seconds. The interesting part is the copy that stays behind.

That copy lives in Finance, on the Audit log tab — Protokoll in German, Zhurnal diy in Ukrainian. It is a list of financially significant actions, newest first, two hundred entries deep. Not everything that happens in the CRM lands there: the journal is deliberately narrow. It records the moments where the useful question is not what the value is now, but who changed it and when.

A line usually carries three things: what happened, written as a sentence with the document number; who did it; and the exact time. The action type and the object behind it are stored as well, so a line about invoice 2026-14 is attached to that invoice rather than floating as text. Reading the list feels like reading a bank statement: short sentences, chronological, no interpretation.

The assistant is why this matters more than it used to. Through a tool called update_invoice it can change the issue date, the due date, the supply date, the customer name or the notes of any invoice — draft, sent or paid. One field is stricter: the payment date can only be set on an invoice that is already marked paid, because that date decides which month the money appears in on the charts.

Before the assistant writes, the platform snapshots the fields it is about to touch: issue date, due date, supply date, payment timestamp, customer name, notes. The new values go into the record; both halves, before and after, go into the journal line as structured data. The summary names the fields in plain words, so the line reads as a sentence rather than as a diff.

Deletion follows the same logic. The assistant can delete an invoice of any status, and the interface answers that a copy stays in the audit log. That copy is the full record as it stood at the moment of deletion, not a reconstruction. It does not restore the invoice by itself, and nobody should expect a button that undoes a deletion — but the evidence outlives the object, which is the point.

The author in the journal is a person, not a model. When the assistant acts, it acts with the rights of the employee who asked, so the line carries that employee's name and the summary adds that the change happened via the assistant. This is a deliberate reading of responsibility: the firm asked a colleague to change the invoice, and the colleague used a tool.

Not every line has a human behind it. Recurring invoices that the platform issues on schedule sign themselves as Automation. Payment reminders that leave on their own carry the same name. Failures in background synchronisation appear as System. These entries are exactly what they look like: a machine doing the routine, with nobody to blame or thank.

Money coming in is recorded at one point. Whether a payment is registered by a person pressing paid, by an acquiring webhook, by a bank statement import or by the assistant, it travels through the same accounting function. That is why the journal does not fill with duplicates when the same transfer is confirmed twice, and why a reverted payment appears as its own line instead of as silence.

One design decision is worth understanding: the journal is written best-effort. If saving the line fails, the invoice edit still goes through. The platform treats the record as a witness, not as a lock. A stricter system would refuse the operation when it cannot write the evidence; Firmspace chooses the opposite trade-off. A gap in the list is therefore a technical incident, not a permissions trick.

Do not read the tab as a compliance certificate. It is not a full audit of every field, it shows the latest two hundred entries, and the before-and-after values are stored as structured data that the list itself does not display. It is a working record for the owner and the team: enough to reconstruct a decision, not a substitute for an accounting archive.

The habit is small. After a session with the assistant, especially one that touched dates, amounts or a customer, open Finance and read the lines marked as done via the assistant. If a month moved on a chart, the old values are right there and a human correction is a normal next step. The value of an AI assistant is not that it never errs; it is that its work can be checked without a screenshot.