What makes cross-rail structuring hard to detect with legacy tools?

Legacy AML transaction-monitoring systems are typically deployed per payment channel, so a structurer can split a movement across ACH, wire, and instant payment and stay under each channel's own reporting threshold without any single monitor seeing the full picture.

What specific pattern does the detector flag?

It flags the case where a sender's combined total across all payment rails in a rolling window exceeds the BSA/CTR reporting threshold of $10,000, while every individual rail's total for that sender stays below the threshold.

Is rail diversity itself scored?

Yes. A sender touching three or more distinct payment rails within 24 hours contributes an independent elevated-risk signal, even absent an aggregate threshold breach.

Cross-Rail Aggregate Structuring Detector

Executive Summary

The Bank Secrecy Act's Currency Transaction Report requirement triggers at $10,000 in a single rail/day, and most structuring-detection systems only watch a single rail's transaction stream for the classic "just-under-threshold, repeated" evasion pattern. JIL Sovereign's cross-rail correlation signal instead aggregates a sender's transaction totals across every payment rail they touched (ACH, wire, card, and instant payment) in a rolling window, and specifically flags the case where the combined sum crosses the CTR-equivalent threshold while every individual rail's total stays under it.

Core Innovation: Cross-rail aggregation, not just cross-transaction aggregation within a single rail, as the structuring-detection surface - plus an independent "rail diversity" signal (three or more distinct rails touched by the same sender in 24 hours) as an elevated-risk indicator even absent an aggregate breach.

Problem Statement

Legacy AML transaction-monitoring systems are typically deployed per channel - the ACH monitoring system watches ACH, the wire desk watches wires, the card network watches card transactions - because those channels historically ran on separate processing cores. A sophisticated structurer exploits exactly this seam: split a $15,000 movement into $6,000 by ACH, $5,000 by wire, and $4,000 by instant payment, and no single-rail monitor ever sees a transaction above its own threshold, because none of them is designed to look across the boundary.

$10,000

BSA/CTR single-rail reporting threshold

4

rails aggregated: ACH, wire, card, instant

3+

distinct rails in 24h - independent diversity signal

Technical Architecture

Detection Flow

For a given sender/receiver pair, the engine aggregates transaction totals grouped by declared payment rail over a rolling seven-day window. Two conditions are then tested independently:

Signal	Condition	Score Contribution
Multi-rail detected	Sender used more than one rail to the same receiver in the window	+30
Cross-rail splitting	Combined total across rails exceeds $10,000 while every individual rail's total stays under $10,000	+40
Sender rail diversity	Sender used three or more distinct rails in 24 hours (any receiver)	+20

The signal triggers at a combined score of 25 or above. It runs alongside a companion four-rail coverage attestation that continuously confirms all four mandated rails - check, ACH, wire, and instant, plus card and crypto - are actively evaluated by the same verdict engine, consistent with the OCC, Federal Reserve, and FDIC's joint expectation of comprehensive rail coverage in transaction-monitoring programs.

Prior Art Differentiation

Approach	Monitoring Scope	Detects Cross-Rail Splitting?
Per-channel legacy core monitoring	Single rail (ACH-only, wire-only)	No - blind to activity on other rails
Generic velocity-only monitors	Transaction frequency, single rail	No - counts frequency, not cross-rail sum
JIL Sovereign	All rails, unified evaluation	Yes - explicit sum-exceeds-but-no-rail-exceeds test

Patent Claim

Independent Claim 131: A computer-implemented method for detecting cross-payment-rail structuring, comprising: aggregating, for a common sending entity over a rolling time window, transaction totals separately by payment rail across a plurality of heterogeneous payment rails including at least automated clearing house, wire, card, and instant-payment rails; computing a combined total across all payment rails for the sending entity over the window; determining that the combined total exceeds a regulatory reporting threshold while every individual per-rail total remains below that threshold; and generating a structuring-risk signal responsive to that determination, the signal being combined with a rail-diversity indicator reflecting the count of distinct payment rails used by the sending entity within a shorter time window.