416.19

v 14.0 Third Party 3
Required Apps Invoicing (account)
Purchase (purchase)
Inventory (stock)
Included Dependencies
Lines of code 1382
Technical Name purchase_budget
LicenseSee License tab
Websitehttp://www.openvalue.cloud
Also available in version v 13.0
You bought this module and need support? Click here!
Required Apps Invoicing (account)
Purchase (purchase)
Inventory (stock)
Included Dependencies
Lines of code 1382
Technical Name purchase_budget
LicenseSee License tab
Websitehttp://www.openvalue.cloud
Also available in version v 13.0

PURCHASE BUDGET

 

This module supports the purchase budget management in the overall indirect procurement process, (expenses allocated on analytic accounts).

It is possible also enabling the budged control at single analytic account level for checking in real time the available budget will not be exceeded.

All the accounting figures are calculated in real time for performing an effective budget control.

 

 

BUDGET MANAGEMENT

In a validity period an amount can be planned for purchasing of some kinds of goods or services to be allocated to a specific analytic account. Therefore, it is possible to assign a budget amount to an analytic account in a period of time for some specific purchasing.

The goods or services nature (so what has to be purchased) is identified through the related product category which is linked to an expenses account; the expenses accounts can be grouped and entered in a budged line.

Each budget line, so each line of purchase budget, is identified through the following three dimensions:

·       validity period

·       analytic account responsible to the purchasing costs

·       account group (group of financial accounts to identify the purchase cost natures)

 

The following figures related to the indirect procurement process are available at budget line level:

          Purchase Amount: the overall purchased amount in a budget period related to an analytic account and a group of financial accounts;

          Commitment Amount: all open amounts in purchase order lines with planned delivery date lying within the budget period, allocated to the budget analytic account and account in the budget accounts group;

          Actual PO Amount: all invoice lines with purchase order lines entered in budget validity period for the budget analytic account and financial account in the budget account groups;

          Actual Amount: all costs (all posted invoice lines without purchase orders are taken into account also) posted in budget validity period the budget analytic account and financial account in the budget account groups;

          Planned Amount: budget allocated to the budget line:

          Available Amount: calculated as planned amount – actual po amount – commitment amount;

 

The overall purchase budget consists of several budget line; therefore, it is possible to move the budget allocated to the single budget lines and still available from a budget line to another one over the time.

The figures Planned Amount, Actual PO Amount and the percentage of Actual PO Amount divided by Planned Amount are available also at overall purchase budget level.

 

When a PO is confirmed or canceled, the open purchasing amount (commitment amount) is updated in real time. When an invoice posted or cancelled with accounting date lying within the budget validity period, the Actual PO Amount (related to effective costs) is calculated. Therefore, the Available Amount (Planned Amount – Commitment Amount – Actual PO Amount) for a budget line is determined in real time.

 

 

BUDGET CONTROL

It is possible to activate the budget control at single analytic account level; that means any purchase order can be confirmed for a specific analytic account or any invoice can be posted only if budget amount is still available. Therefore, it is not possible exceeding the budged amount in performing the procurement process in the budged period allocated to the budget analytic account.

 

 

Budget process has to be performed at company level, so purchasing process and the related budget figures are segregated per company.

Budget currency is always the company budget. The purchase order and invoices with a different currency is also managed. The exchange rate is determined for purchasing at delivery date and for invoices at accounting date.

 

 

Purchase Budget Account Group


Financial Accounts can be grouped for assigning them to a budget line.

It is not possible to assign the same account twice; therefore, an account can be assigned to the same group once.

Budget Account Group has to be confirmed before using it; purchase budget can be confirmed and approved only if all its account groups have been confirmed.

It is not possible to reset the confirmed status to change account group if it has been assigned to an active purchase budget.

Odoo Standard activities feature and logical archiving feature are available also.

 

 

Analytic Account


Control budget can be activated at single analytic account level. By activating it, the budget control feature is enabled to check whether budget amount is still available.

In case no budget line has been approved, when confirming a PO with control budget error message is issued to forbid to proceed in procurement process without any budget line. The same feature has been implemented in posting an invoice.

 

 

Purchase Budget


The following features have been implemented:

          Check the start date is before the end date

          Check at budget confirmation whether a budged line has been entered at least

          Check at budget confirmation whether financial account is set only once for all accounts group

          Check at budget approval whether only one budget is available for the same company and analytic account with no validity period in overlapping

          Check all budget accounts groups have been confirmed

          Document attachment

 

Kanban, pivot, graph and activity views are provided.


In pivot view is possible to have an overview of the following figures calculated at budget document level (so for all its items):

         planned amount

         Actual Purchase Amount

         % Actual/Planned

 

Through the button “compute amount” all figures are updated, so it is possible to recover past POs and invoices backwards.

Odoo Standard activities feature and logical archiving feature are available also.

 

 

Purchase Budget Lines


Budget lines list is available also. It is possible to group budget items per analytic account also.

A pivot view is provided to compare all figures, i.e. planned amount, purchase amount, Commitment amount, Purchase Actual Amount, Actual Amount and Available Amount.

Two lists with all PO items and invoice items  related to budget line are provided also; therefore, it is possible to check in detail the budget figures with the concerned documents.

 

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.
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.