The tables behind Anti-Money Laundering

Use stable source identifiers to resolve references. Assessments.record number identifies the working assessment, while Revision identifies the version being reviewed. Assessment tests.line number and Revision distinguish sample work; do not infer an independent table identity from a line number alone. Review decisions.source revision identifies the assessment revision that received the decision.

Team members.User references Users. Users.User is a self-reference and needs identity mapping during migration. The Users.Role values are View Only, Manager and Admin; configure business responsibilities through the agreed permission model and team members.role name. A label in that text field is not an access grant.

Monitoring alerts.subject reference holds the provider’s subject reference as text. Review decisions.Parent identifies the assessment reviewed. Correlate an alert disposition through the guarded action’s operation and effect references during setup. Agree the permitted scope for restricted subjects explicitly before migration.

1. Resolve Users identities and their self-references, then load Organizations and team members.
2. Load business units, Risks and Controls using stable references and declared risk scales.
3. Load Assessments with ownership, periods and revisions, then assessment tests and record attachments.
4. Load review decisions, monitoring alerts and operation receipts with reconciled revision and action references.
5. Load Findings, corrective actions and Retests in dependency order; preserve actual completion and test evidence.
6. Load restricted subjects, access grants and disclosure events under the agreed access policy, then reconcile links and rehearse denied access.