Skip to content

Document reporting.unrecord and the flow10 add-on requirement #561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alvarolivie merged 3 commits into from
Aug 25, 2026
+9 −1
Merged

Document reporting.unrecord and the flow10 add-on requirement #561

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e15622a
Document reporting.unrecord and the flow10 add-on requirement on record
alvarolivie Aug 21, 2026
7b75cba
Unrecord is allowed until the report is submitted, not only on rejection
alvarolivie Aug 21, 2026
af11ade
Unrecord works until the filing deadline regardless of report state
alvarolivie Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion guides/fr-pa-reporting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ import FAQ from '/snippets/faqs/fr/composers/guide-pa-reporting.mdx';

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](https://docs.gobl.org/addons/fr-ctc-flow10-v1) add-on.
Invoices and payments must declare the [fr-ctc-flow10-v1](https://docs.gobl.org/addons/fr-ctc-flow10-v1) add-on in `$addons`: GOBL applies the Flux 10 rules when the document is built, and the record step rejects documents that don't carry the add-on.

## Sub-flows

Expand Down Expand Up @@ -93,6 +93,14 @@ Lines using `exempt`, `reverse-charge`, `intra-community`, `export`, or `outside

The `key` must match the rate used on the line. Lines on `standard` or `zero` rates do not need a note.

### Correcting a recorded document

To fix a document after it was recorded, run the `gov-fr.reporting.unrecord` action against its silo entry. It removes the document from the pending records so you can correct it and run the record workflow again.

- You can unrecord at any time until the window's filing deadline, whatever state its report is in. The next generation rebuilds the report without the document: as a replacement while the report never reached the PPF, or as a corrective filing when it was already submitted.
- After the filing deadline a submitted or filed report stands, and its documents can no longer be unrecorded.
- Unrecording a document that was never recorded is a no-op, so the action is safe to include in shared correction workflows.

## 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.
Expand Down