The FEC in France: a Legal Obligation with Serious Financial Consequences
Index 
Since January 1, 2014, any company keeping computerized accounting records and subject to a tax audit must be able to provide the auditor with a copy of its accounting entries in a standardized digital format: the fichier des écritures comptables, better known by its acronym, the FEC. What could have looked like a mere technical formality has proven, over time, to be one of the most closely scrutinized points during a tax audit, and one of the few purely formal defects capable, on its own, of triggering a financial penalty independent of any tax reassessment.
Legal basis
The obligation stems from paragraph I of article L. 47 A of the French Tax Procedures Code (LPF), introduced by article 14 of the amending finance law n° 2012-1510 of December 29, 2012. The law requires taxpayers, whenever their accounting is kept through computerized systems, to satisfy their obligation to produce records by handing the auditor, in digital form, a copy of the relevant files. The technical standards the file must meet are set out separately in article A. 47 A-1 of the LPF, resulting from the decree of July 29, 2013. The whole framework is explained in detail by the tax administration in two reference documents of the Bulletin officiel des finances publiques, BOI-CF-IOR-60-40-10 for the obligation itself and BOI-CF-IOR-60-40-20 for the file standards, supplemented by a questions-and-answers document published on impots.gouv.fr that clarifies several points of practical application.
The obligation applies to entities subject to a legal duty to present accounting records (companies liable for corporate income tax, businesses taxed under the industrial and commercial, non-commercial, or agricultural regimes on an actual-profit basis), provided they keep computerized accounts. The administration allows tolerances for certain structures, notably purely real-estate civil companies held by individuals, and micro-entrepreneurs. French branches of foreign companies, by contrast, remain fully subject to the obligation.
When and how the file must be handed over
The FEC must be handed over as soon as the auditor's first on-site visit takes place, for each of the fiscal years covered by the audit notice. This handover is recorded in a written document countersigned by the taxpayer, which certifies whether the files were handed over, not handed over, or found non-compliant. This procedural point is not incidental: it directly conditions a benefit for the company, the suspension of the three-month time limit set by article L. 52 of the LPF for on-site audits of small businesses. This time limit only starts running again once compliant files have been handed over for all the fiscal years under audit. Compliance for a single fiscal year out of several is not enough to trigger the suspension.
The file format
Taxpayers may choose between two technical formats: a flat file, in text or CSV form, with a sequential organization and a zoned structure, or a structured file in XML format conforming to the schemas published on impots.gouv.fr. In practice, the flat-file format dominates usage by far. It relies on a single separator, the vertical bar, and on eighteen mandatory fields whose names must appear on the file's first line. Its absence alone renders the file non-compliant. Each field corresponds to a precise piece of information about the accounting entry: identification of the journal and the entry, of the general account and, where applicable, of the subsidiary account, reference and date of the supporting document, description, debit and credit amounts, matching reference and date, entry validation date, and finally the amount and currency for transactions in foreign currency.
One rule deserves particular attention, as it is a frequent source of errors: for the six fields classified as conditional (the subsidiary account, the matching reference, the currency), the column must always remain present in the file structure, only its value may stay empty when the company does not use subsidiary accounting, matching, or foreign-currency transactions. Filling these cells by default with a zero or a blank space renders the file non-compliant just as a missing column would. The file name itself follows a strict naming convention, SirenFECAAAAMMJJ, where the date corresponds to the fiscal year-end. In case of large volumes, splitting the file into several parts is allowed, but only by period, monthly or quarterly, and never by entry type, with each resulting file required to repeat its own header line.
The FEC is not self-sufficient. Any internal coding used by the company (journal codes, currency codes, conventional values used for entries without a supporting document, numbering method adopted) must be explained in an accompanying description filed together with the file. This document, whose format is unrestricted, is not subject to any technical standard, but its absence alone constitutes a compliance defect, regardless of the quality of the file itself.
Risks incurred
The penalty attached to this requirement is set out in article 1729 D of the French General Tax Code. It applies equally to a total failure to hand over the file and to the handover of a file that does not meet the standards of article A. 47 A-1 of the LPF. A technically unusable file amounts, from this standpoint, to no file at all. The amount of the fine, increased by the amending finance law of August 8, 2014, stands at 5,000 euros per fiscal year under audit. Where the audit results in a reassessment, the fine is raised to 5,000 euros or 10% of the additional tax due, whichever is higher. On an audit covering several fiscal years, each fiscal year for which the file is missing or non-compliant gives rise to a separate fine.
Beyond this financial penalty, article L. 74 of the LPF provides for an even heavier consequence: failure to comply with the obligation to produce the FEC allows the administration to assess the taxpayer's tax base unilaterally, that is, to bypass the normal adversarial procedure and set the taxable amounts itself. This power, available for audits initiated since January 1, 2014, places FEC compliance among the most sensitive formal issues in a tax audit.
What the DGFiP questions-and-answers document clarifies
The questions-and-answers document published by the administration provides several useful clarifications in practice. Gaps in the entry numbering sequence are tolerated when they result from the draft-mode operation of the accounting software, without requiring renumbering. Files must not be transmitted compressed by default, although compression remains acceptable on request. Since fiscal years closed in 2015, accounting must be kept in French according to French accounting standards, which excludes journal or account descriptions written in a foreign language for French subsidiaries of international groups. No volume, however large, justifies the administration rejecting the file.
This double architecture, a precise legal obligation and dissuasive penalties on one side, detailed technical standards down to the smallest field on the other, explains why generating the FEC cannot be treated as a simple data export. The next article in this series looks at how Microsoft Dynamics 365 Business Central structures this process, from the module's architecture to the extensions dedicated to France.
Sources
BOI-CF-IOR-60-40-10, obligation to present accounting records in digital form: https://bofip.impots.gouv.fr/bofip/9026-PGP.html/identifiant%3DBOI-CF-IOR-60-40-10-20170607
BOI-CF-IOR-60-40-20, file standards for accounting entries: https://bofip.impots.gouv.fr/bofip/9028-PGP.html/identifiant%3DBOI-CF-IOR-60-40-20-20170607
DGFiP, questions and answers on computerized accounting: https://www.impots.gouv.fr/1metier2professionnelcomptabiliteinformatiseequestionreponsepdf
Article 1729 D of the CGI, Légifrance: https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000033815103
No comments yet.