Documentation Index
Fetch the complete documentation index at: https://docs.invopop.com/llms.txt
Use this file to discover all available pages before exploring further.
Use case: B2C sales and cross-border B2B — any transaction outside the regulated e-invoicing flow. Records accumulate locally and are submitted to the PPF on a periodic cadence.
fr-ctc-flow10-v1 add-on, distinct from the fr-ctc-flow2-v1 add-on used for e-invoicing. Both invoice and payment data are reported.
Registration
Reporting is registered at the SIREN level as part of the party registration workflow. The registration step captures two things and reuses them for every report submitted afterwards:- The SIREN. Invopop opens an internal record keyed by SIREN. Every invoice and payment recorded later is attached to and aggregated under this record.
- The reporting cadence. Invoice and payment data have separate schedules, and the cadence is determined by the party’s VAT regime — pick the one that matches.
Cadence — invoice and transaction data
| VAT regime | Period | Submit to PPF |
|---|---|---|
| Monthly Actual | Ten-day periods (1–10, 11–20, 21–end) | 10 days after each period |
| Quarterly Actual | Monthly | 10th of the following month |
| Simplified VAT | Monthly | Between 25th and 30th of the following month |
| Non-Established Taxpayer | Bimonthly | Between 25th and 30th of the following month |
Cadence — payment data
| VAT regime | Period | Submit to PPF |
|---|---|---|
| Monthly Actual | Monthly | 10th of the following month |
| Quarterly Actual | Monthly | 10th of the following month |
| Simplified VAT | Monthly | Between 25th and 30th of the following month |
| Non-Established Taxpayer | Bimonthly | Between 25th and 30th of the following month |
Recording
Send each invoice or payment through a recording workflow. The singleRecord for Reporting step stores the document against the registered SIREN and queues it for the next periodic report. B2C sales and foreign B2B transactions both go through the same step — only the invoice context differs.
Periodic submission
A second workflow generates and submits the report. It is triggered automatically by the cadence chosen at registration — if recorded data exists for the period when the cadence fires, Invopop builds the report and sends it to the PPF without any manual intervention.Corrective reports
When a previously submitted period needs to change — a wrong amount, a missing transaction, an invoice that should not have been included — trigger a corrective report. It runs the sameGenerate Report and Send Report to PPF steps but is scoped to the period being amended rather than the current one.
🇫🇷 Invopop resources for France
🇫🇷 Invopop resources for France
| Compliance | Compliance timeline |
| Apps | |
| Guides | ChorusPro Guide PA Guide — Registration · Invoicing · Status · Reporting |
| FAQ | France FAQ |
| GOBL | |
| GitHub | gobl.xinvoice |