Experiences from implementing machine learning (ML) for forecasting

Experiences from implementing machine learning (ML) for forecasting

By Asif Khan, Global FP&A at PayU

The democratization of technologies is underway. Technologies like machine learning which just until a decade ago were confined to universities, hedge funds or investment banks, are now finding their way into industry-wide applications. Our finance function is set to reap the benefits of this democratization wave.

In my company’s finance function, last year we decided to test ML’s effectiveness in forecasting the financials. Below I share our thought process about WHY and HOW we went about implementing ML-based models for forecasting. 

Starting with WHY

The first step of the path towards implementing ML in finance function was to understand the WHY? As Simon Sinek puts it in his hugely viral video “Start with Why”

Before starting with ML-based forecasting, we were doing bottom-up forecasting on a monthly basis. This involved the finance teams of regions/countries to discuss with commercial teams, do pipeline analysis and perform seasonality checks, etc. to come to a forecast. However, the results of the forecast were suboptimal due to four key factors: 

  1. Industry growth: Our company operates in Fintech and payments industry where some markets are growing substantially on a yearly basis which makes forecasting difficult. Therefore, the bottom-up forecast results for these hyper-growth markets were off significantly – sometimes even by 5-10% variance for the upcoming quarter 
  2. Drivers: The above is explained to an extent by the fact that the industry is relatively new and therefore business drivers are not always fully clear. While doing bottom-up forecasting, the regions and countries were taking mostly internal drivers as inputs, while there was less focus on external drivers 
  3. Time taking exercise: The bottom-up forecasting is manual, requiring inputs from multiple departments and taking significant man-hours from start to finish
  4. Biases: Biases feed into the forecasting process. For example, a commercial team member might be too aggressive or pessimistic on the growth expectations   

Hence, our WHY to implement ML-based models was to improve the accuracy levels and speed of forecasting while reducing the time needed to come to forecast.  

Proceeding with HOW

We took a very agile approach to ML model implementation in our company - not going all in on ML with a lot of resources. The idea was to come to prototype versions of ML models – and test if there is some real merit in using these models. The criterion of success of prototype was very simple: Can the prototype models forecast better than bottom-up process?

To come to the prototype, we formed a small team. Having engineers in finance team helped (my one direct report and I, both have engineering backgrounds), and we also sought help from tech team members on a part-time basis. Since machine learning was a new area for us all, we took self-learning classes from some of the fantastic courses available on leading online learning platforms. 

Next step was data preparation. We had data sitting in silos – so connecting all the data sources, cleaning it, removing the outliers and then making a useable and clean data repository was a crucial step. 

Finally, we managed to start implementing ML algorithms on the processed data sets. We divided the data into 2 sets: (i) Training data: to train the ML models, and (ii) Test data: To test the trained models on actual historical data. This helped us to increase our confidence in the predictive power of the models. 
It took us around 3 months to have a prototype version of the ML models. This timeframe really depends on the complexity of each individual companies, and the purpose of usage. 

Figure 1: Architecture supporting ML Project for forecasting

Benefits achieved in the first 3 months

In our case, using ML models for forecasting really lived up to the expectations and promise. We used these models to forecast revenue, gross margin and EBITDA. Utilizing these models also provided several benefits across accuracy, speed and flexibility:

  1. Accuracy: The forecast variance versus actuals using ML models was down to less than 2% even in case of difficult to forecast markets where we earlier had a variance of 5-10%. With our high growth rates, this is a substantial improvement
  2. Speed: Complete bottom-up forecasting took us in some cases almost a week. Now using the trained ML models, we can perform robust forecasting in a day 
  3. Flexibility: Using ML algorithms enabled us to: (i) test number of drivers relatively quickly, and (ii) helped in process of driver discovery – or finding new drivers which we were unaware of. We can also quickly consider and test more drivers – both internal and external. This improves the understanding of business and sometimes helps give early warning signs


Our initial foray into using ML capabilities for forecasting has been successful. ML models are data hungry, so we have continued to enrich our models and are still testing them to get better accuracy levels. We will also be creating new models for products which were not in scope for the prototype version. 

Our experience with implementing ML models for forecasting has encouraged us to also look at other processes within the finance function where ML can be used to full advantage.   

The full text is available for registered users. Please register to view the rest of the article.
to view and submit comments