| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 164 |
| Technical Name |
eg_account_dynamic_approve |
| License | OPL-1 |
| Website | https://www.inkerp.com/ |
| Versions | 16.0 17.0 18.0 19.0 |
Our Most Suggested Products
Dynamic Approve in Account
Dynamic Approve in Account is an Odoo module designed to bring structured, multi-level approval control to the invoice validation process. It allows businesses to assign multiple approvers, define approval sequences, and link invoice approvals to specific account teams, ensuring that invoices are reviewed and posted only through an authorized workflow.
Features
Screenshots
Support
Service
Features
Account Team-Based Approval Configuration
Administrators can create dedicated account teams and use them as the foundation for invoice approval responsibilities. This makes it easy to group the right users together and assign approval authority according to departments, finance roles, or internal team structures.
Approval Flow Enforcement with Access Validation
Once an approval flow is assigned to an invoice, the module ensures that only the users included in that flow can approve and move the invoice forward. If an unauthorized user attempts to confirm the invoice, the system blocks the action and presents an error, protecting the integrity of the workflow.
Screenshot
1.) Invoicing Account Team Configuration
Administrators can access the Account Teams option from the invoicing configuration area to create and manage the teams responsible for invoice approvals. This setup provides the foundation for organizing approvers into logical groups, making it easier to control who participates in the approval process and how responsibilities are distributed across the finance team. 2
2.) Account Team Approval Flow Setup
The approval flow can be defined directly within the selected account team, allowing administrators to establish the sequence or structure of invoice approvals. This makes the approval process more intentional and standardized, ensuring that invoices move through the correct chain of authorization before they can be finalized.
3.) Invoice Form with Assigned Approval Flow
While creating or reviewing an invoice, users can select the relevant approval flow through the associated account team. Once assigned, the invoice follows the configured approval path automatically, ensuring that every approval action is aligned with the team structure and the workflow rules set by the administrator.
4.) Unauthorized User Validation Error
If someone outside the assigned account team tries to confirm the invoice, the module prevents the action and returns an error. This safeguard reinforces approval discipline by ensuring that only authorized users can participate in the process, and that all required approvals are completed before the invoice reaches the Posted state.
User Guide
Teams
team@inkerp.com
Suggested Products
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 164 |
| Technical Name |
eg_account_dynamic_approve |
| License | OPL-1 |
| Website | https://www.inkerp.com/ |
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