France Budget Rejection Sidelines Crypto Tax Amendments

France's National Assembly has rejected the revenue section of the 2027 state budget, and with it, three crypto-related amendments lawmakers had just adopted are no longer in the text heading to the Senate. Nothing is law, and nothing is dead either: the proposals, which touch stablecoin taxation, self-custody reporting and platform penalties, can be reintroduced in the Senate. For finance teams, the practical lesson is that stablecoin accounting and wallet-level data readiness should be planned as scenarios now, not after a final vote.

What happened in the National Assembly

Late on Wednesday, the Assembly voted down the revenue section of the 2027 budget at first reading. The count was 458 against none in favour, with two abstentions, according to the official vote record cited in the reporting. The revenue section is the part of a finance bill that deals with government income, including taxes, which is why it is the natural vehicle for tax amendments of any kind, crypto included.

The consequence is mechanical rather than ideological. Once the revenue section is rejected, the government sends the Senate its original budget text. The amendments adopted by deputies during the Assembly debate are not part of that text. A lawmaker's amendment only matters if it is attached to a bill that keeps moving, and this one has stalled at the first hurdle.

Before the vote, Faustine Fleuret, global head of public affairs at lending protocol Morpho, told Cointelegraph that rejecting the revenue section could result in the rejection of the whole bill in the Assembly, including provisions added by amendment. That is exactly how it played out for the crypto measures.

The three amendments that fell away

The source describes three adopted amendments that are now sidelined. Two are described in some detail:

• Self-custody reporting: adopted on Tuesday, an amendment would have required taxpayers to report crypto holdings totalling at least 100,000 euros, with the threshold assessed on Dec. 31 of the tax year.
• Platform penalties: another amendment would have raised penalties from 10,000 euros to 50,000 euros for crypto platforms that fail to provide information requested by tax authorities.
• Stablecoin taxation: the third adopted measure concerned the taxation of stablecoins. The source does not set out its mechanics, so this article does not speculate on rates, triggers or scope.

That last point matters for anyone tempted to model the stablecoin proposal in detail. There is no published design to model, only the fact that lawmakers adopted something on the topic and that it has now been removed from the text going forward.

What happens next in the Senate

The Senate is scheduled to begin debating the finance bill on Nov. 20, followed by an examination of the revenue section's articles on Nov. 23, according to its calendar as cited by the source. Senators can reintroduce the crypto proposals, but they would then need to survive the rest of the budget process before becoming law.

A pause is not a repeal

It would be a mistake to read the rejection as a policy verdict on crypto taxation. The 458 to 0 vote reflects the fate of the whole revenue section, not a judgment on the individual crypto provisions. The same amendments, or revised versions of them, can come back through the Senate. Equally, the Senate may choose not to revive them, or may reshape them. Both outcomes are plausible, and the source does not tell us which is more likely.

Why the timeline is short

The dates the source gives are close together: debate opening on Nov. 20 and article-level examination of the revenue section on Nov. 23. If the proposals return, the Senate window is where it will become visible first. Teams that wait for a final enacted text before touching their data model will be reacting, not preparing.

Stablecoin accounting implications for finance teams

The classification of this item focuses on tax reporting and stablecoins. Even without a published mechanism for the stablecoin amendment, the fact that French lawmakers adopted a stablecoin tax measure is a signal worth taking seriously in your accounting design. It does not change today's treatment. It does tell you which questions a future rule would force you to answer.

USDC accounting and the data a rule would demand

For firms that hold or move USDC and other stablecoins for themselves or for clients, any stablecoin-specific tax rule would likely hinge on data points you should already be able to produce on demand. That is an analytical expectation, not a statement about what the amendment said. Useful questions for your own readiness review include:

• Can you produce a dated, wallet-level and exchange-level balance history for each stablecoin, reconciled to your general ledger?
• Can you separate stablecoin-to-fiat movements, stablecoin-to-crypto swaps and stablecoin transfers between your own wallets?
• Do you capture the fair value or fiat reference at each event in a way an auditor can re-perform?
• Are cost basis and holding-period records for stablecoins kept to the same standard as for volatile assets, rather than treated as cash-like and ignored?

Many teams apply light-touch processes to stablecoins because price movement is small. That shortcut is exactly what a stablecoin-specific rule would expose. Good stablecoin accounting means the same transaction-level discipline you apply elsewhere, with particular attention to volume, because stablecoins often generate the largest number of transactions in a ledger.

Where software and bookkeeping controls fit

This is where the choice of crypto accounting software and your wider bookkeeping controls earn their keep. Whatever tooling you use, the test is whether it can ingest on-chain and exchange data, preserve an audit trail, and let you re-cut balances by asset, wallet and date without manual rework. Crypto bookkeeping software that only produces year-end summaries will struggle if a rule demands a snapshot as of a specific date. Digital asset accounting software that tags self-custody wallets separately from platform accounts will be far better placed if wallet-level reporting returns.

Self-custody reporting and the 100,000 euro threshold

The self-custody amendment is the one with the most concrete detail in the source, and it is the one most likely to affect both firms and their clients if it comes back. As described, it would require taxpayers to report crypto holdings totalling at least 100,000 euros, with the value assessed on Dec. 31 of the tax year.

What a year-end snapshot test means in practice

