Treasury Withdraws the $250 Travel Rule Proposal: What Finance Teams Should Do

The US Treasury has withdrawn a long-pending proposal that would have pushed the Travel Rule threshold down from $3,000 to $250, so the current recordkeeping baseline stays in place for now. For teams running crypto accounting software, nothing changes on Monday morning. What does change is the planning assumption: a sharp, near-term jump in per-transaction data collection is off the table, while the policy question itself remains open.

What FinCEN and the Federal Reserve actually withdrew

On Friday, the Financial Crimes Enforcement Network (FinCEN), part of the Treasury Department, and the Federal Reserve Board of Governors rescinded the proposed amendments to the Recordkeeping Rule and the Travel Rule. The proposal dates to 2020. It would have required financial institutions to collect and pass along information on transactions of $250 or more, instead of the existing $3,000 threshold.

The two agencies gave three reasons for pulling it. More than five years have passed since the proposal. The convertible virtual currency (CVC) industry has changed in that time. And additional public input would be helpful before anything moves forward. In their words, any future amendments related to CVC should be considered in light of these recent developments so that they are fit for purpose.

What the withdrawal does and does not do

It is important to read the notice for what it is. A withdrawn proposal is not a final rule, and it was never in force. Nobody was operating under a $250 threshold, so there is no compliance obligation to unwind. The existing $3,000 threshold continues to be the operative figure referenced in the source reporting.

It is also not a statement that the agencies have abandoned the policy goal. The agencies explicitly left room for future, potential amendments. The signal is about process and timing: if a revised version comes, it would be built on a fresh record rather than on a 2020 docket.

Why the original proposal drew fire

When FinCEN first put the idea forward, its argument was that bad actors were increasingly moving illicit funds through smaller transactions. That is a coherent AML rationale: threshold-based rules invite structuring below the line, and a lower line narrows that room.

Crypto advocacy groups saw it differently. Coin Center warned that dropping the threshold from $3,000 to $250 would sweep many ordinary transactions into what it called warrantless financial surveillance. The Crypto Council for Innovation's CEO, Ji Hun Kim, called the withdrawal the right call and said the proposal had not advanced over the years for good reason. In his view, lowering the cross-border threshold would have placed undue burden on institutions.

The wider pattern: two withdrawals in two months

This is not an isolated action. According to Coin Center, Treasury withdrew proposed rules last month covering so-called unhosted wallets and cryptocurrency mixing. The unhosted wallet proposal would have imposed reporting and recordkeeping requirements on transactions involving self-hosted wallets. Coin Center had opposed both of those as well.

Coin Center's summary was that, taken together, the withdrawals close the books on several long-pending proposals that would have expanded the Bank Secrecy Act's already extensive financial surveillance regime. That is an advocacy organisation's framing, and readers should treat it as such. The factual core is simpler: three legacy proposals that sat for years have now been taken off the table in quick succession.

How to read the sequence

Three separate withdrawals across roughly a month suggest a housekeeping approach to the regulatory backlog, at least on these items. The agencies' own language points the same way: age of the proposal, industry change, need for fresh input. We should not over-read it as a policy reversal on crypto AML as a whole, because the source does not say that, and the Bank Secrecy Act framework itself is untouched.

What the sequence does tell planners is that the 2020-era agenda is being cleared. Any successor effort would likely be drafted against today's market, which includes a larger institutional presence, stablecoin growth and the migration of activity onto different rails. Those are context points for your own scenario planning, not claims the agencies made.

What this means for accounting and finance teams

For a CFO, controller or accounting firm advising crypto-active clients, the practical effect is a removed risk and a retained uncertainty. The removed risk is a mandatory, large expansion in the volume of transactions requiring information collection. The retained uncertainty is the form any later proposal takes.

Recordkeeping and data capture

Travel Rule and recordkeeping obligations sit mostly with financial institutions, but their downstream effect lands on the books of the businesses and funds that transact through them. When counterparties collect more information, they ask you for more information. A lower threshold would have meant more transfers triggering those requests, and more internal pressure to show who sent what, to whom, and why.

That pressure is now deferred. It is not gone. Teams whose crypto bookkeeping software already captures counterparty, wallet and purpose data at the transaction level will find any future threshold change a minor adjustment. Teams relying on year-end reconstruction from exchange exports would find it painful. The withdrawal is a reasonable moment to move from the second model to the first, which is the use case digital asset accounting software exists for.

Controls and audit trail

Auditors do not test against proposed rules, only against rules in force and against management's own stated policies. The withdrawal therefore does not alter audit scope. It does affect how defensible your documentation is if a bank, exchange or regulator later asks about small-value transfers. A control that logs transfer purpose and counterparty regardless of size is cheap to run and hard to criticise.

