AML workflow resources
Choose the right resource for the operating problem.
Use practical UK, EU and cross-border guides to frame an onboarding, KYC/KYB, ownership, risk-review, remediation or periodic-review problem, then continue into the relevant product evidence and workflow review.
Implementation boundary: These guides and calculators support research and operating-model planning. They are not legal advice, regulatory conclusions or proof that a product configuration satisfies a firm’s obligations. Confirm current requirements, provider coverage, evidence standards, approval authority and implementation scope for each jurisdiction.
How the workflow fits together
Onboarding
Map KYC and KYB as one customer-acceptance journey
Start with the customer, entity or policyholder path rather than a list of isolated checks. Connect information, evidence, provider-returned results, exceptions and accountable approval.
- Individual, company, trust and related-party paths
- Customer-facing evidence requests and internal review
- A representative clean file and exception file for evaluation
Ownership
Keep complex entities and beneficial ownership operable
Use a relationship-led model for entities, trusts, people, ownership or control links, declarations and supporting evidence. Legal interpretation and evidence sufficiency remain with the firm.
- Relationship context rather than one flat UBO field
- Evidence attached to the relevant person, entity or relationship
- Clear routes for missing or inconsistent information
Review
Design exception, risk and approval routes before selecting software
Test what happens when evidence is missing, a provider returns a possible match, configured risk increases or a reviewer needs more information. Keep final judgement and approval with authorised people.
- Named ownership for every exception state
- Decision context retained with the workflow record
- Provider and human responsibilities made explicit
Refresh
Plan periodic review and remediation as portfolio operations
Define which population enters a review, what changed information matters, how customers are contacted, how evidence and exceptions return, and who approves the refreshed decision.
- Firm-defined timing, populations and trigger inputs
- Controlled customer follow-up and internal queues
- A new decision linked to prior relationship context
Evaluate
Prepare a requirements-led software review
Bring one representative file and ask the supplier to show the customer experience, evidence state, returned checks, exception path, human decision, retained history and later change.
- Separate workflow orchestration from external checks
- Confirm implementation, security and commercial assumptions
- Record gaps and ownership instead of accepting broad feature labels
Jurisdictions
Keep regional requirements and the shared operating model separate
Use jurisdiction hubs to frame terminology, source material and implementation questions. Do not infer that one workflow, provider arrangement or evidence list applies unchanged across markets.
- UK and EU requirements remain visibly distinct
- International finance centres require local validation
- Australian Tranche 2 tools remain available as a separate library
Explore UK and EU AML workflows