/ PRODUCT — AML ANALYSIS

Read the whole book of business, not one receipt at a time.

AML Analysis aggregates every transaction the way the regulations do — same-day, per customer, across every agent and license — then links senders to beneficiaries, clusters the names people use to hide, and puts an AI analyst on the patterns. Structuring, layering, and high-risk clusters surface before a report is ever late.

Schedule a demoWhat it detects

THE DESK OPENS TO FOUR NUMBERS

1,240
UNIQUE CUSTOMERS
distinct senders in scope
38
AGGREGATION EVENTS
same-day totals ≥ $3,000
27
CUSTOMERS AGGREGATING
of 1,240 customers
$412,900
TOTAL $ AGGREGATED
across aggregation days

/ THE PIPELINE

Every source — agents, brands, and Principals — flows into one stream, deduped, scored, and linked into a single ledger you monitor and file from.

/ AML-ANALYSIS

Every license, one ledger.

Transaction analysis across every agent, state license, and reporting agency — normalized into a single stream you can monitor and file from.

AGGREGATION.PIPE — 6 SOURCES → 1 LEDGERSTREAMING
Miami — Flagler StBR-01
Houston — BellaireBR-02
Western UnionMT-0142
UnitellerMT-0871
OmnexMT-0335
VigoMT-2210
MoneyGramMT-0064
XoomMT-0918
MSBCONTROL
ANALYSIS
CLUSTER
1.5K/S
DEDUPE · SCORE · LINK
UNIFIED LEDGER
18,420
TXNS INGESTED TODAY
KYC ALERTS184 det · 171 doc
CTR ALERTS47 det · 47 filed
FUZZY NAMES23 found
COUNTRIES60 detected
AMT DEVIATION+8.4% / region

/ WHAT IT DETECTS

Six ways money hides. All of them, surfaced.

These aren’t alerts you write rules for — they’re computed across the whole book every time you open it.

01 / AGGREGATION

Same-day totals, not lifetime totals

We aggregate every transaction by sender within a single calendar day — the way FinCEN thresholds actually work. A customer who never trips a limit on one receipt, but whose same-day activity crosses $3,000, is flagged KYC-required; cross $10,000 and it flags CTR-required — before the report is missed.

EX.Three receipts — $2,900 + $2,800 + $2,900 — on the same day = $8,600. No single ticket looks large; the same-day aggregate raises a CTR-required flag.
KYC $3,000 · CTR $10,000 (same-day)
02 / IDENTITY MATCHING

The same person under three spellings

Structuring often hides behind near-duplicate names so no single spelling aggregates past a threshold. Our fuzzy matcher clusters near-duplicate sender and beneficiary names — case, accents, punctuation, and word order normalized — and scores each cluster’s similarity. Tune sensitivity Strict / Standard / Loose.

EX.“Juan Pérez”, “Juan Peres”, and “Jaun Perez” cluster at an 88% match — a combined $14,050 that no single spelling would have aggregated.
Fuzzy clustering · identity obfuscation
03 / RELATIONSHIPS

Who’s connected — directly and indirectly

A sender↔beneficiary graph with connected-component analysis: you see not just direct counterparties but everyone reachable through the network. Fan-in (many senders → one beneficiary), fan-out, layering, shared beneficiaries, and circular flows surface as structure, not spreadsheet rows.

EX.One beneficiary in Recife receiving from 12 senders across two licenses — a shared-beneficiary cluster you’d never catch receipt by receipt.
Direct vs indirect counterparties
04 / RISK

Where the dollars concentrate

Every transaction is placed in an amount band, by location, so threshold exposure and volume concentration are visible at a glance — from small-dollar noise to the transactions that carry reporting weight.

EX.A location where 60% of volume sits in the $3K–9,999 band — just under CTR, exactly where structuring lives.
$1–999 · $1K–2,999 · $3K–9,999 · $10K+
05 / GEOGRAPHY

Corridors measured against your own baseline

Transactions map by destination country — Mexico, Guatemala, Honduras, and the corridors your business actually runs. A customer’s average to a country is benchmarked against the agent’s own average to that same country, so an out-of-pattern corridor stands out.

EX.A sender averaging $1,900 to Guatemala when the agent’s baseline to Guatemala is $420.
Destination-country corridors · per-agent benchmark
06 / ONE LEDGER

Across agents, licenses, and locations

