Client & Context

The project was implemented in a banking domain environment, covering multiple service areas including Markets, Services, and other financial modules.

The organization required a unified system to handle planning, budgeting, and reporting across different business units with consistent logic and structure.

Headline results:

• Multiple service modules with separate reporting structures
• Need for centralized reporting and consolidation
• Requirement for dynamic and scalable Cube View design
• Increasing dependency on dashboard-driven insights

Role & Contribution:

• Developed Cube Views for multiple service modules
• Designed and implemented Dashboard-driven reporting workflows
• Built dynamic Business Rules for calculations
• Configured scenario handling and data copy processes
• Supported UAT and validation activities

Challenges

Before OneStream, the month‑end close process was slow, error‑prone, and highly dependent on a few key individuals

Key challenges included:

• Fragmented Reporting Across Modules: Each service module had separate reporting logic, making consolidation difficult.
• Manual Reporting and Data Handling: Significant manual effort was required to generate reports.
• Lack of Reusable Calculation Logic: Business logic was not centralized, leading to duplication.
• Complex Planning and Budgeting Requirements: Handling multiple scenarios (Actual, Plan, Budget) required structured design.
• Limited Dynamic Reporting Capability: Reports were not flexible for year-on-year comparison or multi-dimensional analysis.

The client needed a solution that would reduce manual work, standardize the consolidation model, and provide a scalable foundation for future acquisitions, without disrupting ongoing statutory reporting.

Our Approach

A structured and scalable solution was implemented using Cube Views, Dashboards, and Business Rules.

Initial Development Period – Cube View Design for Service Modules (Weeks 2–5):

• Developed approximately 10 Cube Views covering different banking service areas
• Each Cube View was designed to support:
  • Planning
  • Budgeting
  • Actual reporting

Mid-development Phase – Master Cube View (Weeks 5–6):

• Created a Master Cube View combining all module-level Cube Views
• Included:
  • Capital-related reporting
  • P&L reporting
  • Revenue-based reporting
• Enabled a single consolidated view across all services

Core Development Phase – Dynamic Business Rules Implementation (Weeks 4–7):

• Implemented centralized dynamic Business Rules to control:
  • Column generation
  • Row structure
  • Calculation logic
• Supported dynamic calculations such as:
  • Revenue-based computations
  • Derived financial metrics
  • Scenario-based calculations

Later Development Phase – Dashboard Implementation (Weeks 6–8):

• Designed dashboards to:
  •  Drive Cube View selection
  • Control reporting parameters
  • Provide user-friendly navigation
• Included:
  
  • Scenario selection (Actual, Plan, Budget)
  • Year and period filters
  • Module-level navigation

Development and Pre-UAT Phase – Scenario & Data Copy Process (Weeks 7–8):

• Implemented structured steps for:
  • Scenario selection
  • Data copy between scenarios (e.g., Actual to Plan)
  • Controlled data flow for planning cycles
• Ensured consistency and accuracy in reporting

Final Development Phase – Dynamic Reporting Capability (Weeks 7–9):

• Enabled year-on-year comparison reporting
• Supported:
  • Multi-dimensional analysis
  • Dynamic column updates
  • Flexible report views

Final Phase – UAT & Enhancements (Weeks 10–14):

• Participated in:
  • User Acceptance Testing (UAT)
  • Issue resolution and validation
  • Continuous improvements

Throughout the project, a small joint working group (group finance, IT, and our consultants) met weekly to remove obstacles and make quick decisions on design trade‑offs. This allowed the team to stay on schedule despite the complexity of the multi‑ERP environment.

Results

After go‑live, the client achieved significant improvements in both efficiency and control

Key Outcomes:

• Established a centralized reporting framework across all banking services
• Reduced manual reporting effort significantly
• Enabled dynamic and flexible Cube View reporting
• Improved accuracy through centralized business rules
• Enhanced user experience via dashboard-driven navigation

Business Impact:

• Faster report generation and analysis
• Improved decision-making through real-time insights
• Standardized reporting across modules
• Reduced dependency on manual processes

A senior finance stakeholder summarized the impact by noting that group discussions have shifted “from fixing numbers to understanding what the numbers are telling us”.

What’s Next?

With the consolidation and reporting foundation in place, the client has defined a roadmap to extend OneStream into additional areas

• Expansion of Cube Views to additional banking modules
• Enhancement of advanced analytics and KPIs
• Further optimization of Business Rules for performance
• Increased automation in planning and forecasting processes

Our team continues to support the client through periodic health checks and performance optimization, ensuring the solution keeps pace with business and system changes