Folio v0.9 — CEX + On-chain Consolidation is liveSee what's new →

Cerfa 3916-bis: Declaring Foreign Crypto Accounts in France (2026)

Crypto Finance·

Cerfa 3916-bis: Declaring Foreign Crypto Accounts in France (2026)

Form 3916-bis (Cerfa 3916-bis) is mandatory for French tax residents holding a crypto account on a foreign platform — no threshold. Box-by-box guide, penalties, the link with Form 2086, and the DAC8 cross-check from 1 January 2026.
Author avatar Wag3s TeamEditorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.

Reviewed by Wag3s Editorial Team — verified against article 1649 bis C CGI, article 1736 X CGI, article L. 169 LPF, and the Cerfa 3916/3916-bis notice · Last reviewed May 2026

Cerfa 3916-bis: Declaring Foreign Crypto Accounts in France

Form 3916-bis (Cerfa 3916-bis) is one of the least understood and most actively cross-checked French tax forms. Any French tax resident holding an account on Binance, Coinbase, Kraken, Bitstamp, or any foreign crypto platform must file it every year — with no threshold and no exemption. DAC8, effective 1 January 2026, adds a layer: the DGFiP now automatically receives the list of French accounts hosted by EU-authorised CASPs, making an omission of 3916-bis automatically detectable.

This guide walks the form box by box, covers the edge cases, and sets out the articulation with Form 2086 and the practical impact of DAC8.

TL;DR

  • Who: any French tax resident who held/used/closed a digital-asset account at a foreign provider.
  • Threshold: none — a €10 balance triggers it (contrast Spain's Modelo 721 €50,000).
  • Self-custody excluded; French-authorised providers excluded — only foreign third-party-hosted accounts.
  • Independent of Form 2086 — 3916-bis declares the account; 2086 declares the gains. Both can apply.
  • Penalties (art. 1736 X CGI): €750 per account (€1,500 if balance > €50,000 at any point); fraud → 80% surcharge + 10-year reassessment.
  • DAC8 (from 1 Jan 2026): CASPs report to the DGFiP; 3916-bis becomes a cross-check point.

Who must file

The obligation rests on French tax residents who, during the year, held, used, or closed a digital-asset account opened with an entity established abroad (a foreign CASP / exchange — Binance Global, Coinbase outside France, Kraken outside France, Bitstamp, etc.). The French tax-residence test applies to the taxpayer, not the exchange.

Excluded:

  • Self-custody wallets (MetaMask, Ledger hardware, Trust Wallet) — 3916-bis covers accounts hosted by a foreign third-party provider, not wallets you control directly.
  • Accounts at French-authorised providers — the obligation targets foreign accounts.

So a French resident with a self-custodied Ledger and no foreign exchange account files no 3916-bis; one with any foreign exchange account does, regardless of how little is on it.

No threshold — the defining feature

Form 3916-bis has no de minimis threshold. It is filed as soon as a foreign digital-asset account has been held or used during the year, irrespective of balance or transaction volume. This is stricter than several EU equivalents — the Spanish Modelo 721 has a €50,000 threshold; France has none. A dormant foreign account with €10 on it is reportable.

This is the single most common French compliance failure: assuming a small or unused foreign account is below "some threshold." There is no threshold.

Independent of Form 2086

3916-bis and Form 2086 are independent and both can be required:

FormPurposeTrigger
3916-bisDeclares the existence of a foreign crypto accountHolding/using/closing a foreign account
2086Declares realised capital gainsA taxable disposal (crypto → fiat/goods/services)

Examples:

  • Unused Binance account in 2025, no disposals → 3916-bis only.
  • Sold crypto from a foreign platform → 3916-bis + 2086 (gains computed under 150 VH bis).
  • Self-custody only, sold to fiat via a French-authorised provider → possibly 2086 only (no foreign account).

Box-by-box (what the form captures)

Without reproducing the official form, 3916-bis is organised as:

  1. Account holder identification — taxpayer details (pre-filled in the online return).
  2. Account designation — the provider's name and the account identifier.
  3. Provider details — name and address of the foreign entity hosting the account.
  4. Account characteristics — opening date; closure date if applicable; whether held/used/closed during the year.
  5. One block per account — a separate declaration for each foreign account (no aggregation across providers).

The data burden is one complete block per foreign account, including accounts closed during the year.

Penalties and the reassessment period

Under article 1736 X CGI:

SituationPenalty
Undeclared foreign crypto account€750 per account
Account balance > €50,000 at any point in the year€1,500 per account
Characterised fraud (intentional / repeated / non-cooperative state)80% surcharge on evaded tax

The reassessment period (délai de reprise) is normally 3 years but extends to 10 years where the omission involves a non-cooperative state or characterised fraud (article L. 169 LPF). DGFiP enforcement has tightened where omissions are revealed by cross-checking external data — which is exactly what DAC8 industrialises.

DAC8 and 3916-bis from 2026

DAC8 does not remove the 3916-bis obligation. From 1 January 2026, EU-authorised CASPs automatically report French residents' accounts to the DGFiP. The taxpayer's own 3916-bis declaration still stands. The practical shift: 3916-bis becomes a cross-check point. A CASP-reported account with no matching 3916-bis is an obvious flag, and the first reconciliation follows the first DAC8 authority exchange (by 30 September 2027 for FY 2026 — see DAC8 impact on individuals and DAC8 vs CARF).

For a resident with prior unreported foreign accounts, the window to regularise before the first DAC8 cross-check is finite — this is the France-specific version of the voluntary-disclosure point.

Practical workflow

  1. Inventory every foreign account held/used/closed in the year (including closed and near-empty ones).
  2. Exclude self-custody and French-authorised providers; include all foreign third-party accounts.
  3. File one 3916-bis block per foreign account with the annual return — no threshold to clear.
  4. File Form 2086 separately if there were taxable disposals.
  5. Reconcile against DAC8-reported data; regularise prior omissions before the first cross-check.

How vendor tools handle 3916-bis

Waltio (French-market-specialised) and Koinly can list connected foreign accounts to support 3916-bis preparation. The decisive check: confirm the tool flags every foreign account with no threshold filter (a tool that hides small/dormant accounts will cause an omission), and that it keeps self-custody out of the 3916-bis list. No tool decides tax residence — that is the governing test and a question for a French adviser.

How Wag3s helps

Wag3s Folio inventories connected accounts and flags every foreign third-party-hosted account for 3916-bis (no threshold filter), separates self-custody, and reconciles the list against DAC8-reported activity so a CASP-reported account always has a matching declaration. See the Folio product page.


Further reading

Sources

  • Article 1649 bis C CGI — obligation to declare foreign digital-asset accounts — Légifrance
  • Article 1736 X CGI — penalties for undeclared foreign digital-asset accounts
  • Article L. 169 LPF — reassessment period (3 years; 10 years for non-cooperative states / fraud)
  • impots.gouv.fr — Cerfa 3916 / 3916-bis notice
  • Council Directive (EU) 2023/2226 (DAC8) — EUR-Lex
Editorial disclaimer
This article is informational and does not constitute tax advice. The 3916-bis obligation has no threshold and the penalty/limitation rules are technical. Confirm your position with a French tax lawyer or expert-comptable before filing.