Simplifying Group Consolidation with IBM Controller
5 Practical ways to save time, strengthen controls and make month-end reporting run more smoothly
by Sarah Dow
Group consolidation does not have to become a monthly race against the clock. With the right preparation, communication and use of IBM Controller’s capabilities, finance teams can reduce avoidable work, improve submission quality and focus their energy on review and analysis.
The key is to move as much activity as possible away from the critical close window. The following practical steps can help create a more predictable and efficient consolidation process.
1. Prepare before the close begins
Schedule routine maintenance – such as adding users, updating accounts and changing access – outside the month-end period. A defined maintenance window gives the team time to test access and data input properly, reducing the risk of disruption when reporting deadlines are tight.
Complete any data updates that can be prepared in advance. This may include copying opening balances and journals, processing dormant companies and updating the investment register for acquisitions or disposals.
A clear checklist covering tasks before, during and after month end is invaluable. It provides consistency, supports shared ownership and enables another team member to manage the process confidently when the usual administrator is unavailable.
2. Keep contributors informed
Early communication prevents last-minute confusion. Tell contributors about system or process changes well before month end so they have time to adapt and test their data uploads. During the close, they should be concentrating on loading complete, reconciled data. Not on learning a new process.
Make the maintenance timetable visible and explain why it matters. When everyone understands that controlled change windows protect the reporting timetable, there is less pressure to make risky adjustments during the close.
3. Make the most of Controller Web
Controller Web can make contribution and reconciliation easier by giving users direct browser access, and without requiring the Controller client to be reinstalled after a system upgrade. Its workflow helps guide users towards complete and reconciled submissions and requires them to confirm when their work is complete and ready.
For the central finance team, Controller Web also provides a useful overview of the close. Teams can monitor company and form submission status, copy opening balances, lock or unlock companies and run consolidation activities from one place.
If certain companies are regularly late or need additional support, create filters that show their status by submission and form. This gives the consolidation team a focused exception view, helping them intervene earlier rather than discovering problems close to the deadline.
4. Review what you collect
An efficient close is not only about processing data faster; it is also about avoiding unnecessary collection. Before year end or a budget cycle, review the information requested from reporting units. Confirm that every account and disclosure is still relevant. If an account is redundant, notify users in advance and remove it from the relevant submission’s form set.
5. Structure submissions around the work
Consider whether multiple submissions would improve the flow of the close. For example, collecting intercompany data separately can help contributors focus on reconciliation as a distinct task. Disclosure information can also be separated when it takes longer to prepare than the financial statements, allowing consolidation centres to begin their review while disclosures are still being completed.
The right structure depends on the organisation, but the principle is simple: design the process so that work can progress in parallel and issues become visible as early as possible.
A simpler close starts with discipline
IBM Controller provides the tools to support a controlled and transparent consolidation, but technology works best when it is paired with good operating habits. By planning maintenance outside month end, communicating changes early, monitoring submissions through Controller Web and regularly reviewing the data collection model, finance teams can create a faster and more resilient close.
Quick action checklist
- Agree and publish a maintenance window.
- Complete and reconcile preparatory updates before the close.
- Maintain a shared before, during and after month-end checklist.
- Communicate system changes early.
- Use Controller Web workflow and status views to manage submissions.
- Create exception filters for late or high-support entities.
- Review for redundancy in accounts, forms and disclosures regularly.
- Separate submissions where parallel processing will save time.
If you would like to talk through your specific consolidation process, I would be happy to help you set it up with some bespoke changes to turn your consolidation from a reactive monthly exercise into a repeatable, well-managed process.