Crypto Audit Trail: The Chemin de Révision Web3 Accounting Needs

Accounting has one non-negotiable: every entry traces to its source, and every source to its entries. In traditional books that source is an invoice; in crypto it is a blockchain, and without a deliberately engineered trail the link breaks. This article is about that chemin de révision specifically — what Web3 accounting must build so the trail holds, and why both the FEC and a financial-statement audit fail without it. It underpins the crypto FEC and surfaces in the company tax audit.

What the trail must hold

• The chemin de révision is the unbroken path between an entry and its source, in both directions.
• For crypto, each journal line must tie to a transaction hash and chain, a fiat valuation with its source/market/timestamp, and a wallet, with complete wallet coverage.
• The FEC is the output; the trail is what makes it defensible (see the crypto FEC).
• The same trail underpins the audit's existence assertion and valuation assertion.
• The dominant failure is incomplete wallet coverage: complete in form, empty in substance.
• The trail has to be engineered; it does not exist by default.

What the trail is

The chemin de révision is the requirement that any accounting entry can be traced back to the source that justifies it, and any source traced forward to the entries it produced. It is foundational to French accounting and to any financial-statement audit. It is not a crypto concept; crypto just makes it hard.

Why crypto breaks it

In traditional accounting the source is an invoice or contract. In crypto the source is an on-chain event — and several things break the link unless you engineer it:

• a journal entry with no documented tie to the transaction hash;
• a valuation with no retained source/market/timestamp;
• on-chain activity in wallets nobody mapped — it never reaches the books;
• internal transfers booked as disposals (or vice versa);
• DeFi composition (LP, wrapping, staking) with no decomposition to entries.

Volume and multi-chain activity multiply the breaks. The trail is engineered or absent; there is no default.

What each crypto line must trace to

Both directions must work: from a hash you can find the entries; from an entry you can find the hash and its valuation evidence. Anything less is a broken trail.

One trail, three obligations

The same chemin de révision satisfies three things at once:

• The FEC — a FEC that cannot be traced to on-chain sources is format-valid but fails a vérification (see company tax audit).
• The existence assertion — wallet-to-records linkage is the trail (see existence and ownership).
• The valuation assertion — the per-entry pricing-source evidence is the trail (see auditing fair value).

Build it once; it carries the FEC, the tax audit, and the financial-statement audit.

The two failures that get caught

1. Incomplete wallet coverage — entries are tidy for known wallets while unmapped wallets' activity never enters the books. The trail is complete in form, empty in substance. Detected the instant records are reconciled to the chain.
2. Valuations with no retained source — a price was used; the where and when were not kept. The valuation assertion then has nothing behind it.

Both are reconciliation findings — which is why continuous multi-chain reconciliation is the trail's enforcement mechanism.

Practical guidance

1. Tie every journal line to a transaction hash and chain.
2. Store the valuation source, market, and timestamp with the entry.
3. Maintain a complete wallet inventory — completeness is the trail's hardest part.
4. Classify internal transfers explicitly so they are not mis-booked as disposals.
5. Decompose DeFi events to entries with their on-chain sources.
6. Reconcile to the chain continuously — that is what proves the trail is real.

Where a tool supports the audit trail

Cryptio and Bitwave link journal entries to transaction hashes, retain pricing-source data per entry, and track wallet inventories. Confirm the tool enforces bidirectional traceability (entry to hash and back) and a wallet-completeness reconciliation; a trail is only real if it is complete and reconciled to the chain, not just well-formatted for the wallets you happened to know about.

Where Wag3s fits

Wag3s Ledger ties every entry to its transaction hash and chain, stores the valuation source and timestamp per line, maintains a complete wallet inventory, and reconciles continuously to on-chain activity: one chemin de révision that carries the FEC, the vérification, and the financial-statement audit. The standard your auditor or expert-comptable expects, and the accounting characterisation of each event, are theirs to set; Wag3s engineers and reconciles the trail that meets it. See the Ledger product page and the Wag3s for accountants page.

Further reading

• The FEC for Crypto in France
• Crypto Company Tax Audit (France)
• Auditing Crypto Existence and Ownership
• Auditing Crypto Fair Value
• Proof of Reserves vs a Financial-Statement Audit
• Multi-Chain Reconciliation

Common errors and how they manifest in a vérification

A DGFiP vérification de comptabilité (company tax audit) for a crypto-active entity typically examines three things: completeness, traceability, and consistency. The following are the most common failures the examiner finds.

Missing wallet coverage. The inspectors request a list of all wallets and exchange accounts held or used during the examined period. If the entity provides a list of five wallets but on-chain analysis or CASP-reported data reveals activity in a sixth wallet not in the FEC, the FEC is incomplete in substance even if technically formatted correctly. The examiner can challenge the FEC's regularity, and the entity must either explain the omission or accept an adjustment. The pre-audit procedure should be: enumerate every wallet address the entity controlled, verify each against on-chain history, and reconcile all transactions into the FEC — including wallets used briefly and then abandoned.

Valuations not retained at the transaction level. The examiner asks: for this specific disposal at this timestamp, which price source did you use, which market, and what was the rate? If the accounting system has only the final fiat amount and no attached pricing source, the examiner cannot verify the valuation. The correct setup is to store, per transaction: the on-chain timestamp, the token amount, the price source (CoinGecko, CoinMarketCap, Kraken spot, etc.), the specific market pair used, the rate applied, and the resulting fiat amount. This is the minimum traceability that makes a valuation defensible.

Internal transfers miscoded as disposals. Moving ETH from one company wallet to another company wallet is not a disposal event. If the accounting system treated it as a sale and recognised a gain, the FEC contains a phantom transaction. This inflates revenue and distorts the tax base. Detecting this requires reconciling on-chain transfers against the FEC and verifying that intra-company wallet movements are coded as internal transfers, not sales. If the entity has many wallets, this is a systematic risk.

DeFi events with no decomposition. Adding and removing liquidity from a Uniswap pool creates at least four on-chain events that need individual accounting entries: two deposits (in), an LP token receipt, two withdrawals (out), and an LP token burn. If the entire cycle is recorded as one net transaction, the individual event timestamps, amounts, and valuations are lost and the trail is broken. Each on-chain event should have a corresponding journal entry with its hash and timestamp.

These are not hypothetical failures — they are the findings that practitioners report consistently in digital-asset vérifications. Addressing them before the audit, not during, is the only effective approach.

Sources

• Légifrance — Article A47 A-1 LPF: the FEC format whose validation dates and piece references express the chemin de révision in French accounting.
• BOFiP — Contrôle des comptabilités informatisées : remise du FEC (BOI-CF-IOR-60-40-10): the administration tests the records' traceability to their source.
• AICPA — Accounting for and Auditing of Digital Assets practice aid (non-authoritative): existence and valuation evidence depend on traceable records.
• Reconciliation of records to on-chain activity as the enforcement of traceability.