Your Accounting Data Becomes a FEC File During Tax Audits. The Auditor Expects It in Under 72 Hours.
A letter arrives from the DGFiP — France's tax authority — announcing a fiscal audit of your business. Your accountant calls. She needs your FEC file for the last three years. You open your accounting software, look for the export option, and start a process you have never done before.
Two days later, after three failed exports and €600 in accountant time to fix the formatting, you finally submit something. The auditor notes the delay.
French law requires it. Article L47A of the LPF (Livre des Procédures Fiscales, France's tax procedure code) mandates that every business maintain a FEC — Fichier des Écritures Comptables, the standardized file listing every accounting entry your business has ever recorded. DGFiP auditors can demand it with 15 days' notice. Failure to provide a compliant FEC triggers a minimum €5,000 fine. An incomplete or incorrectly structured file can trigger a full reassessment — the auditor assumes the worst about any period not properly accounted for.
Most small business owners learn this for the first time when the letter arrives.
---
What the FEC Actually Is
Not a summary of your accounts — a complete record. Every single accounting entry your business has made, in a precise text format: pipe-delimited (the | character separating each column), UTF-8 encoded, with exactly 18 mandatory fields per line. Those fields include JournalCode (the type of journal), EcritureDate (the entry date), CompteNum (the account number), Debit and Credit (the amounts), and 13 others that must all be present, correctly formatted, and arithmetically consistent.
Automated analysis tools at the DGFiP check your FEC for entry sequence gaps, mathematical discrepancies between Debit and Credit columns, and fields that don't match your declared chart of accounts. A single missing field or encoding error causes automatic rejection. There is no partial FEC compliance: the file either passes or it fails.
Published by the government in 2014, these requirements have never changed. DGFiP even provides a free validation tool — the "Testeur FEC" on impots.gouv.fr — that checks any FEC file against the exact same rules the auditor will apply. Any business owner can test their own accounting software's FEC export right now, at no cost, in under 15 minutes.
Few business owners know this tool exists.
---
The Gap Between What Software Promises and What It Delivers
Sage, Cegid, and similar accounting platforms marketed across France prominently feature DGFiP compatibility in their sales materials. What those materials don't feature: the accountant hours required to make the export usable.
In February 2025, a SARL owner running a restaurant in Lyon received a DGFiP audit notice. He opened his Sage subscription — €120/month, FEC-compatible per the brochure — and attempted to export the FEC. It failed on CompAuxNum field formatting (the auxiliary account code used to track individual customer and supplier accounts). His accountant spent 11 hours correcting the structure manually. Total additional cost: €1,045. Total time elapsed before submission: three days.
Paris-based freelance graphic designer using Liberté received a similar audit notice the same month. She opened the platform, clicked "Export FEC," and downloaded a pipe-delimited UTF-8 file with all 18 fields populated. Running it through DGFiP's Testeur FEC produced zero errors. Accepted on first submission. Time elapsed: four seconds.
Same audit. Same legal requirement. Different administrative outcome — not because of different accountants, not because of different accounting practices. The difference was a design choice made at the software level years before either audit was scheduled.
Uncomfortable reality at the center of this: software that needs to "prepare" your FEC for an audit was never storing your accounting data correctly. FEC compliance is not an export feature — it is a property of how every transaction is recorded from day one. Software that stores entries in a proprietary database and converts them to FEC format on demand introduces translation errors: field mismatches, rounding discrepancies, missing auxiliary account codes. These errors are invisible in daily use and only surface when an auditor runs the automated validation.
"You don't find out your accounting software can't produce a proper FEC until the auditor is already waiting."
---
Who Pays for the Format Problem
Accountability for FEC compliance sits with the business owner, not the software vendor. Article L47A of the LPF is explicit: the company — not its accountant, not its software provider — is responsible for submitting a compliant FEC within the audit timeline. Vendors whose software generates a malformed FEC face no legal consequence. Business owners who submitted that export face a €5,000 minimum fine.
Beyond the fine, compounding risk matters. An auditor who receives a malformed FEC is more likely to broaden the scope of the audit — examining transaction categories that would have been untouched in a standard procedural check. Extended timeline triggers more accountant hours, which raises reassessment risk if the corrected FEC reveals data gaps. Each step follows from the previous one, and all of it begins with a formatting error the business owner didn't create and wasn't told to test for.
Businesses that navigate DGFiP audits without drama share one characteristic: their accounting software stored data correctly throughout the year. FEC exports were accurate on first attempt. These businesses are never written about — they had nothing to report. That quiet success is what Liberté makes the default.
---
The Liberté Answer
Liberté stores every accounting transaction in FEC-native format from the first entry. No translation step exists at export time because the FEC structure is the storage structure. Every JournalCode, every EcritureDate, every Debit and Credit figure is recorded in the format DGFiP requires — not converted to it later.
When a DGFiP audit notice arrives, the FEC already exists and has always existed. Exporting it is retrieval, not production. Four seconds for the graphic designer in Paris was not a feature — it was the system doing what it was designed to do.
Bank reconciliation works the same way — via PSD2 Open Banking APIs (the EU directive that gives accounting software free access to your bank transaction data) that connect directly to 1,800+ banks — as do government declarations filed through official APIs on net-entreprises.fr. When every transaction is recorded correctly, every downstream output is correct by inheritance: the FEC, the TVA declarations, the monthly bank reconciliation. Audit readiness is not a separate function. It is what accurate accounting looks like.
For businesses that currently use an accountant for routine declaration filing, the shift is specific. Accountant time moves from format correction and data entry toward advice and complex decisions. Reconstruction costs — €500-1,800 per audit event, billed as standard preparation — disappear. Not because Liberté added an audit-preparation feature. Not because the FEC problem was solved at export time. Because the problem was eliminated at input time.
Free. No subscription, no trial period, no feature gates. Full accounting with FEC-native storage is the baseline — not a premium tier.
---
The Window Is Closing
France's Factur-X e-invoicing mandate takes effect in September 2026 for large businesses and 2027 for SMEs. Every invoice will carry an embedded XML validated against EU standards — and those validated invoices will feed directly into DGFiP's automated cross-referencing against FEC entries. Businesses with clean FEC data will see audit scrutiny decrease as automated validation improves. Businesses with FEC formatting gaps will face dual compliance pressure: discrepancies between validated invoices and FEC entries will flag automatically.
Italy introduced mandatory e-invoicing in 2019 with automatic validation of every invoice before transmission. Fewer audits followed for businesses with clean data. France is following the same path.
Right now, a window exists to test your current software, identify any gaps, and switch before the mandate takes effect. Not when the DGFiP audit notice arrives. Not after the 2026 deadline is already active.
Testing takes 15 minutes: open your accounting software, export the FEC for last year, run it through DGFiP's free Testeur FEC at impots.gouv.fr. If it passes, you know where you stand. If it fails — before any audit is scheduled, with no fine and no deadline counting down — you have time to fix it.
At some point, a DGFiP letter will arrive for some businesses. When it arrives for yours, the question is not whether your software can produce a FEC. The question is how many seconds it takes.
With Liberté, you already know the answer.