Document Management | Audit Evidence Packs
Per-filing evidence packs assemble themselves. Hash-verified at export.
The GST return for last quarter? The pack carries the return, the workings behind each box, the underlying invoices, the submission acknowledgement and the proof of payment. The ACRA filing? The financial statements, the supporting entries and the sign-off. One click, hash-verified at export.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Pack scope resolution | Filing or period selection | List of underlying records |
| Component assembly | Return, recon, source, ack, workpapers | Structured pack archive |
| Hash chain | Each file content + chain prior | Per-file hash + signed root |
| Independent verification | Pack archive + verification key | Chain integrity confirmation |
| Re-assembly | Repeated pack request for same period | Identical pack with same root |
-
Pack scope resolution
- Input
- Filing or period selection
- Output
- List of underlying records
-
Component assembly
- Input
- Return, recon, source, ack, workpapers
- Output
- Structured pack archive
-
Hash chain
- Input
- Each file content + chain prior
- Output
- Per-file hash + signed root
-
Independent verification
- Input
- Pack archive + verification key
- Output
- Chain integrity confirmation
-
Re-assembly
- Input
- Repeated pack request for same period
- Output
- Identical pack with same root
Compliance + integrations
Audit packs the auditor and the regulator both accept.
The pack is assembled in the form an engagement file takes, so it goes to your auditor rather than being taken apart and rebuilt by them. The hash-verified chain is what lets them rely on it without re-vouching the source.
Regulations we work within
-
SSA 230 (Audit Documentation)
Evidence assembled and retained in a form the engagement file can take directly.
-
GST Act
Return, workings and supporting invoices held together for the statutory period.
-
Companies Act 1967
Books and supporting evidence retained for the statutory period, with the chain intact.
Connects to
- Audit-pack format Accepted format across firms
- Auditor read-only access Direct platform access
Audit Evidence Packs FAQ
What buyers ask.
How is the hash chain verified independently?
The pack carries a verification key and a small command-line tool. The auditor runs the verification against the archive; the tool confirms each file hash against the chain and the chain root against the signature. Any mismatch flags. The verification is cryptographic, not based on metadata.
For a tax notice from FY 2018-19, can we still pull the pack?
Packs stay re-assemblable for as long as the underlying records are retained. Re-assembling a return from three years ago works exactly like re-assembling last quarter's, and the hash chain stays intact across the whole retention period, which is the part that matters if anyone questions whether the evidence changed.
What if the auditor wants to add their own working papers to the pack?
Auditor working papers can be uploaded against the pack with auditor sign-off. They become part of the audited pack with their own hash and audit trail. The pack signed by both the auditor and the system carries dual integrity.
More in Document Management
Related features
Statutory Documents Vault
GST returns, CPF submissions, ACRA filings and corporate tax records per period and per entity.
See Statutory Documents VaultDocument Versioning
Replace a document; the old version stays. Audit trail of every upload, edit and delete.
See Document VersioningSecure Document Sharing
Time-boxed links for auditors and lenders. Role-based access, watermarks, view-only or download.
See Secure Document Sharing
Run an audit pack on last quarter's GST return.
Connect one entity. Pick last quarter's return. The pack assembles in seconds with the return, the workings, the underlying invoices and the submission acknowledgement, hash-verified at export.