The week before Shrawan 1 is budget week for many Nepali businesses. The CFO opens a new Excel file, types in last year's revenue number, adds an optimistic 20% growth assumption, and copies down the expense line items with a similar adjustment. The process takes two days. The result is a budget that nobody believes, a spreadsheet that does not connect to the accounting system, and a planning cycle that is already behind before the fiscal year begins.
Annual financial planning done well looks different. It starts in Chaitra with a review of the current year's actuals - what actually happened versus what was planned, and why. Revenue trends by product, customer, and region inform next year's revenue projections. Actual cost patterns replace guessed percentages. Capital expenditure plans are surfaced and approved by the board before commitments are made. When the budget is finalized by Jestha, the management team has a document they built together from real data, and the new fiscal year begins with clarity rather than confusion.
An ERP system that holds the full year's actual data - every sale, every purchase, every expense - turns annual financial planning from a guessing exercise into a data-driven process. The prior year's monthly actuals, cost-center breakdowns, and trend analysis are immediately available. New year projections build from this foundation rather than from memory and assumption. The budget that results is more accurate, more credible, and more useful as a management tool throughout the year.
How ERP Historical Data Transforms Annual Planning
The most powerful input to next year's budget is last year's actual. Not what last year's budget said - what actually happened. The ERP provides this without any manual compilation: monthly revenue by product line, by customer category, by region; monthly expenses by account code, by department, by cost center; seasonal patterns showing which months are high and low for both revenue and cost. This historical data makes the annual planning conversation grounded rather than speculative.
For a Nepali trading company, the data might show that 38% of annual revenue concentrates in Ashwin-Kartik (festival season), operating costs spike in Shrawan-Bhadra (monsoon maintenance and logistics costs), and finance costs peak in Ashadh (year-end bank facility renewals). These patterns - visible in the ERP - should drive monthly budget allocations, not a simple 1/12 monthly split that ignores seasonality entirely.
Historical vendor pricing data from the ERP also improves cost budgeting. If the purchasing module shows that a key input material cost increased 12% last year and the supply chain team expects another 8-10% increase in the new year, the budget reflects that expectation rather than copying last year's cost with an arbitrary adjustment. The conversations between finance, operations, and procurement that happen during budget preparation are more productive when they are grounded in data from the system rather than in conflicting verbal accounts of what prices were.
ERP historical data replaces assumptions with analysis. The difference between a budget built from ERP actuals and one built from memory is not just accuracy - it is credibility. When the CFO presents a budget to the board that is grounded in data the board can verify, the planning process earns the confidence it deserves.
Revenue Budget: Building From Sales Trends and Growth Assumptions
The revenue budget starts with the sales team's projection for each major product line or customer category. This projection is not a wish - it is a target built from historical base, market expectation, and growth initiatives. The ERP provides the base: last year's actual sales by product, by customer, by territory. The sales manager adds the growth assumption and justification: the new distributor in Birgunj adds rū 30 lakhs in the first year; the existing top-10 customer base grows 15% based on expanded orders already in discussion; one low-margin product line is reduced by 20% as pricing is improved.
Monthly phasing matters for cash flow planning. A business where 40% of revenue hits in Ashwin-Kartik needs a revenue budget that reflects that - not a flat monthly target that will show a variance every month except Ashwin and Kartik. The ERP's monthly actuals from prior years provide the phasing pattern. Apply the growth assumption to the annual total, then distribute monthly in proportion to the historical seasonality.
Nepal's Nepali fiscal year creates specific planning milestones that should be built into the annual planning calendar. CIT advance tax installments (Poush, Chaitra, Ashadh) affect cash flow and should be included in the budget. SSF monthly obligations, festival bonus accrual (for Dashain, typically provisioned monthly and paid in Ashwin), and VAT payment cycles should appear in the cost budget with correct monthly phasing. Missing these known obligations from the budget plan creates predictable shortfalls that then need to be explained as "unexpected" when they were entirely foreseeable.
Monthly revenue phasing based on historical seasonality is more useful than a flat monthly split. A business that knows 40% of its revenue lands in two months should build cash flow and staffing plans around that concentration - not be surprised by it every year.
Cost Budget: Using Prior Year Actuals as the Base
Cost budgets built by adding a percentage to last year's budget inherit the errors in last year's budget. Cost budgets built from last year's actuals - the amounts that were actually spent - start from reality. The ERP provides department-level cost actuals at account code level. The starting point for the new year's cost budget is last year's actual spend, adjusted for known changes: new headcount, planned salary increments, changes in activity level, known price changes for major inputs.
Zero-based budgeting - justifying every line from zero rather than adjusting from prior year - is theoretically superior but practically very time-consuming for most Nepali businesses. A practical middle ground is to use prior year actuals as the base for fixed and semi-fixed costs (salaries, premises, utilities), while requiring explicit justification for any variable cost that increases more than 15% from prior year actuals. This focuses the justification effort on the significant changes rather than requiring justification for every routine expense.
Capital expenditure planning - decisions to buy vehicles, equipment, computers, or furniture - should be separated from the operating cost budget. Capex decisions typically require board or owner approval at higher levels than routine operating expenses. The ERP's fixed asset register shows the current asset base, planned disposals, and the depreciation impact of any new purchases. A vehicle purchased in Bhadra at rū 35 lakhs will add approximately rū 7 lakhs in annual depreciation (at 20% WDV) to the cost budget from Bhadra onward - a meaningful budget impact that should appear in the annual plan, not emerge as a surprise mid-year.
Start cost budgeting from prior year actuals, not prior year budget. The actuals show what the business actually spent; the budget may have been aspirational or poorly calibrated. Adjusting from actuals produces a more accurate base for the new year's cost projections.
Presenting the Annual Budget to Board or Investors
The annual budget presentation serves different purposes for different audiences. The board wants to see: revenue growth assumption and its basis, cost discipline versus revenue growth, expected profit margin, capital expenditure plan and its return rationale, and the cash position at year end. Banks reviewing a credit facility renewal want the same financial projections in a format that shows debt service capacity. Investors want to see how the business will deploy capital and what return it will generate.
An ERP-generated budget presentation is more credible than a standalone Excel model because the audience can ask "how does this relate to your actual performance?" and the answer is direct: the budget is built on the ERP's historical actuals, using the same account structure and reporting format as the management accounts they have been reviewing. The budget P&L, budget cash flow, and budget balance sheet are all derived from the same source data as the actual financial statements. This consistency builds confidence in the projections.
The annual budget planning calendar for a Nepali business should look like this: Chaitra - review current year performance and begin revenue discussions with sales; Baisakh - department heads submit cost budget drafts; Jestha - CFO consolidates and challenges submissions; Ashadh - board approves final budget; Shrawan 1 - new fiscal year begins with approved budget entered in the ERP. This timeline gives three months for a serious planning process - enough time to do it well without letting it consume the entire last quarter of the current year.
A three-month budget preparation cycle starting in Chaitra is achievable for most Nepali businesses and produces a budget that the management team believes in and the board can rely on. The Shrawan 1 deadline is fixed - starting earlier is the only variable the business controls.
Frequently Asked Questions
For a first-year business, use industry benchmarks and known commitments as the base. Revenue projections should be conservative and grounded in signed contracts or realistic pipeline. Fixed costs are usually known with high confidence: premises rent, staff salaries, insurance, and utility estimates. Variable costs should be benchmarked against similar businesses in the sector. Most importantly, model the cash flow monthly - a first-year business often has good revenue projections but does not account for the ramp-up period where costs precede revenue. The cash position in months 1-6 is typically the most critical planning challenge.
The annual budget should be detailed enough to hold departments accountable but not so detailed that it takes more time to maintain than it is worth. A practical level is major account code groups within each department - staff costs, premises costs, marketing, travel, professional fees, and operations - with monthly phasing. Individual expense line items (printer cartridges, office tea supplies) do not need their own budget line. The budget should fit on a one-page summary for the board and a detailed departmental breakdown for management. If the budget takes more than three Excel tabs, it is probably too detailed for the business's current size.
Yes - a contingency provision of 3-5% of total budgeted costs is standard practice for Nepali businesses operating in an environment with political, weather, and supply chain uncertainty. This contingency is held centrally by the CFO, not distributed to departments. It is released to cover genuine unforeseen events - a monsoon landslide disrupting supply chain, an unexpected tax assessment requiring professional fees, a sudden price increase in a key input. The contingency provision prevents unplanned events from immediately breaking the budget and triggering an emergency revision process. It should not become a routine top-up for poor budget discipline in individual departments.
Annual Financial Planning Grounded in Your ERP Data
MISAC's financial planning capability starts with the data it already holds. Every year of actuals - monthly revenue by account code, cost by department, asset purchases, bank movements - is available as the planning baseline without any manual compilation. The CFO exports the prior year actuals in the planning format needed, builds the new year's adjustments, and enters the budget into MISAC for the start of the new fiscal year. From Shrawan 1, every accounting entry is automatically compared to the budget, and the budget vs actual report updates in real time.
Custom financial statement grouping means the budget can be presented in any format required - a simplified four-line summary for the board, a detailed departmental breakdown for management review, or the account-code-level detail for the CFO's own analysis. All three views come from the same budget data in the same system. When the board asks how the current year is tracking against plan, the CFO pulls the same budget vs actual report that has been reviewed internally all year - there is no gap between the internal management view and the board presentation view.
MISAC Intelligence Pvt. Ltd. has supported annual financial planning for businesses across Nepal's trading, construction, education, and NGO sectors. The consistent finding is that the first year using ERP historical data for budget preparation takes more effort than the Excel guessing method - but produces a budget that actually guides management decisions through the year. By the second year, the process is faster because the ERP has two years of comparable data, and the planning conversations are more productive because everyone is working from the same numbers.
Ready to See MISAC in Action?
Contact us to see how MISAC's budget and planning module works with your existing accounting data for next year's financial plan.