The same customer transacting under different agents or state licenses is aggregated into one view. Multi-license and multi-country activity is flagged, so splitting across licenses doesn’t split the picture.

EX.A customer sending $2,700 under one license and $2,600 under another, same day — one ledger, one $5,300 aggregate.
Cross-license · multi-country flags

/ CASE STUDIES

What it looks like when it catches something.

STRUCTURING

The split that stayed under $10k

A sender ran three receipts the same afternoon, each below the single-ticket limit. Per receipt, nothing. Same-day aggregation summed them and raised a CTR-required flag the same day.

$2,900 + $2,800 + $2,900
= $8,600 same-day · CTR flag
IDENTITY OBFUSCATION

One customer, three spellings

Three near-identical names moved money to the same beneficiary. Fuzzy clustering pulled them into one identity at 88% similarity — revealing an aggregate no single spelling would have crossed.

$14,050
combined · 88% name match
NETWORK CLUSTER

Twelve senders, one beneficiary

A fan-in pattern hid across two licenses: twelve unrelated-looking senders, one shared beneficiary. Connected-component analysis surfaced the cluster as a single structure to investigate.

12 → 1
senders → beneficiary · 2 licenses

/ AML WATCH

Walk the network, hop by hop.

An interactive graph of senders and beneficiaries. Pan and select, marquee a group, or isolate a node to its connected component. Scrub the timeline to watch the network build day by day, and expand outward up to six hops and 150 entities.

Pan · Select · Marquee · IsolateTimeline playback 1× / 2× / 4×Up to 6 hops · 150 entitiesC = CTR requiredK = KYC required
NETWORK.VIEWISOLATE · CLUSTER #4471
CK
12 senders → 1 beneficiary · $48,200 / 30 days
AML PATTERN ANALYSIS
Possible identity obfuscation across two licenses
Name relationships
Flags identical, spelling-variant, or similar names — the same individual appearing as different people.
Patterns & relationships
Fan-in / fan-out, layering, circular flows, shared beneficiaries and senders.
Money movement
Dated flows with the licenses and countries they cross — amber when multi-license or multi-country.
Risk factors
Jurisdiction risk, out-of-pattern corridors, and same-day threshold pressure.
Pending alerts
KYC on file, KYC required, KYC requested — carried into the observation.
Watch points
What to keep an eye on next — framed for investigation, never as a conclusion.

AI-generated observations for investigative review — not a determination or legal conclusion. Verify against source records before any action.

/ AI PATTERN ANALYSIS

Select a cluster. Get an analyst’s read.

Marquee-select entities in AML Watch and run Analyze. An AI model, prompted as a senior AML/BSA analyst, reads the selection — using same-day figures, never lifetime totals — and returns structured, hedged observations you can act on:

It names relationships, describes patterns and money movement, calls out risk factors and pending alerts, and leaves watch points — in the careful language of “consistent with” and “may indicate.” It never reaches a conclusion; that’s your job, with the record in front of you.

/ HOW WE ANALYZE OPERATIONS

From raw receipts to a structured read.

01

Ingest

Pull the full scoped book of transactions — sender, beneficiary, amount, date, country, license, agent.

02

Place

Bucket each transaction by amount band, destination country, license, and sender-per-day.

03

Aggregate

Same-day per sender for KYC / CTR thresholds; across licenses and locations into one ledger.

04

Relate

Build the sender↔beneficiary graph and connected components; cluster near-duplicate names.

05

Review

Explore AML Watch, select entities, and let the AI analyst return observations for review.

Analysis runs on demand over your full scoped book — recomputed when you open the view or sync KYC — not as a black-box score. Every signal is traceable back to the transactions behind it.

/ FROM SIGNAL TO ALERT

Detect → flag → request → escalate.

Every customer carries a status. Request KYC and the customer moves into AML Alerts in Compliance Alerts — nothing falls through.

Verified
KYC on file
KYC required
same-day ≥ $3,000, not on file
KYC requested
sent to Compliance Alerts
CTR required
same-day ≥ $10,000

See it run on your licenses.

Schedule a demoKYC

/ THE FILING DESK

Regulatory changes, before your examiner.

A short monthly brief on FinCEN guidance, enforcement actions, and AML practice for money services businesses.

@

MONTHLY · NO SALES MAIL · UNSUBSCRIBE ANYTIME