Non-Compliant FEC: The Costly Rejection of Your Accounts

Quick answer. A non-compliant FEC exposes you to two distinct risks: a 5,000 euro penalty under article 1729 D of the French Tax Code for failure to produce the file or for a non-compliant format, and, more importantly, if the anomalies are serious, the rejection of your accounts. This rejection allows the tax authority to reconstruct your turnover and taxable income using its own methods, which almost always costs far more than the penalty.

The FEC (Fichier des Ecritures Comptables, the accounting entries file) is the first document a tax inspector requests. For many business owners it stays abstract until an audit is announced. The problem: once the audit notice arrives, it is too late to fix a poorly configured file. Everything is decided upstream, in day-to-day bookkeeping.

The FEC is the standardised export of all your accounting entries, in a format imposed by the tax authority. The obligation to produce it is set out in article L47 A of the French Tax Procedures Code for any business keeping its accounts through computerised systems, which today covers almost every structure.

The format is strict: a flat file, eighteen mandatory fields, a precise order, sequencing and totalling rules. For the technical detail, we documented it in our article on the format and mandatory fields of the FEC.

During an audit, the FEC serves as the foundation. The inspector imports it into analysis tools, cross-checks the totals against your returns, tests the chronological sequence, spots numbering gaps, back-dated entries or inconsistent balances. A clean file closes the door on part of the suspicion. A flawed file opens an investigation.

You must clearly distinguish two consequences, because they are not triggered at the same threshold.

The 5,000 euro penalty (article 1729 D of the French Tax Code)#

Article 1729 D of the French Tax Code provides for a 5,000 euro penalty in the event of failure to produce the FEC or production in a format that does not comply with the standards set by the tax authority. This article was created by Law no. 2012-1510 of 29 December 2012 (the amending finance law for 2012). The penalty applies to audits whose verification notice is sent on or after 1 January 2014, according to the administrative doctrine (BOI-CF-IOR-60-40-10, paragraph 20).

This penalty is fixed for small structures, but it can be increased. Above all, it is only the visible part: it sanctions the container, not the substance.

Rejection of the accounts#

Rejection of the accounts is of a different nature. When the irregularities are serious enough, the tax authority considers that your accounting no longer has evidential value. It can then set the accounts aside and reconstruct your taxable bases by its own means: margin coefficients, sector ratios, analysis of bank accounts, cross-checks with suppliers.

Rejection of the accounts is not automatic. According to the administrative doctrine (BOI-CF-IOR-10-20), it is assessed with discernment, in light of the extent and seriousness of the failings observed. A slightly imperfect format does not on its own justify rejection; however, non-chronological entries, missing supporting documents, implausible balances or an unusable file change the picture.

In the files we support, the most costly mistake is never the format itself: a poorly formatted file can be regenerated. What hurts is the gap between the FEC and the declared reality. A business owner who kept the accounts hastily, mixed up accounts, omitted revenue or piled up undocumented manual entries starts at a disadvantage. The inspector is not criticising a semicolon, but a broken chain of evidence.

Our recommendation fits in one sentence: a compliant FEC is built at source, in the software and in disciplined data entry, not the day before the audit.

The risk business owners see the least is extrapolated reconstruction. When the tax authority rejects accounting, it does not merely correct the proven anomalies: it reconstructs the entire income on a reconstructed, often unfavourable, basis, and it is then up to the company to show that the method is excessive. The burden of proof shifts. You move from a position where the authority must prove, to a position where you must defend yourself against an estimate. This reversal is what makes rejection so serious.

Two legitimate approaches coexist when you want to make your file reliable.

The first relies on the built-in controls of modern software. Most tools on the market, such as a piece of accounting software that generates a compliant FEC, automatically produce a correctly formatted file and flag sequence breaks. This approach is enough for a simple, up-to-date structure with no complex manual entries.

The second is to have the FEC audited by a professional, simulating the tests the tax authority runs. This is the option to favour as soon as there are stakes: a cash-heavy restaurant, multi-flow e-commerce, a holding with intra-group transactions, or simply an uneven entry history. The cost of a diagnostic is incomparable with that of a reconstruction.

The right trade-off depends on the level of sector risk and the cleanliness of your bookkeeping. For sensitive activities, for example restaurant accounting, preventive auditing is not a luxury.

Here is the sequence we apply in our accounting and review engagements in Paris.

1. Extract the FEC for the closed financial year from your software, in the standardised format (flat file, compliant encoding and separator).
2. Check technical compliance: presence of the eighteen fields, order, absence of forbidden characters, balanced debit and credit totals.
3. Check the chronological sequence: continuous numbering per journal, consistent entry dates, no back-dating.
4. Cross-check against the returns: the turnover in the FEC must match the VAT returns and the tax bundle; any gap must be explained.
5. Test the justification of sensitive entries: manual entries, closing journal entries, shareholder current accounts, inventory operations.
6. Document the grey areas: keep the supporting documents and explain adjustments in writing, so you can respond quickly if a point is raised.

• Does my software generate a standardised-format FEC with no manual handling?
• Are my entry numbers continuous, with no gap or duplicate?
• Does the total of debits equal the total of credits across the whole file?
• Does the turnover in the FEC match my VAT returns and my tax bundle?
• Are all my manual entries backed by a supporting document?
• Have I avoided back-dated entries and untraced corrections?
• For a cash activity, is my revenue recorded day by day?

Some situations call for heightened vigilance. Cash-heavy activities (restaurants, retail) are scrutinised on the regularity of revenue recording. Year-end rebates and supplier credit notes, if poorly recorded, distort the general ledger: we covered the topic in our article on recording rebates without distorting the general ledger. Finally, automating data entry, including through AI applied to accounting, improves regularity but does not replace consistency checks: a generated file remains your responsibility.

• The FEC is the first document requested during an audit; its compliance shapes the rest of the inspection.
• The penalty under article 1729 D of the French Tax Code is 5,000 euros for failure to produce or for a non-compliant format; it applies to audits whose notice is sent on or after 1 January 2014.
• The real danger is not the penalty but the rejection of accounts, which opens the way to income reconstruction.
• Rejection is assessed with discernment, in light of the extent and seriousness of the failings (BOI-CF-IOR-10-20).
• A compliant FEC is built at source, through disciplined data entry and suitable software, not the day before the audit.
• Preventive auditing of the FEC pays off as soon as there is sector risk or an uneven entry history.