Finance teams outgrow native ERPNext budgeting quickly. Core Budget in ERPNext ties a monthly-distributed amount to a single Cost Center (or Project) against an account, enforces on a fixed set of transactions, and stops there — it has no first-class notion of a rolling forecast, no reforecast that preserves the original plan, no phased quarterly cadence beyond the monthly distribution table, and only coarse "Stop / Warn / Ignore" actions with no approval trail for changing a number. Controllers end up rebuilding the real budget in spreadsheets, which drift from the ledger the moment a journal posts. This app closes that gap inside ERPNext itself so the plan, the forecast and the actuals live on one system of record.

We ship a proper Frappe app (its own module, versioned git repo, hooks.py) rather than customizations bolted onto stock DocTypes. New DocTypes model the finance objects directly: a Budget Plan header with child Budget Line rows keyed on the full dimension set (Cost Center, Project, Account, plus any Accounting Dimensions you already use), a Budget Period phasing table for monthly/quarterly cadence, and a Rolling Forecast DocType that snapshots the approved plan and layers period-by-period reforecasts on top so original-vs-latest is always recoverable. A Budget Change Request DocType carries every increase, reallocation or reforecast through a Frappe Workflow with role-based approval states and a full version/audit trail — no silent edits to a live budget.

Enforcement is wired through hooks.py doc events. validate / on_submit handlers on the transaction types you choose (Purchase Order, Material Request, Journal Entry, Expense Claim, Sales/Purchase Invoice, or a subset) call a whitelisted server-side commitment engine that sums posted actuals plus open commitments against the relevant Budget Line for the period and dimension, then applies your policy: hard stop (raise frappe.ValidationError and block submission), soft warn (msgprint and log an override), or track-only. Because the check is server-side it holds for REST/API-posted documents too, not just the desk UI. Variance reporting is delivered as Query Reports and a dashboard: budget vs actual vs commitment vs forecast, with drill-down by dimension and period, percentage and absolute variance, and rows that link straight back to the source documents. A scheduler event (scheduler_events in hooks.py) refreshes forecast snapshots and can email period-close variance packs to the controller. Client Scripts add in-form budget headroom hints on the transaction so buyers see remaining budget before they submit, and everything respects Role Profiles and permission rules so FP&A, department heads and approvers each see and do only what they should.

Because this is build-to-order, nothing is a blind download. We start with a short scoping call to confirm your dimension model, which transactions enforce and how hard, your phasing cadence, and your approval hierarchy. We then build against your ERPNext version (Frappe/ERPNext v15 or v16), review the design with you, and validate everything on a staging bench through UAT with a documented rollback plan before touching production. Typical delivery is one working week from confirmed scope. You receive the installable source for your version, install and configuration on your bench, technical and user documentation, a training session, the git repository handover, and a post-go-live support window.