Skip to main content

Documentation Index

Fetch the complete documentation index at: https://invopop-mintlify-changelog-week-1778411791.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Introduction

In this guide, you’ll learn how to issue invoices to French public institutions using Chorus Pro. It will walk you through:
  1. Understanding Chorus Pro and its format requirements
  2. Setting up Invopop workflows:
    • Supplier registration workflow
    • Invoice submission workflow
  3. Preparing the Chorus Pro platform and creating credentials
  4. Registering a supplier with Chorus Pro
  5. Submitting your first invoice to a French public institution

​
What is Chorus Pro?

Chorus Pro is a mandatory service provided by the French government for invoicing French public institutions. The platform allows businesses to upload invoices in multiple e-invoicing formats and track them throughout the French public administration process. All invoices to French public sector entities must be submitted through Chorus Pro. The platform supports various e-invoicing formats including Cross Industry Invoice (CII), and implements the European Norm 16931 (EN16931) European standard for electronic invoicing with additional French-specific requirements.

​
Understanding Chorus Pro Format Requirements

Chorus Pro accepts invoices in CII format based on the EN16931 European standard. However, it adds specific French extensions and validation requirements: EN16931 Standard The EN16931 defines the semantic data model for electronic invoices. The standard ensures interoperability across European Union (EU) member states while allowing for country-specific extensions. Chorus Pro Extensions Chorus Pro extends the base EN16931 standard with additional French requirements:
  • SIRET number validation for French entities
  • Specific invoice types for different purposes
  • Service codes for government departments
In GOBL, these formats are handled via addons that you must add to each invoice. You’ll see examples of this further below.
-SandboxLive
SupplierTest Chorus Pro account (qualif.chorus-pro.gouv.fr)Real Chorus Pro account required
AccountsDownloadable CSV with test accounts—

​
Setup

Configure your Invopop Workspace for Chorus Pro invoicing. Complete these steps:
1

Connect the required apps

  1. Go to Configuration > Apps in the Console.
  2. Find UN/CEFACT CII in the app list and click Connect to activate the app.
  3. Find Chorus Pro in the app list and click Connect to activate the app.
After connecting, you’ll see both UN/CEFACT CII and Chorus Pro listed in the Enabled Apps section.
Chorus Pro app connected
2

Configure the supplier registration workflow

Add a new workflow to your workspace for registering suppliers. You can start with the template below.

Chorus Pro supplier registration workflow

This workflow will issue a registration request for a supplier to complete.
Keep the workflow ID at hand as you’ll need it later.
3

Configure invoice workflow

Add a new workflow to your workspace for issuing invoices. You can start with the template below.

Chorus Pro invoice workflow

This workflow will issue an invoice through Chorus Pro.
Keep the workflow ID at hand as you’ll need it later.

​
Chorus Pro Credentials

This section explains what suppliers need to configure within their Chorus Pro account to enable integration with Invopop. To configure Chorus Pro, complete these steps:
1

Create a Chorus Pro account

Sign up for a Chorus Pro account if you don’t have one.
To test in sandbox mode, create an account in the Chorus Pro sandbox. Download a CSV file with test accounts. Use one of the accounts to log in. For more information, visit the Chorus Pro documentation.
2

Navigate to API settings

Once logged in to your Chorus Pro account, navigate to the API configuration area:
  1. Go to Domains > Connections in the main menu
Navigate to Domains → Connections
  1. Click Access Service in the Technical Account section (bottom left)
Navigate to Technical Account
This opens a new page where you can manage your technical accounts.
3

Create a technical account

Set up the technical account credentials, this opens a form to create a technical account:
  • Set the type of request to Creation of a technical account
  • Select your company in the company field
  • This creates a login and password. Copy these credentials as you’ll need them when registering with Invopop
    Technical Account Creation
Click Submit to complete the setup
Return to Invopop for the next steps.

​
Running

Now you’ll learn how to register a supplier and issue Chorus Pro invoices:

​
Register a Supplier

Now that you have a technical account, you can register a supplier with Chorus Pro.
1

Upload a Supplier

Use the Create an entry endpoint to upload a new supplier. Include a party object in the data field. For this step, you only need the VAT number.After successful upload, you’ll see the supplier in the Parties section with status Empty.
Supplier registration in progress
2

Send the Supplier to the registration workflow

Send the supplier to the registration workflow using the Create a job endpoint. Use:
  • The supplier’s silo entry UUID from the previous step
  • The Supplier Registration workflow ID from the Setup section
This workflow generates a unique URL for the supplier to access and complete the registration process. The URL is stored in the supplier’s metadata.
Supplier registration in progress
3

Complete Chorus Pro Authentication

The workflow stays in progress until the supplier completes the registration process. The supplier must access the link and add the credentials they created previously.
Supplier registration in progress
The supplier’s status will change to Registered when authentication is complete.
You can fill the form via API by sending a PUT request to the registration link. The payload should be a JSON object with the following fields:
  • username (string): The supplier’s Chorus Pro username.
  • password (string): The supplier’s Chorus Pro password.

​
Send an Invoice

Once a supplier is registered, you can send invoices to French public institutions through Chorus Pro.
1

Create an Invoice

