Audit Log

The Audit Log is the history of your company file: what changed, when it changed, and whether it came from you in Doric or from connected automation. It gives you a readable trail down to individual transaction splits—and a safe way back when an action can still be undone.

Getting there

Open Audit Log with the document-and-clock icon near the bottom of the left sidebar. Newest activity appears first.

Reading the log

Each row summarizes one action:

When shows the local date and time.
Activity names the operation and the kind of record it affected.
Changes summarizes the fields changed by that action.
By shows the actor and source, such as your local Doric session or an MCP automation.
Status tells you whether the action can be undone.

Click anywhere on a row to expand it. The details show each affected record and the exact field values before and after the action. Bulk work stays grouped as one operation, but expands into its individual transactions or splits when you need the full story.

The numbers are identifiers: labels such as “Transaction #7149” and the smaller numbers beside change details identify the underlying record or audit event. They are useful for distinguishing similar transactions and for support or automation; they are not amounts or sequence numbers from your bank.

Finding a particular change

Search by activity, actor, or operation, or filter by record type, source, undo status, and date range. Click Clear to reset the filters and Refresh to fetch activity created since the page was opened. Doric loads a long history in pages; use Load more to continue backward in time.

Undoing an action

An action marked Can undo has an Undo button. Undo creates a new, recorded action that restores the earlier values; it never erases or rewrites the original history. This makes the trail honest while still letting you recover from a mistake.

Undo is not limited to the most recent action. Doric allows an older action to be undone whenever its affected records are still in the state that action left them in. If a later change touched the same state, undo is blocked instead of silently overwriting newer work.

A bulk action is all-or-nothing: every affected record must still be safe to restore.
If an affected transaction was later deleted, undo the deletion first, then return to the earlier action.
Some actions are recorded for accountability but are not logically reversible; their status shows that undo is unavailable.

Why the check matters: imagine accepting 75 imported transactions and later deleting five. Undoing the acceptance for only the surviving 70 would leave the original bulk decision half-reversed. Doric blocks it until all 75 are available again.

See the history of one transaction

You do not have to search the full log. In the register, open a transaction's vertical three-dot menu and choose View details, then select the History tab. It shows that transaction's creation, edits, split changes, and deletion or restoration history. The same transaction-detail window is available from transaction links in the Audit Log.

Deleted transactions remain available in their history and audit details even though they no longer appear in the register. That preserved record is what makes an eligible delete undoable.

The log stays with your books

Audit history is stored in the same local company file as the rest of your books. It is not sent to a Doric cloud service. The history is append-only: Doric does not offer a way to delete selected audit records, because removing the evidence of a change would defeat the purpose of the log.

Where to go next

Read The Register for working with transactions, or see Invoices and Bills for the document workflows whose changes also appear here.