October 12, 2026

Compliance evidence by design: what belongs in an operational record?

Compliance controls have little value if a business cannot explain what information was reviewed, which rule was applied, who made the decision and what happened afterward. Evidence should be considered during workflow design, not only during a later audit.

Preserve the context

When evaluating risk and sanctions screening, link a record to the party roles, relevant identifying details, screening sources, time of assessment and reviewer disposition. Separate raw machine matches from verified human decisions.

Separate different regulatory purposes

Sanctions workflows, suspicious transaction assessments, threshold-based report obligations and payment service provider risk management can involve different legal tests and deadlines. A product should not flatten them into a generic “compliant” indicator.

Support retention and reconstruction

Changes and decisions should be traceable. Appropriate records and retention requirements depend on the actual entity, activities, applicable law and documented policy. For sensitive records, independent evidence preservation and tested recovery are important design considerations.

This article is general operational information. No software, report candidate or automated rule replaces the obligations of a regulated business or its advisers.