Submit an electronic invoice to the French public sector via the Chorus Pro API (PISTE)
domain: government-tax · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm Chorus Pro applicability: it is described by the operating agency (AIFE) as 'la solution mutualisée de facturation électronique qui a été mise en place pour tous les fournisseurs de la sphère publique afin de répondre aux obligations fixées par l'ordonnance du 26 juin 2014', and it replaced the earlier Chorus Factures system in September 2016.
Check your mandate date against the ordinance's staged rollout: 1 January 2017 for large enterprises (over 5,000 employees) and public entities, 1 January 2018 for intermediate-size enterprises (250–5,000 employees), 1 January 2019 for SMEs (10–250 employees), and 1 January 2020 for micro-enterprises (fewer than 10 employees).
Register on the PISTE platform (Plateforme d'Intermédiation des Services pour la Transformation de l'Etat), described as the single entry point that 'mutualise les services API... de l'Etat et de la sphère publique' and that exposes the Chorus Pro electronic-invoicing API alongside other public-sector APIs.
Connect first to the Chorus Pro Qualification environment and run your technical integration tests there — the AIFE states this step 'est indispensable avant de se raccorder en production' (is essential before connecting to production).
Once qualification tests pass, switch your API calls to the Chorus Pro production endpoint to submit invoices, track their processing status, and retrieve payment returns for the public-sector recipient.
Known gotchas
Chorus Pro supports multiple submission channels (manual entry, PDF/Factur-X deposit, EDI, and API) — API integration is only one option, so confirm with the receiving public entity which channel it expects before building the connector.
The Qualification and Production Chorus Pro portals are separate environments with separate connection setup; credentials and raccordement requests made in Qualification do not carry over automatically to Production.
PISTE also fronts other public APIs (e.g., DUME, Légifrance); make sure your API subscription/habilitation request on PISTE is scoped specifically to the Chorus Pro API rather than a different catalog entry.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?