OdooWiki OCA HUB

Base UBL Payment Banking Mandate

base_ubl_payment_banking_mandate folder_open OCA/edi open_in_new
Hidden License: AGPL-3

Glue module between base_ubl_payment that adds the payment means and account_banking_mandate in order to declare the mandate in the payment means when the code is 49 or 59.

auto_awesome What this module does

AI-generated from the code · Odoo 16.0

Adds the customer's SEPA direct debit mandate reference and bank account to UBL payment files when the payment method code is 49 or 59.

This is a technical glue module with no menus or screens of its own. It works behind the scenes when Odoo generates a UBL payment file (an electronic payment document used for bank transfers and direct debits).

When the payment method used has the UNECE code 49 or 59 (the codes for direct debit), and a mandate is linked to the payment, the module enriches the payment means section of the UBL file with a PaymentMandate block. That block contains:

  • the mandate's unique reference, taken from the mandate record;
  • the payer's financial account number, taken from the bank account linked to the mandate.

If the payment method is not 49 or 59, or if no mandate is present, the file is generated exactly as before, with no mandate information added.

It touches the abstract UBL generation model base.ubl and relies on the mandate data provided by account_banking_mandate and the payment means logic from base_ubl_payment. There are no new models, no menus, no reports and no scheduled actions in this module.

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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation 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.

info

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.