Evidence packs that show
what you did, when, and why
duely turns engagement activity into an audit-ready PDF, generated on demand after approval. Each pack carries version history, an integrity hash, the decision rationale, approvals and supporting context, so the record is ready when you need it instead of rebuilt after the fact.
The evidence tab: each pack version with its date and SHA-256 hash. Sample data. See the full walkthrough
Why this matters
The costliest part of compliance is often reconstructing the file later. Evidence packs reduce that scramble by making the workflow itself the record.
Each pack is generated on demand from the approved engagement record and includes the key decision trail. Packs are versioned, so you can track how the compliance file changed over time. There are two output profiles, a standard pack and one restricted to the AML/CTF compliance officer (AMLCO), so each export suits who will read it.
What's included
PDF evidence pack export
Generate a human-readable PDF that captures verification results, risk assessments, and approvals.
Version history
Track how the evidence pack changed over time. Each version records the state of the compliance file at that point.
SHA-256 integrity hashing
Every evidence pack is hashed so tampering can be detected. You can show the evidence has not changed since the pack was generated.
Approval and rationale capture
Record approver identity, timestamp, and decision rationale alongside the evidence pack.
Standard pack: for everyday use and external review
Default output for everyday compliance use. Includes the designated service, identity verifications (with redacted document content), beneficial ownership, risk assessment, ECDD where triggered, and approval records. Raw data from providers is redacted, and suspicious matter report (SMR) data never appears.
Sensitive pack: AMLCO-only
An AMLCO-only pack, generated on demand, that adds the raw data from identity, sanctions and PEP providers and the detailed screening hits. Use it for internal investigation, discussions with the regulator, or external audit by an authorised reviewer. SMR data still never appears.
Beneficial ownership and structure, where relevant
Beneficial ownership and entity structure are included in the pack where they apply.
Evidence for compliance reviews
- Record-keeping: 7-year retention from anchor date
- Evidence should include: designated service, CDD steps, risk ratings, approvals
- Default exports exclude sensitive provider data and SMR information
- Version history tracks how the evidence evolved
Related features
Other parts of the compliance workflow this connects to.
Audit Trail
Key events from the audit log are excerpted into each evidence pack.
See details →Customer and Engagement Workflow
Evidence packs are generated for each engagement, so each one has its own evidence trail.
See details →SMR Firewall
No evidence pack includes SMR data, including the AMLCO-only sensitive pack.
See details →Make the file easier to defend later
Versioned evidence packs with integrity hashing and approval capture.