A threshold tested on a single date changes what you need to track. Instead of reconstructing gains across a year, you would need an accurate year-end valuation of everything a taxpayer holds, aggregated across platforms and self-custody wallets. That raises several practical points:

• Aggregation: holdings spread across several exchanges and private wallets would need to be consolidated to see whether the threshold is crossed.
• Valuation source: a consistent, documented pricing policy for the Dec. 31 snapshot would be essential, since small valuation differences could move a taxpayer across the line.
• Stablecoins in the total: because the measure refers to crypto holdings in aggregate, large stablecoin balances held off-platform would plausibly count toward any threshold. The source does not specify the definition, so treat this as a question to confirm if the text returns.

Advice for B2B practitioners and for individual clients

For accounting firms and CFOs, the immediate step is a client and entity inventory: which French-resident clients or French-linked entities hold material crypto, and how much of it sits in self-custody. For individual filers, who are the end users of these rules, the same logic applies at a personal level. Knowing your own year-end position, across every wallet and platform, is useful whether or not this amendment becomes law, because it is the foundation of any accurate tax return. None of this is a filing obligation today. It is preparation against a proposal that is currently off the table but not gone.

Platform penalties and the AML and tax data angle

The third described measure targets platforms rather than taxpayers: penalties would rise from 10,000 euros to 50,000 euros for crypto platforms that fail to provide information requested by tax authorities. This is also sidelined for now.

Why it matters to firms that are not platforms

If your organisation is a platform, the signal is obvious: lawmakers were willing to raise the cost of non-response fivefold. If you are an accounting firm, auditor or corporate treasury team, the effect is indirect but real. Platforms that face higher penalties tend to formalise how they respond to authority requests, which can change the data you can obtain from them and how quickly. Your own processes for retrieving statements, transaction histories and account confirmations from platforms are part of your audit evidence, and slow or incomplete platform responses are a control risk regardless of what the Senate does.

Connecting tax reporting to AML hygiene

Tax information requests and AML scrutiny increasingly draw on the same underlying records: who controls which wallet, where funds came from and where they went. A ledger that can trace stablecoin flows by counterparty and wallet supports both. Our recent coverage of how finance teams approach the Illinois digital asset tax and the DEX broker carve-out debate shows the same pattern in another jurisdiction: reporting rules keep arriving as proposals, and the teams that cope best are those whose records were already organised by wallet, asset and date. For a view on how stablecoin settlement is changing ledger design, see our piece on stablecoin accounting questions raised by Hong Kong's 24/7 tokenized settlement trials. For the wider framework, our crypto compliance reporting pillar sets out how tax, AML and accounting records fit together.

What finance teams should do now

No obligation has changed, so avoid over-reacting. Equally, a five-day Senate window starting Nov. 20 argues against ignoring the item altogether. A proportionate response is a short, structured readiness exercise.

A practical checklist for the next two weeks

• Monitor the Senate calendar: note the Nov. 20 debate start and the Nov. 23 examination of revenue section articles, and check whether any crypto amendment is tabled again.
• Inventory exposure: list clients and entities with French residence or French platform relationships and their stablecoin and self-custody holdings.
• Test your snapshot capability: try producing a consolidated, fiat-valued position as of Dec. 31 across all wallets and platforms, and note where manual work creeps in.
• Review stablecoin treatment: confirm that your policy for USDC and other stablecoins covers classification, valuation, transfers between own wallets and disposal events, and that it is documented.
• Check platform data access: confirm you can obtain complete transaction histories and year-end statements from every platform you rely on.
• Brief clients plainly: tell them the proposals were dropped for now, may return, and that good records protect them either way.

What not to do

Do not book provisions, change tax positions or tell clients they owe anything on the strength of an amendment that is not in the bill. Do not assume the stablecoin measure's design from its label, because the source does not describe it. And do not treat a 458 to 0 vote as a signal that the Assembly opposed crypto tax measures. It reflects the rejection of the revenue section as a whole.

FAQ

Did France reject crypto taxes?

Not as such. The Assembly rejected the revenue section of the 2027 budget by 458 to 0 with two abstentions. That removed the crypto amendments adopted by lawmakers from the text sent to the Senate, but it was a vote on the whole section, not on crypto policy specifically.

Can the crypto amendments come back?

Yes. The proposals could be reintroduced in the Senate, which is scheduled to begin debating the finance bill on Nov. 20 and to examine the revenue section's articles on Nov. 23. They would still need to survive the remaining budget process to become law.

What would the self-custody reporting amendment have required?

As described, taxpayers would have had to report crypto holdings totalling at least 100,000 euros, with the threshold assessed on Dec. 31 of the tax year. It is not currently part of the bill.

Should I change my stablecoin accounting now?

Not because of this vote. Nothing has changed legally. It is a good moment, though, to confirm that your USDC and other stablecoin records are complete, reconciled and valued consistently, so you can respond quickly if a rule returns.

How much would platform penalties have increased?

The amendment would have raised penalties from 10,000 euros to 50,000 euros for crypto platforms that fail to provide information requested by tax authorities. It was also removed with the rest of the adopted amendments.

Bottom line

The Assembly's vote clears the crypto amendments from the budget text for now, but the Senate calendar keeps the issue alive in the same month. Treat it as a planning signal: tighten stablecoin records, test your year-end snapshot capability and watch Nov. 20 and Nov. 23.

Source: Cointelegraph Regulation