Mandatory electronic invoicing, the transposition of NIS2, a failure rate that remains high despite a record number of business creations: the regulatory calendar and the economic situation require SME and mid-sized company leaders to make simultaneous technical trade-offs. This article isolates three priority projects and the friction points that most business news summaries do not detail.
Electronic invoicing: what the structured format means for SMEs
A regulatory electronic invoice is not a PDF sent by email. The expected format is a structured file (Factur-X, UBL, or CII) machine-readable, integrating standardized data: SIREN identifiers, VAT codes, time-stamped mandatory mentions. The gap between a standard PDF and a structured flow fundamentally changes the processing chain.
For SMEs and microenterprises, the obligation to issue is set to begin on September 1, 2027. The timeline seems comfortable, but compliance requires choosing a partner dematerialization platform (PDP) or going through the public invoicing portal, and then reconfiguring existing commercial management software.
Several points deserve immediate attention. First, not all invoicing software publishers offer a native connector to a PDP. Second, switching to the structured format requires cleaning up customer references (SIREN, addresses, VAT codes) well before the deadline. We find that companies that initiate this cleanup late face cascading rejection errors during the first submissions.
One last nuance: the receipt of electronic invoices will be mandatory before issuance for certain categories. In other words, even if your company does not yet issue in the structured format, it must be able to process incoming flows from its suppliers already subject to the obligation. Checking the compatibility of your accounting tool with Factur-X and UBL formats is a prerequisite, not an option.
To keep track of these deadlines and other management topics, articles from the Business Info site regularly cover regulatory developments affecting French micro and small businesses.
NIS2 Directive: anticipating cybersecurity compliance without a firm date
The French transposition of the NIS2 directive remains on an uncertain timeline. ANSSI mentions full compliance of the concerned entities by the end of 2028, but some obligations could come into effect sooner once the legislative framework is finalized. This uncertainty is not a reason to wait; on the contrary.
NIS2 significantly expands the scope of affected companies. Mid-sized companies and certain SMEs operating in so-called “important” sectors (logistics, agri-food, waste management, digital services) fall within the scope, where NIS1 only targeted operators of essential services.
Three projects to launch without waiting for transposition
- Map critical digital assets and identify information systems whose unavailability would block operations. This preliminary work conditions everything that follows.
- Establish an incident notification procedure. NIS2 imposes strict reporting deadlines (initial alert within 24 hours). Without a well-established process, the risk of non-compliance is immediate as soon as it comes into effect.
- Audit technical debt. Behind NIS2 lies the question of obsolete systems, unpatched fixes, and access rights that have never been reviewed. Accumulated IT debt is the main barrier to cybersecurity compliance, not a lack of budget.
Waiting for the publication of the final text to start this work amounts to compressing into a few months an effort that requires one to two years of gradual deployment.
Record creations and high failures: reading the economic situation correctly
Business creations reached a record level in September 2026 according to Le Figaro, while the economy remained stagnant and failures remained high. This discrepancy is not a paradox: it reveals a labor market that pushes towards entrepreneurship both by default and by choice.
An increasing number of creations does not guarantee that these businesses will develop sustainably. Structures less than five years old and those with few employees remain the most exposed to failures. The slowdown in the progression of bankruptcies does not mean that the risk decreases for young companies.
What these figures change for daily management
For an already established SME leader, interpreting this data imposes two reflexes. The first concerns supplier risk: when failures remain at a high level, the failure of a subcontractor or client can occur without prior warning. Strengthening the monitoring of customer receivables (scoring, credit insurance, retention of title clauses) is not a luxury.
The second relates to recruitment. The flow of business creations diverts some qualified profiles towards self-employment. Attracting and retaining talent requires competing with the perceived flexibility of self-employed status, not just with the salary scales of direct competitors.
Prioritizing projects: decision grid for SME leaders
All these issues arise simultaneously. Electronic invoicing has a firm deadline. NIS2 does not yet have one, but the delay will be costly once the text is published. Monitoring the risk of failure is ongoing.
| Project | Deadline | Immediate Action |
|---|---|---|
| Electronic invoicing | September 1, 2027 (SME issuance) | Choose a PDP, clean up the customer database |
| NIS2 compliance | End of 2028 (ANSSI estimate) | Map critical assets, audit IT debt |
| Supplier/client failure risk | Ongoing | Strengthen credit scoring, diversify key suppliers |
The trap would be to treat these three files in silos. Data cleaning for electronic invoicing also feeds into the NIS2 mapping (identifying critical data flows). And monitoring failures protects the cash flow that finances the other two projects. Addressing one without the other recreates risk where one thought to reduce it.
