| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4156 |
| Technical Name |
l10n_fr_invoice_lifecycle_status |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4156 |
| Technical Name |
l10n_fr_invoice_lifecycle_status |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
France e-Invoice Status
The French e-invoicing lifecycle (cycle de vie) — deposited, made available, approved, refused, collected — as a guarded state machine with a full audit trail
The French e-invoicing reform (issuance for large/mid companies from 1 September 2026, SMEs from 1 September 2027) defines a normative set of invoice lifecycle statuses that every Plateforme Agréée (PA / PDP) and every trading party must support. This app turns that cycle de vie de la facture into a real, transition-checked status engine on your invoices, exchanges the statuses with your platform, and keeps a verifiable history.
Built on the e-Invoice Core Engine and the France PDP Routing connector — for Odoo 18 and Odoo 19.
Lifecycle state machine
The complete reform status catalogue — déposée, reçue par la plateforme, mise à disposition, prise en charge, approuvée, approuvée partiellement, en litige, suspendue, rejetée, refusée, paiement transmis and encaissée — each with its two-digit reform number, French/English label, mandatory / recommended classification and the actor that sets it. A legal transition graph blocks illegal moves.
Guarded changes with back-fill
Setting a later status automatically records the intermediate mandatory statuses it passed through (for example received → made available → approved), so the trail is complete even when the platform reports a status late. A breadth-first path search finds the shortest legal route between any two statuses.
Audit trail you can rely on
An append-only status-history model captures every change with the previous status, the actor (platform / supplier / buyer), the actor SIRET, the reason (motif), the source (manual, polled, automatic, inbound, back-filled) and the exact event time. Read-only in the UI and never edited in place.
Buyer-side actions
On a received invoice the buyer can approve, partially approve, dispute, suspend, refuse or mark a payment as sent — with a mandatory reason where the reform requires one. Each action is validated against the current status and pushed to the platform as a cycle-de-vie event.
Platform polling & reconciliation
Poll your Plateforme Agréée for the latest status and reconcile it against what Odoo holds — advance, back-fill or flag a conflict. The platform is treated as authoritative: a conflicting authoritative status is journaled and applied. A scheduled action can drain non-terminal routed invoices automatically.
Partner notifications
Email the trading partner whenever a lifecycle status changes, in French or English, surfacing the reason on a refusal or rejection. A fully-paid routed customer invoice advances automatically to the terminal encaissée status that drives VAT-on-collection.
BYOK & standards-based
Bring your own key: the status exchange runs over the France PDP Routing connector's transport, which talks only to the certified platform endpoint you configure. No data is sent anywhere else, and your API token is stored solely on your own database. The status catalogue, numbers and labels follow the reform's published spécifications externes; SIRET identities are validated with the real Luhn algorithm provided by the routing connector.
Disclosure: this module exchanges lifecycle status data only with the Plateforme Agréée endpoint configured in the France PDP Routing connector. Compatible with Odoo 18 and Odoo 19.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module