Context: Questions from the Front Lines
When FinCEN published its Financial Trend Analysis on suspected human smuggling in August 2026, it left MSB compliance departments with many questions. The report analyzed 67,540 BSA reports and identified nearly $5 billion in suspicious activity, with MSBs filing approximately 97% of those reports. This highlights the significant reporting responsibility on MSBs.
Since then, compliance officers at check cashers, remittance providers, and currency exchanges have been asking similar questions. These are practical issues where regulatory guidance meets operational reality. Here's what you and your team need to know.
Q1: "We send thousands of transfers to Mexico and Central America daily. Are we supposed to flag all of them?"
No, geography alone isn't suspicious.
FinCEN's analysis identified Mexico, Guatemala, Honduras, and Colombia as common destinations, reflecting migration patterns, not a directive to treat these countries as high-risk. Your customers have legitimate reasons to send money to family, pay vendors, or support dependents there.
Focus on the transaction pattern. In 59% of MSB reports analyzed, the absence of a verifiable familial relationship was a key indicator. This doesn't mean flag every transfer to Guatemala. It means if a customer claims to send money to a cousin but can't explain the relationship when asked, that's worth noting.
Look for transfers along migration routes, combined with other factors: evasive customers, frequently changing beneficiaries, or amounts structured to avoid reporting thresholds.
Q2: "What counts as 'unverifiable relationship' in practice?"
A relationship is unverifiable when the customer's explanation doesn't hold up under basic questioning.
For example, a customer says they're sending $900 to their brother in Honduras. You ask the brother's name, and they hesitate or provide a name that doesn't match previous transactions. You ask how often they send money, and they say "monthly," but records show this is the first transfer in two years. They claim it's for "family support" but can't provide specifics.
This differs from a customer who regularly sends money to the same beneficiary, can explain the relationship clearly, and whose transaction history supports their stated purpose.
Document these conversations. If the customer's explanation is vague, inconsistent, or changes when probed, note that in your case file. This context is crucial when deciding whether to escalate to your MLRO.
Q3: "We're seeing a lot of cash deposits just under $10,000. How do we distinguish structuring from coincidence?"
Structuring has a pattern; coincidence doesn't.
FinCEN's analysis noted excessive cash activity near the U.S. southwest border and suspected structuring in MSB reports. Structuring means breaking up transactions to evade Currency Transaction Report requirements. You're looking for deliberate behavior, not random variation.
Red flags include: the same customer making multiple deposits of $9,000 or $9,500 across several days, customers who previously deposited $12,000 suddenly switching to $9,800 deposits, or multiple individuals depositing similar amounts to the same beneficiary account within a short timeframe.
Your transaction monitoring rules should flag micro-structuring patterns: multiple transactions by the same customer or to the same beneficiary that collectively exceed $10,000 within a rolling 24-hour or 7-day window. Don't just set a threshold and forget it. Review the alerts for patterns that suggest coordination.
Q4: "What's a funnel account, and how do we spot one?"
A funnel account receives funds from multiple unrelated individuals and then consolidates or forwards those funds elsewhere.
FinCEN's analysis identified funnel accounts as a typology in depository institution reports. For MSBs, you'll see this when one beneficiary receives transfers from numerous senders who claim to be unrelated family members or friends. The account holder might then withdraw the funds in cash, transfer them to another account, or use them for purchases that don't align with the stated purpose of the incoming transfers.
Practical indicators: an account receives 15 transfers in a week from different senders in different states, all claiming the recipient is a family member. The amounts are similar (often just under reporting thresholds). The recipient withdraws the funds immediately after each deposit. When you ask the recipient about the senders, they can't explain the relationships or provide inconsistent information.
Your monitoring system should flag accounts with unusually high inbound transfer volumes from multiple unique senders, especially when combined with rapid outbound activity.
Q5: "How do we handle travel agencies that book trips for customers?"
Legitimate travel agencies aren't inherently suspicious, but FinCEN noted that travel businesses arranging transportation for migrants can range from sham operations to legitimate companies that may unknowingly facilitate human smuggling.
If you provide services to travel agencies, watch for: agencies that primarily book one-way tickets along migration routes, customers who book travel for multiple unrelated individuals using similar payment patterns, or agencies that operate from residential addresses with minimal online presence.
The key word in FinCEN's guidance is "unknowingly." A legitimate agency might not realize they're being used by smuggling networks. If you see unusual booking patterns, document them and consider whether the activity warrants a conversation with the business owner before escalating to a Suspicious Activity Report.
Q6: "Our SAR volume tripled after we tightened our rules. Are we over-reporting?"
Maybe, but the alternative is worse.
FinCEN's analysis found that suspected human smuggling-related BSA reports fell by 62% in 2025 after peaking in 2024. That decline could reflect changes in smuggling patterns, shifts in migration flows, or institutions tightening their monitoring rules and then recalibrating after an initial surge in alerts.
When you adjust your transaction Transaction Monitoring Rules, you'll generate more alerts initially. That's expected. The question is whether you're investigating those alerts thoroughly before filing SARs. If you're filing based solely on automated flags without investigating the context, you're over-reporting. If you're investigating each alert, documenting your findings, and filing SARs when the totality of circumstances supports suspicion, you're doing your job.
Review your SAR narratives. Are they specific? Do they explain the pattern of activity, not just the individual transactions? Do they provide context about the customer's stated purpose and why it doesn't align with the observed behavior? If your narratives are generic, you're probably over-reporting.
Where to Go for More
Start with FinCEN's Financial Trend Analysis published August 13, 2026. It's not light reading, but it contains specific typologies and case examples that can inform your Transaction Monitoring Rules.
Review your institution's Customer Due Diligence procedures. Make sure your staff knows how to ask follow-up questions when a customer's explanation seems vague or inconsistent. Train them to document those conversations in your case management system.
Finally, test your transaction monitoring rules against the patterns FinCEN identified: unverifiable relationships, migration-route activity, structured cash deposits, and funnel accounts. If your rules can't detect these patterns, you're flying blind.
