Account Invoice Ubl Payment Mandate
This module extends the UBL invoice generation to include direct debit mandate information in the PaymentMeans block.
When the invoice payment means code is 49 (Direct debit) or 59 (SEPA direct debit), the generated UBL XML contains a PaymentMandate node with the mandate reference and the payer bank account.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds direct debit mandate details to UBL invoice XML files. When an invoice is paid by direct debit, the generated electronic invoice now includes the mandate reference and the payer's bank account.
This module extends the electronic invoice (UBL) generation so that direct debit information is included in the XML file sent to customers or authorities.
When an invoice's payment means code is 49 (Direct debit) or 59 (SEPA direct debit), the module adds a PaymentMandate block inside the PaymentMeans section of the UBL document. That block contains the mandate's unique reference and the payer's bank account number (IBAN).
Business rules added by the module: - If the payment means code is 49 or 59 but no mandate is linked, the system stops and shows an error asking for a mandate reference. - If the mandate exists but has no payer bank account, the system also stops with an error.
This works together with the banking mandate and UBL invoice modules. It does not add new menus or screens; it changes the content of the UBL file produced when generating an electronic invoice. The mandate information comes from the mandate linked to the invoice, and the bank account comes from the mandate's payer bank account.
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/edi.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.