Public sector invoicing in France

Invoices to French public entities (the State, local authorities, hospitals, public establishments) have had to go through Chorus Pro, the government’s invoicing portal, since 2020. Under the 2026 reform, Chorus Pro becomes one more platform on the French Directory, listed under its own matricule, so a public entity is simply a customer whose Annuaire line points to it. That is what makes B2G invoicing in Invopop the same as B2B invoicing. A B2G invoice is recorded like any other, its F1 copy and 200 Déposée status reach the PPF unchanged, and the same send workflow handles every customer. Only delivery differs: the invoice goes to Chorus Pro instead of Peppol. Invopop holds the connection with Chorus Pro, so there is nothing to register on the public portal. This guide covers:

Who this guide is for: French companies on the PA use this path; foreign entities use the standalone Chorus Pro app.
How routing works: the record step decides whether a customer is a public entity, and the workflow branches on it.
Setup: the send workflow with the public-sector branch.
What a public buyer needs: the SIRET, service code and commitment number, and the limits Chorus Pro adds on top of the norm.
Following the invoice: the Chorus Pro lifecycle and how the job reports it.
Receiving from a public entity (G2B): public bodies can now invoice you through the same channel.
Testing in sandbox and example invoices.

Who this guide is for

There are two ways to reach Chorus Pro through Invopop, and which one applies depends on the supplier, not the customer.

Supplier	Use	Why
French company with a SIREN, registered in the Annuaire through Invopop	This guide, with the France app	Invopop is the company’s Plateforme Agréée. Chorus Pro is reached through the PA connection, with the F1 copy reported to the PPF as the mandate requires.
Foreign entity without a French SIREN invoicing a French public body	The standalone Chorus Pro app and its supplier registration and issuing guides	A company outside the French mandate has no Annuaire line. It submits directly to Chorus Pro with its own Chorus Pro credentials.

Don’t combine the two. A French company that already uses the standalone Chorus Pro app should move its public-sector invoicing to the PA path described here, so that every domestic invoice is recorded and reported the same way.

-	Sandbox	Live
Supplier	Any party registered in the sandbox Annuaire	Party registered in the Annuaire through the registration guide
Chorus Pro	Qualification environment	Production
Annuaire	Qualification directory	Production directory

Prerequisites

A registered supplier: follow the registration guide to connect the France app and register the party in the Annuaire. The same registration serves B2B and B2G.
The public entity’s identifiers: its SIRET and, where the entity requires them, a service code and a commitment number. The public entity gives you these; see What a public buyer needs.
The invoicing guide: this page builds on the Invoicing in France guide and assumes you know how recording, formats and the PPF copy work.

How routing works

You do not mark an invoice as B2G yourself. When the Record outgoing document step records an invoice, it looks the customer up in the Annuaire. A customer whose line is routed to Chorus Pro’s public sphere, under matricule 9999, is a public entity, and the invoice is flagged b2g. The flag is only set while the line is in force, so a party that leaves Chorus Pro stops being B2G. The Is B2G? step then reads that flag and answers true or false, so the workflow can branch on it the same way it branches on Directory lookup:

Result	Meaning	Deliver with
`true`	The customer’s Annuaire line points to Chorus Pro	Send to Chorus Pro
`false`	Everything else	Send Peppol document

Keep Is B2G? after the record step, which is where the answer comes from. For a document that has not been recorded, the step asks the Annuaire directly. Everything after the branch is shared: both paths Forward document to PPF.

Record

The invoice is validated against the French rules, the customer is checked in the Annuaire, and the invoice is flagged b2g when the customer is a public entity. The Chorus Pro rules are applied at this point, so a breach is reported here rather than minutes later by Chorus Pro.

Is B2G?

Reads the flag and branches.

Send to Chorus Pro

Deposits the invoice with Chorus Pro and waits for its answer. The job stays queued until Chorus Pro has received the invoice and made it available to the public entity. See Following the invoice.

Forward document to PPF

Sends the F1 copy and the 200 Déposée status to the PPF, exactly as for a B2B invoice.

Setup

All of the following steps must be carried out from the Invopop Console. The PPF send document (public sector) template is the regular send workflow with the Is B2G? branch inserted after the record step. Use it in place of the regular one: it handles every customer, public or not, so you need only one send workflow.

