PPF Integration in France: Connect Your ERP with Unified APIs

A finance team in Paris was chasing invoices across systems, some buried in the ERP, some stuck in email threads, others inexplicably rejected by the Portail Public de Facturation (PPF). Deadlines loomed. Payments stalled. Compliance risks quietly built up in the background.

France’s e‑invoicing mandate didn’t just introduce a new requirement; it introduced a new reality. From 2026, all businesses established or VAT‑registered in France must be able to receive structured e‑invoices, with issuance and e‑reporting phased in by size. Companies that once controlled invoicing workflows entirely inside their ERP suddenly depended on external validation systems, strict data formats, and near real‑time tax reporting.

Understanding PPF Integration in France

France’s PPF sits at the heart of its new e‑invoicing and e‑reporting ecosystem. It acts as a central hub that receives structured data, synchronises status information, and makes it available to the tax authority. But PPF is not alone in this story.

In the final Y‑model architecture:

• PPF acts as a central directory and data hub, collecting invoice and payment data for reporting and lifecycle tracking. It is not designed to function as a universal B2B invoice exchange channel.
• PAs (Plateformes Agréées, formerly PDPs) serves as the mandatory intermediary for e-invoicing. These accredited private platforms are responsible for validating invoices, converting them into compliant formats such as Factur‑X, UBL, or CII, routing them to the recipient, and transmitting required reporting data to the PPF.

Direct integration with the PPF is not permitted for issuing or receiving B2B invoices. All invoice flows must pass through a PA.

• Chorus Pro remains in place for B2G invoicing and can be accessed either directly or via a PA.

Unlike traditional invoicing, you can’t just email a PDF; you must send a structured e‑invoice that passes schema and tax checks and is reported near real time, because every rejection hits both compliance and cash flow.

How to Integrate ERP with PPF API

At first glance, PPF integration seems straightforward: connect ERP to an API, send invoices, receive responses. In reality, it unfolds in stages that span data modelling, security, error handling, and long‑term maintenance.

1. Understand PPF API Requirements

Before writing any code, you need clarity on:

• Required fields: SIREN/SIRET, VAT numbers, regime codes, payment terms, document type, nature of transaction.
• Accepted formats: EN 16931‑aligned syntaxes such as Factur‑X, UBL, and CII—structured XML, not PDFs.
• Validation rules: Tax logic, identifier formats, timestamp rules, status life‑cycle constraints.

2. Choose and Onboard an Accredited PA 

To use PPF for B2B e‑invoicing, your ERP must go through an accredited PA or a unified API connected to one, which acts as your compliant gateway to route invoices, manage directory lookups, and send mandated reporting.

• Select an accredited PA or unified API connected to a PA
• Complete contractual and technical onboarding
• Confirm supported formats and flows (invoices, credit notes, self‑billing, B2C)
• Define who owns validation, enrichment, and error handling

3. Set Up PPF Authentication

Authentication is often underestimated. Depending on your model (direct PA vs unified API), you will need:

• Secure credentials or OAuth tokens
• Sometimes certificates and delegated access setups
• Clear separation between TEST and PROD environments

4. Map ERP Data to PPF Schema

Most ERPs were not designed with French formats in mind. That means:

• Mapping internal invoice objects to PPF‑compatible schemas
• Ensuring VAT calculations align with EN 16931 rules
• Filling in country‑specific fields that may not exist today

5. Build Submission and Validation Logic

Once your data is structured correctly:

• Submit invoices through your PA or unified API
• Handle synchronous and asynchronous responses
• Track statuses like validated, rejected, delivered, reported

6. Handle Errors and Exceptions

Common failures include:

• Missing mandatory fields or invalid identifiers
• Incorrect VAT breakdown
• Format mismatches or unsupported scenarios (credit notes, self‑billing, B2C)

7. Monitor and Maintain Compliance

France updates specifications, formats evolve, and DGFiP refines requirements especially as the 2026–2027 rollout progresses. Without continuous monitoring and version management, a system that is compliant this year can silently drift out of compliance next year.

Why Most PPF Integrations Struggle

Many companies start building their own PPF integration with confidence, only to hit a wall within weeks. The pattern is repeating across France.

• Fragmented systems
  Invoices are created in ERPs, but compliance logic lives elsewhere. The gap between business data and regulated data is larger than expected.
• Hidden complexity
  The “simple API” hides layered validation logic, country‑specific rules, directory dependencies, and continuously evolving technical specifications.
• Manual error handling
  Without structured responses and good UX, rejected invoices turn into email chains, spreadsheets, and late‑payment headaches.
• No path to scale
  Once you add Italy, Poland, or another CTC regime, every difficulty in France multiplies: new formats, new portals, new semantics. A French‑only solution quickly becomes a multi‑country nightmare.

Developer‑first unified APIs already exist that let you “plug in once, expand everywhere.”

How DDD Invoices Simplifies PPF Integration

Instead of forcing ERP vendors and SaaS platforms to navigate every country’s specifics, DDD Invoice provides a single unified API that abstracts away local complexities, including France’s PPF‑centric model.

One API, Many Countries

You integrate once using a standardized REST API and send a canonical JSON invoice with about 60 data fields. Roughly 98% of this schema stays identical across all supported countries.

DDD Invoice then:

• Generates the required French formats (Factur‑X, UBL, CII, etc.)
• Validates invoices against EN 16931 and DGFiP rules
• Routes invoices through connected networks (PAs, Peppol, national portals)
• Submits reporting payloads to the appropriate authorities, including PPF‑linked flows

DDD Invoice's compliance layer centralizes validation, tax logic, status tracking, and country‑specific auth, then returns structured errors and clean data into your ERP and AI‑based capture, making French PPF integration a reusable, near‑invisible multi‑country layer.

FAQs

What is PPF integration in France?
PPF integration connects your ERP or billing system, via an accredited platform or unified API, to France’s public invoicing and reporting hub so invoices can be validated, routed, and reported under the 2026 mandate.

How do I integrate an ERP with the PPF API?
You connect your ERP to an accredited PA (or a unified API using one), not directly to the PPF, and use that connection to send France‑compliant e‑invoices and receive status updates.

What are common PPF API requirements?
Typical requirements include EN 16931‑aligned XML formats, mandatory identifiers like SIREN/SIRET and VAT data, correct VAT rules, and near real‑time reporting of invoices and their life‑cycle statuses.

What are typical PPF invoice submission errors?
Frequent errors involve missing mandatory fields, invalid identifiers, incorrect VAT breakdowns, unsupported document types, and authentication or certificate issues between systems and platforms.