PA (Plateforme Agréée) Guide

Introduction

The workflow steps and API used in this guide are subject to change. We are actively working on new approaches to event handling for a more global use case. The examples here are functional and can be used today, but expect updates before the September 2026 mandate.

France handles e-invoicing through approved PA (Plateforme Agréée) platforms as part of its electronic invoicing reform. Invopop is an officially approved PA platform, as listed on the French government’s official list of approved platforms. Invopop is Plateforme Agréée (Approved Platform) by the French tax administration, meaning we have successfully provided all necessary documentation for the registration procedure and passed the technical compliance verification.

Prerequisites

To use the France PA integration, you will need:

Invopop workspace with the Peppol and France apps enabled.
French company registration details including SIREN/SIRET numbers.
Understanding of your invoicing flows (B2B, B2C, domestic, cross-border) to plan registration and reporting requirements.
Business processes for status updates to implement the mandatory lifecycle status workflow.

Key Concepts


Annuaire	The French e-invoicing directory where parties must be registered to participate in regulated e-invoicing flows.
PPF	Portail Public de Facturation — the French government system that receives mandatory invoice data and lifecycle updates. Invopop handles all communications with the PPF automatically.
Regulated Flow	An invoice exchange where both the sender and receiver are registered in the annuaire. These follow the complete French e-invoicing process including Peppol transmission and PPF reporting.
Non-Regulated Flow	An invoice exchange where only one party is registered in the annuaire. Invoices are stored for e-reporting to the PPF but may not be transmitted via Peppol.
E-Reporting	France requires two types: real-time reporting for B2B national (regulated) flows via F1 format; and periodic reporting for non-regulated flows and B2C transactions.
CDAR	Cross Domain Acknowledgement and Response. The format used for lifecycle status updates (“cycle de vie”) in France, communicated between parties and to the PPF.
F1 Invoice	Simplified UBL format used for e-reporting to the PPF for regulated flows. Generated automatically by Invopop.

Registration workflow

The registration process prepares parties to send and receive invoices in France. It builds on the standard Peppol registration workflow with additional French-specific steps.

Approval

Standard approval process to verify party details and authorization.

Register the party in the annuaire (French e-invoicing directory) under Invopop’s name. Required for the party to participate in French e-invoicing.

Complete standard Peppol registration. Invopop uses Peppol as the designated method for sending and receiving invoices in the French PA system.

Enable Reporting

Optional Enable e-reporting for the party to comply with French tax reporting requirements.

Sending workflow

The workflow steps below are subject to change. We are working on new methods of handling events for a more global use case. This example is functional today, but expect refinements before the September 2026 mandate.

The sending workflow records the invoice for France PA compliance, transmits it via Peppol, and then forwards it to the PPF. The same workflow handles both French and non-French invoices — the France-specific steps are automatically skipped when the sender is not registered in the annuaire.

How it works

Set state to Processing — marks the job as in progress.
Sign the envelope — locks the GOBL document against further modification.
Record Invoice (France) — registers the invoice with the France PA system. Determines whether this is a regulated or non-regulated flow based on annuaire registration status of both parties.
Generate UBL Document — produces a Peppol France CIUS–compliant UBL invoice or credit note.
Send via Peppol — transmits the invoice to the receiver’s PA platform over the Peppol network.
Set state to Sent — marks successful Peppol delivery.
Forward to PPF — sends the F1 invoice and the mandatory déposée (deposited) status to the government data concentrator. For non-regulated flows, records the invoice for periodic reporting instead.
Set state to Completed — marks full completion including PPF reporting.

Workflow code

Template
Code

France PA send invoice workflow

Records and sends a France-compliant invoice via Peppol and the PPF.

Copy and paste into a new Empty Invoice workflow code view.

France PA send invoice workflow