If your team had drafted a contingency procedure for the $250 scenario, there is no reason to delete it. Park it, date it, and note the trigger that would revive it, such as a new proposal appearing in the Federal Register. That keeps the work reusable without implying a live obligation.

Cross-border transfers

The Crypto Council for Innovation's comment specifically referenced cross-border transfers, so firms with international treasury flows are the group most relevant to the original proposal. If you move funds across borders, your records should already tie each transfer to an internal approval, a business purpose and the receiving party. Those fields support Travel Rule style data requests from counterparties whether or not a US threshold changes.

What individual-facing and mixed-practice firms should tell clients

Although this piece is aimed at firms and finance leaders, many practices also serve individual filers, and the questions will come. The accurate message is short. The proposal to cut the threshold to $250 has been withdrawn, so ordinary small transfers are not about to be subject to the stricter collection regime described in 2020. The withdrawal of the unhosted wallet proposal, reported as occurring last month, means that self-hosted wallet users are also not facing the specific reporting and recordkeeping requirements that proposal described.

Those are statements about proposals, not about tax. Nothing in this announcement changes how crypto is taxed, how gains are computed, or what a taxpayer must report on a return. Clients should keep their own transaction records exactly as before, because tax reporting obligations are independent of the Travel Rule.

Managing the wrong conclusion

The risk to manage is a client hearing "withdrawn" and concluding that crypto activity is now less scrutinised. Existing Bank Secrecy Act obligations on regulated institutions continue, and the withdrawal notice itself says future amendments may be considered. Advise clients to keep contemporaneous records of acquisition, disposal and transfers, and to avoid structuring behaviour designed to sit under any threshold.

A practical checklist for the next 30 days

This is a low-urgency development, so the right response is proportionate. The following steps cost little and pay off whether or not a new proposal appears.

Steps for finance and accounting teams

• Confirm your baseline. Document that your policies reference the existing $3,000 threshold and that no $250 procedure is currently mandatory.
• Review data fields. Check whether your crypto accounting software captures counterparty, wallet address, transfer purpose and approver for transfers of any size.
• Reconcile small transfers. Sample low-value transfers from the last quarter and test whether you can explain each one from your records alone.
• Update the regulatory watchlist. Record the withdrawal date, the three stated reasons and the unhosted wallet and mixing withdrawals so your file shows the trajectory.
• Brief the client-facing team. Agree one paragraph of wording that says the proposal is withdrawn, the baseline is unchanged and records should still be kept in full.

What to watch for next

The notice leaves open the possibility of future amendments to the Recordkeeping Rule and Travel Rule as they relate to CVC. If that happens, the agencies have said they want additional public input, which implies a new comment period. That would be the moment for firms and industry bodies to submit data on operational cost and on how crypto accounting software and internal controls handle transfer-level information.

It is also worth tracking the wider US legislative and policy environment. Our coverage of what a Democratic Congress means for US crypto accounting plans and the CLARITY Act setback covers the broader backdrop against which any new Treasury effort would sit. For the full framework, see our crypto compliance and reporting pillar.

Limits of what we know

The source reporting is brief. It does not describe any replacement proposal, a timetable for one, or any change to the existing $3,000 threshold. It does not detail how many institutions would have been affected, and it provides no cost estimates for the withdrawn rule. Anything beyond the agencies' three stated reasons and the reactions from Coin Center and the Crypto Council for Innovation is inference, and we have flagged it as planning analysis rather than reported fact.

For that reason, the sensible stance is neither celebration nor complacency. The proposal is gone, the framework it would have amended remains, and the agencies have said they may revisit the area with a fresh record. Teams that treat this as a prompt to improve transaction-level data capture will be well placed under either outcome.

FAQ

What did FinCEN and the Federal Reserve withdraw?

They rescinded a proposal, first put forward in 2020, to amend the Recordkeeping Rule and the Travel Rule so that information would be collected on transactions of $250 or more, down from $3,000. It was a proposal only and was never in force.

Does the $3,000 threshold still apply?

Yes. The withdrawal leaves the existing $3,000 figure in place. The source reporting describes the withdrawn proposal as the one that would have lowered it to $250.

Why did the agencies withdraw it?

They cited the passage of more than five years, changes in the convertible virtual currency industry, and the value of additional public input. They said any future amendments should be considered in light of recent developments.

Could a new proposal follow?

It is possible. The agencies referred to future, potential amendments, but the source reports no replacement proposal or timetable. Any new version would be expected to come with fresh public input.

Should our firm change its crypto accounting software setup?

No change is required by this withdrawal. It is a sensible moment to confirm that your tools capture counterparty, wallet, purpose and approval data on every transfer, so that a future threshold change would be an adjustment rather than a rebuild.