From e15622a0d10bcfcfd4727ebead2c17b49316fd22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81lvaro=20Olivi=C3=A9?= Date: Fri, 21 Aug 2026 12:44:31 +0000 Subject: [PATCH 1/3] Document reporting.unrecord and the flow10 add-on requirement on record Co-Authored-By: Claude Fable 5 --- guides/fr-pa-reporting.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/guides/fr-pa-reporting.mdx b/guides/fr-pa-reporting.mdx index e0a89ac9..d2bb4ad6 100644 --- a/guides/fr-pa-reporting.mdx +++ b/guides/fr-pa-reporting.mdx @@ -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 @@ -93,6 +93,13 @@ 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. + +- A document already included in a generated report can only be unrecorded if the PPF rejected that report. +- 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. From 7b75cba6a9749d8e3b1a3065734dc7d1571a5911 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81lvaro=20Olivi=C3=A9?= Date: Fri, 21 Aug 2026 14:19:15 +0000 Subject: [PATCH 2/3] Unrecord is allowed until the report is submitted, not only on rejection Co-Authored-By: Claude Fable 5 --- guides/fr-pa-reporting.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/guides/fr-pa-reporting.mdx b/guides/fr-pa-reporting.mdx index d2bb4ad6..74f1e951 100644 --- a/guides/fr-pa-reporting.mdx +++ b/guides/fr-pa-reporting.mdx @@ -97,7 +97,8 @@ The `key` must match the rate used on the line. Lines on `standard` or `zero` ra 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. -- A document already included in a generated report can only be unrecorded if the PPF rejected that report. +- You can unrecord at any time until the window's filing deadline, even if a report XML was already generated — the report is regenerated without the document before it is sent. This also covers reports the PPF rejected. +- Once the report was submitted to the PPF, the document can no longer be unrecorded: corrections from that point go through a corrective filing. - Unrecording a document that was never recorded is a no-op, so the action is safe to include in shared correction workflows. ## Submitting reports From af11ade39e345c4e9ff12a21af1db7af59d78acd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81lvaro=20Olivi=C3=A9?= Date: Fri, 21 Aug 2026 14:36:08 +0000 Subject: [PATCH 3/3] Unrecord works until the filing deadline regardless of report state Co-Authored-By: Claude Fable 5 --- guides/fr-pa-reporting.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/fr-pa-reporting.mdx b/guides/fr-pa-reporting.mdx index 74f1e951..419ecddb 100644 --- a/guides/fr-pa-reporting.mdx +++ b/guides/fr-pa-reporting.mdx @@ -97,8 +97,8 @@ The `key` must match the rate used on the line. Lines on `standard` or `zero` ra 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, even if a report XML was already generated — the report is regenerated without the document before it is sent. This also covers reports the PPF rejected. -- Once the report was submitted to the PPF, the document can no longer be unrecorded: corrections from that point go through a corrective filing. +- 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