Skip to content

French FEC accounting file validator

Pre-check French DGFiP FEC files (Article A.47 A-1 LPF) locally with zero uploads: verify SIREN, columns, dates, and journal balance.

Drop a French {SIREN}FEC{YYYYMMDD}.txt file here

Validates DGFiP Article A.47 A-1 structure, SIREN Luhn checksum, Tab/Pipe delimiter, 18 mandatory columns, YYYYMMDD dates, and Debit = Credit.

Loads a synthetic balanced 732829320FEC20251231.txt ledger.

How to use FEC file checker

  1. Drop your FEC export. Drag a French FEC .txt, .csv, or .tsv file up to 50 MB into the drop zone, or load the built-in 7-line sample file.
  2. Verify filename and format. Check the 9-digit SIREN prefix and YYYYMMDD closing date alongside UTF-8 BOM encoding and delimiter warnings.
  3. Inspect journals and entries. Switch between Validation Checks, Journals, and Entries tabs to inspect unbalanced postings, comma decimals, and PCG classes.
  4. Export audit outputs. Choose Excel Trial Balance and Audit (.xlsx), Normalized DGFiP FEC (.txt), or Validation Issues CSV (.csv) locally.

Everything you type stays in this browser on your device. Nothing is uploaded, and your saved details are never sent anywhere.

French FEC 18 columns, encoding, and delimiter rules

French businesses keeping computerized accounting must deliver a compliant Fichier des Écritures Comptables during a tax audit without exposing sensitive client data to external websites. This browser utility runs an instant DGFiP FEC pre-check on .txt, .csv, and .tsv files up to 50 MB inside a local Web Worker aligned with the DGFiP BOFiP official FEC format doctrine.

Validation check Article A.47 A-1 rule Checker behavior Finding severity
Filename pattern SIRENFECYYYYMMDD Tests 9-digit SIREN Luhn and date Error or warning
Character encoding UTF-8 or ISO 8859 without BOM Flags 0xEF 0xBB 0xBF before JournalCode UTF8_BOM warning
Field delimiter Tabulation or pipe only Rejects commas and semicolons NONCOMPLIANT_DELIMITER
Schema columns 18 ordered BIC/IS or BNC fields Checks count, missing headers, row width Error or casing warn
Dates and decimals YYYYMMDD and comma decimals Parses 0,00 style and detects dots Error or DECIMAL_COMMA

Both the 18-column BIC/IS schema (Debit and Credit) and the 18-column BNC treasury layout (Montant and Sens set to D or C) are checked row by row. You can also verify French SIREN and SIRET Luhn checksums directly when validating counterparty registration numbers alongside your ledger export.

Every row must supply non-blank values for JournalCode, JournalLib, EcritureNum, EcritureDate, CompteNum, CompteLib, PieceRef, PieceDate, EcritureLib, and ValidDate. Auxiliary fields (CompAuxNum, CompAuxLib), letting marks (EcritureLet, DateLet), and currency columns (MontantDevise, Idevise) remain optional and are allowed to be blank without triggering EMPTY_MANDATORY errors.

Mismatched header capitalization triggers a HEADER_CASING warning without halting balance math, whereas rows carrying fewer or more than 18 columns emit ROW_WIDTH errors so analysts can locate shifted fields immediately.

How do debit-credit balance checks and PCG class rules run?

Even when every column header exists in the right order, decimal formatting quirks or missing dates will cause audit software rejections. Our validator converts valid amounts into integer cents immediately upon reading each line so trial balance math stays exact across large ledgers.

Composite JournalCode and EcritureNum balance reconciliation

Because accounting exports often restart sequential entry numbering inside each journal, debit and credit totals are reconciled by pairing JournalCode and EcritureNum as a composite key. Any entry whose debits fail to equal credits triggers an UNBALANCED_ENTRY error, while a mismatch across the entire ledger raises FILE_IMBALANCE in the EUR summary panel.

Multinational finance controllers operating subsidiaries in both France and Germany often inspect statutory trial exports alongside German DATEV EXTF Buchungsstapel validation. Running both format validators locally prevents spreadsheet encoding corruption before closing periods.

Comma decimals, YYYYMMDD dates, and Plan Comptable classes

Amounts must follow strict French non-negative comma decimal syntax (^\d+(?:,\d{1,2})?$) with zero currency signs or thousands separators. Tolerant fallback parsing still computes totals if an export emits decimal dots or trailing characters while raising DECIMAL_COMMA or AMOUNT_FORMAT warnings.

Checking both strict comma rules and fallback values helps accounting teams fix decimal-dot exports or missing YYYYMMDD calendar dates inside ERP settings before generating final statutory deliverables.

Every EcritureDate, PieceDate, ValidDate, and populated DateLet must resolve to an actual YYYYMMDD calendar day, while non-compliant entity prefixes fail against the INSEE official SIREN identifier definition. Account numbers in CompteNum are screened against French Plan Comptable Général root classes 1 through 8 (PCG_ACCOUNT_CLASS warning).

Exporting audit Excel workbooks and normalized DGFiP FEC text

After parsing finishes, sidebar totals summarize line count, unique entry count, total EUR debits, total EUR credits, and unbalanced entry count. Three export modes transform those verified rows into clean spreadsheets or submission-ready text without re-uploading any file.

Four-sheet Excel Balance generale and issue breakdown

