The French statutory tax return package (liasse fiscale) is one of the most costly blind spots in ERP projects deployed in France. Companies invest months configuring general accounting, cost accounting, and treasury management in their ERP — only to discover at year-end close that producing the DGFiP-mandated regulatory forms and transmitting them electronically via EDI-TDFC requires a separate tool, an external accountant, or time-consuming Excel exports. The result: a process that remains largely manual in an area where automation is entirely achievable.
This guide is written for CFOs, financial controllers, and CIOs at mid-market companies operating in France who want to understand what their ERP can realistically deliver for French tax compliance, how to handle group fiscal integration (intégration fiscale de groupe), and which tools can close the final gap in the compliance chain.
French Tax Filing and Your ERP: Why the Connection Is Still Often Manual
ERPs Excel at Accounting — But Tax Compliance Remains a Blind Spot
A modern ERP handles general accounting natively: the French general chart of accounts (PCG), journal entries, account reconciliation, bank matching, statutory audit file (FEC) generation, and monthly close. These are well-mastered core functions.
Regulatory tax compliance is a different discipline. The French statutory tax return requires transforming accounting balances into standardised forms defined by the DGFiP (the French tax authority), applying specific tax adjustments (non-deductible provisions, accelerated depreciation, various add-backs), and producing a file compliant with the current TDFC format. This mechanics demands a detailed knowledge of French tax law (CGI) and the official tax doctrine (BOFIP) — not standard double-entry bookkeeping.
International and generalist ERP vendors typically delegate this work to specialist partners or add-on modules. French mid-market publishers have invested more heavily to embed this workflow natively.
The 3 Operating Models Seen in Mid-Market Companies and Corporate Groups
Model 1: All-in-one ERP with native tax module. The ERP produces the full statutory return directly via an EDI-TDFC-certified module. This model offers maximum traceability because accounting and tax share the same database. Sage FRP 1000 and Cegid XRP are the standard references for this approach in France.
Model 2: ERP + dedicated tax software, integrated. The ERP exports a structured file (FEC, XML, proprietary format) to a specialist tax application that produces and transmits the filing. This model is common for SAP S/4HANA and Microsoft Dynamics 365, whose global architecture does not natively cover French statutory forms.
Model 3: ERP + manual export + external accountant. Still the most common setup in smaller mid-market companies: the accountant extracts data from the ERP, processes it in their own tool, and files on behalf of the company. This model works but creates dependency and reduces responsiveness in the event of a DGFiP audit.
What the French Tax Return Requires from Your ERP
The Cerfa Forms 2050 to 2059: Balance Sheet, Income Statement, Annexes
The French statutory tax return for a company subject to corporate income tax (impôt sur les sociétés, IS) under the standard regime comprises a set of normalised forms, the principal ones being:
| Form | Content |
|---|---|
| 2050 | Balance sheet — assets (fixed assets, current assets) |
| 2051 | Balance sheet — liabilities (equity, provisions, debt) |
| 2052 | Income statement (expenses by nature) |
| 2053 | Income statement (continued, income) |
| 2054 | Fixed assets schedule |
| 2055 | Depreciation schedule |
| 2056 | Provisions schedule |
| 2057 | Subsidiaries and investments |
| 2058 A | Tax profit calculation (reconciliation from accounting profit to taxable profit) |
| 2058 B | Carry-forward losses and capital losses |
| 2059 | Items subject to special tax regimes |
Each line of these forms draws directly from account balances in your ERP. If the chart of accounts does not conform to the PCG or if cost centres are misconfigured, the amounts will be wrong and the return will need manual correction.
Carry-Forward Losses and Group Fiscal Integration (Form 2065)
The corporate income tax declaration (form 2065) is the pivot document summarising taxable profit, tax due, instalments paid, and the balance payable. For groups under the French group tax relief regime (intégration fiscale), it is supplemented by consolidation forms for the parent and subsidiaries (2065-bis and forms 2058 ER/ES/PAP).
The French group fiscal integration regime is available to groups in which the parent holds at least 95% of the share capital of each subsidiary member, directly or indirectly, under Article 223 A of the CGI (BOFIP BOI-IS-GPE-10-20-10). This regime allows the group’s profits and losses to be consolidated, with a single IS calculated at the level of the group head.
Accounting-to-Tax Reconciliation: Permanent and Temporary Differences
The transition from accounting profit to taxable profit (form 2058 A) is the centrepiece of the tax return. It distinguishes two types of differences:
- Permanent differences: expenses that are permanently non-deductible (fines, penalties, executive compensation exceeding certain caps, the 5% add-back on dividends under the parent-subsidiary regime).
- Temporary differences: timing mismatches between periods (provisions recorded but not yet deductible, accelerated depreciation, spread-out capital gains).
These adjustments require the ERP to be configured to tag each expense or income item according to its tax treatment. Without this granularity, reconciliation cannot be automated.
How Leading ERPs Handle French Statutory Tax Filing
SAP S/4HANA with Specialist Partners
SAP S/4HANA includes global tax compliance capabilities (SAP Tax Compliance) for anomaly detection and cross-border obligation monitoring. For French statutory forms specifically, the standard path involves exporting accounting data via a certified connector to a third-party tax application (Wolters Kluwer CCH Tagetik, Cegid Liasse, etc.). Traceability is maintained but the chain requires a technical integration between the ERP and the tax tool.
Sage FRP 1000 and Its Statutory Reporting Module
The “États Comptables et Fiscaux” (ECF) module of Sage FRP 1000 is one of the most complete solutions in the French mid-market. It covers all regimes (standard BIC, simplified BIC, BNC, BA) and includes the group fiscal integration forms: 2058 ER, 2058 ES, 2058 PAP, plus annexes 2066, 2069 A, and 2069 RCI (Sage FRP ECF module).
EDI-TDFC transmission is built in: in a few clicks, the tax return, CVAE, and lease declaration are sent directly to the DGFiP, the approved management centre (OGA), and Banque de France. The module is updated each year to reflect new fields in the current TDFC campaign.
Cegid XRP Flex: French Tax Filing at the Core of the ERP
Cegid, a historic French ERP publisher, has embedded statutory tax return production in its accounting modules for many years. This proximity to DGFiP requirements translates into responsive annual updates and certified EDI-TDFC transmission directly from the ERP — without an intermediary tool for single-entity companies. For groups under fiscal integration, Cegid also provides the necessary consolidation forms.
Dynamics 365 Finance: Export to Third-Party Tax Software
Microsoft Dynamics 365 Finance targets mid-market and international groups. Its global architecture includes a powerful financial reporting engine but does not natively cover DGFiP cerfa formats. French companies using D365 typically rely on a certified partner or add-on module to produce and transmit their statutory return. This two-step model works but requires maintaining data consistency between the two systems.
Odoo and the Limits of Its Accounting Module for French Tax Filing
Odoo Enterprise includes a solid French accounting localisation (chart of accounts, VAT, FEC) but automated production of the cerfa statutory return with EDI-TDFC transmission depends on integration partners. No native DGFiP transmission capability is available in standard Odoo 17 without a third-party module. For SMEs working with an external accountant this remains manageable; for a mid-market company looking to internalise the process, a dedicated tax tool is necessary.
Group Fiscal Integration: 5 Complexity Points for Your ERP
Group fiscal integration multiplies the complexity of the annual tax cycle. These are the five points where ERPs most often show their limits.
1. Centralising tax data from each subsidiary in the right format. Each entity in the consolidated group must submit its individual taxable profit (form 2058 CG) to the group head. When subsidiaries run different ERPs or heterogeneous charts of accounts, tax consolidation becomes a time-intensive manual exercise.
2. Managing elimination adjustments for intra-group transactions. Asset transfers between subsidiaries, dividends paid within the group perimeter, and internal recharges must be eliminated or adjusted to calculate the consolidated group result. These adjustments are not automatic in most standard ERPs.
3. Calculating each entity’s share of the consolidated result and implicit subsidies. Article 223 B of the CGI governs profit transfers between group companies. The concept of implicit subsidy (transfer without consideration) has a direct tax impact on each entity.
4. Managing quarterly IS instalment payments and the final settlement. Subsidiaries in the integrated group pay their instalments to the group head, which remits them to the DGFiP. Managing this tax cash flow (March, June, September, December instalments and the May settlement) requires profit forecasts from each subsidiary sourced from the ERP.
5. Preparing the tax file in the event of a DGFiP audit. In 2025, the DGFiP issued €17.1 billion in additional taxes and penalties, of which €4 billion related to corporate income tax (DGFiP 2025 Activity Report). In the event of an audit of an integrated group, the traceability of adjustment entries between subsidiaries must be complete. An ERP that has not recorded tax adjustment entries will be unable to produce this documentation without manual reconstruction.
FEC, Audit Trail, and Statutory Return: Data Flows Between ERP and Tax Authority
The FEC as the First Layer of Traceability
The statutory audit file (FEC — Fichier des Écritures Comptables) is the starting point of any DGFiP audit. If the FEC totals and the statutory return balances do not reconcile, the auditor has an immediate reason to deepen the review. The ERP must therefore guarantee alignment between the two, which requires that the tax return is produced from the same data as the FEC and not from an intermediary export that has been reworked.
The Reliable Audit Trail and Its Link to the Statutory Return
The reliable audit trail (piste d’audit fiable, PAF), made mandatory for dematerialised invoices since the entry into force of France’s e-invoicing reform, guarantees traceability from the original invoice to the resulting accounting entry. In the context of the statutory return, it enables justification of each expense or income item included in the tax forms, strengthening the file in the event of an audit.
ERP-to-EDI-TDFC Connectors: Who Does What
EDI-TDFC electronic transmission is mandatory for all companies subject to IS under the standard regime, pursuant to Article 1649 quater B quater of the CGI (fiscalnews.fr). For companies whose financial year ends on 31 December 2025, the EDI transmission deadline is 20 May 2026 — 15 calendar days after the online filing deadline (compta-online.com).
The standard technical chain: ERP accounting module → certified tax software via connector or structured export → EDI-TDFC transmission to the DGFiP by an accredited partner (the publisher itself or an EDI service provider).
Certified Tax Software to Interface with Your ERP
When your ERP does not natively cover the French statutory return, three solutions dominate the mid-market in France:
Cegid Liasse: a standalone solution from the French publisher, compatible with the main ERPs on the market via data import. Annual millésime updates, built-in EDI-TDFC. The natural choice if you already use Cegid for accounting.
CCH Tagetik (Wolters Kluwer): a financial performance management platform covering close, consolidation, and tax reporting for groups with an international footprint. Particularly suited to mid-market companies under fiscal integration and group reporting obligations (CCH Tagetik Tax Provision & Reporting).
ediFiscale: a cloud solution specialising in the French statutory return and EDI-TDFC transmission, accessible from a browser. Designed for accounting firms and their clients, with connectors to the main practice management ERPs.
For a mid-market company under group fiscal integration, the annual cost of a dedicated tax solution including group management typically ranges from €3,000 to €10,000, depending on the number of entities and the level of service required. These are indicative ranges: publishers quote on a case-by-case basis.
Annual Tax Close Checklist for the CFO
From 31 December through to DGFiP transmission, here are the 12 steps to industrialise in your ERP and tax software.
- Account reconciliation and matching (by 15 January): receivables, payables, VAT, intercompany accounts.
- Inventory valuation (by 31 January): verify consistency with the ERP’s logistics modules.
- Provision validation (by 15 February): litigation provisions, receivables impairment, risk and charge provisions.
- Depreciation calculation and review: straight-line, declining balance, accelerated, and component depreciation.
- Accruals and prepayments adjustment: rigorous cut-off to avoid period mismatches.
- Export of the final FEC from the ERP (by 15 February): verify the 18 columns, sequential numbering, and trial balance.
- Accounting-to-tax reconciliation: transition from accounting profit to taxable profit, identification of add-backs and deductions.
- Completion or validation of cerfa forms 2050–2059 in the tax module: consistency check against FEC balances.
- Group coordination (fiscal integration): collection of form 2058 CG from subsidiaries, elimination adjustments, consolidated result calculation.
- Payment of the final IS instalment (15 December N) and provisioning for the May N+1 settlement.
- Final consistency review: FEC vs. statutory return comparison, annex validation, carry-forward loss review.
- EDI-TDFC transmission before the deadline (20 May 2026 for companies closing on 31/12/2025): confirm DGFiP acknowledgement of receipt.
The French statutory tax return is not the top priority of an ERP project — but it is often the element that disappoints CFOs most at year-end. A properly configured ERP can feed 80% of the return reliably. The final stretch — tax adjustments and EDI transmission — deserves to be addressed at the start of the project, not six months after go-live.
To explore related topics on DGFiP compliance and financial close, see our complete guide on the FEC and DGFiP tax audit, our analysis of management control and analytical accounting in ERP, and our dossier on FP&A and rolling forecast.