PPF send document (public sector)

Add to my workspace →

Workflow
Code

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

PPF send document (public sector) workflow

{
    "name": "PPF send document (public sector)",
    "description": "Send an invoice via Chorus Pro or Peppol depending on the buyer, and record it with PPF",
    "app_id": "gov-fr",
    "country": "fr",
    "steps": [
        {
            "id": "067bc16d-c1a7-11f1-8390-4eb134dbe674",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            }
        },
        {
            "id": "067e5b0d-c1a7-11f1-a890-4eb134dbe674",
            "name": "Sign envelope",
            "provider": "silo.close"
        },
        {
            "id": "067e5bad-c1a7-11f1-a27a-4eb134dbe674",
            "name": "Document is an invoice?",
            "provider": "silo.if",
            "next": [
                {
                    "status": "NA",
                    "code": "true",
                    "steps": [
                        {
                            "id": "067e5bf8-c1a7-11f1-a34e-4eb134dbe674",
                            "name": "Generate UBL document",
                            "provider": "ubl.generate",
                            "summary": "Peppol France CIUS v1",
                            "config": {
                                "attach_invoice_pdf": false,
                                "doc_type": "peppol-fr-cius",
                                "private": false,
                                "validate_ubl": false
                            }
                        }
                    ]
                },
                {
                    "status": "NA",
                    "code": "false",
                    "steps": [
                        {
                            "id": "067e5c2f-c1a7-11f1-a517-4eb134dbe674",
                            "name": "Generate CDAR Status",
                            "provider": "cii.generate",
                            "summary": "France CTC Flow 6 CDAR (lifecycle status/payment)",
                            "config": {
                                "attach_invoice_pdf": false,
                                "doc_type": "fr-ctc-cdar-flow6",
                                "validate_cii": false
                            }
                        }
                    ]
                }
            ],
            "config": {
                "expr": "doc['$schema'] endsWith 'bill/invoice'",
                "scope": "env"
            }
        },
        {
            "id": "067e5c5e-c1a7-11f1-9b94-4eb134dbe674",
            "name": "Record outgoing document for e-invoicing",
            "provider": "gov-fr.directory.record.outgoing"
        },
        {
            "id": "067e5ddf-c1a7-11f1-aff3-4eb134dbe674",
            "name": "Is B2G?",
            "provider": "gov-fr.chorus-pro.lookup",
            "summary": "Chorus Pro for a public buyer, Peppol otherwise",
            "next": [
                {
                    "status": "NA",
                    "code": "true",
                    "steps": [
                        {
                            "id": "067e5daf-c1a7-11f1-a744-4eb134dbe674",
                            "name": "Send to Chorus Pro",
                            "provider": "gov-fr.chorus-pro.send",
                            "summary": "Deliver to the public sphere"
                        },
                        {
                            "id": "067e5d67-c1a7-11f1-875f-4eb134dbe674",
                            "name": "Forward document to PPF",
                            "provider": "gov-fr.directory.forward"
                        }
                    ]
                },
                {
                    "status": "NA",
                    "code": "false",
                    "steps": [
                        {
                            "id": "067e5c7f-c1a7-11f1-96f3-4eb134dbe674",
                            "name": "Verify document can be sent",
                            "provider": "peppol.validate.endpoint",
                            "next": [
                                {
                                    "code": "true",
                                    "steps": [
                                        {
                                            "id": "067e5ca2-c1a7-11f1-a3ed-4eb134dbe674",
                                            "name": "Send Peppol document",
                                            "provider": "peppol.send"
                                        },
                                        {
                                            "id": "067e5cc1-c1a7-11f1-99dd-4eb134dbe674",
                                            "name": "Forward document to PPF",
                                            "provider": "gov-fr.directory.forward"
                                        }
                                    ]
                                },
                                {
                                    "code": "false",
                                    "steps": [
                                        {
                                            "id": "067e5ce6-c1a7-11f1-81bc-4eb134dbe674",
                                            "name": "Forward document to PPF",
                                            "provider": "gov-fr.directory.forward",
                                            "summary": "Forward to PPF (déposée – non transmise)",
                                            "config": {
                                                "not_transmitted": true
                                            }
                                        }
                                    ]
                                }
                            ]
                        }
                    ]
                }
            ]
        },
        {
            "id": "067e5d0b-c1a7-11f1-af09-4eb134dbe674",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `completed`{.state .completed}",
            "config": {
                "state": "completed"
            }
        }
    ],
    "rescue": [
        {
            "id": "067e6072-c1a7-11f1-ba65-4eb134dbe674",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

The recommended approach for running jobs is to perform two steps: first upload the document to the silo, then create a job.

The workflow is shared with status documents. The Is B2G? step resolves a status or payment to the invoice it answers, so it follows the same channel as that invoice.

What a public buyer needs

A B2G invoice is a regular fr-ctc-flow2-v1 invoice. Chorus Pro needs a few more things on it to find the public entity and route the invoice to the right department.

Data	GOBL field	Notes
Customer SIRET	`customer.identities[]` with `type` `SIRET`	Chorus Pro identifies public entities by SIRET, not SIREN. The add-on tags it with ISO scheme `0009` and derives the SIREN. Rule `BR-FR-CPRO-10`.
Supplier SIRET	`supplier.identities[]` with `type` `SIRET`	Same reason. A supplier giving only a SIREN is refused by Chorus Pro (`BR-FR-CPRO-09`).
Service code (code service, also called code routage)	`customer.identities[]` with `key` `private-id`	The department within the public entity. Many entities require it; the add-on tags it with scheme `0224`.
Commitment number (numéro d’engagement juridique)	`ordering.purchases[0].code`	The purchase order reference, BT-13. Required by entities that work with commitments. 50 characters or fewer.
Contract reference (numéro de marché)	`ordering.contracts[0].code`	BT-12. 50 characters or fewer.
Billing mode	`tax.ext.fr-ctc-billing-mode`	As for B2B. `S3` (subcontracting with direct payment) is specific to public contracts and not yet supported.

Ask the public entity which of the service code and commitment number it requires. Chorus Pro publishes each entity’s requirements, and an invoice missing a required one is rejected by Chorus Pro after deposit.

Invopop cannot yet check whether a given public entity requires a service code or a commitment number, because the Annuaire does not carry that information. Collect it from the buyer when you take the order.

Rules checked at record

Chorus Pro adds its own management rules on top of the norm, BR-FR-CPRO-01 to 50, and they apply only to invoices bound for the public sphere. None of them is covered by the standard schematrons, so without a local check the first time you hear of a breach is Chorus Pro’s rejection, which names a rule but not the field. Once an invoice is flagged b2g, the record step enforces the rules below and reports every breach at once, so a single round of fixes is enough.

Group	Rules	What is checked
Length caps	`02`, `14`, `15`, `30`–`37`, `39`, `41`–`44`	Invoice number and preceding invoice reference 20 characters; contract, purchase order and supporting document references 50; party names and trade names 99; address line and city 400; notes, item descriptions and payment terms 1024; attachment file names 50
Identifiers	`09`, `10`, `17`	Supplier, customer and payee each give a SIRET
Cardinality	`19`, `20`, `26`, `27`	Fewer than one million lines, one preceding invoice reference, one contact per party
Payment	`48`, `49`	IBAN of exactly 27 characters, counted as written, so no spaces; BIC of 8 to 11 characters
Billing framework	`24`, `47`	`S5` is refused, as are the multi-vendor modes `B8`, `S8` and `M8`

The IBAN rule is the one that catches most people. Chorus Pro counts the IBAN as written, so FR76 3000 6000 0112 3456 7890 189 is 33 characters and is refused. Write it without spaces. Rules that depend on data Invopop does not hold (whether the entity requires a service code or commitment number, 11 to 13), that the norm itself marks as unverifiable, or that turn on the S3 billing mode are not checked locally and remain enforced by Chorus Pro.

Following the invoice

Send to Chorus Pro deposits the invoice and then waits. Chorus Pro first acknowledges the deposit as a whole, then walks the invoice through its own lifecycle, which is richer than the PPF’s accepted or rejected pair. Invopop keeps the codes as Chorus Pro sends them, so the workflow and the France dashboard show the same vocabulary as the Chorus Pro portal.

Answer	Meaning	Job
Receipt `500`	The deposit was readable and accepted for processing	Keeps waiting
Receipt `501`	The deposit was irrecevable: a file Chorus Pro could not read. The invoice never entered a lifecycle	KO
202 Reçue	Chorus Pro has received the invoice	Keeps waiting
203 Mise à disposition	The invoice is available to the public entity	OK
204 Prise en charge, 205 Approuvée	The entity is processing or has approved it	OK
208 Suspendue	The entity needs more information	Keeps waiting
209 Complétée	The missing information was supplied	OK
210 Refusée, 213 Rejetée	Refused by the entity, or rejected by Chorus Pro’s own checks	KO
211 Mandatée, 212 Mise en paiement	Payment ordered, then paid	OK

The job completes as soon as Chorus Pro has made the invoice available (203) or any later code arrives. Later statuses keep updating the invoice after the job has finished, and each is visible on the invoice in the France dashboard. Chorus Pro does not always deliver statuses in the order it applied them, so the invoice keeps whichever carries the latest timestamp. A 213 from Chorus Pro names the rule that failed. If it is one of the rules checked at record, the invoice was flagged b2g after the fact; otherwise fix the field the rule names and send a new invoice.

For an invoice you issued, the public entity drives the lifecycle through Chorus Pro. Statuses you build on such an invoice are not forwarded: Chorus Pro rules on the invoices it receives, and Invopop does not answer them. Statuses you send only travel to Chorus Pro for invoices a public entity sent to you, described next.

Receiving from a public entity (G2B)

G2B is the same exchange in reverse: a French public entity issues an invoice to your business. It is new with the 2026 reform. Public bodies previously had no route to invoice the private sector electronically. The path differs from a B2B invoice in where it comes from, not in what you do with it:

The public entity submits the invoice to Chorus Pro, in UBL or Factur-X.
Chorus Pro delivers it to Invopop, addressed to the Annuaire line your party is registered under. That line decides which workspace receives it, so the party must be registered before any public entity can invoice it.
Receive document from Chorus Pro converts it to GOBL and hands it to your receive workflow, which records it against your party with the same controls as an inbound Peppol invoice.

From there it behaves like any other received invoice: it appears in the France dashboard, and you answer with status updates as it is accepted, disputed or paid. Build each status as you would for a B2B invoice and run it through the send workflow. Is B2G? resolves it to the invoice it answers, and Send to Chorus Pro deposits it on the public circuit. The statuses you send back follow the AFNOR norm rather than Chorus Pro’s own vocabulary. Chorus Pro translates its internal codes before they reach you, so a rejection arrives as 210 and its own motifs arrive as their AFNOR equivalents.

Testing in sandbox

A sandbox workspace delivers B2G invoices to Chorus Pro’s qualification environment, and the record step reads the qualification Annuaire to decide whether a customer is a public entity. Both are separate from production, so a public entity you find in the production Annuaire is unknown there, and the invoice routes to Peppol instead. To exercise the Chorus Pro branch in sandbox, use a customer registered as a public entity in the qualification Annuaire. Contact us for test buyer details if you don’t have any.

Example invoices

PA B2G invoice (public buyer)

An invoice from a French company to a French public entity. It uses the same fr-ctc-flow2-v1 add-on as a domestic B2B invoice, with the data Chorus Pro needs on top.Notice:

both parties give a SIRET identity, which the add-on tags with iso-scheme-id 0009 and from which it derives the SIREN,
the customer carries a private-id identity with the public entity’s service code, which the add-on tags with scheme 0224,
ordering.purchases[0].code holds the numéro d’engagement juridique and ordering.contracts[0].code the contract reference, each 50 characters or fewer,
the invoice number is 20 characters or fewer and the IBAN is written as 27 characters without spaces, as Chorus Pro requires.

{
    "$schema": "https://gobl.org/draft-0/bill/invoice",
    "$regime": "FR",
    "$addons": [
        "fr-ctc-flow2-v1"
    ],
    "type": "standard",
    "series": "FAC",
    "code": "2026-00042",
    "issue_date": "2026-10-14",
    "currency": "EUR",
    "tax": {
        "ext": {
            "fr-ctc-billing-mode": "S1",
            "untdid-document-type": "380"
        }
    },
    "supplier": {
        "name": "Fournisseur Example SARL",
        "tax_id": {
            "country": "FR",
            "code": "732829320"
        },
        "identities": [
            {
                "type": "SIRET",
                "code": "73282932000009"
            }
        ],
        "inboxes": [
            {
                "key": "peppol",
                "scheme": "0225",
                "code": "732829320"
            }
        ],
        "addresses": [
            {
                "num": "123",
                "street": "Rue de la Paix",
                "locality": "Paris",
                "code": "75001",
                "country": "FR"
            }
        ],
        "emails": [
            {
                "addr": "facturation@fournisseur.fr"
            }
        ]
    },
    "customer": {
        "name": "Commune Example",
        "tax_id": {
            "country": "FR",
            "code": "356000000"
        },
        "identities": [
            {
                "type": "SIRET",
                "code": "35600000000006"
            },
            {
                "key": "private-id",
                "code": "SERVICE01"
            }
        ],
        "addresses": [
            {
                "num": "1",
                "street": "Place de la Mairie",
                "locality": "Example",
                "code": "75002",
                "country": "FR"
            }
        ],
        "inboxes": [
            {
                "key": "peppol",
                "scheme": "0225",
                "code": "356000000"
            }
        ]
    },
    "ordering": {
        "purchases": [
            {
                "code": "EJ2026-0001"
            }
        ],
        "contracts": [
            {
                "code": "MARCHE-2026-12"
            }
        ]
    },
    "lines": [
        {
            "quantity": "10",
            "item": {
                "name": "Prestation de conseil",
                "price": "150.00",
                "unit": "h"
            },
            "taxes": [
                {
                    "cat": "VAT",
                    "rate": "standard"
                }
            ]
        }
    ],
    "payment": {
        "terms": {
            "key": "due-date",
            "due_dates": [
                {
                    "date": "2026-11-13",
                    "percent": "100%"
                }
            ]
        },
        "instructions": {
            "key": "credit-transfer",
            "credit_transfer": [
                {
                    "iban": "FR7630006000011234567890189",
                    "bic": "AGRIFRPP"
                }
            ]
        }
    }
}

{
	"$schema": "https://gobl.org/draft-0/bill/invoice",
	"$regime": "FR",
	"$addons": [
		"eu-en16931-v2017",
		"fr-ctc-flow2-v1"
	],
	"type": "standard",
	"series": "FAC",
	"code": "2026-00042",
	"issue_date": "2026-10-14",
	"currency": "EUR",
	"tax": {
		"rounding": "currency",
		"ext": {
			"fr-ctc-billing-mode": "S1",
			"untdid-document-type": "380"
		}
	},
	"supplier": {
		"name": "Fournisseur Example SARL",
		"tax_id": {
			"country": "FR",
			"code": "44732829320"
		},
		"identities": [
			{
				"type": "SIRET",
				"code": "73282932000009",
				"ext": {
					"iso-scheme-id": "0009"
				}
			},
			{
				"scope": "legal",
				"type": "SIREN",
				"code": "732829320",
				"ext": {
					"iso-scheme-id": "0002"
				}
			}
		],
		"endpoints": [
			{
				"uri": "iso6523-actorid-upis::0225:732829320"
			}
		],
		"inboxes": [
			{
				"key": "peppol",
				"scheme": "0225",
				"code": "732829320"
			}
		],
		"addresses": [
			{
				"num": "123",
				"street": "Rue de la Paix",
				"locality": "Paris",
				"code": "75001",
				"country": "FR"
			}
		],
		"emails": [
			{
				"addr": "facturation@fournisseur.fr"
			}
		]
	},
	"customer": {
		"name": "Commune Example",
		"tax_id": {
			"country": "FR",
			"code": "39356000000"
		},
		"identities": [
			{
				"type": "SIRET",
				"code": "35600000000006",
				"ext": {
					"iso-scheme-id": "0009"
				}
			},
			{
				"key": "private-id",
				"code": "SERVICE01",
				"ext": {
					"iso-scheme-id": "0224"
				}
			},
			{
				"scope": "legal",
				"type": "SIREN",
				"code": "356000000",
				"ext": {
					"iso-scheme-id": "0002"
				}
			}
		],
		"endpoints": [
			{
				"uri": "iso6523-actorid-upis::0225:356000000"
			}
		],
		"inboxes": [
			{
				"key": "peppol",
				"scheme": "0225",
				"code": "356000000"
			}
		],
		"addresses": [
			{
				"num": "1",
				"street": "Place de la Mairie",
				"locality": "Example",
				"code": "75002",
				"country": "FR"
			}
		]
	},
	"lines": [
		{
			"i": 1,
			"quantity": "10",
			"item": {
				"name": "Prestation de conseil",
				"price": "150.00",
				"unit": "h"
			},
			"sum": "1500.00",
			"taxes": [
				{
					"cat": "VAT",
					"key": "standard",
					"rate": "general",
					"percent": "20%",
					"ext": {
						"untdid-tax-category": "S"
					}
				}
			],
			"total": "1500.00"
		}
	],
	"ordering": {
		"contracts": [
			{
				"code": "MARCHE-2026-12"
			}
		],
		"purchases": [
			{
				"code": "EJ2026-0001"
			}
		]
	},
	"payment": {
		"terms": {
			"key": "due-date",
			"due_dates": [
				{
					"date": "2026-11-13",
					"amount": "1800.00",
					"percent": "100%"
				}
			]
		},
		"instructions": {
			"key": "credit-transfer",
			"credit_transfer": [
				{
					"iban": "FR7630006000011234567890189",
					"bic": "AGRIFRPP"
				}
			],
			"ext": {
				"untdid-payment-means": "30"
			}
		}
	},
	"totals": {
		"sum": "1500.00",
		"total": "1500.00",
		"taxes": {
			"categories": [
				{
					"code": "VAT",
					"rates": [
						{
							"key": "standard",
							"ext": {
								"untdid-tax-category": "S"
							},
							"base": "1500.00",
							"percent": "20%",
							"amount": "300.00"
						}
					],
					"amount": "300.00"
				}
			],
			"sum": "300.00"
		},
		"tax": "300.00",
		"total_with_tax": "1800.00",
		"payable": "1800.00"
	},
	"notes": [
		{
			"key": "payment",
			"text": "Conditions de paiement selon les conditions générales de vente.",
			"ext": {
				"untdid-text-subject": "PMT"
			}
		},
		{
			"key": "payment-method",
			"text": "Pénalités et indemnités de retard applicables conformément aux conditions générales de vente.",
			"ext": {
				"untdid-text-subject": "PMD"
			}
		},
		{
			"key": "payment-term",
			"text": "Aucun escompte n'est accordé pour paiement anticipé.",
			"ext": {
				"untdid-text-subject": "AAB"
			}
		}
	]
}

FAQ

Invoicing questions

How do I configure my workspace for French invoicing?

Two channels depending on the recipient: B2G uses Chorus Pro (CII format); B2B from September 2026 uses the Plateforme Agréée model (UBL, CII, or Factur-X via Peppol). Invopop is an approved PA — install the France PA app for B2B and the Chorus Pro app for B2G.

How can I view an XML attached to a PDF?

In Factur-X PDFs, the XML file is embedded within the PDF itself. To extract and view it, use the Attachments section in Adobe Acrobat Reader, or a tool like the SysTools PDF Extractor.

Is Invopop ready for the September 2026 mandate?

Invopop is an officially approved Plateforme Agréée under the DGFiP mandate. Registration, invoicing, and lifecycle status are available today; e-reporting (Flow 10) is in active development. See the PA hub readiness matrix for the current state.

What GOBL addons are required for France PA?

The base FR tax regime plus the EN 16931 profile. For Peppol delivery, peppol-bis-v3. The forthcoming fr-ctc-flow10-v1 addon covers e-reporting payloads — separate from the e-invoicing flow.

Is a self-billed invoice a different document type in France?

No. Most Peppol countries treat self-billing as a document type of its own, but France models it as a standard invoice with the untdid-document-type extension set to 389. In GOBL you never set the code yourself: add the self-billed tag and the fr-ctc-flow2-v1 add-on applies it automatically. See Self-billing for the full flow.

Why was my VAT-exempt invoice never sent to the PPF?

Transactions exempt under articles 261 to 261 E of the CGI — insurance, medical care, education and the rest of that range — sit outside the e-invoicing mandate, and the PPF rejects them if you deposit one. When an invoice’s whole VAT breakdown is exempt and carries a VATEX-FR-CGI261* code, Invopop records it but sends no F1 and raises no lifecycle status, and the dashboard shows it as Exempt. Keep issuing the invoice to your customer as usual. An invoice that mixes exempt and taxable lines is still sent normally, and so is VATEX-FR-FRANCHISE. See VAT-exempt invoices.

How many pops does a B2B e-invoice through France PA cost?

Each invoice or lifecycle status sent through France PA costs 5 pops: 1 pop for the conversion to UBL/CII, 2 pops to send it over Peppol, 1 pop to forward it to the PPF, and 1 pop for the silo entry. See Pops & pricing for how pops work.

What does the record document step check against the Annuaire?

Before an invoice is recorded, the PPF record document step looks up both the supplier and the customer SIREN in the Annuaire. What each party must satisfy depends on the workflow’s role:

Role	Annuaire state	Outcome
Both	The SIREN has no effective entry	Rejected
Receiving	The SIREN has at least one effective entry	Accepted
Sending	The SIREN’s only entry is the PPF’s default line (matricule `9998`)	Accepted
Sending	The party’s `0225` peppol endpoint matches one of the SIREN’s entries	Accepted
Sending	The party’s `0225` peppol endpoint matches none of the SIREN’s entries	Rejected

Sandbox invoices skip the Annuaire check entirely.

What should I do if the customer isn't registered in the Annuaire?

Don’t block the sale. An exchange where only one party has an effective Annuaire entry is a non-regulated flow: it leaves e-invoicing (flux 2) and is covered by e-reporting (flux 10) instead.In practice:

Run a Directory lookup against the customer’s SIREN before you generate the invoice — ideally in a separate validation workflow run against customer data, so you can prompt them to fix their registration ahead of time.
If the SIREN has no effective entry, route the invoice through your reporting workflow rather than the PA send workflow.
If it slips through, the send workflow degrades rather than failing: the Verify document can be sent step branches and forwards the invoice to the PPF as déposée – non transmise.

A missing entry is common and not necessarily an error. A SIREN visible in the public annuaire-entreprises registry is not the same as an effective entry in the DGFiP Annuaire, which only covers entities in scope of the mandate. It can also be absent because the buyer hasn’t yet appointed a PA, or because their tax records don’t match.

Should I check the Annuaire at order time or at invoice time?

Both, for different reasons. A lookup at order or onboarding time is a data-quality check: it lets you warn the customer and get their SIREN or PA sorted before invoicing. A lookup at invoice time is the one that decides the flow, because registrations are added and withdrawn continuously and a party found at checkout may no longer be routable days later (and vice versa).Treat the early result as advisory, resolve again at generation, and store the resolved electronic address on the transaction — the routing address isn’t always the bare SIREN. See Directory lookup.

How do I know whether an invoice is B2G?

You don’t decide it yourself. When the invoice is recorded, Invopop looks the customer up in the Annuaire: a party whose line is routed to Chorus Pro is a public entity, and the invoice is marked B2G. The Is B2G? workflow step reads that answer and branches to Send to Chorus Pro instead of Peppol. See the public sector guide.

Do I need a Chorus Pro account to invoice French public entities?

Not if your company has a French SIREN and is registered in the Annuaire through Invopop. Invopop holds the connection with Chorus Pro, so B2G invoices use the same send workflow as any other French invoice. Only foreign entities without a French SIREN still go through the standalone Chorus Pro app, which requires Chorus Pro credentials.

Where do I put the service code and the numéro d'engagement on a B2G invoice?

The service code (code service or code routage) is a private-id identity on the customer, and the commitment number (numéro d’engagement juridique) is the purchase order reference in ordering.purchases[0].code. Both are supplied by the public entity. The public sector guide lists every field.

Receiving questions

How do I import received invoices in France?

Register the recipient with Invopop as their Plateforme Agréée. Inbound documents (UBL, CII, Factur-X) are converted to GOBL and stored in the Expenses folder. Chorus Pro inbound flow is separate and routes via the Chorus Pro app.

How does Invopop convert received French invoices into GOBL?

UBL via gobl.peppol; CII and Factur-X via gobl.cii. The original structured XML (or PDF/A-3 with embedded XML) is preserved as a silo entry attachment.

How do I import received invoices via France PA?

Register the recipient via Invopop as their PA. Inbound UBL/CII/Factur-X documents are routed to the configured Import workflow and become GOBL silo entries. Lifecycle status updates (CDAR) feed back to the issuer through the same channel.

What format do received France PA invoices arrive in?

UBL, CII, or Factur-X (PDF with embedded CII XML), all conforming to EN 16931 and the French CTC profile. Invopop preserves the original and exposes the GOBL conversion.

Can I receive invoices at more than one platform (PDP) for the same company?

Yes. A single company can be reachable at several destinations by registering different routing identifiers (electronic addresses) in the Annuaire — one per PDP or inbox. Invoices addressed to a given identifier are delivered to the platform registered against it, so you can route some invoices to Invopop and others to a different PDP (for example a travel-and-expense tool) for the same SIREN.The Annuaire supports several address formats that map to increasingly granular destinations within the same company:

SIREN — the company as a whole.
SIREN_SIRET — a specific establishment.
SIREN_SIRET_ROUTINGCODE — a site, department, or workflow within an establishment.
SIREN_SUFFIX — a custom routing suffix.

Give each PDP or inbox a distinct identifier and share the matching address with each issuer, so their invoices reach the intended destination. You can look up an electronic address in the Annuaire to confirm where it currently routes.

What is checked before a received invoice is recorded?

An invoice arriving from another platform goes through three controls, run in the order the PPF applies them:

Syntax — the invoice XML against the Flux 2 schematron for its syntax.
Addressing — both parties carry a SIREN registered in the Annuaire, the transport addresses belong to the parties the invoice names, and the invoice is addressed to a party registered in your workspace.
Unicity — the invoice is not already recorded for this party, number and year.

An invoice that passes every control is recorded on the receiving side. Only invoices are validated this way; incoming lifecycle statuses are simply recorded.

What reason does a rejected invoice come back with?

Each control rejects under its own CDAR motif, carried on the 213 Rejetée status returned to the platform that sent the invoice:

REJ_SEMAN — rejet pour erreur sémantique, when the invoice fails the Flux 2 schematron.
ADR_ERR — adresse de facturation électronique erronée, when the addressing control fails.
REJ_UNI — rejet sur contrôle unicité, when the invoice is already recorded.

More available in our France FAQ section

🇫🇷 Invopop resources for France


Compliance	Invoicing compliance in France Compliance timeline
Apps	France Peppol Chorus Pro France
Guides	Chorus Pro — Supplier registration · Issuing invoices PA Guide — Registration · Invoicing · Status · Reporting · Public sector
FAQ	France FAQ
GOBL	France Tax Regime Chorus Pro Addon French Factur-X Addon
GitHub	gobl.xinvoice

Participate in our community

Ask and answer questions about invoicing in France →

Networks

Countries

Set-up

GOBL

Apps

API

Features

Public sector invoicing in France

Who this guide is for

Prerequisites

How routing works

Setup

PPF send document (public sector)

What a public buyer needs

Rules checked at record

Following the invoice

Receiving from a public entity (G2B)

Testing in sandbox

Example invoices

FAQ

Participate in our community

​Who this guide is for

​Prerequisites

​How routing works

​Setup

PPF send document (public sector)

​What a public buyer needs

​Rules checked at record

​Following the invoice

​Receiving from a public entity (G2B)

​Testing in sandbox

​Example invoices

​FAQ

Participate in our community

Who this guide is for

Prerequisites

How routing works

Setup

What a public buyer needs

Rules checked at record

Following the invoice

Receiving from a public entity (G2B)

Testing in sandbox

Example invoices

FAQ