Auditor Evidence Pack
One ZIP for a date range with every ledger line and posting, who drafted, approved and posted each one, the month closes and reopens, certified statements, the integrity checks and the accounting audit trail, each file fingerprinted so the copy your auditor received can be proved unchanged.
Year-end audit requests usually arrive as a list: the ledger, the journals with their approvals, proof that closed months stayed closed, the statements as signed off. The auditor evidence pack answers that list from the books in one download.
Building One
- Open Certified statements at
/accounting/certified-statements. - Under Auditor evidence pack, choose From and To — usually the financial year under audit.
- Press Build and download. The ZIP is built there and then and downloads straight away.
What Is In It
| File | What it holds |
|---|---|
ledger_lines.csv | Every ledger line in the range, with its posting, account, side, amount, reference, department, branch, project, cost center, sales channel and currency. |
postings.csv | Every posting: who drafted it, who approved it and who posted it, and when. |
period_closes.csv and reopen_requests.csv | Month closes, reopens, and the requests behind each reopen with who asked and who approved. |
close_evidence/ | The evidence pack stored at each close: the books as they stood, never changed afterwards. |
certified/ | Every certified statement version overlapping the range. |
integrity.json | The ledger integrity checks as they stand on the day you build the pack. |
accounting_audit_log.csv | The accounting audit trail for the range. |
manifest.json | The SHA-256 checksum of every file above. |
Proving The Copy Is Unchanged
Each pack is kept privately in your workspace once it is built, and the SHA-256 of the whole ZIP is written to the audit log. If a question comes up later about what the auditor was given, compare the checksum of their copy with the one in the log; inside the ZIP, the manifest does the same for each file.
Permissions
- Export audit evidence — build and download the pack. It is a separate permission from viewing accounting, so the person who can see the books need not be the person who can hand them out.
The pack is built on the web. It is different from the Security evidence packs, which bundle audit logs, approvals, access history and document activity across the whole workspace.
Common Mistakes
- Building the pack before the year is closed and certified. It then has no close evidence or certified statements for the last months. Close and certify first.
- Sending a second build and expecting the same checksum. Each build is a new file with its own checksum, and the integrity checks reflect the day it was built. Keep the one you sent.
Related
- Certified Statements & Board Pack — the frozen statements the pack includes.
- Month-End Close — closes, reopen approval and the close evidence pack.
- Audit Logs — the tamper-evident trail behind it.
- Audit trail integrity — the feature page.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.