MODULES / FINANCE

Budgets

Prepare account and period budgets, route them for separate approval and compare them with posted ledger actuals.

Overview

Module idask_budget
Version1.0.0
Who uses itAnyone who uses the screens listed below.
InstalledOn demand, from Settings → Modules. Anything it needs is installed with it.

Where to find it

AccountingBudgets

The menu entries appear once the module is installed and your role allows them.

How it links to other modules

  • Needs: Accounting
  • Works better with: no other module in particular
  • Needed by: no other module

A module that is needed cannot be turned off while the module that needs it is on.

Details

Budget module (ask_budget)

ask_budget is an optional per-company planning module adapted from Odoo 18's om_account_budget. It supports budgets by profit-and-loss account and date range. The module is implemented as an ASKERP-native addon and leaves the accounting posting engine as the sole source of posted actuals.

Workflow

  1. An authorized Accounting user creates a draft with a name, start/end dates, and positive planned amounts for active P&L accounts.
  2. The requester submits the saved plan. The service locks it and its lines; only a different authorized company member may approve or reject it.
  3. The approved budget shows actuals from posted journal items through today, capped at the budget end date. Expense actuals follow debit-minus-credit; revenue actuals follow credit-minus-debit. Each actual links to the General Ledger for the same account and period.
  4. A decision can be closed while preserving the reviewer, timestamp and decision history. Past decision evidence is not edited to reset a plan.

Integrity and security

The service derives company and actual amounts from the active company and posted ledger, never from browser-calculated values. PostgreSQL enforces forced RLS, company-composite references, valid account/state rules, and state-aware immutability. Mutations use row locks to serialize submission and decisions. The module must be installed for the company, and existing Accounting authorization applies to its screens and actions.

Migrations 0103_account_budgets.sql and 0104_budget_close_evidence.sql create the schema and add the closed-state evidence rule. The second migration is additive because the first may already have been applied to a populated database. Rollback is intentionally not automated: dropping budget tables would destroy planning and approval evidence. Back up the database and use a reviewed, data-preserving migration if rollback is required.

Boundaries

The module does not budget departments, branches or projects; track purchase commitments; block or alert on overspending; provide multi-step approval, versioned baselines, or budget-specific PDF/XLSX exports; or automatically post accounting entries. A budget is a planning and review record, not a reserve of cash or authority to bypass transaction-level approvals.

Regression coverage: addon.test.ts.

Budgets | ASKERP Docs