B2B Software Consulting in Paris
France switches on 1 September 2026: every Paris company must receive electronic invoices through a plateforme agréée, and large entreprises and ETI must issue them. ERPStack builds Paris ERP and CRM systems remote-first — Factur-X emitting, CNIL-auditable, on AWS eu-west-3 or Microsoft Azure France Central.
Quick Answer
In short: from 1 September 2026 a Paris company must receive its invoices through a plateforme agréée. ERPStack builds custom ERP that emits the Factur-X, UBL and CII profiles of EN 16931, keeps CNIL délibération 2021-122 journalisation in PostgreSQL, and runs in AWS eu-west-3, three Availability Zones and roughly 8 ms across Île-de-France.
Regional Compliance
- Facturation électronique via a plateforme agréée from 1 September 2026
- Factur-X, UBL and CII profiles of EN 16931 emitted by the ERP
- CNIL délibération 2021-122 log retention modelled in PostgreSQL
- HDS referential v2 hosting for French health data the CRM touches
- GDPR under the loi Informatique et Libertés, with RBAC and SOC 2 evidence
- SecNumCloud and ISO 27001 controls for cloud de confiance procurement
Security & Compliance Architecture
French compliance is prescriptive, so a Paris ERP inherits schema decisions from the CNIL, the DGFiP and the code de la santé publique — not a generic GDPR policy.
CNIL journalisation sets your retention
Délibération n° 2021-122 of 14 October 2021 recommends six months to a year of logs, up to three years for internal control, each entry naming user, timestamp and equipment. A Paris ERP partitions that Immutable Audit Trail monthly in PostgreSQL, with RBAC deciding who may read it.Consent is a table, not a cookie
The CNIL fined Shein €150 million on 1 September 2025 under article 82 of the loi Informatique et Libertés for trackers set after refusal. A Paris retail CRM therefore stores consent state and its history in PostgreSQL, and the Next.js front end reads that record rather than the browser.HDS is a hosting boundary, not a badge
The HDS referential published 16 May 2024 requires physical hosting inside the EEA, with existing hosts compliant by 16 May 2026. ERPStack holds no HDS certification, so we design Paris healthcare systems where the certified host owns clinical tables and the ERP owns the rest in PostgreSQL behind one API.DSN turns payroll into an event log
The déclaration sociale nominative replaces dozens of filings with one monthly submission to URSSAF under the NEODeS norm, carrying prélèvement à la source. A Paris ERP keeps 35-hour and RTT balances as event rows in PostgreSQL under Drizzle ORM, because a correction replays an earlier month exactly for Paris finance clients.
Engineering Blueprint
Paris has a hard deadline the rest of Europe does not: 1 September 2026, when every French business must receive invoices through a plateforme agréée. A Paris ERP is designed around Factur-X and e-reporting, not around a generic REST API.
The PDP is transport; the ERP owns the data
Grandes entreprises and ETI in Paris must also issue electronically from 1 September 2026, with PME and microentreprises following on 1 September 2027. ERPStack keeps the Factur-X payload and its lifecycle in PostgreSQL under Drizzle ORM and treats the plateforme agréée as a swappable adapter, validated with Zod and TypeScript before anything leaves the ERP.
// Zod: e-reporting payload validated before the PDP adapter, France 2026
export const eReportingLine = z.object({
siren: z.string().regex(/^\d{9}$/),
facturxProfile: z.enum(['MINIMUM', 'BASIC WL', 'BASIC', 'EN 16931', 'EXTENDED']),
lifecycle: z.enum(['issued', 'received', 'rejected', 'cashed']),
tvaRate: z.number().nonnegative(), // TVA rate carried per line
});Paris cloud topology and the health split
AWS eu-west-3 sits in France with three Availability Zones and Microsoft Azure France Central is in Paris, so a Paris ERP genuinely runs in-country — unlike Amsterdam, where AWS operates no region. Healthcare is the exception: article L.1111-8 forces HDS-certified hosting, so we split the schema and let the Paris CRM hold identifiers in PostgreSQL while the certified host keeps clinical rows, joined through one API.
Evaluate Your Stack
Take our interactive audit to see if your architecture is ready for operational scale.
Start Free AuditRegional Infrastructure
Infrastructure Region
Latency Metrics
Primary Datacenter
Success Stories in Paris
Real-Time Fraud Detection Platform
Real-time fraud detection and risk scoring platform
Read Case StudyTarget Industries in Paris
Frequently Asked Questions
On 1 September 2026 every French VAT-registered business, including small Paris firms, must receive electronic invoices through a plateforme agréée; grandes entreprises and ETI must issue from that date, PME and microentreprises from 1 September 2027. So a Paris ERP emits structured PostgreSQL data through an API, and Paris retail and finance teams are re-platforming now.
No. A plateforme de dématérialisation partenaire is an operator registered by the French administration for a renewable three-year term, and from 1 September 2026 Paris invoices must transit one. ERPStack treats the PDP as an outbound adapter: the Paris ERP owns the Factur-X payload in PostgreSQL and the plateforme agréée owns transport, so switching provider is a configuration change.
Factur-X for anything a human reads: it embeds EN 16931 XML inside a PDF/A-3, so a Paris buyer sees an invoice and the ERP sees data. Release 1.09, published 10 June 2026, is identical to ZUGFeRD 2.5, with profiles MINIMUM through EXTENDED. Pure UBL or CII suits machine-only partners in Paris manufacturing and retail.
For the general ledger, SAP S/4HANA or Microsoft Dynamics 365 usually wins in Paris finance and insurance — regulatory reporting is worth buying. The custom build belongs one layer out: claims, broker portals and the aerospace or luxury retail supplier workflows those packages force into spreadsheets. We integrate through a REST API rather than replace the ledger.
Six months to a year for ordinary security logs. CNIL délibération n° 2021-122 of 14 October 2021 recommends that range, up to three years where internal control justifies it, each entry carrying user identifier, timestamp and equipment. A Paris ERP partitions its Immutable Audit Trail monthly in PostgreSQL under RBAC.
You need an HDS-certified host; ERPStack holds no HDS certification. Article L.1111-8 of the code de la santé publique requires it, and the referential published 16 May 2024 forces physical hosting inside the EEA, existing hosts compliant by 16 May 2026. We split the Paris healthcare schema so the certified host owns clinical rows and the ERP keeps the rest in PostgreSQL.
SecNumCloud, the ANSSI cloud qualification, is required only for sensitive state workloads but increasingly requested in French public procurement — ERPStack holds none and builds so a Paris ERP runs on a qualified provider. France had not published its NIS2 transposition law when we checked ANSSI guidance, so Paris aerospace and finance scope dates stay provisional.
Through the DSN. The déclaration sociale nominative replaces dozens of filings with one monthly submission to URSSAF on the 5th or 15th under the NEODeS norm, carrying prélèvement à la source. A Paris ERP keeps 35-hour and RTT balances as event rows in PostgreSQL under Drizzle ORM, because a correction replays an earlier month exactly.