Budget setup
- Budget headers
- Line planning
- Period controls
- Dimension support
Finance And Revenue
Budget Management
Accounting-owned budget planning with availability checks, transfers, encumbrance evidence, preview-only AI planning, and owner launch-readiness evidence.
Implemented
Evidence-first module page
Primary users
Budget owner
Finance manager
Department manager
Controller
App-derived visual
Budget management workspace
Availability
Checked
AI planning
Preview-only
Launch gates
Paused
| Area | Status | Evidence |
|---|---|---|
| Budgets | Line controlled | Dimension proof |
| AI planning | Human reviewed | Preview evidence |
| Owner readiness | Review ready | LR rollup |
Core workflows
What the module helps operators complete.
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Step 1
Create operating and project budgets
Step 2
Import and validate budget lines
Step 3
Review availability, transfers, and encumbrance evidence
Step 4
Analyze variance, preview AI planning narratives, and prepare owner launch-readiness evidence
Feature checklist
Capabilities grouped the way operators look for them.
Availability control
- Availability checks
- Transfers
- Encumbrance evidence
- Limit guardrails
Budget reporting
- Variance views
- AI planning previews
- Owner UAT evidence
- Launch rollup export
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | Relationship |
|---|---|
| Accounting | Budget dimensions, ledgers, and variance reporting |
| Procurement | Purchase commitments and encumbrance evidence |
| Projects | Project budget controls and delivery cost tracking |
| BI | Budget variance dashboards and executive reporting |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
Governance
- Budget transfer control
- Import validation
- Encumbrance evidence
- Preview-only AI
- Paused launch gates
Reports
- Budget variance
- Availability
- Encumbrance
- Owner review evidence
- Launch-readiness rollup
AI coverage policy
What ERPStack can honestly claim for this module today.
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI L3 ready| Coverage claim | Current AI coverage: Accounting L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 9 registered tools, 9 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: 1/1 ready (Finance Close Variance Monitor). |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
Module pages explain value, workflow, control, and proof in one place.
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Feature clarity
Buyers can see concrete function groups instead of vague capability claims.
Operational fit
Workflows, users, and connected modules show where the module belongs.
Governance proof
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Review path
Public pages link back to app routes so reviewers can compare page claims to product surfaces.