Submit, approve, reject or void a project budget
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Move a project budget through the configured approval chain and preserve the decision history.
What you’ll accomplish
Move a project budget through the configured approval chain and preserve the decision history. It forms part of Pixie CRM Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.
How it works
The controller includes submit_project_budget_for_approval and change_project_budget_status, and interface text includes confirmation for voiding an approved budget.
Approval steps use the module's configured approval mechanisms. One-person approval can be enabled where organisational policy allows it.
A status change affects governance; it does not itself post a ledger transaction.
Follow these steps
- Go to the budget detail.
- Check project, dates, manager and category values.
- Use Submit for Approval.
- Each assigned approver reviews and approves or rejects.
- Record a reason for rejection or void.
- After approval, verify transaction-control behaviour.
- For a material change, follow the approved revision process.
Settings to check
Check it worked
After the action is saved, Pixie CRM keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.
- Open the saved record and confirm its final status.
- Review the source reference and every debit and credit line where ledger data was created.
- Use the relevant register, ageing, reconciliation or report to verify the wider effect.
Common mistakes to avoid
- Do not self-approve where segregation is required.
- Do not bypass the configured chain.
- Do not void without reviewing linked transactions.
- Retain reasons and timestamps.
- Use the least destructive correction available and record the reason for material changes.
- Do not bypass a permission, approval or closed-period control by changing unrelated data.