{
    "name": "Send an invoice France",
    "description": "",
    "schema": "bill/invoice",
    "steps": [
        {
            "id": "72bc5070-1a17-11f1-a82f-e740c226ef51",
            "name": "Set Silo Entry State",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            }
        },
        {
            "id": "f5aaed10-13c9-11f1-98a6-7dfa4cb26122",
            "name": "Add Signature",
            "provider": "silo.close"
        },
        {
            "id": "f1e30fa0-13c9-11f1-98a6-7dfa4cb26122",
            "name": "Record Invoice (France)",
            "provider": "gov-fr.invoice.record"
        },
        {
            "id": "1b5850d0-13bf-11f1-bc3b-b99ec414b63d",
            "name": "Generate UBL Document",
            "provider": "ubl.generate",
            "summary": "Peppol France CIUS UBL Invoice/CreditNote",
            "config": {
                "attach_invoice_pdf": false,
                "doc_type": "peppol-fr-cius",
                "private": false,
                "validate_ubl": false
            }
        },
        {
            "id": "ab598990-16f0-11f1-86ba-d13d91b4f398",
            "name": "Send Peppol Document",
            "provider": "peppol.send"
        },
        {
            "id": "79bd38d0-1a17-11f1-a82f-e740c226ef51",
            "name": "Set Silo Entry State",
            "provider": "silo.state",
            "summary": "Set state to `sent`{.state .sent}",
            "config": {
                "state": "sent"
            }
        },
        {
            "id": "e1f6ce90-16eb-11f1-86ba-d13d91b4f398",
            "name": "Forward Invoice to PPF",
            "provider": "gov-fr.invoice.forward"
        },
        {
            "id": "80a9d5e0-1a17-11f1-a82f-e740c226ef51",
            "name": "Set Silo Entry State",
            "provider": "silo.state",
            "summary": "Set state to `completed`{.state .completed}",
            "config": {
                "state": "completed"
            }
        }
    ],
    "rescue": [
        {
            "id": "892a8070-1a17-11f1-a82f-e740c226ef51",
            "name": "Set Silo Entry State",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

Status update workflow

France requires mandatory lifecycle status updates to be reported to the PPF for B2B national invoices. You must implement workflows for the two statuses that are your responsibility:

Status	Code	Trigger
Encaissée (cashed/paid)	`212`	Invoice has been paid
Refusée (refused by buyer)	`210`	Buyer refuses the invoice (business rejection)

The following statuses are handled automatically by Invopop and do not require a workflow:

Status	Code	When
Déposée (deposited)	`200`	Sent automatically when the invoice is created
Rejetée (rejected by platform)	`213`	Sent automatically on processing failure

You can also send additional non-mandatory statuses (e.g. 205 Approuvée, 207 En litige) for lifecycle tracking. The status workflow below handles all of these.

How it works

Generate Status (France) — creates a CDAR document with the specified status code and reason code. The status_code, reason_code, and optional reason_text are configured per workflow or passed as job arguments.
Send via Peppol — transmits the CDAR to the counterparty over Peppol.
Forward to PPF — for mandatory statuses (210, 212), sends the notification to the PPF in the required format.

Using job arguments

Instead of hardcoding the status in the workflow configuration, you can pass the status details as job arguments when creating the job. Arguments take priority over the workflow’s configured values, so you can use a single workflow for multiple status types. The supported arguments are:

Argument	Description
`code`	Status code (`200`–`213`). Overrides `status_code` in the workflow config.
`reason-code`	Reason code (e.g. `MONTANTTOTAL_ERR`). Overrides `reason_code` in the workflow config. If omitted, a default reason code is applied based on the status code.
`reason-text`	Optional free-text explanation. Overrides `reason_text` in the workflow config.

For example, to trigger a Refusée (refused) status using a workflow that is configured with a different default:

{
  "args": {
    "code": "210",
    "reason-code": "DOUBLON",
    "reason-text": "Duplicate invoice already processed"
  }
}

This approach is useful when you want a single status workflow that can handle multiple status types dynamically, driven by your business logic.

Workflow code

The example below is configured for status 207 (En litige / Disputed) with reason code MONTANTTOTAL_ERR. Change status_code and reason_code to match your use case, or override them at runtime using job arguments as described above.

Template
Code

France PA send status workflow

Generates and forwards a lifecycle status update (CDAR) via Peppol and the PPF.

Copy and paste into a new Empty Invoice workflow code view.

France PA send status workflow

{
    "name": "Send state",
    "description": "",
    "schema": "bill/invoice",
    "steps": [
        {
            "id": "e600d990-16f5-11f1-86ba-d13d91b4f398",
            "name": "Generate Status (France)",
            "provider": "gov-fr.status.generate",
            "summary": "Generate 207 status (MONTANTTOTAL_ERR)",
            "config": {
                "reason_code": "MONTANTTOTAL_ERR",
                "reason_text": "",
                "status_code": "207"
            }
        },
        {
            "id": "eb002590-16f5-11f1-86ba-d13d91b4f398",
            "name": "Send Peppol Document",
            "provider": "peppol.send"
        },
        {
            "id": "ef5500c0-16f5-11f1-86ba-d13d91b4f398",
            "name": "Forward Status to PPF",
            "provider": "gov-fr.status.forward"
        }
    ],
    "rescue": []
}

We recommend creating a separate workflow for each mandatory status type (paid, refused) with the appropriate code pre-configured, rather than a single generic workflow. This keeps your operational runbooks simple and reduces the risk of sending the wrong code.

Available status codes

Code	French	English	Mandatory to PPF
`200`	Déposée	Deposited	Yes (automatic)
`205`	Approuvée	Accepted	No
`206`	Partiellement approuvée	Partially Approved	No
`207`	En litige	Disputed	No
`208`	Suspendue	Suspended	No
`209`	Complétée	Completed	No
`210`	Refusée	Refused by buyer	Yes (manual)
`211`	Paiement transmis	Payment transmitted	No
`212`	Encaissée	Cashed/Paid	Yes (manual)
`213`	Rejetée	Rejected by platform	Yes (automatic)

Reason codes by status

Each status code accepts specific reason codes. Statuses not listed below (e.g. 205, 209, 211, 212) do not require a reason code.

200 — Déposée (Deposited)

Reason Code	Description
`NON_TRANSMISE`	Destinataire non connecté

Default: NON_TRANSMISE

206 — Partiellement approuvée (Partially Approved)

Reason Code	Description
`AUTRE`	Autre
`TX_TVA_ERR`	Taux de TVA erroné
`MONTANTTOTAL_ERR`	Montant total erroné
`CALCUL_ERR`	Erreur de calcul de la facture
`NON_CONFORME`	Mention légale manquante
`DOUBLON`	Facture en doublon
`DEST_ERR`	Erreur de destinataire
`TRANSAC_INC`	Transaction inconnue
`EMMET_INC`	Émetteur inconnu
`CONTRAT_TERM`	Contrat terminé
`DOUBLE_FACT`	Double facture
`CMD_ERR`	N° de commande incorrect ou manquant
`ADR_ERR`	Adresse de facturation électronique erronée
`SIRET_ERR`	SIRET erroné ou absent
`CODE_ROUTAGE_ERR`	CODE_ROUTAGE absent ou erroné
`REF_CT_ABSENT`	Référence contractuelle nécessaire
`REF_ERR`	Référence incorrecte
`PU_ERR`	Prix unitaires incorrects
`REM_ERR`	Remise erronée
`QTE_ERR`	Quantité facturée incorrecte
`ART_ERR`	Article facturé incorrect
`MODPAI_ERR`	Modalités de paiement incorrectes
`QUALITE_ERR`	Qualité d’article livré incorrecte
`LIVR_INCOMP`	Problème de livraison

Default: AUTRE

207 — En litige (Disputed)

Reason Code	Description
`AUTRE`	Autre
`TX_TVA_ERR`	Taux de TVA erroné
`MONTANTTOTAL_ERR`	Montant total erroné
`CALCUL_ERR`	Erreur de calcul de la facture
`NON_CONFORME`	Mention légale manquante
`DOUBLON`	Facture en doublon
`DEST_ERR`	Erreur de destinataire
`TRANSAC_INC`	Transaction inconnue
`EMMET_INC`	Émetteur inconnu
`CONTRAT_TERM`	Contrat terminé
`DOUBLE_FACT`	Double facture
`CMD_ERR`	N° de commande incorrect ou manquant

Default: AUTRE

208 — Suspendue (Suspended)

Reason Code	Description
`JUSTIF_ABS`	Justificatif absent ou insuffisant
`SIRET_ERR`	SIRET erroné ou absent
`CODE_ROUTAGE_ERR`	CODE_ROUTAGE absent ou erroné
`REF_CT_ABSENT`	Référence contractuelle nécessaire
`REF_ERR`	Référence incorrecte
`CMD_ERR`	N° de commande incorrect ou manquant
`ADR_ERR`	Adresse de facturation électronique erronée

Default: JUSTIF_ABS

210 — Refusée (Refused by buyer)

Reason Code	Description
`COORD_BANC_ERR`	Erreur de coordonnées bancaires
`TX_TVA_ERR`	Taux de TVA erroné
`MONTANTTOTAL_ERR`	Montant total erroné
`CALCUL_ERR`	Erreur de calcul de la facture
`NON_CONFORME`	Mention légale manquante
`DOUBLON`	Facture en doublon
`DEST_ERR`	Erreur de destinataire
`TRANSAC_INC`	Transaction inconnue
`EMMET_INC`	Émetteur inconnu
`CONTRAT_TERM`	Contrat terminé
`DOUBLE_FACT`	Double facture
`CMD_ERR`	N° de commande incorrect ou manquant
`ADR_ERR`	Adresse de facturation électronique erronée
`SIRET_ERR`	SIRET erroné ou absent
`CODE_ROUTAGE_ERR`	CODE_ROUTAGE absent ou erroné
`REF_CT_ABSENT`	Référence contractuelle nécessaire
`REF_ERR`	Référence incorrecte
`PU_ERR`	Prix unitaires incorrects
`REM_ERR`	Remise erronée
`QTE_ERR`	Quantité facturée incorrecte
`ART_ERR`	Article facturé incorrect
`MODPAI_ERR`	Modalités de paiement incorrectes
`QUALITE_ERR`	Qualité d’article livré incorrecte
`LIVR_INCOMP`	Problème de livraison

Default: TRANSAC_INC

213 — Rejetée (Rejected by platform)

Reason Code	Description
`REJ_SEMAN`	Rejet pour erreur sémantique
`REJ_UNI`	Rejet sur contrôle unicité
`REJ_COH`	Rejet sur contrôle cohérence de données
`REJ_ADR`	Rejet sur contrôle d’adressage
`REJ_CONT_B2G`	Rejet sur contrôles métier B2G
`REJ_REF_PJ`	Rejet sur référence de PJ
`REJ_ASS_PJ`	Rejet sur erreur d’association de la PJ
`IRR_VIDE_F`	Contrôle de non vide sur les fichiers du flux
`IRR_TYPE_F`	Contrôle de type et extension des fichiers
`IRR_SYNTAX`	Contrôle syntaxique des fichiers du flux
`IRR_TAILLE_PJ`	Contrôle de taille des PJ
`IRR_NOM_PJ`	Contrôle du nom des PJ
`IRR_VID_PJ`	Contrôle de PJ non vide
`IRR_EXT_DOC`	Contrôle de l’extension des PJ
`IRR_TAILLE_F`	Contrôle de taille max des fichiers
`IRR_ANTIVIRUS`	Contrôle anti-virus
`DEST_INC`	Destinataire inconnu
`ADR_ERR`	Adresse de facturation électronique erronée
`DOUBLON`	Facture en doublon
`CALCUL_ERR`	Erreur de calcul de la facture
`TX_TVA_ERR`	Taux de TVA erroné
`MONTANTTOTAL_ERR`	Montant total erroné

Default: REJ_SEMAN

Receiving

Receiving invoices and incoming status updates via Peppol is supported by the France app, but documentation is not yet available. It will be published ahead of the September 2026 mandate.

🇫🇷 Invopop resources for France


Compliance	Invoicing compliance in France Compliance timeline
Apps	Peppol ChorusPro France
Guides	ChorusPro Guide PA Guide Factur-X Guide
FAQ	France FAQ
GOBL	France Tax Regime Chorus Pro Addon French Factur-X Addon
GitHub	gobl.xinvoice

France FAQ

Find answers to frequently asked questions about invoicing in France →

Participate in our community

Ask and answer questions about invoicing in France →

Networks

Countries

Set-up

GOBL

Apps

API

Features

PA (Plateforme Agréée) Guide

Introduction

Prerequisites

Key Concepts

Registration workflow

Sending workflow

How it works

Workflow code

France PA send invoice workflow

Status update workflow

How it works

Using job arguments

Workflow code

France PA send status workflow

Available status codes

Reason codes by status

Receiving

France FAQ

Participate in our community

Networks

Countries

Set-up

GOBL

Apps

API

Features

​Introduction

​Prerequisites

​Key Concepts

​Registration workflow

​Sending workflow

​How it works

​Workflow code

France PA send invoice workflow

​Status update workflow

​How it works

​Using job arguments

​Workflow code

France PA send status workflow

​Available status codes

​Reason codes by status

​Receiving

France FAQ

Participate in our community

Introduction

Prerequisites

Key Concepts

Registration workflow

Sending workflow

How it works

Workflow code

Status update workflow

How it works

Using job arguments

Workflow code

Available status codes

Reason codes by status

Receiving