Audit Pack
An Audit Pack answers the auditor's question in one file: can this close be reproduced, and has anything changed since? DayZero builds it from records it already keeps, seals it with a cryptographic hash and a server signature, and lets you share it with a read-only link.
Key capabilities
- Replay the close on a throwaway copy of your books and compare the copy with what was posted, to the cent, by account code
- Verify the audit trail for the period: every change record still links to the one before it and none is missing
- Collect every approval a person gave to an agent's write during the period, with who decided and when
- Count the calculation traces behind the numbers the agent produced for the period
- Attach the evidence binder, the close workpaper with its trial balance tie-out and verification checks
- Seal it with a hash over the whole manifest and a signature only DayZero's servers can produce
- Share it with one public link your auditor, lender or board can open without an account; revoke it at any time
How it works
Requesting a pack starts a background job. It copies the books, replays the period's close on the copy, grades the copy against the real books, and deletes the copy. It then checks the audit trail for the period, gathers the approvals and traces, writes the binder, and seals the manifest. The pack appears on the period as Ready, usually within a few minutes.
flowchart LR
request["Request on a closed period"] --> copy["Copy the books"]
copy --> replay["Replay and compare"]
replay --> trail["Verify the audit trail"]
trail --> collect["Approvals and traces"]
collect --> binder["Evidence binder"]
binder --> seal["Hash and sign"]
seal --> share["Drawer and public link"]If a model version used in the original close is no longer available, the pack does not pretend to replay it. The replay step falls back to verifying the calculation traces that were stored at the time, and the pack says so in plain words in its replay section. The same fallback applies when no copy of the books can be made.
How to use it
- Open Accounting Periods and find a closed or locked period.
- Click Audit pack, then Generate audit pack. The drawer follows the job.
- When the status reads Ready, read the replay result, the audit-trail verdict, the approvals list and the hash.
- Click Download binder for the workpaper, or Share to create the public link. Copy it right away; it is shown once.
- Ask Regent "is the audit pack for September ready?" to get the same summary in chat, or "build the audit pack for September" to request one (Regent asks you to approve first).
Pro tips
- Build the pack right after you close. The audit-trail check covers the period through the day it was closed, so a late reopen shows up as a new pack with a new hash.
- The hash is recomputed by the server every time the pack is opened. If the badge ever reads Not verified, the stored pack no longer matches its seal; request a new one and tell support.
- Share the public link instead of emailing the binder. The link carries the hash and signature with it, and you can revoke it later.
- A pack that says it verified stored traces instead of replaying the close is still valid evidence; it tells the reader exactly what could and could not be reproduced.
- One pack builds at a time per period. If a request is refused as already running, wait for the current one.
In-depth guide
What the public link shows
The business name, the period, the replay result, the audit-trail verdict, the approvals (tool, decision, who, when), the trace count, the hash, the signature, a server-recomputed Verified badge and the binder download. No ledger rows, amounts or customer names appear on the page.
Replay result
Entries replayed is the number of journal entries the copy produced for the first month of the period. Differences counts every account, step or entry whose figure or state differed between the copy and the real books; the first ten are listed. Zero differences means the close reproduced exactly.
Audit trail
The audit trail is a chain of change records where each record carries the fingerprint of the previous one. Verified means every record in the period re-hashed to its stored fingerprint, every link held and no sequence number was missing. When the verification service is unavailable the pack says Not verified and explains why, rather than guessing.