France Crypto Tax Amendments: What the Budget Vote Means
France's Assembly rejected the 2027 budget revenue section, sidelining three crypto proposals. Here’s what was proposed and what could happen next.

France's Budget Vote Puts Three Crypto Proposals on Hold
France's National Assembly has put three proposed crypto measures on hold - not by voting on each one separately, but by rejecting the revenue section of the country's 2027 budget. The proposals had been adopted as amendments during the budget debate. After the revenue section failed, they were left out of the original budget text sent to the Senate.
The distinction matters. These measures aren't law, and the Assembly's vote didn't decide the underlying policy questions. The Senate could still take them up, but they would have to clear the rest of the budget process before they take effect. For crypto holders, the immediate impact is uncertainty, not a new reporting or tax obligation.
The amendments targeted three areas: gains when converting crypto into stablecoins, disclosure of large self-custodied holdings, and penalties for platforms that fail to provide information requested by tax authorities. Here's what the Assembly rejected, what each proposal would have changed, and what to watch next as the bill moves to the Senate.
What did France's National Assembly reject?
At first reading, the Assembly rejected the revenue section of the 2027 state budget. The vote was 458-0, with two abstentions, based on the official voting record. Revenue provisions cover how the government raises money, including tax rules - so this vote was about a major part of the budget, not a standalone crypto bill.
The practical consequence was straightforward: the government would send the Senate the original budget text, without the crypto amendments lawmakers had adopted during the Assembly's debate. Those proposals didn't make it into the version moving forward from the Assembly.
It's tempting to read this as a head-on rejection of each crypto measure, but that's not what happened. The three amendments were adopted before the revenue section was voted down. Once the revenue section failed, the adopted provisions were removed along with it. The Assembly didn't run a fresh, final vote on each amendment as a standalone decision about whether stablecoin conversions should be taxable or whether self-custodied assets should be disclosed.
Why the procedural detail matters
A budget amendment can pass one stage and still never become law. It has to stay in the bill as it moves through the later stages, and the final text has to complete the legislative process. An amendment being adopted during debate isn't the same thing as an enacted rule.
Here, the revenue section's rejection meant the adopted crypto provisions weren't included in what the government sent to the Senate. Lawmakers could reintroduce them, but the fact that they cleared the Assembly earlier doesn't guarantee they'll return - or survive later debate.
Faustine Fleuret, global head of public affairs at Morpho, warned before the vote that rejecting the revenue section could lead to rejection of the whole bill in the National Assembly, including provisions introduced by amendment. The point is that the fate of these measures depended on the wider legislative package around them, not only on their individual adoption in the Assembly.
What the vote does - and does not - tell us
What you can say with confidence is limited and specific: these three proposals aren't in the original budget text now going to the Senate. What you can't conclude from this vote alone is that French lawmakers have permanently dropped the ideas, or that the vote itself has created any new crypto tax or reporting requirement.
If you're tracking this, the most useful next step is to watch the next version of the finance bill. Reports that the Assembly "adopted" an amendment describe an earlier stage. Reports that the measures "fell away" describe what happened after the revenue section was rejected. Both can be accurate - and neither should be treated as proof that anything is already in force.
What did the three crypto amendments propose?
The three amendments dealt with separate issues in the relationship between crypto holders, trading platforms, and tax authorities. One addressed when a crypto gain might be taxed. Another focused on reporting certain assets held outside custodial services. The third would have raised penalties for platforms that fail to provide information to tax authorities.
They're not one bundled policy. A tax rule affects how a transaction is treated; a disclosure rule affects what holders must report; and a penalty rule affects what happens when a platform doesn't comply with an information request. Each proposal targets different actors and raises different implementation questions.
Taxing gains on crypto-to-stablecoin conversions
On October 16, lawmakers adopted an amendment that would make gains from crypto-to-stablecoin conversions taxable. The key point is the gain - not a tax on the full amount converted. The proposal was about whether a conversion that produces a gain should trigger tax consequences.
That distinction matters for day-to-day portfolio moves. A holder might swap a volatile crypto asset for a stablecoin to reduce exposure without withdrawing funds to a bank account. Under a rule that treats a conversion as a taxable event when it realizes a gain, moving into a stablecoin could still trigger a tax calculation - even if the holder stays inside the crypto ecosystem.
The available information doesn't include the proposed tax rate, the method for calculating gains, or any exemptions. Those details would be essential for understanding how any real transaction would be treated and what records a taxpayer would need. In any case, the amendment was sidelined when the revenue section was rejected, so it isn't an enacted rule based on this vote.
Disclosing large self-custodied holdings
A second amendment, adopted on Tuesday before the revenue-section vote, would have required taxpayers to disclose self-custodied crypto holdings worth at least €100,000. The threshold would be assessed on December 31 of the tax year. The source estimates that euro figure at about $112,000.
"Self-custody" generally means the person controls the keys rather than relying on a platform to hold the assets. So the proposal focused on holdings held directly by a taxpayer, not only balances visible on an exchange. The December 31 valuation date also makes timing relevant: what matters is the position at year-end, not at some earlier point.
The available account doesn't spell out how wallets across multiple accounts would be valued or combined, what information a disclosure would require, or how the rule would apply to assets with changing prices. Those are design questions that would affect whether people could comply consistently and how tax authorities could compare declarations.
Increasing penalties for platform non-compliance
The third amendment would have raised the penalty for crypto platforms that fail to provide information requested by tax authorities - from €10,000 to €50,000. This measure was aimed at platform cooperation with information requests, rather than directly changing the tax treatment of a user's assets.
A higher penalty can make it more expensive to ignore a formal request, but the real impact would depend on how broadly requests are defined, how platforms can challenge requests, and what counts as non-compliance. The source doesn't specify those conditions. So this should be understood narrowly: it sought to raise the stated penalty, not to create a general new tax on crypto platforms.
What does the vote mean for crypto users and businesses?
For now, the vote doesn't make any of the three proposed rules effective. Crypto holders shouldn't read the earlier adoption of an amendment as a cue to file a new disclosure or treat every stablecoin conversion as taxable under these proposals. The revenue section was rejected, and the measures were omitted from the budget text sent to the Senate.
That doesn't mean the proposals are irrelevant. They lay out policy questions French lawmakers may revisit: whether crypto-to-stablecoin conversions should be taxed, what holders with significant self-custodied balances should report, and how strongly platforms should be penalized for withholding information from tax authorities.
Separate current obligations from proposed changes
If you're doing compliance work, the first step is separating rules that are already in force from proposals that are still moving through Parliament. A draft amendment can influence planning and public debate, but it isn't a substitute for checking the actual law and the guidance that applies to the relevant tax year.
For individuals, the proposed €100,000 threshold raises practical questions about wallet records, valuation, and aggregation. Those are reasonable topics to understand - but the sidelined amendment doesn't itself impose the disclosure obligation. Anyone making tax decisions should stick with current French rules and, where needed, qualified advice, rather than assuming the proposal has taken effect.
For businesses and platforms, the penalty increase is a sign to keep information-request processes tidy: track requests, assign responsibility, and retain records of responses. That's sensible operational practice, but it shouldn't be confused with a current €50,000 penalty created by this vote. Since the amendment didn't make it into the budget text sent to the Senate, it isn't in force.
Why the stablecoin provision would matter operationally
The stablecoin proposal would have made transaction tax treatment relevant even when a user didn't cash out into euros. That affects portfolio management, trading records, and how users expect the numbers to work. A platform might show a conversion as one step in a trading workflow, while the tax system might treat the disposal of the original asset as the event that has to be calculated and documented.
If a similar measure returns, details will matter more than the headline. Users and advisers would need clarity on what assets are covered, how gains are calculated, how transaction costs are handled, and whether any exceptions apply. Businesses would also need clear explanations in product interfaces and transaction histories, so customers can identify which events could matter. None of that can be assumed from the amendment summary alone.
The bottom line isn't that French crypto policy is settled. It's that the legislative process interrupted a set of proposals that could come back. Treating something as already enacted creates compliance risk; ignoring a proposal that might return creates planning risk. The challenge is keeping those risks separate.
Could the proposals return in the Senate?
Yes - according to the source reporting, the proposals could be reintroduced in the Senate, but it's still a possibility, not a guarantee. The Senate was scheduled to begin debate on the finance bill on November 20, followed by examination of the revenue section's articles on November 23.
Those dates are milestones, not promises. The Senate could move forward without these amendments, revisit one or more of them, or change their wording. And even if an amendment returns and passes a stage, it still has to survive the remaining budget process to become law.
What to monitor in the next version
A practical way to follow the debate is to track each proposal on its own rather than just watching for broad headlines about crypto regulation. The amendments address different policy effects, and their paths could diverge as the bill moves forward.
- Whether an amendment is reintroduced: A proposal left out of the Assembly text would need to return through a later legislative step before it can be considered again.
- Whether its wording changes: A new version could adjust the threshold, tax trigger, penalty amount, or scope.
- Whether it is adopted at that stage: Reintroduction isn't the same as passage. The votes and the resulting text matter.
- Whether the provision remains in the final legislation: Even if adopted, an amendment can still be affected by later stages of the budget process.
- When any enacted rule would apply: Effective dates and transitional arrangements determine when obligations begin.
A practical decision framework
If you're a crypto holder, platform, or adviser, use three questions to separate immediate action from monitoring. First, what rule applies today? Second, has a new version of the amendment actually entered the bill? Third, has the final legislation been enacted, and does it apply to your situation and tax year?
Until those questions have clear answers, it's reasonable to keep usable transaction records and follow the Senate debate. It's not reasonable to treat the proposed provisions as current law based only on their earlier adoption in the Assembly. If the Senate changes the bill, reassess the text itself - not the earlier headlines.
The broader lesson is procedural: the path an amendment takes matters as much as what it says. The Assembly vote removed these proposals from the text going to the Senate, but it didn't eliminate the chance of another attempt. The next meaningful signal will be the bill and amendments the Senate actually considers, followed by the final outcome of the budget process.
Conclusion
France's Assembly vote removed three proposed crypto measures from the budget text sent to the Senate, but it didn't permanently end the debate. The stablecoin tax, self-custody disclosure threshold, and higher platform penalty are still proposals that could return in a later stage.
For now, separate enacted obligations from amendments that may be reconsidered. Follow the Senate's actual bill text, and judge any future changes by their wording, scope, and effective date - not by the fact that an earlier version cleared a vote in the Assembly.