Objective
Design budget control thinking that prevents overspend early while allowing controlled exceptions.
Case study 14
Portfolio knowledge project
Budget Control & Encumbrance Design
Budget control structures, reservation points in P2P, override governance, and reporting so spend stays visible before it becomes an invoice surprise.
Knowledge / portfolio case study only. Not employment history, not a named client engagement, and not a certification claim.
Context
Without reservations, finance discovers overspend at invoice time — too late.
Scope
Control budget structure, reservation events, override path, and budget vs actual reporting.
Approach
Define control segments → set reservation points → design override approvals → test PO/invoice paths → build budget variance pack.
- 01Control designWhat is controlled and at what grain.
- 02Reservation pointsRequisition/PO/invoice.
- 03Override governanceWho can break the rule.
- 04UAT pathsPass, fail, override.
- 05ReportingBudget vs actual & override log.
01Control design
02Reservation points
03Override
04UAT paths
Budget Control & Encumbrance Design
Key design decisions
- Hard control on high-risk cost centers
- Soft elsewhere initially.
- Overrides are visible
- Never silent.
- Align budget segments to CoA
- Avoid mapping gymnastics.
Walkthrough
Create PO that reserves funds → increase PO → attempt over-budget PO → override with approval → invoice and release → report variance.
Controls
Overrides require named approver; override log reviewed monthly; soft vs hard controls documented.
Oracle modules in focus
Budgetary Control
AP
Purchasing
GL
Deliverables
Control matrix
override playbook
UAT scenarios
variance report outline.
Outcomes
Connects purchasing behavior to financial control outcomes.