FEC Accounting Entries File France 2026: Legal Requirements, Structure and Penalties

The fichier des écritures comptables is the standardised export of a company's accounting records, which the French tax authority may demand on day one of an audit (article L. 47 A, I, of the Tax Procedure Code). Its format comes from article A. 47 A-1: 18 fields for commercial accounting. Failure to produce it costs EUR 5,000, once per audit and not per financial year (article 1729 D of the Tax Code).

Up to date as of 15 May 2026.

The Fichier des Ecritures Comptables (FEC) is France's standardised, timestamped export of a company's entire accounting ledger, delivered in a structured text format. The DGFiP (French tax authority) may demand it on day one of any tax audit. A missing or non-compliant FEC triggers a penalty of 5,000 euros under article 1729 D of the French Tax Code, applicable once per audit whatever the number of years reviewed, or a 10% surcharge on reassessed tax if that amount is higher. Since the arrêté of 29 July 2013, the format is fully standardised: 18 mandatory columns for commercial accounting, ASCII, ISO 8859-15 or UTF-8 encoding, tab or pipe delimitation. In 2026, the FEC coexists alongside mandatory e-invoicing and remains one of the 10 checkpoints in the voluntary Examen de Conformite Fiscale (ECF) programme.

Article L47 A of the Livre des Procedures Fiscales#

The obligation to provide a FEC is embedded in Article L47 A of the LPF. Any company subject to a comptabilite informatisee (computerised accounting) verification must hand over the file to the auditor on the very first day of the tax inspection. There is no grace period. This requirement makes it essential to produce and test the FEC long before any audit procedure begins.

The Arrete of 29 July 2013#

This ministerial order fixes the exact content, structure, and encoding of the FEC. It has since been supplemented by administrative commentary published in BOFiP (BOI-CF-PGR-60-40). Every serious accounting software package has natively respected this format since 2014. Companies still using Excel or outdated software must independently verify that their exports comply.

Code de Commerce : Article L123-12#

The obligation to maintain regular, sincere accounts giving a true and fair view is established by French commercial law. The FEC is not an obligation of bookkeeping but an obligation of communication: it materialises the accounting records in a format that the tax authority's analytical tools can process.

The table below lists all 18 columns required by the arrete of 29 July 2013. The order, exact column name, and field format are standardised. Any missing or incorrectly named column renders the file technically non-compliant.

File format: tab-separated (TSV) or pipe-delimited text. Article A. 47 A-1 accepts three character sets: ASCII, ISO 8859-15 or Unicode UTF-8. The filename follows the SirenFECAAAAMMJJ convention, that is the Siren, the letters FEC, then the closing date: for example 123456789FEC20261231.

The FEC obligation applies to all entities subject to corporate income tax (IS) or reporting BIC (commercial profits), BA (agricultural profits), or BNC (non-commercial profits) under the controlled declaration regime, provided they maintain computerised accounting.

Excluded: micro-entrepreneurs under the micro-BIC or micro-BNC regime (not required to keep double-entry accounting), unless they have opted for a real-profit regime.

Edge cases: SCIs subject to IS, LMNP landlords under the real regime, associations subject to statutory audit, and liberal professions operating through a SELARL or SELAS all fall within scope. The practical test is straightforward: if you file a tax return, you produce a FEC. Watch the field count, however, as it depends on how the books are kept: 18 for commercial accounting, 22 for BNC professionals on a cash basis (the 18 plus DateRglt, ModeRglt, NatOp and IdClient) and 21 for farmers on a cash basis. A 2035 filer producing an 18-column file submits a non-compliant FEC.

During an audit, DGFiP agents run the FEC through analytical software (ACL Audit Analytics, IDEA, Alteryx) to automatically test compliance. The main checks include:

