Why Cross-Border Financial Enforcement Is Difficult

Financial misconduct can cross borders in seconds, but legal authority remains largely national. A regulator may identify suspi­cious trading, payments or ownership abroad without having power to compel a foreign bank, question a witness or freeze an asset directly. The resulting delay is not always regulatory failure; it often reflects lawful limits on juris­diction, evidence sharing and due process.

Map the conduct across jurisdictions

Start with an entity-and-event map: suspects, companies, accounts, platforms, inter­me­di­aries, assets, servers and affected customers. Record where each act occurred and which authority regulates each partic­ipant. Separate the regulator that detected the conduct from the authority able to obtain evidence or impose a remedy.

Our guide to financial intel­li­gence units explains why an FIU analyses and dissem­i­nates intel­li­gence but does not replace police, prose­cutors, regulators or courts. Confusing these roles leads to unreal­istic expec­ta­tions about immediate enforcement.

Identify the legal gateway for every request

For each required record or action, specify the channel: regulator-to-regulator cooper­ation, FIU exchange, mutual legal assis­tance, a production order, civil disclosure, insol­vency assis­tance, extra­dition or recog­nition of a judgment. Each has different thresholds, permitted uses, confi­den­tiality rules and timescales.

The IOSCO Multi­lateral Memorandum of Under­standing is an inter­na­tional benchmark for securities-enforcement cooper­ation and infor­mation exchange. It helps signa­tories obtain defined categories of infor­mation, but it does not create a borderless regulator or override domestic law.

Why requests slow down or fail

Common obstacles include incom­plete legal and factual descrip­tions, dual-crimi­nality require­ments, bank or profes­sional secrecy limits, data-protection rules, trans­lation, incom­patible evidence standards, competing inves­ti­ga­tions and insuf­fi­cient staff. Assets may move again while a request is being clarified. Companies can also place ownership, accounts, data and opera­tions in different countries.

FATF’s current 40 Recom­men­da­tions include inter­na­tional cooper­ation, while its consol­i­dated infor­mation-sharing standards call for complete factual and legal infor­mation and expedi­tious channels. These standards support cooper­ation; actual execution still depends on national imple­men­tation, available powers and the facts of the case.

Build requests that can be executed

State the suspected offence or regulatory breach, relevant dates, persons, accounts, legal basis, records requested, intended use, confi­den­tiality needs and urgency. Explain the connection between the requested country and the conduct. Ask the foreign authority which format and gateway it requires before sending a large package.

Maintain a request tracker showing owner, date, acknowl­edgement, clari­fi­cation, legal deadline and result. Preserve source restric­tions so intel­li­gence is not used as court evidence without permission. Michael Schmitt’s analysis of cross-border enforcement in practice provides useful practi­tioner context on service, cooper­ation and recog­nition; case strategy must follow the applicable treaties and domestic laws.

Measure outcomes, not request volumes

Count time to acknowl­edgement and production, usable records received, assets preserved, duplicate requests avoided and cases reaching an evidence-based decision. A high number of memoranda or infor­mation exchanges does not prove effective enforcement.

Inves­ti­gators should also preserve alter­native expla­na­tions and excul­patory material. Cross-border complexity must not lower the standard of proof. Effective cooper­ation turns a suspicion into admis­sible, attrib­utable evidence while respecting the rights of affected parties—and states clearly when legal authority, rather than inves­tigative effort, limits the result.