01The legal format, column by column
The FEC has 18 columns in a fixed order: JournalCode, JournalLib, EcritureNum, EcritureDate, CompteNum, CompteLib, CompAuxNum, CompAuxLib, PieceRef, PieceDate, EcritureLib, Debit, Credit, EcritureLet, DateLet, ValidDate, Montantdevise, Idevise. Pipe or tab separator, comma decimals, YYYYMMDD dates.
The filename itself is standardized: SIREN + FEC + closing date, for example 123456789FEC20261231.txt. A detail that fails many exports: the file must not start with a BOM (encoding marker); the administration's test tool rejects it.
02Lettrage and PieceDate: the columns sloppy exports skip
EcritureLet and DateLet trace lettrage: which entries settle each other (invoice and payment). A FEC without lettrage is not invalid per se, but it triggers questions: how do you justify your receivables and payables?
PieceDate is the supporting document's date, distinct from the entry date. Many exports copy EcritureDate because the real document date was never stored; during an audit, invoice-entry consistency becomes unverifiable. Check your tool stores and exports both dates.
03Test before being audited
The good reflex: generate a test FEC at every year-end close and run it through the administration's test tool (Test Compta Demat). Rejections are fixed calmly offline, not under audit deadlines.
In Procura, the FEC exports in one click from the accounting module in the exact DGFiP format: 18 columns, automatic SIREN filename, no BOM, lettrage and PieceDate filled from the books. Since accounting is fed by the purchasing cycle (invoices matched to their POs), every entry has its document, and every document its date.