Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
Lines of code | 473 |
Technical Name |
vendor_bill_payment_approval |
License | OPL-1 |
Website | https://sodexis.com/ |
Versions | 14.0 16.0 17.0 |
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
Lines of code | 473 |
Technical Name |
vendor_bill_payment_approval |
License | OPL-1 |
Website | https://sodexis.com/ |
Versions | 14.0 16.0 17.0 |

Vendor Bill Payment Approval
Description
This module introduces an approval mechanism for vendor bills before payment registration.
Configuration
The settings include configurable options for the Vendor Bill Approval Request process.
There are two user groups available in the User Settings for managing vendor bill approvals.
- “Can Request for Payment Approval” is to provide access to create the approval request from the vendor bill.
- “Payment Manager” is to approve or cancel the request to proceed for the payment process.
Functionality
This application facilitates the approval process for vendor bill payments, ensuring efficient and accurate authorisation.
Approval Request Based on Threshold Amount:
If the “Approval Request is Based on Threshold Amount” boolean is False.
When the vendor bill with any amount is confirmed, the “Request Approval for Payment” button is enabled for users who have “Can Request for Payment Approval” access. Additionally, the “Register Payment” button is not displayed.
If the “Approval Request is Based on Threshold Amount” option is enabled and the bill amount exceeds the specified threshold, the “Request Approval for Payment” button becomes active.
Note: For amounts below the threshold, the process follows the standard Odoo workflow.
Create Approval Request Automatically:
If the “Create Approval Request Automatically” option is enabled, the “Request Approval for Payment” button remains disabled. Instead, an approval request is automatically generated, moving the bill to the “Waiting Approval” stage, with the “Waiting Approval” ribbon displayed on the bill.
When a vendor bill is created, an approval request is automatically generated.
For manual approval request creation, set the "Create Approval Request Automatically" boolean to false.
Turn off Approval Request Email:
If the “Turn off Approval Request Email” option is false, no email will be sent for the approval request. Emails will only be sent if this option is true.
Channel:
If a Channel is set, a scheduled action will post a daily message in that channel listing vendor bills that need approval.
Managers can approve the bills directly from the channel or via email.
Note: We have default filters available—"Can be Requested for Payment Approval" and "Waiting Approval Bills"—to easily identify bills that require approval.
Credits
Contributors
- Sodexis <apps@sodexis.com>
This module is maintained by Sodexis.
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