Crypto accounting software: test the records before choosing a tool
Published 12/12/2024 · Updated 08/09/2026 · Houssen Issouf Aly, French chartered accountant
Crypto-assets · Companies · Directors
Practical guidance for companies and directors. Revised on 7 September 2026.
Choose around the actual accounting file
A tool may import many transactions without producing a usable accounting file on its own. Start with the business’s platforms, wallets, networks, volumes, currencies, entities and evidence. An advertised connector count does not establish historical completeness.
Request a demonstration using a limited representative sample and appropriate access rights. Identify what works, what needs review and what requires correction. A promise to remove all manual work does not define responsibilities.
Build a revealing test sample
Use transactions with independently known outcomes so competing tools can be assessed consistently.
- A purchase funded from the company bank account.
- A transfer between company wallets, including fees.
- A customer receipt linked to an invoice.
- An asset conversion with euro valuation.
- An incomplete transaction needing evidence.
- A reward or protocol interaction where relevant.
- Opening and closing balances that can be independently checked.
Include a genuine difficult case while limiting disclosed data. A demonstration containing only straightforward trades may conceal closing-work requirements.
Follow the data through the workflow
Collection
Check historical coverage, duplicates, connection failures and missing exports. Assign responsibility for monitoring imports.
Classification
Ask how corrections are made, logged and preserved after another import. An internal transfer should not automatically become revenue.
Valuation
Establish price sources, timestamps, currencies, fees and missing-price treatment. The retained result must be explainable.
Output
Test accounting integration, supporting records, entry detail and the ability to move the file to another provider.
A FEC export is not the whole accounting review
The French tax authority publishes FEC format requirements and Test Compta Demat for structural checks. Passing such a check does not alone establish complete transactions or correct accounting treatment. Connect the output to the entity’s complete accounts.
Clarify whether the advertised FEC is crypto-only entries, an intermediate export or the final general-ledger file. Assign checks over integration, accounts, balances and closing adjustments.
Compare total effort and exit options
Compare subscriptions, volumes, networks, users, assistance and correction time. Ask about retention, hosting, access and data recovery. Low subscription cost can be outweighed by repeated manual reconstruction.
Fictional example: two tools import 200 movements. One flags 25 unclassified items; the other classifies everything but misidentifies three internal transfers as sales. The classification percentage alone cannot determine the better choice. Detecting and correcting errors matters as much as automation.
Agree the operating process
Finish the test with an exception list, owners for each check and acceptance criteria. Keep the sample for targeted testing after significant changes.
Are private keys needed?
Collection and reconciliation should use suitable exports and read-only access without transfer authority.
How does the tool fit the accounting engagement?
Our accounting support connects records and controls. Read the wallet guide and ANC 2026 guide, then describe your environment.