The short answer: Tag and select the notes you need, start a new proof pack, review the disclosure, set expiry, and export. The pack never includes your UFVK.
What a pack contains
Classified rows you chose, fingerprints needed for integrity, and metadata for the reviewer. It does not contain a viewing key, seed, or spend path.
Build it in order
Clean the ledger first
Classify income, change, expense, and fees. Fix tags and memos so the pack reads like books, not raw chain noise.
Start New Proof Pack
Select the date range and rows that match the request. Prefer the minimum set that answers the question.
Read the disclosure
ZecBooks shows what leaves the vault. Confirm you are comfortable sharing those rows with the recipient.
Set expiry and export
Choose an expiry that matches the engagement. Export the encrypted pack to a path you control.
Good scope example
Accountant asks for Q2 client income. You include Q2 income rows plus related fees — not the entire multi-year vault, and not untagged noise you have not reviewed.
Common mistakes
- Exporting everything “to be safe.”
- Skipping tags so the reviewer cannot tell income from change.
- Confusing CSV/PDF side exports with the encrypted pack format.
Ready for Mac?
Download ZecBooks and keep spend keys out of the books workflow.