Crypto Accounting Pennylane Export

Pennylane is the fastest-growing French accounting platform for SMEs and accounting firms. It handles PCG, FEC export, multi-entity bookkeeping, and the workflow expectations of French expert-comptables. What it does not do natively is crypto. For Web3 startups and businesses with on-chain activity, the question is how to feed clean PCG-aligned crypto journals into Pennylane so the cabinet review can run normally.

This guide covers the integration pattern, the PCG account structure for crypto, the FEC compliance requirements, the DAC8 implications for French cabinets in 2026, and how Wag3s Ledger handles Pennylane export specifically.

TL;DR

• Pennylane is the system of record. The subledger (Wag3s Ledger or alternative) is the crypto-aware layer that posts clean journals to Pennylane.
• Posting can be API-based (Pennylane REST API, supported by Wag3s) or CSV import (for cabinets preferring 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 ≥ 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 are correctly structured. The subledger must populate all required PCG fields.
• DAC8 from 1 January 2026 changes the cabinet workflow — reconciliation of Pennylane books against DAC8-reported data is the new annual procedure.

Why Pennylane and not just Sage?

Sage 100 and Pennylane both target the French SME market but with different positioning:

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.

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:

1. Connects to all wallets (Ethereum and L2s, Solana, Bitcoin) and exchanges (Coinbase, Binance, Kraken, etc.).
2. Normalizes each on-chain transaction into one or more accounting events.
3. Applies cost basis methodology (PMP is the French default; FIFO available).
4. Allocates gas per economic event.
5. Classifies events into PCG-aligned categories.
6. 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:

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:

1. Client provides wallet addresses and exchange access.
2. Cabinet (or subledger) computes annual gains/yield.
3. Cabinet files annual return (2086 personal + corporate FEC).

After DAC8 (from FY 2026, first reports September 2027):

1. Same as before, plus:
2. Cabinet receives or accesses the DGFIP-side DAC8 data showing the client's CASP-reported activity.
3. Cabinet reconciles the Pennylane books against DAC8 data.
4. 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.
5. 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.

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:

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 Accounting NetSuite Integration
• Crypto Accounting QuickBooks Integration
• Crypto Accounting Xero Integration
• Crypto Accounting Sage 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 Developer Documentation — Public API
• Autorité des Normes Comptables — Règlement ANC 2018-07 and Règlement ANC N°2026-01 du 9 janvier 2026 (crypto-asset accounting framework)
• DGFIP — BOFiP-Impôts (consult current guidance on crypto reporting and DAC8)
• Council Directive (EU) 2023/2226 — DAC8 text
• BOFiP FEC specifications — Article L. 47 A du LPF