When every spending decision routes through one finance manager or owner, the business has a structural bottleneck it calls financial control. It is not control - it is centralized approval dependency. The finance manager approves stationery purchases, vehicle fuel advances, marketing expenses, and IT subscriptions at the same time they are trying to close the monthly accounts. Everything slows down. The people closest to the spending decisions have no authority or visibility over their own budgets. And yet the spending happens anyway - just slowly and with more friction than necessary.
Departmental budget planning is the organizational approach that decentralizes this. Each department head is given a budget for the year - a defined amount for each expense category within their control. They are responsible for managing within that budget. Finance's role shifts from approving every transaction to monitoring compliance with the agreed budget and approving exceptions. The department head gains autonomy within a defined boundary; finance gains visibility and accountability without becoming a bottleneck for routine expenses.
This is a sign of a maturing Nepali business. Organizations that have moved to departmental budget ownership consistently find that spending discipline improves when the person spending the money also owns the budget. When a department head can see that their travel budget is 70% consumed by month 7, they manage the remaining months differently than if they have no visibility of their own position. Ownership creates accountability that central control cannot manufacture.
Define Department Boundaries and Budget Categories
The first step is defining which departments exist for budgeting purposes and what expense categories each department controls. A typical Nepali trading business might have: Sales, Operations, Finance, HR, and IT. Each department gets a budget for the expense categories it controls. Sales controls marketing spend, client entertainment, and team travel. Operations controls vehicle running costs, warehouse expenses, and maintenance. Finance controls audit fees, banking charges, and financial software. HR controls training, recruitment, and employee welfare. IT controls hardware, software subscriptions, and internet costs. Shared costs (premises, utilities) are managed at the organization level by finance. Getting this mapping right is more important than the budget numbers - unclear ownership creates boundary disputes that undermine the whole process.
Build the Bottom-Up Budget Submission Process
Departmental budgets built by finance without department head input are compliance exercises. Budgets built by department heads with finance guidance are ownership exercises. The process works as follows: finance provides each department head with the previous year's actuals for their cost categories and a template for the coming year's submission. Department heads fill in their projected spending for each category, with notes on significant changes from the prior year. Finance reviews submissions for reasonableness, challenges unusual items, and consolidates into the organization budget. The department head who built the numbers owns them; they cannot claim the budget was unrealistic if they built it themselves.
Nepal's Shrawan fiscal year start makes Chaitra-Baisakh (April-May) the natural budget preparation window. Budget preparation in the last month of the fiscal year (Ashadh) is too rushed; starting in Chaitra gives time for a proper bottom-up process with two rounds of review before the new year begins. Many Nepali businesses skip the budget process entirely and reset from scratch in Shrawan - this article's process gives a practical framework for those doing it properly for the first time. The first year requires more effort; subsequent years build on the prior year actuals already in the ERP.
Configure Budget Access and Approval Levels
Once the annual budget is set, configure the system so each department head sees their own budget vs actual at any time. Define the approval authority levels: expenses within budget require only department head approval; expenses that would exceed budget require CFO or owner approval. Set up the alert thresholds - notify the department head when 70% of their budget is consumed, escalate to the CFO when a department exceeds 100%. These configurations are one-time settings that apply throughout the year without finance intervention per transaction. The result: routine expenses within budget move quickly through department head approval. Only exceptions require the CFO's time.
Budget access control needs to be granular but not complex. Department heads should see their own department's full budget vs actual, including all line items. They should not see other departments' budgets. Finance and the CFO should see all departments. Where shared cost centers exist (premises, utilities), those should be visible to finance only, or to a selected group of department heads if cross-departmental cost allocation is being managed. Setting these permissions in the ERP at the start of the year takes 30 minutes; it replaces months of ad-hoc access decisions throughout the year.
Run Monthly Budget Review Meetings
The budget review meeting - monthly, 30-45 minutes, with department heads and the CFO - is where budget ownership becomes tangible. Each department head presents their budget vs actual for the month: what was planned, what was spent, what drove variances, and what they expect for the remainder of the year. Finance prepares the consolidated view. The CFO challenges significant variances and approves budget revisions where justified. This meeting structure makes budget management a shared conversation rather than a finance-only exercise. After two or three monthly cycles, department heads arrive prepared because they have been monitoring their position during the month - the meeting becomes a confirmation and alignment session rather than a first look at the numbers.
Handle Budget Revisions Formally
Mid-year budget revisions happen in every business. The discipline is in the formal process: a revision requires a written justification explaining why the original budget is no longer appropriate, a revised figure, and CFO approval. Revisions should be documented in the system so the audit trail shows the original budget, the revision, and the approver. Some revisions are legitimate - a new product launch requires unplanned marketing spend; a large new customer requires additional operations headcount. Others reflect poor original planning or lack of discipline. The formal revision process distinguishes between the two and creates the institutional memory that improves future budgets.
Departmental budget ownership is a five-step journey: define department boundaries, build budgets bottom-up with department head input, configure self-service access and approval levels, run monthly review meetings where department heads present their own numbers, and handle revisions formally with audit trail. Each step builds the organizational capability for the next one. Most Nepali businesses can complete this journey in one fiscal year if they start the process in Chaitra-Baisakh.
Frequently Asked Questions
The budget is a ceiling, not a target. Setting this expectation explicitly at the start of the process matters. Reinforce it in the monthly review meetings: departments that come in under budget are recognized positively, not penalized by receiving a reduced budget the following year. If department heads believe underspending leads to budget cuts, they will spend up to their limit regardless of need. Carry-forward provisions - allowing some portion of underspend to roll into the next year's budget - incentivize genuine frugality rather than end-of-year panic spending.
Emergency or unforeseeable expenses that exceed budget should go through a quick exception approval process: the department head submits a brief written request explaining the expense and the reason it was not anticipated, with the amount and cost category. The CFO approves or declines with a note. If approved, the expense is coded to the department's budget with an overrun approved marker - it counts against the budget for reporting purposes but is flagged as an approved exception. This process should take no more than an hour end-to-end for genuine emergencies. The goal is not to create bureaucracy but to maintain the audit trail that distinguishes authorized exceptions from undisciplined spending.
Formal departmental budgeting with separate department heads and monthly review meetings is typically appropriate from 25-30 staff upward. Below that, an organization-level budget tracked monthly by the owner or a single finance person usually works better. The transitional step for smaller businesses is to categorize expenses clearly in the chart of accounts (even without formal departmental ownership) and review budget vs actual at the category level monthly. When the business grows to the point where individual cost categories are managed by different people, that is the natural trigger for introducing departmental budget ownership.
Departmental Budgets in the Same Platform as Your Accounts
MISAC's budget module integrates directly with the chart of accounts. Department budgets are entered against cost center codes that correspond to the department structure - every expense entry in the accounting system automatically updates the relevant department's budget consumption. There is no separate budget tracking sheet to maintain alongside the accounts, and no end-of-month exercise to reconcile the two. The budget vs actual is always current because it draws from the same entries as the P&L.
Access control is configured at the department level: each department head logs into their own MISAC view and sees their department's budget vs actual, their approval queue for expenses within their authority, and alerts for approaching budget thresholds. The CFO sees the consolidated view across all departments plus the exception approvals that escalate to them. Pivot table analysis lets the CFO drill from the organizational budget summary into any department, any cost category, and any individual transaction in one click - without switching tools, exporting data, or waiting for someone to pull a report.
MISAC Intelligence Pvt. Ltd. has helped Nepali organizations move to departmental budget ownership by configuring the cost center structure, budget entry, and approval levels in the same implementation as the core accounting setup. The transition from central control to departmental ownership is a process change more than a technology change - but the technology needs to support the process. MISAC's modular design means you can start with finance-only budget tracking and extend to department head access when the organization is ready for the next step.
Ready to See MISAC in Action?
Talk to us about setting up departmental budget planning and tracking for your organization in MISAC.