1. Presence of all 18 columns in the correct order with exact names
2. Debit equals credit within each accounting entry (double-entry balance)
3. Continuous entry numbering (EcritureNum with no gaps or duplicates)
4. No duplicates on the EcritureNum + JournalCode combination
5. PCG-compliant account codes (numbers starting 1 through 7)
6. Correct date format YYYYMMDD (using DD/MM/YYYY is the most frequent error)
7. UTF-8 encoding verified via French accented characters
8. Positive amounts only for both debit and credit fields
9. Comma as decimal separator (not a period)
10. Auxiliary accounts consistent with the corresponding parent accounts (4011, 4111, etc.)
11. ValidDate populated and after EcritureDate
12. PieceRef not empty for invoicing entries
13. Journals consistent with the nature of operations recorded
14. Closing balance equals opening balance of the following fiscal year
15. Consistent reconciliation between payments and invoices
16. No illegal characters in labels (stray tabs, embedded line breaks)
17. Coverage spans the entire fiscal year under review
18. Overall debit and credit totals balanced across the entire file

The article 1729 D penalty: EUR 5,000 per audit#

Article 1729 D of the French Tax Code imposes a penalty of EUR 5,000 when the FEC is not submitted or is submitted in a non-compliant format. Contrary to a common belief it is not charged per year: the official guidance states that it applies only once per audit, whatever the number of years reviewed. Article L74 of the Tax Procedure Code, sometimes cited on this point, governs assessment by default where a taxpayer obstructs an audit and imposes no penalty at all.

The 10% Surcharge#

Where the tax reassessment exceeds a defined threshold (to confirm under current LPF provisions), a 10% surcharge on reassessed amounts may apply in place of the flat-rate penalty if it yields a higher figure. The tax authority selects whichever option is more favourable to it.

Assessment by Default#

When no FEC is provided or when the accounting is judged unreliable, the administration may discard the accounts entirely and reconstruct taxable profit using its own methods. Article L66, which belongs to the Tax Procedure Code and not to the Tax Code, covers assessment by default where returns are missing or late: it is not the basis for reconstruction after accounts are rejected. This is the most severe practical consequence, as it reverses the burden of proof: the company must demonstrate that the reconstruction is excessive.

The formal procedure under the LPF works as follows:

1. Notice of verification sent by registered letter. Article L47 of the Tax Procedure Code sets no fixed number of days but a reasonable period allowing the taxpayer to seek advice: practice points to around three weeks, and case law to a minimum of two clear days.
2. FEC submission on day one of the verification, on a digital medium (USB drive or secure transfer).
3. Analysis at DGFiP offices using ACL, IDEA, or Alteryx: cross-checks between the FEC, VAT returns, DSN payroll declarations, and potentially bank statements.
4. Exchanges with the company on detected anomalies.
5. Proposed reassessments if non-compliance is found, with a 30-day response window.

Our view: the period between the audit notice and the first visit is not fixed by the text, and nothing guarantees it will exceed a few weeks. That is a short window to produce a FEC whose compliance has never been tested. The difficulty concentrates on companies that have never exported their file outside a live audit. A preventive annual FEC audit, distinct from the ECF, removes that risk.

The Examen de Conformite Fiscale (ECF)#

The ECF is a voluntary programme in which a trusted third party (chartered accountant or statutory auditor) certifies compliance with 10 fiscal checkpoints, including the FEC. Signing an ECF reduces, but does not eliminate, the risk of reassessment on certified points. Key caution: the ECF certifies FEC compliance at a specific date. If the accounting software changes or a prior-year entry is restated after signature, the FEC must be re-tested.

E-Invoicing 2026#

Ordonnance 2021-1190 and its implementing texts introduce mandatory electronic invoicing through an approved platform (PA, formerly PDP). The public portal is no longer an invoice exchange channel: its role has been narrowed to the directory and to transmitting data to the tax authority. This framework governs invoice flows between VAT-registered businesses. It does not replace the FEC: both obligations coexist. In practice, invoices received via a PDP continue to feed the accounting software, which continues to produce the FEC on export.

Practical Articulation#

A tax audit in 2027 covering the 2026 fiscal year will still rely on the 2026 FEC, regardless of whether invoices were issued electronically. E-invoicing improves traceability but does not reduce the FEC obligation.

Our recommendation: regardless of software, export the FEC at least once a year, run it through a compliance-testing tool, and keep a record of each test. An untested FEC is not a reliable FEC.

