Installation

1. Install the module from the Odoo Apps menu.
2. Confirm the following dependencies are installed:
   • base, purchase, product (Odoo Core)
   • account, analytic (Odoo Accounting)
   • mail, hr (Odoo Messaging & HR)
3. Assign users to the appropriate security groups.

Security Groups

The module provides two access levels:

Budget Levels

Configure budgets at different organisational levels:

• Organisation: Company-wide budget allocation
• Department: Budget per department or cost centre
• Category: Product category-specific budgets
• Project: Project or campaign budgets
• Product: SKU-level budget allocation

Budget Periods

Each budget has a period type and a validity date range:

• Annual: Full fiscal year
• Quarterly: Three-month rolling budget
• Monthly: Month-by-month allocation

Threshold Configuration

Each budget supports multiple configurable thresholds. When a purchase order's projected utilisation crosses a threshold, the configured action triggers automatically:

When multiple thresholds are breached simultaneously, the highest-percentage threshold determines the action.

To add a threshold, open a budget record, navigate to the :guilabel:`Thresholds` tab, and add rows specifying the percentage, action, and approver list.

Creating a Budget

1. Navigate to :menuselection:`Budget Control --> Budgets`.
2. Click :guilabel:`New`.
3. Fill in the required fields:
   • Budget Level: Select the organisational level.
   • Period Type: Annual, Quarterly, or Monthly.
   • Date Range: Start and end dates for the budget period.
   • Total Budget: Allocated amount in the company currency.
4. Optionally link a department, product category, project, product, or analytic account.
5. Add threshold rules in the :guilabel:`Thresholds` tab.
6. Click :guilabel:`Activate` to put the budget in effect.

Assigning a Budget to a Purchase Order

Open a purchase order and select a budget in the Budget field on the order header. Optionally override the budget on individual order lines to split the cost across multiple budgets.

When the order is confirmed (:guilabel:`Confirm Order`), the module:

1. Evaluates all assigned budgets for threshold breaches.
2. Creates an approval request if a require_approval threshold is breached, then blocks confirmation.
3. Hard-blocks confirmation if a block threshold is breached.
4. Creates idempotent commitment records for the confirmed order amount (one per budget assignment).

Budget Tracking

The budget form displays real-time financial positions:

Budget Status Indicators

The list view uses colour-coded row decorations:

• Red row: Utilisation ≥ 100% (over-budget)
• Warning row: Utilisation ≥ 80%
• Normal: Utilisation < 80%

Commitment Tracking

A commitment record is created for each purchase order assignment to a budget. Commitments transition through three states as vendor bills are posted:

Vendor Bill Spend Capture

When a vendor bill linked to a budgeted purchase order is posted, the module automatically:

1. Creates a spend line on the budget for each relevant bill line.
2. Converts the amount to the budget currency if currencies differ (using the bill date rate).
3. Updates the commitment's released_amount (transitioning to partial or released state as appropriate).

When a vendor bill is reset to draft, all corresponding spend lines are removed and commitment states are recalculated.

Budget Adjustments

To request a budget adjustment:

1. Open the budget and navigate to the :guilabel:`Adjustments` tab, or go to :menuselection:`Budget Control --> Adjustments`.
2. Click :guilabel:`New` and choose Increase or Decrease.
3. Enter the amount and a reason, then click :guilabel:`Submit for Approval`.

A Budget Manager can then :guilabel:`Approve` and :guilabel:`Apply` the adjustment, which updates the total_budget on the budget header. Decreasing the budget below committed_amount + spent_amount is prevented.

Budget Transfers

To move funds between two active budgets:

1. Open the source budget and click :guilabel:`Transfer Funds` (Budget Manager only).
2. Select the target budget (must share the same company currency).
3. Enter the transfer amount (must not exceed the source budget's available amount) and a reason.
4. Click :guilabel:`Transfer Funds` to execute.

Approval Requests

When a purchase order breaches a require_approval threshold, an approval request is created automatically and the designated approvers are notified by email.

To review and act on pending requests, navigate to :menuselection:`Budget Control --> Approval Requests`.

The requester is notified by email once the request is approved or rejected. If approved, the purchase order can be confirmed manually.

Burn-Down Dashboard

Navigate to :menuselection:`Budget Control --> Reporting --> Budget Burn-Down` to open the interactive OWL dashboard. For a selected budget, the dashboard displays:

• Daily cumulative spend over the last 30 days
• Remaining budget trend
• Current utilisation percentage
• Daily burn rate
• Projected budget exhaustion date

Workflow States

Models

Key Fields

Purchase Budget (grev.purchase.budget)

• name: Auto-generated reference (sequence BUD-XXXXX)
• budget_level: organisation | department | category | project | product
• period_type: annual | quarterly | monthly
• date_from / date_to: Budget validity period
• total_budget: Allocated amount (non-negative)
• committed_amount: Sum of net commitments (amount − released_amount, computed stored)
• spent_amount: Sum of spend lines (computed stored)
• available_amount: total_budget − committed_amount − spent_amount (computed stored)
• utilization_percent: (committed + spent) / total_budget × 100 (computed stored)
• forecast_amount: Manual what-if forecast entry for variance analysis
• analytic_account_id: Optional analytic account for cross-module reporting
• state: draft | active | closed | cancelled

Calculation Formulas

Available Budget:

Available = Total Budget − Committed − Spent

Budget Utilisation:

Utilisation % = ((Committed + Spent) / Total Budget) × 100

Variance:

Variance Amount = Total Budget − Forecast Amount
Variance %      = (Variance Amount / Total Budget) × 100

Savings:

Savings % = Savings Amount / Total Budget × 100

Integration Points

purchase.order (core Odoo Purchase)

• button_confirm() is extended to run budget validation and create commitments.
• button_cancel() is extended to release all active commitments.

account.move (core Odoo Accounting)

• action_post() is extended to capture spend lines from vendor bills.
• button_cancel() is extended to reverse spend lines when a bill is reset to draft.

grev_od_spend_analytics (optional)

Aggregated spend vs budget reporting consumes budget data via read-only access.

Performance

• Budget validation at PO confirmation: < 2 seconds.
• Computed amounts use store=True for query performance.
• Key dimension fields (department_id, category_id, analytic_account_id) are indexed.
• Commitment and spend line creation is idempotency-guarded to prevent duplicates.