The Exports section of the compliance hub builds an archive you can hand a regulator or an auditor: one deal, one client's whole file, or every record your team holds, bundled together and stamped with a hash so anyone can prove later that nothing in it changed.
When You'd Use This
Reach for this when someone outside the brokerage - a lender, an insurer, a regulator - needs proof of what your compliance work covered, or when you just want your own copy of a file before it's archived. It lives in the Exports section, in the Compliance Export card above the retention schedule and any legal holds.
Choosing a Scope and Generating the Export
Pick one of three scopes: a single deal, a single client across every deal they've touched, or the whole book. Deal and client exports are bounded, so they build immediately and hand back a manifest on the spot. A whole-book export is unbounded work, so it queues to a background job instead - the history row below shows how many of the deals in it have finished building while it runs, rather than leaving you staring at a spinner with no sense of progress.
Reading the Manifest and Its Hash
Once an export is ready, it shows a count of what went into it - screenings, EDD cases, alerts, and whatever else the scope touched - next to a SHA-256 hash of the manifest itself. That hash is what lets you or anyone you hand the archive to confirm later that the file wasn't altered after the fact: recompute it against the manifest and it should match exactly. A copy button sits beside the hash so you're never retyping it by hand.
Downloading From History
Every export you've generated stays listed in History, with what it covers, its status, its hash and when it ran. Status is one of three things: still building, archived with a downloadable ZIP, or manifest-only when there was nothing to bundle into a file. A download button appears only once there's an actual archive to fetch - a row with no ZIP shows no disabled button, because there's nothing behind it to wait for. Downloading opens a short-lived signed link rather than a permanent URL, so an old link sitting in someone's inbox can't be used to pull the archive indefinitely.
Common Gotchas
- A whole-book export can take a while. Watch the completed-count on its history row instead of assuming a build that hasn't finished has stalled.
- Manifest-only isn't a failure - it means the scope you picked had nothing to package into a ZIP, not that something went wrong.
- The hash covers the manifest, not the underlying files individually - use it to confirm the summary wasn't tampered with, not to verify any one document inside the archive.
What to Do Next
- Download the Compliance File for a Deal for a single deal's record without building a full export.
- Produce Your Program Package for a Regulator for the brokerage-wide package an admin sends or downloads directly.