Audit trail

What it is

A paper register shows the current entry and, at best, a crossed-out line. A spreadsheet shows only the latest cell value. An audit trail keeps the history: when a stock count was adjusted, who did it and what the count was before; when an invoice amount was edited, by whom and why; when a payment was approved and by which manager. Entries are written by the system itself, not by the user, and cannot be quietly edited or removed afterwards.

In a well-built ERP or portal, the audit trail sits underneath every important table — items, prices, orders, invoices, payments, stock movements, user permissions — and is readable in context: open a record and see its history. It is complemented by login records and, where regulations require, by version histories of documents. Retention is a policy decision: some entries must be kept for years, others can be summarised.

Why it matters for a growing business

Once more than a handful of people touch the same records, questions arrive that memory cannot answer: why does the stock not match the count, who changed this price, when was this delivery marked complete, who approved this payment? Without a trail, the answer is a meeting and a guess. With one, it is a lookup — and the mere existence of the record discourages careless or dishonest edits.

The trail is also what external parties expect. Auditors, tax authorities, banks and — in garments and manufacturing — buyers' compliance teams want to see that figures can be traced and that changes were authorised. In Germany, the GoBD require that bookkeeping-relevant records be traceable, unalterable and documented in their changes; an audit trail is how a system meets that. For any company, it is what turns “trust me” into “here is the record”.

How AutoProbaho uses it

AutoProbaho builds an audit trail into every custom ERP, portal and workflow it delivers: field-level change history on business records, approval and login logs, and reasons captured for sensitive edits such as stock adjustments or price overrides. Trails are stored append-only in the client's own database, viewable per record and exportable for auditors or the Steuerberater, and access to them is itself controlled by role.