Multi-Entity Consolidation Without the Workpapers: How Cloud ERP Changes Month-End for Hospital Networks
If you run finance at a multi-site healthcare organization, you already know how this works.
Close starts. Each entity exports its trial balance. Someone reformats the data in Excel. Intercompany transactions get identified, matched, and eliminated by hand. Consolidation workpapers are built, cross-checked, and rebuilt when numbers do not tie. Board packages get assembled manually from the rolled-up data. The whole process takes 12 to 18 business days, and the team spends most of that time on work the system should be doing for them.
This is not a process. It is a workaround that hardened into a routine.
For Controllers and VP Accounting leaders at hospital networks, multi-entity consolidation is consistently the single largest operational pain point. Not because the team lacks skill or effort, but because the underlying system was not designed for the way healthcare organizations actually operate.
Here is what that process looks like on a legacy ERP, what it looks like on a properly configured cloud platform, and why the difference matters more than most organizations realize.
The Legacy Consolidation Workflow: Where the Time Goes
Let’s map where the hours actually accumulate during a typical monthly close at a multi-entity healthcare organization running on-premise ERP.
Data extraction (Day 1 to 3):
Each entity runs its own close process. Trial balances are exported from the ERP, usually as CSV or flat files. If the organization runs different GL structures across entities (which is common after acquisitions), someone has to reformat and remap account codes before anything can consolidate. At organizations with 10 or more entities, this step alone can consume 2 to 3 full days of staff time.
Intercompany reconciliation (Day 3 to 7):
Management fees, shared services allocations, intercompany payables and receivables all need to be identified and matched. On legacy systems, this is a manual hunt through transaction detail. Mismatches trigger back-and-forth between entity-level accountants. One unresolved intercompany difference can hold up the entire consolidation.
Workpaper assembly (Day 5 to 10):
This is the layer that most legacy organizations have built over years: Excel workbooks that consolidate trial balances, apply elimination entries, and produce rolled-up financials. These workbooks are fragile. They depend on consistent formatting from source data. They break when entities are added. They require the person who built them to maintain them, because the logic lives in nested formulas that no one else fully understands.
Board package preparation (Day 10 to 15):
Once consolidated numbers are final, they get formatted into board-ready reports. This is another manual step: copying data into PowerPoint or Word templates, rebuilding charts, adding commentary. By the time the board sees the numbers, they are 3 to 4 weeks old.
Audit support (ongoing):
Auditors request supporting detail. Because the consolidation lives in workpapers, not in the system, the finance team has to reconstruct the audit trail from Excel files, manually trace eliminations back to source transactions, and explain workpaper logic that was built by someone who left two years ago.
At a 10-entity healthcare organization, this process consumes 200 to 400 staff hours per close cycle. Scale that to 20 or 30 entities, and you are looking at a team that spends the majority of its time on data manipulation, not financial analysis.
The Cloud-Native Alternative: Dimensional Consolidation
Moving to the cloud alone does not fix consolidation. Plenty of cloud-hosted platforms still require the same manual rollups, the same workpaper layer, the same multi-day process. What changes the consolidation model is not the delivery method. It is the architecture underneath it.
Sage Intacct was designed from the ground up around a dimensional general ledger, and that architectural decision is what makes the difference.
Instead of maintaining a separate chart of accounts for each entity, Intacct’s dimensional GL uses a single, unified COA with dimensions that tag every transaction: entity, department, location, service line, payer, fund, grant. Consolidation is not a step. It is a view. You are not rolling up separate databases. You are slicing one database along different axes.
Here is how the same close process looks:
Data flows continuously:
Transactions from each entity post to the same GL in real time. There is no export step. There is no reformatting step. When a clinic posts a journal entry at 3pm, consolidated financials reflect it by 3:01pm.
Intercompany entries are automatic:
The system is configured with intercompany rules that trigger entries as transactions post. When Entity A bills Entity B for a management fee, the system creates the intercompany entry automatically. No manual matching. No reconciliation spreadsheets. No hold-ups waiting for one entity to confirm a balance.
Consolidation is a report, not a project:
Pulling consolidated financials across 5, 10, or 40 entities is a report parameter, not a multi-day process. You select the entities. You select the period. The system produces consolidated financials with drill-down to the transaction level. The same report that took two weeks to build in Excel takes seconds.
Board packages are always current:
Because consolidation is continuous, board-ready dashboards and reports can be generated at any point in the month, not just after close. Some organizations move to a model where the board sees preliminary financials by day 3, with final numbers by day 5. The lag between reality and reporting shrinks from weeks to days.
Audit trail is native:
Every elimination entry, every intercompany transaction, every consolidation adjustment lives in the system with a complete audit trail. There is no workpaper layer to reconstruct. Auditors can trace from consolidated balances to source transactions without leaving the platform.
The Workflow Comparison: Side by Side
| Close Activity | Legacy ERP (Manual) | Cloud-Native (Dimensional GL) |
|---|---|---|
|
Data extraction and reformatting
|
2 to 3 days, manual CSV exports and remapping
|
Eliminated. Continuous data flow.
|
|
Intercompany reconciliation
|
3 to 5 days, manual matching and follow-up
|
Automatic. Rules-based elimination on posting.
|
|
Workpaper-based consolidation
|
3 to 5 days, Excel workbooks with nested formulas
|
Eliminated. Consolidation is a real-time report.
|
|
Board package assembly
|
2 to 3 days, manual formatting in PPT/Word
|
Automated dashboards, always current.
|
|
Audit support
|
Ongoing, reconstruct trail from workpapers
|
Native. Full drill-down from consolidated to source.
|
|
Total close timeline
|
12 to 18 business days
|
3 to 5 business days
|
|
Staff hours per close
|
200 to 400+ hours (10 entities)
|
40 to 80 hours (10 entities)
|
The hours freed up do not disappear. They redirect. Controllers who spend 60% of their month on consolidation mechanics start spending that time on variance analysis, service-line profitability reviews, and proactive financial guidance to operational leaders. That is the shift from accounting department to strategic finance function.
What This Means at Scale
The consolidation problem compounds. Every entity you add to the network adds another data source, another set of intercompany transactions, another column in the workpaper. On a legacy system, growth is a linear multiplier on close effort.
On a dimensional GL, adding an entity is a configuration task, not an implementation project. A new clinic or ambulatory surgery center gets its own dimension values, its intercompany rules get defined, and transactions start flowing into the consolidated view. Time to add a new entity: minutes, not months.
This is the math that changes the headcount conversation. One healthcare network grew from 36 to 86 facilities and covered the expansion with two additional accountants and one AP specialist. On the legacy system, they would have needed a proportionally larger team just to maintain the same close timeline. The platform absorbed the complexity. The team did not have to.
For Controllers evaluating modernization, this is the most concrete business case you can build: the direct labor savings on consolidation alone often cover a significant portion of the platform investment. Add the indirect savings (faster close enabling better decisions, reduced audit costs, lower risk from manual errors) and the ROI model strengthens further.
The Questions to Ask Your Team
If you are a Controller or VP of Accounting at a multi-site healthcare organization, run these questions against your current environment:
How many hours does your team spend on consolidation workpapers each month? Track it for one cycle. Include the time spent building, checking, fixing, and explaining the workpapers to others. The number is almost always higher than people estimate.
What happens when you acquire a new facility? How long does it take to integrate a new entity into your close process? If the answer involves weeks of COA mapping, new workpaper tabs, and additional headcount, the system is the constraint.
How old are the numbers your board sees? If board packages lag reality by 3 to 4 weeks, leadership is making decisions on stale data. In an industry with 1% margins, the cost of that delay is real.
Could your team do this without the person who built the workpapers? If one person’s departure would break your consolidation process, you have a continuity risk that no amount of documentation fully mitigates.
What percentage of your team’s time goes to data manipulation versus financial analysis? If the answer is more than 50%, your team is underutilized. Not because of the people. Because of the system.
Moving From Workpapers to Real-Time Consolidation
The transition from manual consolidation to a dimensional GL is not a flip-the-switch project. It requires careful COA design, intercompany rule configuration, and testing against real close data. But it is also not the multi-year undertaking that some organizations fear.
Most implementations for mid-market healthcare organizations (10 to 40 entities) take 3 to 4 months from kickoff to go-live. The first close on the new system is always the hardest. By the third close, teams are running significantly faster than they were on the legacy platform.
The key is working with an implementation partner that understands healthcare accounting, not just the software. The intercompany structures, shared services allocations, grant accounting requirements, and service-line reporting needs are specific to this industry. A partner who has done this with real hospital finance teams will configure the system differently than one who learned the platform in manufacturing or professional services.
Start the Conversation
DSD Business Systems is a Sage Intacct implementation partner specializing in mid-market healthcare organizations. Our consultants include former Controllers and Directors of Finance from healthcare systems who know what month-end close looks like from the inside.
If multi-entity consolidation is consuming your team’s capacity, we can show you what the alternative looks like. Not a generic demo. A conversation about your specific entity structure, your current close process, and what it would take to eliminate the workpaper layer entirely.
Douglas Luchansky
Director, Client Transformation
