How CGB Enterprises Brought Reporting Across 15 Business Units into One Environment
Replacing repeated report versions with a shared reporting structure across Microsoft Dynamics GP and Business Central.
Download the original case study PDF
Illustrative photograph/US%20Case%20Studies/CGB%20Enterprises_Case%20Study.png?width=400&height=400&name=CGB%20Enterprises_Case%20Study.png)
Grain, agriculture and distributionUS customer story
- Customer
- CGB Enterprises
- Industry
- Grain, agriculture and distribution
- ERP
- Microsoft Dynamics GP / Business Central
At a glance
CGB combined four reporting systems into one and replaced 30 versions of the same report with a shared report using reporting trees.
The Situation
CGB Enterprises operates grain trading, storage, logistics and related businesses in the US. Reporting across 15 business units involved four systems and financial packs assembled in Excel.
What Was At Stake
- Information needed checking across separate systems.
- Multiple versions increased report maintenance.
- Group reporting needed consistency alongside local views.
The Turning Point
CGB selected Solver for its Excel-based design, reporting trees and central account mapping across Dynamics GP and Business Central.
This US project was implemented with a Solver Gold Partner in three phases over two to three years, as documented in Solver Global’s case study.
What the Team Did
Creating a Shared Report Structure
Reporting trees provide different business-unit and location views from a single report.
Centralising Mapping and Access
Account mappings are maintained centrally, while dimension-level security controls the data users can see.
“We can build a single report and utilize trees to produce the financials we need across all our business units.”
The Result
CGB reports that report creation moved from days to minutes.
- Four reporting systems were brought into one.
- Repeated report versions were reduced.
- Month-end reconciliation and location onboarding use the same platform.
What They Can Do Now
- Run shared reports across business units.
- Maintain account mappings in one place.
- Provide authorised views of local financial information.
Why It Worked
Consistency Built into the Design
For a group finance team, consistency is easier to maintain when reporting rules have a clear home. A shared structure gives the team a way to address changes once and consider their effect across the reporting hierarchy.
Local Detail Within a Group View
A consolidated view needs to remain useful to the people managing individual operations. Designing the hierarchy and access rules together helps a reporting process serve both central oversight and local responsibility.
Discuss your multi-entity reporting requirements.
Based on Solver Global’s original CGB Enterprises customer story. Customer details and outcomes relate to the implementation described in that source.