Account Banking Mandate Sale Contact
This module combines the functionality of account_banking_mandate_sale with account_banking_mandate_contact and to allows you to add a specific contact mandate to sale orders.
Table of contents
Configuration
To configure this module, you need to:
Go to Settings/Sales/Invoicing and select the Default Mandates option. This allows you to choose if you want the mandate of the sale partner, invoice address or delivery address.
If you want to specifically change the default mandate for a customer, you can go to the “Sales & Purchase” tab of his contact form.
Usage
For selecting the mandate at contact level:
Go to Invoicing > Customers > Customers.
Open or create one contact.
On the “Sales & Purchase” page, fill Contact Mandate.
Then, when you select a payment mode that requires mandate on a sale order, Odoo will choose the mandate selected at contact level. That mandate will be copied from the sale order to the invoice.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Alberto Martínez <alberto.martinez@sygel.es>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/bank-payment project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-account-banking-mandate-sale-contact 18.0.1.0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_account_banking_mandate_sale_contact-18.0.1.0.1.3-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_account_banking_mandate_sale_contact-18.0.1.0.1.3-py3-none-any.whl |
Release files / odoo_addon_account_banking_mandate_sale_contact-18.0.1.0.1.3-py3-none-any.whl
| Download URL | odoo_addon_account_banking_mandate_sale_contact-18.0.1.0.1.3-py3-none-any.whl |
|---|---|
| Size | 56.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75eb4b1e527e6d186d0a3ebaee1c0c8f7464ebe9f5c030d238bc69185cdbca2c
|
|
BLAKE2b-256 checksum How to use checksums |
552b05af83b68528f8eef46da9671084f10cc8ef0bb18911a3209a28d164a7b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-account-banking-mandate-sale-contact 18.0.1.0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
