Nepal's economic environment makes static annual budgets genuinely inadequate as management tools. Consider what a Nepali CFO faced in a single 12-month period in recent years: a 15-18% diesel price increase announced by NOC in Poush, a significant rupee depreciation against the USD affecting import costs through Chaitra-Baisakh, a political transition creating procurement uncertainty in Shrawan-Bhadra, and an unexpected credit policy change from NRB that tightened working capital facility terms in Mangsir. Each event materially changed the cost structure and revenue outlook for businesses operating in Nepal. A budget prepared in Ashadh of the prior year bore no relationship to this reality by Poush.
This is not a criticism of annual budgeting - it is an observation about the limits of static planning in a volatile environment. The annual budget still has value: it represents the management team's best judgment at the start of the year about what the business should achieve, and it provides a fixed baseline for accountability. But a document prepared once per year is a planning artifact, not a management tool, if it cannot respond to material changes in the business environment within the fiscal year.
A rolling forecast is the management tool that addresses this gap. Unlike the annual budget - which is fixed once approved - a rolling forecast is updated monthly or quarterly to reflect actual performance and revised expectations. It always covers the next 12 months, regardless of where in the fiscal year the business currently sits. In Poush, the rolling forecast covers Poush through the following Mangsir. In Baisakh, it covers Baisakh through the following Chaitra. The management team always has a 12-month forward view built from the most current available information.
The Limitations of Static Annual Budgets in Nepal
A static annual budget has three structural limitations in Nepal's operating environment. First, the planning assumptions that seemed reasonable in Ashadh may become obsolete within 2-3 months when import costs change, a key customer reduces orders, or a competitor changes pricing. Second, the budget comparison in month 9 or 10 shows a variance but cannot indicate whether the full-year outcome will be better or worse than plan - the past variance is visible but the future remains unexamined. Third, operating against an irrelevant budget creates perverse management behavior: departments declare victory against targets that stopped being meaningful months ago, while the real business challenges are not surfaced because nobody has articulated what the revised expectations are.
The CFO who realizes in Falgun that this year's profit will be 30% below budget because of cost increases that were not anticipated in Ashadh faces a choice: present the bad news against an irrelevant budget baseline, or have a different conversation about where the business actually is and what it should do in the remaining 4 months. The second conversation is more useful, and it requires a rolling forecast, not a fixed budget.
"A rolling forecast does not replace the annual budget's accountability function - it adds the forward-looking management function that the static budget cannot provide. They work best together."
A principle from management accounting practice in high-volatility markets
The annual budget is fixed for a reason - it provides accountability. The rolling forecast is dynamic for a reason - it provides management relevance. Running both simultaneously gives the CFO the best of both tools: a fixed baseline for accountability and a continuously updated forward view for decisions.
Building a Rolling Forecast Structure
A rolling forecast has three components: the actuals to date (direct from the ERP), the forward projection for the remaining months in the 12-month window (the forecast), and the key assumptions that drive the forward projection. The actuals to date are objective - they are what happened. The forward projection is the CFO's best current judgment about what will happen. The assumptions are the drivers that link the two: if the USD/NPR rate stays at the current level, the import cost assumption holds; if it depreciates another 5%, the cost assumption needs revision.
Revenue forecasting in the rolling model starts with the pipeline: confirmed orders and expected orders from the sales team by customer and period. This is supplemented by a run-rate analysis: if the business has been growing at 12% in the first eight months, the forward projection for the remaining four months uses that rate unless there is a known reason for the trend to change. Changes in the pipeline (a major customer order confirmed or delayed) update the forecast in the next monthly cycle.
Nepal's specific macro drivers that should be modelled explicitly in a rolling forecast: NOC fuel price (affects transport cost for trading and logistics businesses), NRB buying/selling rate for USD (affects import cost for businesses with foreign currency purchases), Kathmandu wholesale price index changes for major commodities (affects input cost for manufacturers and traders), and political event calendar (elections, bandhs, major festivals) affecting sales volume and logistics timing. A rolling forecast that models these four drivers as explicit inputs - rather than leaving them as implicit assumptions - gives the CFO the ability to run sensitivity analysis: "what if diesel increases 10% in Poush?" and immediately see the full-year profit impact.
Making Nepal's major economic drivers explicit in the rolling forecast model turns sensitivity analysis from an Excel exercise into a real-time capability. When NOC announces a fuel price change, the CFO can model the impact on the 12-month forward view within an hour, not a day.
The Rolling Forecast Update Process
A monthly rolling forecast update follows a consistent process. Week 1 of each month: accounts are closed for the previous month, and actuals are confirmed. Week 2: the forecast team reviews the forward months - revenue pipeline update from sales, cost assumption updates for any known changes (confirmed new hires, price notices from suppliers, changes in loan terms), and capex timing updates. The rolling forecast model automatically extends by one month when the near-term month becomes actuals, maintaining the 12-month forward window. The full update cycle should take 2-3 working days for a business of 20-50 staff.
The rolling forecast review meeting - monthly, attended by the CFO, department heads, and the business owner or CEO - has a different agenda from the budget review meeting. The budget review asks: "What happened and why did we miss budget?" The rolling forecast review asks: "What is our current best view of the next 12 months and what decisions should we make based on it?" The second question drives forward-looking action: adjust a supplier contract, defer a capital purchase, accelerate a collection campaign, revise a pricing decision. These actions have impact because there are still months ahead for them to take effect.
Rolling forecasts require a discipline shift that goes beyond the technical setup. Finance teams accustomed to monthly reporting (backward-looking) need to develop the capability for monthly forecasting (forward-looking). The skills are different: reporting requires accurate data entry and reconciliation; forecasting requires judgment, assumption-building, and the willingness to commit to a forward view that may be wrong. Building forecasting capability in the finance team takes 2-3 quarterly cycles. The first rolling forecasts are often over-detailed and inaccurate in the outer months; by the third cycle, the team has calibrated their assumptions and the outer months' accuracy improves significantly.
The value of a rolling forecast comes from the forward view it enables, not from its accuracy in the outer months. Accept that months 10-12 of the forward window will be approximate. The management value is in identifying trends and inflection points early - not in precise prediction of what will happen in a specific future month.
From Annual Budget Compliance to Business Forecasting Culture
The cultural shift that rolling forecasts require is significant. In a static budget culture, the management conversation is backward-looking: "We are 8% over budget on marketing this year." In a rolling forecast culture, the conversation is forward-looking: "Based on the current forecast, we are on track to end the year 12% over on marketing. Here is what we are doing about it in the remaining four months." The first conversation explains the past; the second conversation manages the future.
Building this forecasting culture requires consistent leadership from the CFO and business owner. If the monthly rolling forecast review becomes a performance evaluation meeting where managers are penalized for revising their forecasts, they will stop revising - which defeats the purpose. The forecasts must be explicitly positioned as management tools that are expected to change as conditions change. Stability in the annual budget (accountability anchor) combined with responsiveness in the rolling forecast (management tool) is the right balance.
For businesses ready to move beyond annual budgeting, the transition need not happen all at once. Start by adding a simple 6-month rolling revenue forecast to the monthly management pack - just the revenue line, updated monthly from the ERP actuals and sales pipeline. Once the team is comfortable with the forward revenue view, add cost forecasting for the major variable cost categories. By the end of the first year, the rolling forecast capability is established and the business has made its first management decisions based on forward-looking data rather than backward-looking variance reports.
Start the rolling forecast journey with revenue forecasting only - 6 months forward, updated monthly from ERP actuals and pipeline. Master one component before adding cost forecasting. The goal is building the organizational muscle for forward-looking financial management, not deploying a complex model on day one.
Frequently Asked Questions
An updated annual budget stops at the end of the fiscal year regardless of when it is updated. A rolling forecast always extends 12 months forward from the current date - so a forecast updated in Poush covers the next 12 months (Poush through Kartik of the following year), extending one month beyond the current fiscal year. This matters because planning decisions made in Poush about staffing, capital investment, or financing often have effects that extend into the next fiscal year. The rolling forecast makes these cross-year implications visible, while an updated annual budget stops at Ashadh even though business decisions do not.
For a business with 20-100 staff and a single operational entity, a monthly rolling forecast update should take 1-2 working days by month 3-4 of the process. The first two cycles take longer (3-5 days) as the team builds the model and establishes the update process. The model itself - a structured spreadsheet or ERP-linked template - does most of the mechanical work; the finance team's time is spent on judgment calls about the forward assumptions, not on data compilation. The investment of 2 days per month for a forecast that guides management decisions for the remaining 11 months is one of the highest-return activities in finance.
No - they serve different purposes. The annual budget is the accountability anchor: it represents the management commitment made at the start of the year, and performance against it is assessed in the annual review. The rolling forecast is the management tool: it provides the continuously updated forward view that drives current decisions. Replacing the annual budget entirely with a rolling forecast removes the accountability reference point - departments could argue that any outcome was "within the forecast" if the forecast is revised every month. Running both - a fixed annual budget for accountability and a rolling forecast for management - is the approach used by most sophisticated finance functions globally.
Rolling Forecasts Built From Live ERP Data
MISAC's reporting infrastructure provides the actuals foundation for rolling forecasts in real time. The monthly actual data - revenue by product and customer, cost by department and account code, cash position - is always current because it draws from the live accounting system. When the finance team updates the rolling forecast, the actuals side of the model is already correct; the only manual input required is the forward assumption updates for the next 12 months. Pivot table analysis on the actuals data makes run-rate calculations - the extrapolation of current trends into the forward months - fast and accurate.
MISAC's AI capabilities extend into pattern recognition: identifying cost trends that are diverging from plan, flagging revenue lines where the actual run rate is significantly above or below the forecast, and surfacing anomalies that warrant management attention before they become problems. The AI does not replace the CFO's judgment on forward assumptions - it directs the CFO's attention to the areas where judgment is most needed, rather than the areas where the business is running as expected. This is particularly valuable in businesses with many cost lines where manual review of every line monthly is not practical.
MISAC Intelligence Pvt. Ltd. has supported rolling forecast implementation for Nepal's larger trading companies, manufacturing firms, and NGOs operating in volatile funding environments. The technical implementation is straightforward; the cultural change - from budget compliance to forward-looking financial management - is where we spend most of the advisory effort. The businesses that succeed with rolling forecasts are those where the CFO and the business owner both commit to using it as the primary management conversation tool, not just as an additional finance report.
Ready to See MISAC in Action?
Talk to us about building a rolling forecast capability on top of your existing MISAC accounting data.