The Audit Trail is a set of read-only reports for accountants, auditors and compliance officers. Nothing is entered here — every report reads straight from the postings made across the modules, so an auditor sees the same figures the business runs on.
Read-only reports — nothing can be altered here
Financial, customer, supplier and user trails
Preview, Print, Email or Export PDF from the viewer
If the trail lives in spreadsheets, exports and someone’s memory, fieldwork turns into a search for evidence that should already be sitting in the ledger.
The trail is stitched together by hand
Postings, corrections and approvals are pulled from different places and reconciled by hand, so nobody is quite sure the picture is complete.
No clear record of who did what
When a balance moves or a master record changes, there is no by-user log to show who made the change, when, or whether it was authorised.
Approvals cannot be evidenced
An approval happened in an inbox or a conversation, so the authorisation chain behind a payment or a posting cannot be reconstructed for the reviewer.
The statutory payment return is a chore
The UK payment-practices return is pieced together by hand from invoice and payment dates each half-year, when the figures it needs are already sitting in the ledger.
Overview
One database, one trail.
Every report reads from the postings the business already made.
A chronological listing of every posting in a period
Chronological listing grouped by source module. Built for period-end review and audit fieldwork.
Read-onlynothing can be altered
By sourcepostings grouped where they came from
Every movement for a customer or supplier in the period
Invoices, credit notes, receipts, allocations and journal corrections. Closing balance reconciles from the opening balance.
Read-onlynothing can be altered
Opening → closingthe balance reconciles in full
A by-user log of significant actions
Log-ins, posting events, authorisation actions and master-record changes. Grouped by user for internal control reviews.
Read-onlynothing can be altered
By useractions attributed to a person
Every authorisation event behind a document
Approvals, rejections, escalations and out-of-office re-routes. Read straight from the Document Authorisation chain.
Read-onlynothing can be altered
Every eventfrom the authorisation chain
In their words
Order processing, stock and accounts sit on one system, so the whole team works from the same picture.
MatconManufacturing & engineering
Explore more
Works with the rest of DataFlow.
The Audit Trail reads from the modules that do the posting.
Can anything be entered or changed on these reports?
No. The Audit Trail is a set of read-only reports. Nothing is entered here — every report reads from the postings made across the modules, so what an auditor sees is the same data the business runs on.
How do the customer and supplier trails reconcile a balance?
They list every movement for the account in the period — invoices, credit notes, receipts, allocations and journal corrections — so the closing balance reconciles from the opening balance without a separate calculation.
Can I evidence who authorised a payment or posting?
Yes. The transaction authorisation history shows every authorisation event from the Document Authorisation chain — approvals, rejections, escalations and out-of-office re-routes — so the chain behind a document can be reconstructed.
How do I get a report out for the audit file?
Every report runs through the report viewer with four outputs: Preview, Print, Email and Export PDF. There is also a Payment Practices Report for the UK statutory payment-times return.
See it on your data
Give your auditor the trail, not a scavenger hunt.
