Dynamic level approval for PO, Vendor Bill

by
Odoo

24.91

v 17.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Purchase (purchase)
Invoicing (account)
Discuss (mail)
Lines of code 785
Technical Name bill_purchase_approval_route
LicenseOPL-1
Websitehttps://www.odoocode.com
Versions 17.0 16.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Purchase (purchase)
Invoicing (account)
Discuss (mail)
Lines of code 785
Technical Name bill_purchase_approval_route
LicenseOPL-1
Websitehttps://www.odoocode.com
Versions 17.0 16.0

Multi level approval for PO, Vendor Bill with Dynamic, Flexible and customizable rules for approval Team

This module is applicable in Odoo Enterprise, Odoo Community and Odoo.sh


Features:

- Assigned roles for the approver with your set of dynamic rules, applied on each stage.

- Lock total feature which disallow user to change total sum in complete approval process.

- More than one approver in one team and several team for each approve process from RFQ to Po or PO to Vendor Bill.

- Set your team configuration flexibly like team compulsory required or optional or no team.

- Unlimited level of "step by step" approval process.

- Multi Company and Multi Currency features are supported.

- Apply maximum and minimum amount for each approver to which approver rule applies.




Guidelines


In configurations settings go to teams where you can create up your teams and in general settings



Team Page to create up a new team or to view the existing functioning teams



A very clear view to create a new team with ,team leader appoint, minimum and maximum amount approval, sequence of roles assigned approvers, lock amount feature on particular approver also dynamic custom conditions apply coloumn if you require more dynamic way to approve your orders.



Already defined my PO Team,Let's see how it works.



Already assigned a team a opted for optional user approval, So when RFQ is confirmed it stages to 'to approved' stage waits for the complete team to create a PO



Approval route with the status of approver visible to only admin and team leader



After the complete team approves the order the RFQ is turned to PO.



Similarly if the bill is to be generated of that particular PO you can apply the similar approval process, with same or different team.



At last the bill is turned to posted after the approval of last approver



Atharv ERP Services

We provide the following services :


Odoo development

Odoo Development

Odoo Implementation

Odoo Implementation

Odoo Integration

Odoo Integration

Odoo Data Migration

Odoo Data Migration

Odoo Code Migration

Odoo Code Migration

Odoo Training

Odoo Training

Odoo Configuration

Odoo Configuration

Odoo Support

Odoo Support




Do not hesiste for further assistant at atharverp@gmail.com for more support or hire dedicated resources.

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.