On 28 September 2026, the French tax authority reminded businesses that every company should have been able to receive electronic invoices since 1 September. SMEs do not have to issue electronic invoices and submit e-reporting data until 1 September 2027, but that gap should be treated as a project schedule rather than spare time. The DGFiP update published on 28 September confirms the deadlines without postponing them.
The promise heard everywhere: “SMEs still have a year”
The common message sounds straightforward: select an approved platform — still frequently referred to as a PDP — connect it to the invoicing system and let electronic exchanges replace emailed PDF files.
The promise has a solid technical basis. An approved platform routes invoices, transfers relevant data to the tax authority and provides processing statuses. A compatible business application can remain the user-facing tool, so employees do not necessarily have to work in the platform’s portal.
The September 2027 deadline may therefore encourage SMEs to wait for their ERP vendor, accountant or platform provider to release a ready-made connector. Compliance would then become a configuration task completed during the summer of 2027.
That shortcut is where the operational risk begins.
What is true
SMEs and microbusinesses must issue electronic invoices and transmit the relevant e-reporting data from 1 September 2027. Invoice receipt is different: it has been mandatory for companies of every size since 1 September 2026 and must operate through an approved platform. The official reform timetable clearly separates these obligations.
Standardisation can also reduce manual data entry and improve traceability. Structured data, directory-based routing and lifecycle statuses can replace controls previously handled through inboxes and spreadsheets.
However, these benefits depend on accurate customer records, clear accounting rules and a workable approval process. The platform carries information; it does not decide who approves a credit note, how a rejection should be corrected or when collection activity should begin.
What is false, or only true under certain conditions
Selecting a platform is not the same as achieving compliance. The company must decide which system creates the reference invoice, how it connects to the approved platform, where statuses are stored and which system feeds the accounts. Our article on e-invoicing compliance scenarios distinguishes manual portals, compatible solutions and ERP integration.
E-reporting is not merely a by-product of domestic B2B invoicing. Consumer sales, certain international transactions and, where applicable, payment data for services require their own reporting path. An SME may therefore pass its Factur-X tests while leaving part of its reporting scope unresolved.
Statuses do not replace accounts receivable processes. A technical rejection, a business refusal and an unpaid accepted invoice require different actions. The minimum vocabulary for Factur-X, e-reporting and lifecycle statuses helps teams separate document format, tax reporting and operational processing.
The initial tolerance period is not a postponement. The authorities announced a tolerant approach during the end of 2026 for businesses facing genuine implementation issues. Yet the DGFiP practical startup guide requires an active, documented compliance path followed by corrective action. It explicitly distinguishes implementation problems from inertia or a lasting refusal to enter the system.
What going in unprepared actually costs
The first cost is a duplicate process. The same supplier invoice may arrive through the approved platform, by email and through a supplier portal. Without matching rules, accounting teams must inspect each occurrence manually, with risks of duplicate approval, posting or payment.
The second cost affects cash flow. A customer invoice that is technically rejected, routed to the wrong establishment or left in a workflow with no owner will not move normally through the customer’s approval process. Collection activity then starts from unreliable information.
The third cost is vendor dependency. An integration built without documenting formats, exports, responsibilities and fallback procedures makes a future platform change harder. The company becomes dependent not only on a contract but also on configuration that nobody internally controls.
A late project also concentrates every correction into the same period: customer master data, invoice fields, connectors, e-reporting rules, user permissions and accounting procedures. What began as a compliance task becomes a business continuity issue.
The sensible way forward: a calendar that produces evidence
The plan should follow five practical principles:
- Secure invoice receipt first, because that obligation is already in force.
- Clean data before building interfaces, so errors are not automated.
- Test complete business cycles, not isolated screens or file transfers.
- Connect statuses to accounts receivable, rather than leaving them inside the platform.
- Retain evidence of tests and decisions, both to manage corrections and demonstrate progress.
The following roadmap can be adjusted to the SME’s systems and transaction profile:
| Month | Main owner | Action | Required deliverable |
|---|---|---|---|
| October 2026 | Finance director | Confirm the receiving platform, registered entities, directory data, user access and notification handling | Register of entities, users, channels and incidents |
| November 2026 | Accounting and sales administration | Classify domestic B2B, consumer, international, public-sector, credit-note, deposit and service flows | Matrix identifying e-invoicing, e-reporting or a specific channel |
| December 2026 | Master-data and finance teams | Correct company identifiers, addresses and required invoicing fields | Validated dataset with an owner assigned to each remaining anomaly |
| January 2027 | Finance and IT | Approve the target architecture covering the ERP, invoicing software, compatible solution, approved platform and archive | Flow diagram and responsibility matrix |
| February 2027 | Accounts payable | Test receipt, duplicate detection, approval, accounting integration and archiving | Inbound test report with defects and decisions |
| March 2027 | Sales administration | Test invoices, credit notes, rejections, refusals and status updates through to the business application | Outbound test log and recovery rules |
| April 2027 | Tax owner or accountant | Map transaction and payment data falling outside domestic B2B e-invoicing | Mapping of sources, controls and e-reporting fields |
| May 2027 | Project manager | Run a pilot on a controlled scope with available customers and suppliers | List of real incidents, root causes and approved corrections |
| June 2027 | Credit control and sales administration | Connect statuses, due dates, disputes and receipts to collection rules | Exception queue and documented collection workflow |
| July 2027 | Finance and IT | Prepare for system downtime, exports, reversibility and temporary processing | Business continuity procedure and escalation directory |
| August 2027 | Project management | Run a full rehearsal and approve acceptance only after reviewing evidence | Acceptance report, reservations and correction plan |
| September 2027 | Finance director | Monitor rejected, unrouted, unreported and delayed invoices during production startup | Daily control dashboard and named action owners |
For platform selection, use the six criteria for choosing a French approved platform. Before production, apply a functional acceptance process based on tests rather than a vendor demonstration.
Our position at D1 Consulting
We do not recommend portal-only compliance when it creates another inbox to monitor and a second source of invoice statuses. The objective is not merely to generate an accepted format on 1 September 2027. It is to establish a process that accounting, sales administration and credit control can operate without parallel manual work.
Our e-Factu application supports compliant electronic invoicing, including Factur-X generation and connection to an approved platform. Our e-invoicing reform service covers flow scoping, target architecture, integration, testing and operational readiness.
The final design should also connect invoice statuses to payment monitoring. Once those statuses are reliable, teams can distinguish technical failures, commercial disputes and genuine overdue balances, then extend the process through controlled invoice reminder automation.
👉 Book your free 30-minute diagnostic and leave with your next project milestone, the owner to involve and the deliverable to produce.
