Payment Term Restriction Purchase
This module adds the possibility to restrict the use of Payment Terms in Purchases.
Only Payment Terms having the applicable on value as Purchases or All can be applied in Purchase Orders.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Restricts which payment terms can be used on purchase orders and on vendor records, so only terms marked as applicable to purchases (or to all) are allowed.
This module adds a control on payment terms used in the purchasing side of Odoo. It relies on the payment term restriction feature and extends it to purchases.
- On a purchase order, when a payment term is set, Odoo checks that the term is allowed for purchases. If the term is not marked as applicable to purchases (or to all), the order cannot be saved and an error is shown.
- On a vendor (supplier) contact, the default supplier payment term is checked in the same way. If the term is not allowed for purchases, the contact cannot be saved.
The check is automatic and happens whenever the payment term field is changed or the record is saved. It applies to the purchase.order and res.partner models. There are no new menus, buttons or reports; the module only adds validation rules to existing screens.
This helps keep purchasing documents consistent with the payment terms that the company has decided to allow for purchases, preventing users from selecting terms meant only for sales or other uses.
Depends on
Models and fields (2)
- res.partner · extends an existing model
- purchase.order · extends an existing model
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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/account-payment.
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.