IBM Controller + IBM Planning Analytics (PA) = Enterprise Performance Management (EPM) 

By Mark Whitney

Many organisations use IBM Controller for consolidation and IBM Planning Analytics for planning and reporting, but do not always take full advantage of how powerful these applications become when used together. 

When correctly integrated, IBM Controller and IBM Planning Analytics (PA) form a modular Enterprise Performance Management (EPM) solution, combining strong financial control with flexible reporting, analysis, and forecasting. 

This article outlines how the two applications should work together, and why a strategic approach to their integration can deliver significant long-term benefits. 

IBM Controller provides the foundation for group financial reporting. When paired with PA, that foundation can be extended into a far more dynamic EPM solution. 

Configuration and postings managed within IBM Controller can be represented directly within PA. Structures and data that must be controlled carefully for accounting compliance during period-end close in Controller can then be combined with the flexibility, processing power, and analytical capability of PA. 

For example, where Controller presents structured tables for reporting, PA can provide dashboards, interactive analysis, and extended reporting views. Where drill-down in Controller may be limited to standard reports, PA can allow drill-through to much more granular data, including transaction-level detail where required. 

However, the integration between Controller and PA should be viewed strategically, not simply as a technical connection. For IBM customers using only one of these products, or using both without full integration, there is often significant untapped potential. 

We strongly recommend that customers using IBM Controller and Planning Analytics consider the following: 

Use IBM Controller as the single point of ownership for core financial structures.
Controller is well suited to holding key metadata such as company structures and account hierarchies.
Changes should be managed in one place, ensuring consistency and auditability across the group. 

Establish a circular flow of date between Controller and Planning Analytics.
Actuals can flow from Controller into PA for reporting and analysis. Forecasts and budgets created in PA can then be transferred back into Controller, allowing comparison using the same controlled structures and consolidation processing. 

Extend Planning Analytics with additional data sources.
PA can combine financial data with information from other systems, such as HR, operational, or project data. For example, employee headcount and absentee rates can be incorporated to enhance reporting packs, then providing deeper insight via the inclusion of HR metrics.  

Use Planning Analytics to hold detailed reporting cubes ahead of Controller. 
PA can store granular local data, such as cost centre detail or local account codes within single or multiple reporting cubes, then before it is summarised and posted to Controller. Once consolidation results are published back to PA, this allows full end-to-end drill-through from group results down to local ledger detail. 

If you are reviewing your reporting, consolidation, or planning processes, it may be worth exploring how these applications can work together more effectively. We are always happy to share our experience. Speak to one of our specialists. 

Read More Controller Updates & Insights