A finance budget expresses a plan in the same GL-account structure used by the ledger. The implemented reporting path can compare budget lines with posted actuals. The repository also contains availability and commitment services, but current purchasing and expense handlers do not call them, so this page does not present budget control as an active spend gate.
The demo2 Budget create layout currently includes tenant-specific fields that do not correspond cleanly to the core Budget entity. A screenshot would teach the wrong configuration, so this page remains text-only.
Core budget record
The core Budget header stores:
- fiscal year;
- partner account;
- optional business unit and cost centre;
- status and active state; and
- planned amount.
Budget lines carry the GL account, period, business unit, branch, amount, partner account and cost centre used for the comparison. Use those core dimensions when designing layouts or integrations; do not rely on a demo-only Name, Label or Budget Type field as a platform contract.
Keep the header and line scope coherent. A line for a different partner, period or organizational dimension can make the statement look incomplete even when both records saved successfully. Before activating a budget, reconcile the sum of its lines with the intended plan and document how null dimensions should be interpreted by the reports used in your deployment.
Budget vs Actual
Budget variance reporting is implemented. It reads the applicable budget amount and compares it with posted ledger actuals for the requested scope. An overrun therefore appears in the variance result after the responsible transaction reaches the ledger.
Use the report as the current system of record for budget monitoring:
- Select the intended fiscal year and organizational scope.
- Confirm the expected GL accounts have budget lines.
- Compare actual and budget amounts and investigate scope mismatches before changing the plan.
- Trace actuals back to posted journals or source documents.
Availability checks are not a universal gate
An availability service can calculate whether a proposed amount fits against budget. The code currently has no production caller from the purchasing, invoice or expense save/post paths audited for this page. A transaction can therefore proceed without consulting that service.
If the business requires hard prevention, treat that as an implementation project: identify every committing and posting path, call the check server-side, define override permissions and add integration tests that prove an over-budget transaction is rejected. A report or a standalone service is not itself a control.
Commitments are not yet end-to-end
Commitment methods exist to create, consume and close a budget commitment. The audited document handlers do not wire those methods to purchase-order creation, billing, cancellation or posting. Consequently, this documentation cannot claim that an open purchase order automatically reduces budget availability or that its bill automatically replaces the commitment.
Until that workflow is implemented and tested, track commitments through the organization's approved external process and use Budget vs Actual for posted spend. Do not add an unverified commitment amount to a public screenshot or reconciliation.
Forecast behaviour
The current forecast calculation is an actuals-based run rate. It does not calculate “actuals plus open commitments.” Interpret it as a projection from historical posted activity, not a committed-spend forecast.
Common questions
What happens when a budget is exceeded?
The variance report can show the overrun after posting. Current spending flows are not universally blocked by the budget-availability service, so do not promise pre-transaction prevention unless your deployment has added and tested that integration.
Can I budget by branch, business unit or cost centre?
The line model carries branch, business-unit and cost-centre dimensions in addition to GL account and period. Verify that the report or custom consumer you use applies the same dimension semantics before depending on a finely scoped control.
Do purchase orders reserve budget automatically?
Not in the audited first-party flow. Commitment services exist, but create/consume/close calls are not wired into the relevant document lifecycle.