Your fraud team catches a customer depositing altered checks. Meanwhile, your AML team flags the same customer for structuring deposits below reporting thresholds. Both teams spend three days duplicating investigative work before comparing notes.
This checklist helps you decide whether to integrate your fraud and AML operations, coordinate them more tightly, or keep them separate. It's designed for financial institutions and fintechs evaluating how to structure financial crime prevention when both teams use similar detection tools but serve different regulatory objectives.
Prerequisites
Before using this checklist, ensure you have:
- Clear documentation of your current fraud and AML reporting lines.
- Access to both teams' technology stacks and data sources.
- Authority to review cross-departmental workflows.
- Understanding of your institution's BSA/AML obligations and fraud loss metrics.
Integration Readiness Checklist
1. Map Your Detection Tool Overlap
Action: Document which systems both teams use for monitoring software, transactional data analysis, watchlist screening, and peer group definitions.
Done when: You have a single-page matrix showing shared tools, team-specific tools, and gaps where one team lacks visibility the other has.
Good looks like: Your fraud team's transaction monitoring platform and your AML team's suspicious activity detection system query the same core datasets, but you've identified that fraud sees real-time authorization data while AML only sees settled transactions 24 hours later.
2. Define Each Team's Primary Objective in Writing
Action: Have each department head write a one-paragraph mission statement. Fraud departments typically focus on preventing financial loss to the institution. AML departments focus on regulatory compliance and protecting the broader financial system from illicit funds.
Done when: Both statements are approved by executive leadership and explicitly acknowledge the difference between protecting organizational profit and fulfilling regulatory obligations.
Good looks like: Your fraud mission reads "minimize unauthorized transaction losses and protect customer accounts," while your AML mission reads "ensure compliance with Bank Secrecy Act requirements and file accurate Suspicious Activity Reports to protect financial system integrity."
3. Assess Cultural and Commercial Alignment
Action: Review how each department measures success. Fraud teams often report cost savings in prevented losses. AML teams report SAR filing accuracy, examination findings, and regulatory feedback.
Done when: You've documented whether leadership evaluates both teams using compatible metrics or fundamentally different performance frameworks.
Good looks like: You recognize that fraud operates as a cost-effective loss prevention function with clear ROI, while AML operates as a compliance function where "success" means zero regulatory violations, not recovered funds. If you're considering integration, you've identified how to preserve both measurement frameworks.
4. Test Information Sharing on a Predicate Offense
Action: Select a recent fraud case involving deception or misrepresentation. Document how information flowed between teams. Did the fraud team notify AML when they identified the deception? Did AML receive the investigative file in time to assess layering or integration activity?
Done when: You've mapped the actual timeline and identified delays, handoff failures, or duplicated investigative work.
Good looks like: Your fraud team identified altered checks on Day 1, but AML didn't learn about it until Day 4 when the customer had already moved funds through three additional accounts. You now have a concrete case showing the cost of siloed operations.
5. Review Regulatory Examination Findings for Both Functions
Action: Pull your last three years of BSA/AML examination reports and any fraud-related regulatory feedback. Look for examiner comments about coordination gaps, information sharing, or integrated financial crime risk management.
Done when: You've identified whether regulators have explicitly encouraged integration or raised concerns about your current structure.
Good looks like: The FFIEC BSA/AML Examination Manual specifically discusses coordination between fraud and AML. You've documented whether your examiners noted this expectation and whether your current structure addresses it.
6. Inventory Customer and Account Information Access
Action: List what customer data each team can access. Include account opening documents, beneficial ownership information, transaction histories, and external data sources.
Done when: You've identified information asymmetries where one team has context the other needs.
Good looks like: Your fraud team has real-time access to device fingerprinting and IP geolocation data that could help AML assess structuring patterns, but AML has beneficial ownership documentation that could help fraud understand why a business account shows unusual payment flows.
7. Establish a Coordination Model (If Not Integrating)
Action: If full integration isn't viable, design a formal coordination protocol. Specify triggers that require fraud to notify AML (and vice versa), response timeframes, and shared case documentation standards.
Done when: You've written a procedure that both teams have signed off on, including escalation paths when coordination fails.
Good looks like: Your protocol states: "Fraud team will notify AML within 24 hours of identifying any deception-based scheme exceeding $10,000 or involving multiple accounts. AML will provide fraud with watchlist screening results for any customer subject to fraud investigation within 48 hours of request."
8. Validate Technology Integration Feasibility
Action: If considering operational integration, have your technology team assess whether your monitoring software can support unified case management while maintaining separate reporting outputs (fraud loss reports vs. SARs).
Done when: You have a technical architecture proposal showing how integrated teams would share investigative workflows without compromising regulatory reporting accuracy.
Good looks like: Your vendor confirms that a single case management platform can route investigations to appropriate teams based on typology, maintain separate audit trails for BSA/AML and fraud purposes, and generate both SAR narratives and fraud loss reports from the same underlying case data.
Common Mistakes
Assuming integration always reduces costs. If your fraud team's commercial culture conflicts with AML's regulatory focus, you may spend more managing internal friction than you save on headcount.
Merging teams without preserving AML's regulatory independence. If AML decisions become influenced by fraud's profit protection mandate, you've created compliance risk. AML's purpose is to secure the financial system, not optimize your institution's bottom line.
Expecting immediate ROI from coordination. The benefit of AML and fraud coordination is comprehensive threat visibility and rationalized compliance response, not necessarily faster fraud detection or lower SAR filing volumes.
Forgetting that fraud is the predicate offense. Money laundering requires an underlying crime. If your fraud team identifies deception but doesn't share that intelligence with AML, you're missing the layering and integration activity that follows.
Next Steps
If this checklist revealed significant tool overlap and information gaps, start with a 90-day coordination pilot before considering full integration. Select five recent fraud cases involving deception and retrospectively assess whether AML visibility would have identified subsequent money laundering activity.
If your regulatory examiners have noted coordination weaknesses, prioritize item 7 (the coordination protocol) and implement it within 60 days.
If cultural and objective differences (item 3) are substantial, coordination is safer than integration. Preserve each team's distinct mission while building formal information-sharing bridges.
Your fraud and AML functions don't have to merge to be effective. But if they're investigating the same customers without talking to each other, you're doubling investigative costs and missing the connection between the predicate offense and the laundering that follows.
