Decisions made on stale numbers
Most finance teams don't have a visibility problem because nobody's tracking the numbers. They have one because the numbers everyone's tracking are stale by the time anyone sees them. A department head submits a purchase requisition, it works its way through two or three approval levels over several days, and only after it's finally approved does anyone discover that the budget line it draws on was already spent down by a different requisition that cleared the day before. By the time the report runs, the decision has already been made on bad information.
This was the core problem we solved for a client running a multi-branch, multi-department operation on ERPNext. The business needed strict financial governance: nobody should be able to raise a material requisition, a purchase order or a purchase receipt without it passing through the right chain of approvers. But governance on its own doesn't prevent budget overruns. It just slows down the paper trail around them. What the client actually needed was for the budget itself to be visible and current at every step of that approval chain, not just in a monthly reconciliation report.
Approvals with the live budget built in
We started with the access and approval layer. Every material requisition, purchase order and purchase receipt now runs through a multi-level approval workflow, and creation itself is restricted to authorised users based on their role and department. That's standard ERP governance. The part that made it useful was wiring the budget directly into those same forms. Allocated Budget, Utilised Budget and Remaining Budget now appear as live fields on the requisition and purchase workflows, updating as submissions happen, not after the fact.
An approver looking at a requisition isn't just checking "does this follow policy". They're looking at the actual remaining budget for that department or branch at the moment they're reviewing it. The same numbers carry through to the printed approval documents, so the audit trail isn't just "who approved this and when". It's "what did the budget picture look like when they approved it".
A chart of accounts built around the business
Underneath that sits something less visible but arguably more important: the chart of accounts had to be rebuilt to match how the organisation actually operates. A generic ERPNext chart of accounts doesn't know about a specific company's expense heads, branch structure or reporting needs. It has to be designed around them.
We restructured the chart of accounts to align with the client's real expense categories and operational units, then configured dependent filtering so that selecting an expense head on a form narrows the account choices to the ones that are relevant to it. That sounds like a small UX detail, but it removes a very common and costly error: someone posting a transaction to the wrong account because the dropdown showed forty options instead of the four that made sense. We mapped more than fifty individual budget allocations into this structure, each tied to a specific operational unit, so the budget checks on the approval forms run against numbers that reflect the organisation's real financial structure, not a simplified placeholder.
No new manual work
The last piece was making sure none of this created manual work elsewhere. We built dependent field logic so that selecting a department on a form filters and shows the correct branches, then surfaces that branch's allocated budget without anyone looking it up separately. We also built export functionality so ERPNext data maps cleanly into Tally's import format, along with importer configurations for users, suppliers, items, tax codes, and the budget and chart of accounts structures themselves. Bringing a large organisation's existing master data into the new structure didn't mean months of manual re-entry.
Why the three pieces only work together
Approval governance, live budgeting and chart of accounts design don't work especially well in isolation. Approval workflows without real budget visibility just add friction. Budget dashboards that aren't tied to the actual approval moment get checked too late to matter. The value came from wiring all three together, so the person approving a spend decision is looking at the same numbers the finance team will reconcile against weeks later, not a different, outdated version of them.
If your organisation has strong approval discipline but still gets end-of-month budget surprises, it's worth asking whether the gap is a policy problem or a plumbing problem. Often it's the plumbing: the right numbers exist somewhere in the system, they're just not showing up at the moment someone is making the call. If you'd like a second pair of eyes on yours, our free ERP Health Check is a 30-minute way to start.
In short
- Multi-level approvals on requisitions, purchase orders and receipts, with creation limited to authorised users.
- Allocated, utilised and remaining budget shown live on the approval forms and printed documents.
- A chart of accounts designed around real expense heads, with dependent filtering and 50+ budgets linked to operational units.
- Dependent department and branch fields, Tally-ready exports and importers for master data.
