When the ATO issues a review notice, or when a client asks "who changed that transaction last month?", your audit trail is the difference between a confident, documented answer and a stressful reconstruction exercise. ReconLink was designed from the ground up with audit-readiness as a first-class feature — not a checkbox added after the fact. Here is what the audit log captures, how to access it, and why it matters for multi-user practices.
What the Audit Log Captures
Every action that modifies data in ReconLink is recorded to an immutable audit log. The log captures:
Transaction-level events:
- Initial import of a transaction (from a CSV, Excel, or PDF statement, or the per-client email inbox)
- Manual creation of a transaction
- Any edit to a transaction's amount, date, description, or reference
- Deletion or reversal of a transaction
Coding events:
- Assignment of an account code (e.g., 6-3000 Office Expenses) to a transaction
- Assignment of a GST code (GST, FRE, INP, N-T, CAP)
- Acceptance of an auto-suggested code from ReconLink's rules engine or AI layer
- Override of a suggested code with a manual selection
- Rule creation triggered by a confirmed coding pattern
User identity and timing:
- The exact user (name and email) who performed each action
- The timestamp to the second (stored in UTC, displayed in your practice's local timezone)
- The IP address of the session — useful for identifying actions taken outside normal office hours
Reconciliation events:
- Opening and closing of a reconciliation period
- Matching of transactions to bank statement items
- Approval of a reconciliation by a reviewer
This means that if a coding was changed three weeks ago, you can see exactly who changed it, what it was before, what it became, and when. That information does not change — it cannot be edited or deleted by any user, including practice administrators.
How to Export the Audit Log for an ATO Review
When the ATO requests records supporting your client's BAS or income tax return, the audit log is a primary piece of supporting evidence. It demonstrates that your reconciliation process is documented, supervised, and not subject to retroactive manipulation.
To export the audit log in ReconLink:
- Navigate to Settings > Audit Log within the client's workspace
- Set the date range to match the period under ATO review
- Apply filters as needed — filter by transaction ID, user, event type, or date range
- Export as CSV or PDF
The CSV export includes all columns in a structured format suitable for importing into Excel for further analysis. The PDF export produces a formatted report suitable for attaching to an ATO response or keeping in the client file.
For BAS reviews, filter by the BAS period dates and export the full coding history for that period. This gives the ATO reviewer a complete picture of how every transaction was classified, and by whom, without requiring you to reconstruct anything manually.
Why Immutability Matters for Multi-User Practices
In a single-bookkeeper practice, the audit trail is primarily about error recovery and compliance. In a multi-user practice — where multiple staff members, junior bookkeepers, and possibly the client themselves all have access to the workspace — it becomes an essential governance tool.
Common scenarios where the audit trail provides concrete value:
Reviewing junior work: A practice manager can review the coding decisions made by a junior bookkeeper over the past week, see where the AI suggestion was accepted without review, and identify training opportunities — all without asking the junior to reconstruct their memory of each decision.
Client access governance: If a client has read access to their workspace (a common arrangement), and a transaction is subsequently disputed, the audit log shows definitively whether the client's access was exercised and whether any coding changes were made by the client or by practice staff.
Staff transitions: When a bookkeeper leaves the practice and their client portfolio is transferred, the incoming bookkeeper can review the full history of how accounts were coded without relying on handover notes. The audit trail is a complete, reliable record of past decisions.
Error investigation: When a BAS has been lodged and a discrepancy surfaces, the audit log allows the practice to identify whether the error was a coding mistake (which transaction, when, by whom), a reconciliation error, or a statement import issue — and address it specifically rather than re-reviewing everything.
Compliance Benefits and Client-Facing Value
Beyond the internal governance benefits, the audit trail has direct client-facing value. Australian bookkeepers registered with the Tax Practitioners Board are required to keep adequate records of their work. The ATO expects that if a BAS position is questioned, the preparer can explain how it was derived.
ReconLink's audit trail provides a ready-made record that satisfies this obligation. More than that, it is a demonstrable quality marker you can use in client conversations: every coding decision in your client's books is tracked, timestamped, and attributable. That level of accountability is not available in a spreadsheet workflow and is not standard in all bookkeeping software.
When onboarding a new client — particularly one who has had issues with previous bookkeepers or has been through an ATO audit — walking them through ReconLink's audit log is a powerful way to build trust early. Show them the live log in a demo session. Explain that every change is tracked and nothing can be altered silently. For a client who has experienced unexplained discrepancies in previous accounts, that demonstration is often the close.
Audit trails are not glamorous. But when an ATO review letter arrives or an unexplained balance surfaces, the practice that can answer every question with a timestamped, user-attributed record is the one that resolves it fastest — and with the least stress.