$ 46.74
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 711 |
| Technical Name |
bd_payment_dynamic_approval |
| License | OPL-1 |
| Website | https://www.beyondatagroup.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 711 |
| Technical Name |
bd_payment_dynamic_approval |
| License | OPL-1 |
| Website | https://www.beyondatagroup.com |
| Versions | 17.0 18.0 19.0 |
Dynamic Payment Approval
Key Highlights
Dynamic Payment Approval
Minimum Amount Threshold
Set a specific Minimum Amount to trigger approval only for payments at or above this value, allowing small payments to bypass workflow.
Customer/Vendor Specific Rules
Configure rules separately for Customer or Vendor payments via Rule Applied field, enabling different thresholds and approvers per payment type.
Company-Specific Configuration
Assign rules to specific Companies for multi-company setups, ensuring each entity follows its own approval policies and limits.
Multi-Level User/Group Approvals
Define sequential levels in Approval Details using By User (specific persons) or By Group (team members), with automatic level progression.
Automated Notifications
First approver gets instant email/in-app alerts when payment is submitted; subsequent approvers notified after each level completion.
Reject with Mandatory Remarks
Approvers uses a Reject button triggering a wizard for rejection reason; payment moves to the Rejected state with visible history.
Waiting for Approval Views
Smart menus/filters in Accounting show pending payments by approver, allowing bulk review and action from dedicated lists.
Auto-Posting on Final Approval
After last level approval, payment automatically confirms/posts per Odoo standards, streamlining finance processes.
Overview
Dynamic Payment Approval
The Dynamic Payment Approval module adds a configurable multi‑level approval workflow for
customer and vendor payments before they are confirmed or posted in Accounting.
This gives finance teams stricter control over both incoming and outgoing cash movements,
especially for high‑value transactions that must follow an authorization hierarchy.
SCREENSHOTS
Configuration
Approval Configuration :
- Go to Accounting Module → Configuration → Payment Approval Configuration.
- Create a Payment Approval Rule by defining the Minimum Amount, Rule Applied (Customer/Vendor), Company, and setting the Approval Details.
-
There are two types of approval processes: 1) User and 2) Group.
Select 'User' as the approval type and specify the person responsible for approving payments meeting the rule criteria.
- Select 'Group' approval type and assign a user group. Any member of the selected group can approve the payment.
Generate and Submit Payment :
- After generating a Customer or Vendor payment, click the 'Confirm' button to start the approval process.
- If approval is configured by Minimum Amount, the system checks the payment total before routing it for approval.
- The system automatically fetches the approval levels based on the configured rules, minimum amount, rule applied (Customer/Vendor), and company set.
Email Notification for First Approval :
- When a payslip is submitted for the first approval, an email notification is sent to the first approver, informing them that action is required.
Approve Payment by First Approver :
- The first approver can open the payment and click the 'Approve' button to approve it.
- Once approved, the process automatically moves to the next approver (if configured).
- Each approval updates the 'Approval Info' tab with details such as approver name, remarks, and timestamp.
Approve Payment by Final Approver :
- The final approver can click the 'Approve' button to complete the approval process.
- Once all approvals are completed, the payment gets automatically paid.
- All related details approver sequence and approval time are displayed under the 'Approval Info' tab.
Reject Payment:
- If any approver rejects the payment, they can click the 'Reject' button to stop the approval process.
- A Rejection Wizard will pop up, requiring the approver to enter the reason for rejection.
- Once rejected, the payment moves to the 'Rejected' stage.
- The rejection reason and approver details are visible under the 'Approval Info' tab.
Email Notification for Rejected Payment :
- An email notification is sent to the payment creator and Accounting team when a payment is rejected, including the reason for rejection.
Waiting for Approval Menu :
- Go to Accounting Module → Customers/Vendors → Payments → Waiting for Approval to view all payments pending approval.
- The user can view payments that are in the “Waiting for Approval” stage and take action to approve or reject them from there.
Our Service
For any Query
Checkout our Apps
Check App Demo
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