The Transaction Audit Trail gives you a complete, permanent record of what happened to every transaction in your books, who created or changed it, when, exactly what changed, and the login session behind each action. It's built for accountability: for your own control, and for handing an auditor evidence instead of assurances.
Who can access it
The Transaction Audit Trail is permissioned and read-only.
It is enabled by default for the Account Owner.
The Owner can grant it to any other user — including an external auditor — through User Permissions.
No one can edit or delete audit records, regardless of permission. The trail is view-and-export only.
Where to find it
Go to Reports → Transaction Audit Trail.
Reading the main list
Each row is one transaction — one entry posted to your ledger. The columns:
Column | What it shows |
Serial ID | The audit record's own reference (TRA…) |
Created Date | When the transaction was created |
Transaction ID | The transaction/document ID (INV…, RC…, JV…) |
Transaction Date | The accounting date of the entry |
Source Document | The document this transaction came from (clickable) |
Category | Invoice, Receipt, Refund, Journal Entry, Bill, etc. |
Amount | The transaction value |
Created By | The user who created it |
Timestamp | Time of creation |
Reviewed | Yes / No |
Actions | View activity (eye) and download PDF |
Filtering
Narrow the list using the controls at the top: Category, Status, a custom date range (from / to), Created By, and Changed By. Set your filters and select Filter.
Created By finds everything a user originated; Changed By finds everything a user edited — useful when you want to isolate one person's activity across a period.
Transaction vs. Document — the key idea
A document is what you work with — an Invoice or a Bill. A transaction is what the system posts to the books from it. One document can produce several transactions: the invoice itself, a receipt, a refund.
Changes are recorded at the transaction level, because that's what affects the ledger. But you usually want to ask "what happened to this invoice" — so the trail gives you two ways in:
Eye icon → what changed inside that one transaction
Source Document link → everything that happened to that invoice or bill
View what changed inside a transaction
Select the eye icon on a row to open Transaction Activity — a plain-language history of that single transaction: created, then each change, with the user and time.
Example — Receipt RC2026-00004: created, then the amount changed from JOD 1,000.000 to JOD 750.000, with the matching line-level credit and description changes listed beneath it.
View everything that happened to a document
Select the Source Document link (e.g. INV2026-00009) to open Document Activity — every transaction generated by that document, in order.
Example — Invoice INV2026-00009 · 3 transactions · 4 events:
INV2026-00009 · Invoice — created
RC2026-00004 · Receipt — created, then changed (with the full field-level before → after table)
RF2026-00005 · Refund — created
Why some rows have no eye icon
The eye icon appears only where there's activity inside a transaction. A Refund raised against an invoice is a new transaction, not a change to an existing one — so there's nothing to show inside it. It appears in the Document Activityview instead.
The audit trail PDF
Select the download icon on any row to export that transaction's full trail as a branded, timestamped PDF — a ready-to-file working paper.
Each PDF contains:
Transaction header — Serial ID, Transaction ID, dates, Source Document, Category, Amount, Reviewed status.
Activity — every creation and change in order, each with the user, the timestamp, and the field- and line-level before → new value (only the fields that actually changed).
Login session on every event (see below).
Example — Journal Entry JV2026-00008: created, then the amount changed from 580.000 to 625.000, a Utilities line added, and a Project Identifier set — each event stamped with its session.
The login session block
Every creation and change carries the session it came from:
Login (session start) · Method · Device · OS · Browser · IP address · Location
This is what turns a change into evidence. It's not enough to know what changed — the session shows the change came from a known device and location, or flags one that doesn't fit the user's normal pattern. Session detail appears on the PDF, the evidentiary export.
Reviews and control events
The trail also records control events, not just data edits:
Reviewed — a transaction marked as reviewed (shown as Yes in the list)
Review removed — a review lock lifted
Re-reviewed — reviewed again after a change
Each is logged with the user, date, time, and session — so the un-doing of a review is as visible as the review itself.
FAQ
Can anyone edit or delete the audit trail? No. Records are immutable and read-only for every user, including the Account Owner.
Can I give my external auditor access? Yes — grant the Transaction Audit Trail permission through User Permissions. Access is read-only.
Why does a journal entry show "–" under Source Document? A manual journal entry has no originating document, so there's nothing to link.
How long is the history kept? The full history is retained — no changes age out or are removed.