Crypto Accounting Pennylane Export: Connecting Web3 Books to the French Plan Comptable in 2026
Crypto Accounting Pennylane Export: Connecting Web3 Books to the French Plan Comptable in 2026
Reviewed by Wag3s Editorial Team — verified against Pennylane public API documentation, ANC Règlement 2018-07 and ANC Règlement 2026-01 (9 January 2026), and PCG account-number conventions · Last reviewed May 2026
Crypto Accounting Pennylane Export
Exporting crypto into Pennylane is a French-accounting problem before it is a technical one. Pennylane's API speaks the Plan Comptable Général — it creates ledger entries against PCG accounts, generates a conforming FEC for the DGFIP, and fits the cabinet-and-client review workflow French expert-comptables expect. So the job is to feed it crypto journals that are already PCG-aligned and FEC-complete: the right 522X holding accounts, the gas treatment your cabinet has chosen, every required EcritureNum and PieceRef in place, so the entries clear FEC validation the day an audit asks for them. Pennylane has no native notion of a wallet, a token, or a transaction hash, so a subledger always sits between the chain and the platform.
This guide covers exactly that export path: how journals post to Pennylane (REST API or CSV), the PCG sub-account structure for crypto under the French ANC framework, the FEC fields the subledger must populate, the DAC8 reconciliation that reshapes the cabinet workflow from 2026, and how Wag3s Ledger handles Pennylane export for French firms and SMEs. For why Pennylane rather than Sage, see the comparison below; for the cross-ERP posting-feed engineering, see the subledger-to-ERP API integration guide.
What this guide covers
- Pennylane is the system of record; the subledger (Wag3s Ledger or an alternative) is the crypto-aware layer that posts clean PCG-aligned journals to it.
- Posting is API-based (Pennylane's REST API) or CSV import for cabinets that prefer batch review.
- French crypto accounting is governed by ANC Règlement 2018-07 and the ANC Règlement 2026-01 refonte (9 Jan 2026, mandatory FY from 1 Jan 2027). Established sub-account practice: 522X for holdings, 758 for yield income, 678/778 for losses/gains, 6278 for gas.
- FEC export is generated by Pennylane natively when journals carry every required PCG field — the subledger has to populate them at posting.
- DAC8 from 1 January 2026 adds an annual cabinet step: reconciling the Pennylane books against the CASP-reported data the DGFIP receives.
Why Pennylane and not just Sage?
Sage 100 and Pennylane both target the French SME market but with different positioning:
| Dimension | Pennylane | Sage 100 |
|---|---|---|
| Architecture | Cloud-native | Cloud-hybrid (originally desktop) |
| API maturity | High (REST, OAuth 2.0) | Moderate (Web API on Cloud edition) |
| Cabinet workflow | Built for cabinet collaboration with clients | Single-user oriented |
| User onboarding | Modern UI, self-serve | Heavier learning curve |
| Bank feed coverage | Strong (Powens connector for French banks) | Moderate |
| Pricing | SaaS, ~€20-100/month per entity | Per-user licensing |
| Market share (FR SMB 2026) | Fastest-growing | Established |
For new Web3 businesses launching in France in 2026, Pennylane is the more common choice. Established businesses with existing Sage 100 deployments typically stay on Sage.
The crypto subledger integration logic is the same for both, but the API maturity makes Pennylane integration simpler in practice.
The PCG account structure for crypto
Below is the established practitioner sub-account structure under the ANC framework (Règlement 2018-07; refonte via Règlement ANC 2026-01 of 9 January 2026, mandatory for FY opened from 1 January 2027). The recognition and measurement rules are set by the ANC; the specific sub-account numbers are convention. Variations exist; confirm with your cabinet.
| PCG account | Label | Use |
|---|---|---|
| 5221 | Crypto-actifs - Bitcoin | BTC holdings across all wallets |
| 5222 | Crypto-actifs - Ethereum | ETH holdings (mainnet and L2 aggregated or split by chain) |
| 5223 | Crypto-actifs - Stablecoins | USDC, USDT, DAI, EURC, etc. |
| 5224 | Crypto-actifs - Autres tokens | Long tail of ERC-20s, governance tokens |
| 5225 | Crypto-actifs - Positions DeFi | LP tokens, staked positions, LRTs |
| 5226 | Crypto-actifs - NFTs | NFT holdings if material |
| 758 | Produits financiers divers - Rendements crypto | Staking, yield, lending interest |
| 758 | Produits financiers divers - Airdrops | Airdrops, fork receipts (sub-account if material) |
| 778 | Produits exceptionnels sur opérations en capital | Gains réalisés sur cessions crypto |
| 678 | Charges exceptionnelles sur opérations en capital | Pertes réalisées sur cessions crypto |
| 6278 | Autres frais et commissions sur prestations bancaires | Frais de gas (option 1) |
| or 20X / 21X | Immobilisations incorporelles | Gas capitalisé dans le coût d'acquisition de l'actif (option 2) |
The 6278 vs 20X/21X choice for gas treatment is the most contested point. Under the ANC framework the treatment follows the asset's classification and the entity's accounting policy. For Web3 businesses with substantial DeFi activity, capitalizing gas into cost basis (option 2) produces cleaner P&L and more accurate cost basis for disposal computations, but adds operational complexity. Confirm the policy with your expert-comptable in light of ANC 2026-01.
For staking yield, the 758 classification is the practitioner consensus. Some cabinets argue for 7587 (revenus assimilés à des intérêts) as a more precise sub-account, particularly for entity-level treasury yield strategies.
The integration architecture
Wallets & Exchanges
│
▼
Wag3s Ledger (crypto subledger)
│
Daily/monthly summary journals
with PCG-aligned account structure
│
▼
Pennylane (system of record)
│
▼
Cabinet review + FEC export + DGFIP filings
The subledger does the heavy lifting:
- Connects to all wallets (Ethereum and L2s, Solana, Bitcoin) and exchanges (Coinbase, Binance, Kraken, etc.).
- Normalizes each on-chain transaction into one or more accounting events.
- Applies cost basis methodology (PMP is the French default; FIFO available).
- Allocates gas per economic event.
- Classifies events into PCG-aligned categories.
- Produces summary journals (typically monthly) for posting to Pennylane.
Pennylane stores the journals as PCG entries. The cabinet reviews them like any other client books. The FEC export is generated by Pennylane natively when needed for DGFIP filings or audit.
FEC field requirements when posting from the subledger
The FEC (Fichier des Écritures Comptables) is the standardized tax-audit file the DGFIP requires. Every line must have the following fields:
| FEC field | What it means | How the subledger populates it |
|---|---|---|
| JournalCode | Journal code (e.g. "CRYPT" for crypto journal) | Configured per subledger client |
| JournalLib | Journal description | "Journal des opérations crypto" |
| EcritureNum | Sequential entry number | Auto-generated, never reset within fiscal year |
| EcritureDate | Entry date | Date of the on-chain transaction (or month-end if summary) |
| CompteNum | PCG account number | From classification rules |
| CompteLib | PCG account name | Matched to entity's chart of accounts |
| PieceRef | Supporting document reference | Subledger journal ID + on-chain tx hash |
| PieceDate | Document date | Date of the underlying transaction |
| EcritureLib | Entry description | Counterparty + chain + amount |
| Debit, Credit | Amounts in EUR | After PMP cost basis computation |
| Montantdevise | Foreign currency amount | Original asset amount (e.g. 1.5 ETH) |
| Idevise | Foreign currency code | "ETH", "BTC", "USDC", etc. |
| EcritureLet, DateLet | Lettering for reconciliation | Used for matching disposal entries to acquisition lots |
| ValidDate | Validation date | Lock date when journal becomes immutable |
Missing fields at posting time mean a failed FEC validation at audit. Wag3s Ledger's Pennylane connector enforces field completeness before posting; entries that fail validation surface in a review queue rather than being silently truncated.
The DAC8 cabinet workflow in 2026
From 1 January 2026, EU CASPs report aggregate annual transaction data on French residents directly to the DGFIP. The cabinet's role shifts:
Before DAC8:
- Client provides wallet addresses and exchange access.
- Cabinet (or subledger) computes annual gains/yield.
- Cabinet files annual return (2086 personal + corporate FEC).
After DAC8 (from FY 2026, first reports September 2027):
- Same as before, plus:
- Cabinet receives or accesses the DGFIP-side DAC8 data showing the client's CASP-reported activity.
- Cabinet reconciles the Pennylane books against DAC8 data.
- Material discrepancies need investigation: missing wallet, mis-classified counterparty, timing differences. Set the materiality threshold per the cabinet's own documented policy — there is no regulatory figure prescribed for this reconciliation.
- Cabinet documents the reconciliation in the client file.
As a matter of professional diligence, cabinets handling crypto clients should establish a written DAC8 reconciliation procedure. Confirm the current DGFIP guidance and your professional-body obligations — DAC8 cross-checking against client books is the practical expectation once the first FY 2026 data is exchanged (by 30 September 2027).
How Wag3s Ledger handles Pennylane export
Wag3s Ledger is designed for the French market:
- PCG account structure built-in aligned with the ANC framework (Règlement 2018-07 / 2026-01)
- PMP cost basis as default (FIFO available)
- Monthly summary journals posted to Pennylane via REST API
- FEC field completeness validated at posting
- Multi-entity support for cabinets managing multiple crypto clients
- DAC8 aggregation per French-resident user for CASP clients
- Audit trail: every Pennylane entry references the subledger journal ID and the underlying on-chain transaction hash
For cabinets onboarding multiple crypto clients, Wag3s Ledger supports a multi-tenant configuration where the cabinet manages all clients from a single admin panel with per-client billing. The connector keeps the export clean and FEC-ready, but it does not replace the cabinet's review: the PCG sub-account choices, the gas-treatment policy, the cost-basis method, and the DAC8 reconciliation judgement remain the expert-comptable's, applied and documented by Ledger for that review rather than decided in its place.
See the Wag3s Ledger product page for module details and the Wag3s for accountants page for cabinet-specific workflows.
Setup workflow for a French cabinet
Typical timeline for onboarding a crypto client onto Pennylane via Wag3s Ledger:
| Week | Activity |
|---|---|
| 1 | Client wallet/exchange inventory; Pennylane and Wag3s Ledger access setup |
| 2 | PCG chart of accounts validation with the cabinet; cost basis method choice (PMP default) |
| 3 | Historical sync of client wallets to inception of the entity |
| 4 | First test journal posted to Pennylane; cabinet validation of structure |
| 5-6 | Historical entries finalized; first live month-end |
| 7-8 | FEC test export from Pennylane; cabinet validation; DAC8 reconciliation procedure documented |
Realistic timeline accounts for the historical reconciliation phase, which is the most variable. A clean entity with 6 months of activity and 2 wallets clears in 2-3 weeks. A 3-year-old DAO with 15 wallets, 5 chains, and DeFi positions takes 6-8 weeks.
Further reading
- Crypto Subledger to ERP: API, Idempotency, Reconciliation — the posting-feed engineering common to Pennylane and every other system of record
- Crypto-to-ERP Journal Entry Export — the general subledger-to-GL export pattern
- Crypto Accounting Sage Integration — the other French SME option, Sage 100
- Crypto Accounting NetSuite Integration
- Crypto Accounting QuickBooks Integration
- Crypto Accounting Xero Integration
- On-Chain Bookkeeping Basics for Web3 Finance Teams
- Multi-Chain Reconciliation Across 20+ Blockchains
- France Crypto Tax Guide 2026
- DAC8 Compliance Guide 2026
- DAC8 vs CARF Difference
Sources
- Pennylane — API overview and the "Create Ledger Entries via API" guide: the REST endpoints a subledger posts PCG-aligned crypto journals to. Pennylane is the French financial-management platform at pennylane.com.
- Autorité des Normes Comptables — Règlement ANC N°2026-01 du 9 janvier 2026: the French crypto-asset accounting framework (refonte of Règlement 2018-07), mandatory for financial years opened from 1 January 2027, behind the recognition and measurement rules the PCG sub-accounts implement.
- DGFIP — BOFiP-Impôts and Article L. 47 A du LPF: the FEC (Fichier des Écritures Comptables) field specifications Pennylane's export must satisfy.
- Council Directive (EU) 2023/2226 — DAC8: the EU framework requiring CASPs to report client transaction data, behind the 2026 cabinet reconciliation workflow above.
The Rise of Cryptocurrencies: From Speculation to Financial Infrastructure
How cryptocurrencies moved from speculation to real financial infrastructure — stablecoin payments, DAO treasuries, on-chain payroll — and what it means for B2B finance teams in 2026.
USDC vs USDT vs DAI for Corporate Treasury in 2026: Risk, Yield, Compliance and the Stablecoin Choice
How USDC, USDT and DAI compare for corporate treasury operations in 2026: issuer risk, reserve quality, MiCA and GENIUS Act compliance, yield availability, and the practical choice for a Web3 finance team running treasury on stablecoins.
Every chain, integration, and competitor mentioned in this article gets its own page — coverage detail, comparison signals, and the audit trail your finance team needs.
- Integration
Pennylane
PCG-mapped JE sync, Cerfa 2086 pre-fill.
View page - Chain
Ethereum
ERC-20, DeFi, gas, restaking — the largest ecosystem.
View page - Chain
Solana
SPL tokens, native stake, Jupiter, Metaplex NFTs.
View page - Integration
NetSuite integration
Mid-market and enterprise crypto subledger.
View page - Integration
QuickBooks integration
SMB GL with daily JE sync.
View page - Integration
Safe integration
DAO and corporate multi-sig accounting.
View page