Choosing Excel Trial Balance & Audit (.xlsx) writes four structured worksheets: Validation Issues, Journal Summary, Balance generale aggregated per CompteNum with debit, credit, and net EUR balances, and FEC Entries holding up to 5,000 sampled rows. Cross-border reporting teams also connect trial balance outputs with our iXBRL viewer when reconciling annual statements.

Normalized UTF-8 tab-delimited FEC .txt conversion rules

Exporting Normalized DGFiP FEC (UTF-8 Tab .txt) converts comma-separated, semicolon-separated, dot-decimal, or BNC Montant/Sens files into standard 18-column BIC/IS tab-delimited text with CRLF line endings and comma decimals. Embedded tabs and line breaks inside text descriptions become spaces, and leading BOM bytes are omitted per the Unicode UTF-8 Byte Order Mark FAQ.

  • Excel audit workbook (.xlsx): Produces Validation Issues, Journal Summary, Balance generale, and FEC Entries with native numeric amounts.
  • Normalized FEC (.txt): Names files {SIREN}FEC{YYYYMMDD}.txt when metadata is valid, stripping UTF-8 BOMs and normalizing YYYYMMDD dates.
  • Validation Issues (.csv): Exports RFC 4180 CSV issues and journal summaries with UTF-8 BOM and sanitizeCsvTable CWE-1236 formula protection.

Teams preparing CSV audit logs for Microsoft Excel appreciate sanitizeCsvTable prefix neutralization on any cell starting with =, +, -, @, or |. Account numbers and journal codes export as text cells inside Excel so spreadsheet auto-formatting never drops leading zeros on Plan Comptable accounts or zero-padded entry numbers.

Test Compta Demat alignment, 50 MB limits, and audit scope

Browser-based validation lets finance staff test exports on Windows, macOS, or Linux immediately before installing or running official desktop utilities. Reviewing structural flags early saves repeated round-trips with external bookkeeping vendors during statutory closings.

Comparing browser pre-checks against Test Compta Demat

The Validation Checks, Journals, and Entries tabs surface missing columns, header casing mismatches, BOM bytes, delimiter errors, invalid dates, and out-of-balance journals immediately onscreen. For statutory submissions, guidance in the DGFiP BOFiP computerized tax audit procedures confirms that final official formatting verification belongs to DGFiP Test Compta Demat.

Opening the Journals tab ranks each ledger book by line count, unique entry count, total EUR debits, total EUR credits, and net imbalance so teams isolate posting discrepancies without manual sorting.

50 MB upload cap, 300-row previews, and compliance scope

Browser memory limits restrict uploads to 50 MB, cap stored diagnostic lists at 300 issues, store up to 5,000 sampled rows, and preview 300 rows in the HTML UI while keeping processing 100% private offline. International finance teams checking automated payables alongside French ledgers can also review US NACHA ACH batch totals before treasury reconciliation.

Tip: Click Load sample FEC file to load synthetic ledger 732829320FEC20251231.txt. It includes balanced AN, VE, and BQ journals, TVA account 445710, and lettered A1 entries so you can preview Balance generale immediately.

Diagnostic checks and exported workbooks are intended for informational purposes only and do not constitute legal, tax, accounting, or financial advice. French enterprises face strict statutory penalties and 10 years archival rules, so always run final files through DGFiP Test Compta Demat and obtain review from a qualified expert-comptable, chartered accountant, or tax advisor.

Questions

How does the FEC validator check a 9-digit French SIREN filename?

Compliant filenames follow the 9-digit SIREN plus FEC plus YYYYMMDD closing-date pattern before any file extension. The checker validates the 9 digits with the INSEE Modulo-10 Luhn checksum and verifies that the closing date matches a real calendar day, raising warnings if renamed.

What are the 18 mandatory FEC columns for BIC/IS vs BNC accounting?

Standard BIC and corporate IS exports require Debit and Credit columns across an ordered 18-field header from JournalCode through Idevise. BNC treasury ledgers swap Debit and Credit for Montant and Sens with D or C flags while keeping all other 16 columns unchanged.

Why does the checker warn on UTF-8 BOM headers and non-tab delimiters?

Leading EF BB BF UTF-8 Byte Order Mark bytes before JournalCode can confuse strict header checks in DGFiP Test Compta Demat. Allowed field separators are tabulation and pipe characters, whereas commas and semicolons trigger a non-compliant delimiter error during parsing.

How are unbalanced entries grouped by JournalCode and EcritureNum?

Every amount is converted to exact integer cents so floating-point rounding cannot hide a one-cent mismatch. Entries sharing the same JournalCode and EcritureNum key are summed together, flagging each imbalanced entry and reporting any ledger-wide variance between total debits and total credits.

What does the normalized DGFiP FEC export change in the output file?

Normalized FEC export converts valid rows into standard 18-column BIC/IS layout with UTF-8 encoding without a BOM, tabulation separators, CRLF line endings, YYYYMMDD dates, and two-decimal comma amounts. Embedded tabs or line breaks inside labels are replaced by spaces to protect row widths.

Is this browser validator an official substitute for Test Compta Demat?

No. This pre-check catches structural and arithmetic defects offline on macOS, Linux, or Windows before an audit, but official pre-filing verification still requires running DGFiP Test Compta Demat and having an expert-comptable review substantive tax accounting entries.

Updated