FinCEN and Federal Reserve abandon proposed lower threshold for cross-border transfer records

The Financial Crimes Enforcement Network announced on 6 November that it and the Federal Reserve Board were withdrawing a proposed rulemaking on US Recordkeeping and Travel Rule obligations for transfers of funds. The proposal had addressed convertible virtual currencies and would have lowered the applicable threshold for transfers beginning or ending outside the United States. That is materially different from reducing actual current reporting duties: the regulators have abandoned a proposed change, not repealed the existing Bank Secrecy Act framework.[1][2]

This distinction matters to banks, payment processors, crypto brokerages and firms that automate payment-message enrichment. A compliance vendor might have been preparing new data fields or tighter screening for smaller transfers in anticipation of a lower threshold. It would be wrong to assume that every prospective change has become mandatory simply because a consultation was published. Equally, an institution cannot read the withdrawal as permission to omit originator and beneficiary information on transfers that remain in scope under the current rules.[1][2]

The announcement is short but consequential: both agencies have withdrawn the notice of proposed rulemaking. The release does not prescribe a replacement threshold, launch a new rule or announce an effective date for revised documentation. There is therefore no evidentiary basis for recalculating a regulatory cost saving on the assumption that a proposed lower threshold was already being enforced. Any bank business case must distinguish expenses actually incurred from implementation expenditure merely budgeted.[1][2]

The compliance work that still remains

For operators supporting both fiat transfers and digital-asset withdrawals, compliance rules arise from several sources: domestic transfer requirements, sanctions, licensing, counterparties and platform risk controls. Withdrawal of one proposed technical amendment does not remove those obligations. Firms should verify which customer-data checks were tied to the abandoned proposal and which are independently required by current law or existing partner banks.[1][2]

A useful practical takeaway is version control. Update the regulatory-obligations inventory, annotate the old consultation as withdrawn, record the decision date and keep open supervisory issues separate. The firm should not roll back established screening merely because a reform no longer proceeds. For news readers, the meaningful outcome is a halted policy pathway rather than a new exemption.[1][2]

Report an error or submit an update