Step 1 — identify your obligations
Check whether you are established in France and subject to VAT. The reform covers companies liable for VAT, including companies under VAT exemption schemes and micro-enterprises.
A practical France e-invoicing checklist for SMEs and micro-companies: deadlines, approved platform choice, software checks, data fields and source links.
Check whether you are established in France and subject to VAT. The reform covers companies liable for VAT, including companies under VAT exemption schemes and micro-enterprises.
Separate B2B domestic invoices, B2C transactions, exports, intra-community transactions and service/payment flows because e-invoicing and e-reporting can apply differently.
Decide whether to use your accounting software, accountant-led platform, ERP integration or a dedicated approved platform.
Run sample invoices with customer SIREN, delivery address, VAT/payment options and status tracking before relying on the system.
List where invoices are created today, who approves them, how they are sent, how supplier invoices are received, and what your accountant needs each month. This process map prevents buying a tool that does not fit the real workflow.
Clean SIREN numbers, VAT numbers, legal company names, billing and delivery addresses, payment terms, VAT options and customer categories before testing e-invoicing workflows.
Run one sample domestic B2B invoice, one supplier invoice receipt, one correction, one export/B2C reporting scenario if relevant, and one archive/search test with your accountant.
For SME checklist: French SMEs usually need to know when the deadline applies, whether a PDF is still enough, which platform path to use, how Factur-X relates to UBL and CII, what data must be cleaned, and how the accountant will work with the new flow. This guide answers those questions from an SME workflow perspective.
For SME checklist: A good decision compares legal deadline, receiving readiness, issuing workflow, software integration, accountant access, archive/search and support. If two tools look similar, choose the one that can demonstrate your real invoice scenario end to end before the deadline.
Use this guide to decide whether SME checklist affects your France workflow and which evidence is still missing. Start with approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields, then test receive a structured supplier invoice and issue a Factur-X or UBL/CII invoice before comparing software.
For SME checklist, the important terms are SME checklist, France, approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields, e-reporting cases, accountant handoff. Clean these fields in customer, supplier, tax and accounting records before rollout; otherwise validation and support issues appear during daily invoicing.
For SME checklist, ask vendors to show show French platform routing, structured format handling, e-reporting, archive and accountant access using your examples. The demo should cover receive a structured supplier invoice, issue a Factur-X or UBL/CII invoice, simulate an e-reporting case, correct customer master data and explain who handles errors, corrections, archive access and accountant handoff for approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields.
Keep official links, screenshots, test invoices and the decision reason for SME checklist. For SME checklist, the implementation file should prove how approved platform path, Factur-X, UBL or CII data, SIREN/SIRET and VAT fields, e-reporting cases were checked, not just that a tool was selected.
Do not close SME checklist until someone can explain SME checklist in France, name the workflow owner, show one tested invoice scenario and describe how the team avoids choosing software for France before proving the real SME checklist workflow.
Receive e-invoices by 1 September 2026
Issue e-invoices by 1 September 2027 if SME/micro-company
Choose approved platform path
Verify structured format support
Prepare mandatory invoice fields
Document decisions and sources
SMEs and micro-companies have until 1 September 2027 to issue e-invoices, while all companies must receive from 1 September 2026.
Official French guidance says micro-enterprises and freelance entrepreneurs come under the reform scope.
You should not wait completely because receiving readiness starts in 2026 and software/accountant onboarding can take time.
Map current invoicing workflows and ask your accountant/software provider which approved platform path they support.
Prepare SIREN, customer legal names, VAT details, delivery address when relevant, payment terms and transaction category.
Not always. If your current software supports the required platform and structured invoice workflow, you may be able to keep it.
It depends on invoice volume, software complexity and accountant involvement. SMEs should start early enough to test before the deadline.
You may struggle to receive, approve or book invoices correctly. Receiving readiness starts earlier than SME issuing obligations.
Yes. They should separate B2B, B2C and international transactions because invoice and reporting treatment can differ.
Be able to receive, create, validate, send, archive and find sample structured invoices before the legal deadline.
For SME checklist: They usually search for deadlines, whether PDFs are still valid, approved platforms, Factur-X, software choices and what their accountant needs.
For SME checklist: The practical risk is choosing software that cannot handle receiving, issuing, corrections, archive or accountant access in the real workflow.
For SME checklist, start with receive a structured supplier invoice, issue a Factur-X or UBL/CII invoice, simulate an e-reporting case because those scenarios reveal whether the workflow is practical.
The main risk is choosing software for France before proving the real SME checklist workflow.
Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.
We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.