An IT services SME (10 employees, IS, year-end 31 December) engaged us for a preventive FEC audit ahead of a statutory auditor change. The company had been using Sage 100 for eight years.

Anomalies detected during the 18-point review:

1. Incorrect date format: the Sage export profile was set to DD/MM/YYYY instead of YYYYMMDD. All dates in the FEC were unreadable by DGFiP tools. Fix: reconfigure the export profile.

2. Discontinuous numbering: a journal purge performed in year N-2 had deleted reversal entries, creating a 47-line gap in EcritureNum. Without correcting the source accounting, this gap required documented explanation.

3. Non-UTF-8 encoding: labels containing typographic apostrophes and em-dashes were not encoded in UTF-8. The file displayed correctly in Excel but was rejected by the DGFiP validation tool.

Takeaway: all three anomalies are fixable in a few hours once identified. Left uncorrected, they would have rendered the FEC non-compliant in a live audit. The cost of a preventive audit is trivial compared to the article 1729 D penalty and, above all, to the risk of having the accounts rejected.

Most Frequent Mistakes#

• Date format DD/MM/YYYY instead of YYYYMMDD: the number-one error, usually a misconfigured export setting
• Encoding outside the three accepted sets (ASCII, ISO 8859-15, UTF-8), typically Windows-1252: French accented characters become corrupted
• Period as decimal separator instead of comma: incompatible with the French norm
• Empty CompAuxNum and CompAuxLib columns when auxiliary accounts exist: supplier and customer ledgers must be detailed
• Non-sequential numbering after a migration or corrective period close
• Partial FEC that does not cover the full fiscal year

2026 Best Practices#

• Annual FEC audit after each year-end close and before any procedure (ECF, statutory audit, M&A due diligence)
• Retain the FEC for at least 6 years (LPF art. L102 B) : in practice 10 years for fiscally significant years
• Re-test after every software update: updates sometimes alter export profiles silently
• Name the file according to the convention: SirenFECAAAAMMJJ, for example 123456789FEC20261231
• Document known anomalies: if a numbering gap is unavoidable, a written memo in the working file provides protection in a live audit

The vast majority of French SMEs never test their FEC between two tax audits. They assume that a certified accounting software automatically produces a compliant file. This is generally true at installation, but a modified export parameter, a version migration, or a system codec change can silently render the FEC non-compliant : with no error message. The risk does not lie in the accounting records themselves, but in the technical layer between the accounting system and the export function.

During a verification, auditors typically focus on:

• Consistency between FEC and VAT returns: total VAT collected accounts must match CA3 or CA12 filings
• Unusually high expense accounts relative to sector benchmarks
• Payments with no document reference (empty PieceRef)
• Year-end entries (provisions, accruals) whose economic substance may be challenged
• Transactions with related parties (suppliers or customers linked to the directors)

• FEC exported and tested for the current year and the two prior years
• All 18 columns present, in the correct order, with exact column names
• Date format is YYYYMMDD throughout
• Encoding is one of the three accepted sets, ASCII, ISO 8859-15 or UTF-8 (verify using Notepad++ > Encoding menu or a hex editor)
• Decimal separator is a comma
• Entry numbering is continuous with no gaps or duplicates
• Auxiliary accounts populated for all counterparties
• Total debit equals total credit across the entire file
• File named according to the SirenFECAAAAMMJJ convention
• Written memo included for any known, uncorrectable anomaly

At Hayot Expertise in Paris, FEC compliance auditing is integrated into our annual statutory review mission for IS and BIC/BNC (real regime) clients. We produce and test the FEC after each year-end close, ahead of any ECF or statutory audit engagement. If you have never tested your FEC or have recently migrated to a new accounting system, contact us for a diagnostic review.

This article provides general information only. It does not replace a review of your specific situation, your fiscal years, your accounting software configuration, and the regulations in force at the date of any audit. Consult a chartered accountant before making any decision.

Sources: LPF art. L47 A, L47, L102 B and arrêté A. 47 A-1 (Legifrance) ; French Tax Code art. 1729 D (Legifrance) ; BOFiP BOI-CF-IOR-60-40-10 ; Code de commerce art. L123-12 (Legifrance) ; impots.gouv.fr/fec.