Skip to main content
E-reporting covers everything that is out of scope for regulated e-invoicing (B2C sales, cross-border B2B, and any flow where one party is not registered in the Annuaire). Instead of routing each invoice individually, you record each invoice and payment, Invopop generates a Flux 10 XML for each reporting window, and sends it to the PPF. Reports use the fr-ctc-flow10-v1 add-on.

Sub-flows

Each recorded document is classified into one of four sub-flows based on supplier and customer SIREN:

Recording workflow

Every invoice and payment that requires reporting goes through a single Record workflow. The action looks at the supplier and customer SIRENs and files the document into the right sub-flow (10.1 to 10.4) ready for the next report.

PPF record document for reporting

Add to my workspace →

Payments

For 10.2 international B2B payments set lines[i].document on the payment to the invoice it settles. The minimum reference is the invoice number and issue date:
This is what tells the record action to file the payment as 10.2 (international B2B payment) rather than 10.4 (domestic B2C payment), and allows GOBL to allocate the cashed amount across the invoice’s VAT rates for you. For B2C payments (10.4), specify the tax breakdown directly on the payment line:

Exemption reasons

Lines using exempt, reverse-charge, intra-community, export, or outside-scope rates must include a free-text reason. Add it to the invoice’s tax block:
The key must match the rate used on the line. Lines on standard or zero rates do not need a note.

Submitting reports

A separate workflow bundles the records for a closed reporting window into a single Flux 10 report and sends it to the PPF. Invopop runs it automatically on the cadence set by the VAT regime — you do not need to trigger it.

PPF generate and send reporting document

Add to my workspace →
Tell Invopop which workflow to run on the schedule: in the Apps view, open the France app, click Configure to open the configuration sidebar, and select this workflow under Reporting Workflow.
France app configuration sidebar with the Reporting Workflow selector

Selecting the reporting workflow in the France app configuration sidebar

You can also trigger this workflow manually against any registered party — useful for testing, or to bring a party up to date after onboarding.

Picking a VAT regime at supplier registration

If you have a single supplier, or all your suppliers have the same cadence, you can configure the Register party for reporting step in the PPF register supplier workflow to a specific cadence. For multiple suppliers (whitelabel use cases) where different suppliers have different cadence, pass it as a job argument with key vat-regime when creating the job. When not stated, the default is real_normal_monthly. The cadence must match the regime registered with the tax office. If in doubt, check with your local accountant.

Reading submitted transactions

The France dashboard’s Transactions Flow 8 / 9 tab lists every document submitted for e-reporting. In the Console, open the Apps view, select the France app, and switch to the Transactions Flow 8 / 9 tab. The tab shows one sub-flow at a time: the Flow type filter is always active, defaults to International B2B invoices (10.1), and switches between the four sub-flows. It can be changed but not cleared. Each row shows the Document code and Document date, when it was Recorded, whether a report already covers it (Generated report), the Supplier SIREN, the *low type, the Role (Seller or Buyer; domestic B2C rows carry no role), the Silo entry, and the amounts the report will carry: Currency, Taxable total, Tax total (EUR), Amount (EUR), and FX rate, plus the counterparty identification and, on B2C rows, the category code.
Clicking on the Generated report column opens the Reporting Flow 10 tab filtered to that report. A dash means the row is still waiting for its reporting window to close.
Filter the table by Document code, Supplier SIREN, Flow type, or the Recorded date range.

Reading generated reports

The Reporting Flow 10 tab lists the generated Flow 10 XML reports. Each row shows the Reporting period the report covers, the SIREN, the Kind (Transactions for invoice data, Payments for payment data), the Role of the stream (Seller, Buyer), the submission Status, the report Sequence number, the PPF Ack ref, the Submitted at timestamp, and the Period ID. Click options on this tab:
Clicking Download fetches the exact XML submitted to the PPF, the same payload the /xml endpoint returns.
Filter the table by SIREN, Period ID, the Reporting period window, or Kind.

Reading what’s filed

Four read endpoints expose submission status and the raw report XML, all scoped to the party’s silo entry id: GET /v1/reports/:silo_entry_id
Summary per kind (current window, next deadline, last filed report)
GET /v1/reports/:silo_entry_id/periods
Paginated history of filed periods (filter with ?kind=tx or ?kind=py)
GET /v1/reports/:silo_entry_id/periods/:period_id
A single period’s metadata
GET /v1/reports/:silo_entry_id/periods/:period_id/xml
The raw report XML sent to the PPF

FAQ

For TVA, file via DGFiP’s portal — Invopop does not generate CA3 yet. For e-reporting (Flow 10): submit via your Plateforme Agréée — Invopop’s e-reporting workflow batches transactions per period and submits to the PPF.
TVA: DGFiP’s EDI-TVA XML schema. E-reporting Flow 10: a structured JSON/XML payload defined by the PPF specification (currently in beta). Invopop emits Flow 10 via the upcoming fr-ctc-flow10-v1 GOBL addon.
Flow 10 e-reporting: 3× per month (every 10 days) for B2C and cross-border transactions. Lifecycle status (CDAR): per event, near real-time. Specific deadlines depend on the supplier’s tax filing cadence (monthly/quarterly).
Flow 10 uses a JSON envelope wrapping aggregated transaction data, defined in the PPF technical specification. Lifecycle CDAR payloads are XML messages exchanged over Peppol with structured status codes.
More available in our France FAQ section