Use the Create an entry endpoint to create a new invoice. Include an invoice object in the data field.
In this example, we’re issuing a Chorus Pro invoice for business-to-government transactions in France. Chorus Pro is the mandatory platform for submitting invoices to French public sector entities.Notice:
  • the minimal version (chorus-pro-b2g.min.mdx) contains only the essential fields required to create the B2G invoice,
  • the fr-chorus-pro-v1 addon ensures the document will be validated using the Chorus Pro rules built into the GOBL library,
  • the customer must be a French public sector entity with a valid SIRET number,
  • specific Chorus Pro extensions and identifiers are required for public procurement (such as service codes and commitment numbers),
  • there are no totals or calculations in the minimal version; all these will be calculated automatically when running gobl build,
  • the built version (chorus-pro-b2g.mdx) shows the normalized document with calculated totals, line item sums, TVA breakdowns, and automatically generated fields,
  • the invoice will be formatted according to Chorus Pro requirements and submitted through the platform, and,
  • all invoices to French public entities above €25,000 must be submitted through Chorus Pro.
{
    "$schema": "https://gobl.org/draft-0/bill/invoice",
    "$regime": "FR",
    "$addons": [
        "eu-en16931-v2017",
        "fr-choruspro-v1"
    ],
    "uuid": "019783e7-33b1-7000-a1a5-6139e214b447",
    "type": "standard",
    "series": "SAMPLE",
    "code": "2345",
    "issue_date": "2025-06-18",
    "currency": "EUR",
    "supplier": {
        "name": "Provide One Inc.",
        "tax_id": {
            "country": "FR",
            "code": "43498927917"
        },
        "identities": [
            {
                "type": "SIRET",
                "code": "49892791768734"
            }
        ],
        "addresses": [
            {
                "num": "42",
                "street": "Calle Pradillo",
                "locality": "Madrid",
                "region": "Madrid",
                "code": "28002",
                "country": "ES"
            }
        ],
        "emails": [
            {
                "addr": "billing@example.com"
            }
        ]
    },
    "customer": {
        "name": "Sample Consumer",
        "tax_id": {
            "country": "FR",
            "code": "39356000000"
        },
        "identities": [
            {
                "type": "SIRET",
                "code": "35600000012345"
            }
        ],
        "addresses": [
            {
                "num": "1",
                "street": "Rue Sundacsakn",
                "locality": "Saint-Germain-En-Laye",
                "code": "75050",
                "country": "FR"
            }
        ],
        "emails": [
            {
                "addr": "email@sample.com"
            }
        ]
    },
    "lines": [
        {
            "i": 1,
            "quantity": "20",
            "item": {
                "name": "Development services",
                "price": "90.00",
                "unit": "h"
            },
            "sum": "1800.00",
            "discounts": [
                {
                    "reason": "Special discount",
                    "percent": "10%",
                    "amount": "180.00"
                }
            ],
            "taxes": [
                {
                    "cat": "VAT",
                    "rate": "standard"
                }
            ],
            "total": "1620.00"
        }
    ],
    "payment": {
        "advances": [
            {
                "description": "Paid in full",
                "percent": "100%",
                "amount": "1944.00"
            }
        ],
        "instructions": {
            "key": "card"
        }
    }
}
Review the example above. Notice that you need both the eu-en16931-v2017 and the fr-choruspro-v1 addon. These addons enable all the necessary validations in your GOBL invoice.
1

Send to Chorus Pro

Send the invoice to Chorus Pro using the Create a job endpoint. Use:
  • The invoice’s silo entry UUID from the previous step
  • The Chorus Pro Invoice workflow ID from the Setup section
The system generates a CII XML file with Chorus Pro extensions and submits it to the platform.
Invoice sent to Chorus Pro
2

Track Invoice Status

After submission, track your invoice in Chorus Pro using the invoice identifier (series plus code).
Chorus Pro allows document modifications after submission. If a document is rejected or contains errors, update the GOBL details and resubmit to the same workflow until the document is accepted. Once accepted, do not modify the invoice.
The invoice identifier in Chorus Pro corresponds to your GOBL invoice series and code combined. This identifier helps you locate and track invoices across both systems.

​
FAQ

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.
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.
Chorus Pro primarily supports CII format based on EN16931. Invopop currently focuses on CII with plans to add additional formats in the future.
French businesses need a SIRET number. Foreign businesses can use their local tax identifier, but should verify acceptance with the receiving French institution.
Yes, you can modify and resubmit invoices until the receiving institution accepts them. Once accepted, invoices become locked and cannot be modified.
Use your GOBL invoice series and code combined as the invoice identifier in the Chorus Pro portal to locate your submitted invoices.
Chorus Pro has specific file size and format requirements. Invopop handles these automatically when generating CII XML files from your GOBL invoices.
The recipient’s SIRET (or equivalent identifier) plus a Chorus Pro service code where applicable. Invopop generates EN 16931 CII XML by default — UBL is also accepted by Chorus Pro.
In countries where Peppol is the standard but not mandatory, you may still need to issue an e-invoice when the recipient isn’t on the network. Both parties can agree on an alternative transfer method, but the invoice must still be EN16931 compliant.Recommended approach:
  • Set up a separate workflow that generates the XML without the send-Peppol-document step
  • Or reuse your existing workflow without the customer Peppol ID — the send step is automatically skipped
  • Fetch the generated XML and deliver it through the agreed channel, typically email
B2C invoices typically lack the structured customer information required for Peppol delivery, and most consumers don’t have inboxes. Use a conditional workflow:
  1. Add an If/Else step that checks for a customer inbox using count(customer.inboxes, true) > 0.
  2. On the false branch, generate a PDF and email it to the customer, then stop the flow.
This routes B2B invoices through Peppol while keeping a smooth path for consumers.
If a job fails with KO and receiver not found in the peppol network, treat it like an invalid email address — the recipient simply isn’t reachable on Peppol. Add the Lookup Participant ID step (ideally in a separate validation workflow run against customer data) so you catch missing IDs before generating the invoice.
No. The regime is automatically derived from the supplier’s settings, which is the recommended approach for Peppol — leave it unset on the document.
See the oasis-ubl-v2 addon and the Peppol app reference for required fields, supported document types, and Participant ID schemes.
More available in our France FAQ section

Participate in our community

Ask and answer questions about invoicing in France →