Building an exchange venue schedule your auditor will accept
A venue schedule is not a screenshot dump. Structure balances, cutoffs, and missing statements so the pack stands alone.
Auditors ask for evidence that can be re-performed. A folder of exchange screenshots fails that test because timestamps, account names, and asset tickers rarely align.
Minimum fields we require
For each venue: legal account name, entity that owns it, assets in scope, balance as of a single KST cutoff, and the export file hash or statement ID. Dormant accounts stay on the list with a zero and a note — omitting them is how insurance schedules go wrong.
Where OTC tickets fit
Unsettled OTC trades belong beside exchange balances when the same treasury owns both. An exchange exposure check maps tickets to counterparties so Crypto Portfolio Desktop monitoring does not treat them as “mystery variance.”
Cadence after the first schedule
Once the schedule exists, weekly monitoring becomes cheaper. You are no longer discovering venues; you are watching movement against a known set.