ERP Business Analyst, France

Turning the e-invoicing reform into requirements

France is moving business-to-business invoicing onto structured electronic formats, with invoice and transaction data shared with the tax administration via approved platforms. Scope and timing vary with company size and the calendar has moved more than once, so the dates that apply to you should come from your expert-comptable. A requirements document can already make sure the chosen ERP will not be the weak link.

I break the reform into concrete requirements. Outbound: issue invoices and credit notes in an accepted structured format, such as UBL, CII or the hybrid Factur-X format, and transmit them to the approved platform you select. Inbound: receive supplier invoices from that platform, match them to orders and receipts, and route exceptions. Lifecycle: record the statuses that come back, such as rejected, approved or paid, and show them to the right teams. Master data: hold accurate company identifiers for every customer and supplier, because a missing SIREN will stop an invoice regardless of the software.

Public-sector customers add another channel, Chorus Pro, which may already be part of your invoicing routine. I write those flows into the same section so they are tested together. The Odoo and Zoho pages for France look at how each platform approaches these points.

The FEC, the French chart of accounts and group mapping

French statutory books follow the national chart of accounts and French accounting rules, and in a tax audit the company can be asked for the FEC, a standardized file listing every accounting entry. For a subsidiary, the parent usually wants its own chart, calendar and reporting format as well. Requirements must serve all three without forcing finance to rebuild figures in spreadsheets.

I write the accounting section of the BRD with your expert-comptable involved from the outset. It specifies the account structure and how group accounts map to French ones, the journals and numbering the books need, how sequences and document links must behave so the FEC holds together, and which closing and reporting outputs the French entity and the group each require. Where the group reports under a different framework, the adjustments are recorded as requirements with an owner, while the accounting judgments stay with the accountants.

Every item becomes a test. In the test phase, an FEC generated from sample transactions goes to your accountant for review, a trial close is run, and the group reporting pack is compared with expected figures. My ERP gap analysis work then records how each platform handles these points, as standard or through extensions. The Dynamics 365 page for France covers group setups on that platform.

Payroll, TVA and the other French data sources

Payroll in France is usually produced by specialist software or an outsourced provider, which also prepares the regular social declarations. The ERP seldom calculates salaries itself, but it must receive the outcome: payroll journals, employer charges and cost allocations by department, site or project. I write that interface as a requirement with a defined file, mapping, timing and reconciliation step, so finance can show the ledger matches payroll every month.

TVA requirements follow the logic I apply to tax everywhere: your expert-comptable confirms the treatments, and I make sure each one is captured as a code with the invoice mentions, return lines and intra-EU reporting data it must drive. French invoices carry a set of mandatory mentions, and I list the ones your accountant confirms so templates can be tested against them.

Other sources get short specifications as well: bank statements and SEPA payment files, expense tools, e-commerce orders and EDI with large retail customers where relevant. Each specification states the data, the owner, the frequency and what happens when an import fails. My requirements gathering page explains the method, and the ERPNext page for France covers what an open-source setup must add.

Interviews with French teams and English-speaking sponsors

A French ERP project often has two audiences who rarely sit in the same meeting: French-speaking process owners who know how the work is done, and English-speaking sponsors in a parent company or international management team who approve budgets and standards. Requirements built from only one side fail in predictable ways.

I schedule separate tracks. Process owners in finance, sales administration, purchasing and logistics take part in working sessions, and a bilingual colleague joins whenever a key user prefers to explain in French; the notes come back in writing for correction. Sponsors and group functions review the consolidated requirements, the account mapping, security and integration standards, and the priorities that drive the shortlist. Points of disagreement go into a decision log with an owner.

Everything I produce is in English. French-language artifacts, such as invoice templates, screen labels, user guides and training material, are listed in the BRD and checked by your staff or a French partner, as part of an engagement that runs in English. Sessions are remote and sit in the French morning, which is my afternoon in India. For broader engagement options, see my freelance ERP consultant page for France; the wider project is described on the French ERP consultant page.