Wednesday, September 16, 2026
1 change · 17.0
Resolved issues and error corrections
Fixes French Flow 10 e-reporting so purchase documents, tax details, VAT cases, and field values are generated in the format expected by the French public platform. Rejected reports now show the reason to users and can be corrected and resent, reducing blocked compliance submissions and manual investigation.
Original PR description
Flow 10 reports could be rejected because purchase document type codes were reversed, generated values did not always respect PPF constraints, and tax summaries could contain unsupported or…
Flow 10 reports could be rejected because purchase document type codes were reversed, generated values did not always respect PPF constraints, and tax summaries could contain unsupported or inconsistent data. Moreover, PPF responses were stored without being processed. Rejected reports therefore remained marked as sent, while users could neither see the rejection reason nor correct and resend them properly. Correct the document type mapping, constrain and validate generated values, fix tax data generation, and process PPF responses. Rejected reports now expose their reasons in the chatter and can be corrected and manually resent while preserving previous payloads. This PR backports the following 18.0+ fixes to 17.0: - [Correct Flow 10 invoice type codes](https://github.com/odoo/odoo/pull/286526) - [Validate Flow 10 report values](https://github.com/odoo/odoo/pull/286536) - [Correct Flow 10 tax data](https://github.com/odoo/odoo/pull/286547) - [Process Flow 10 PPF responses](https://github.com/odoo/odoo/pull/287338) - [Exclude OSS VAT from Flow 10](https://github.com/odoo/odoo/pull/288013) Only the changes required for 17.0 compatibility were made, mainly adapting translation calls, reporting scope checks, and test APIs. No Task ID