Entity-Level Financial Reporting for Hospital Networks: What Real-Time Consolidation Makes Possible
In health systems still managing consolidation manually, the consolidated financial report often reaches leadership between day eight and day twelve after month-end close. By that point, the transactions from the first days of the period may already be five to six weeks old. The report is current as of close. The data inside it is not.
The consolidated number answers one question: how did the organization perform? It does not answer the question leadership actually needs to ask: which entity drove that result, and what is happening there right now?
That gap, between having a consolidated view and having an analytical one, is what real-time consolidation is designed to close.
The Consolidated View Is Not the Goal
It is easy to conflate the consolidated financial report with the end objective. But the consolidated P&L is a summary, and summaries obscure variance. A health system with three hospitals and two clinics running at different margins, different payer mixes, and different cost structures looks like a single organization on a consolidated report. It is not. Each entity has its own dynamics, and the decisions that improve performance have to be made at the entity level, not the consolidated one.
When consolidation is manual, the entity-level view is a project. Someone has to pull reports from each entity, build the comparison, normalize the data, and present it to leadership. By the time it exists, it reflects the past. Leadership can analyze what happened. They cannot act on what is happening. The mechanics of that manual process, and what it costs in close cycle time, are covered in How Multi-Location Health Systems Get Consolidated Financials Without the Spreadsheet Marathon.
When consolidation is automated, entity-level analysis is always available. Not as a deliverable produced by the finance team, but as a view any authorized user can access in real time. The consolidated report and the entity-level drill-down are the same system.
| Reporting Need | Manual Consolidation | Sage Intacct |
|---|---|---|
|
Consolidated financial view
|
Available day 8-12 after close
|
Continuously updated as transactions post
|
|
Entity-level drill-down
|
Manual project, assembled on request
|
Self-service, available anytime |
|
Budget vs. actuals by entity
|
Assembled once per month with significant manual work
|
On demand, standard output
|
|
Anomaly detection
|
Anomaly detection
|
After period close, when options are limited
|
|
Historical data for acquisition decisions
|
Assembled from spreadsheets and workpapers
|
Always current, always accessible
|
|
Adding a new entity
|
Manual process, potential added headcount
|
Configuration only, no additional reporting overhead
|
What Leadership Can See Differently
Automated, real-time consolidation does not just speed up the existing process. It changes what questions leadership can ask on a regular basis, rather than once a month.
Underperforming locations, visible before month-end. When entity-level actuals update continuously, a CFO can see a margin trend developing at a specific location before the close cycle begins. That is a materially different position from seeing the same trend in a report that arrives two weeks after the period ends. In the first case, there is still time to act within the period. In the second, the result is already recorded.
Budget versus actuals at the entity level, on demand. In a manual consolidation environment, budget-to-actuals reporting at the entity level typically happens once a month, after a significant amount of manual work to assemble it. In Sage Intacct, dimensional reporting makes entity-level budget-to-actuals a standard output, available whenever leadership needs it. A CFO reviewing performance before a board meeting is not waiting on a report. They are pulling a view.
Anomaly detection before it becomes a finding. Unusual patterns in AP, an unexpected labor cost variance at one location, a revenue shift in payer mix: these surface in real-time reporting as they happen. In a monthly reporting cycle, the same anomalies are sometimes not caught until after the period has closed, when the options for addressing them are limited.
Payer mix and service line margins by entity. A hospital network with multiple locations typically has a different payer mix at each one. A community hospital serves a different population than a specialty clinic or an ASC. Consolidated payer mix reporting averages those differences away. Entity-level reporting preserves them, which means CFOs can evaluate each location against the right benchmark rather than against the organization’s blended average.
The Acquisition and Expansion Decision
One of the most consequential applications of entity-level financial visibility is the decision to acquire, expand, or exit a facility. These decisions are made on financial data. The quality of that data determines the quality of the decision.
In a manual consolidation environment, the financial analysis for an acquisition typically requires the finance team to assemble historical entity-level data from spreadsheets, reports, and workpapers. The picture is incomplete, the preparation time is significant, and the data may not reflect current operations.
When entity-level financials are maintained automatically in a single system, the historical record is always current and always accessible. A CFO evaluating a potential acquisition can pull granular budget-to-actuals for any entity over any time period without a research project. The analysis reflects what is actually happening, not what someone had time to compile.
One multi-location healthcare organization used this capability to support a formal acquisition review process. Leadership evaluated facility-level financial performance over multiple years to determine whether to proceed with specific acquisitions. The depth of the entity-level data made the go or no-go decision defensible to the board, not a judgment call based on a consolidated summary.
There is also a staffing dimension to consider. When a health system acquires a new facility and adds it as an entity in Intacct, the reporting infrastructure extends to that entity automatically. The finance team configures the new entity, maps the dimensions, and the consolidated view expands to include it. They do not add a person to manage the reporting for the new location. The process that works for five entities works for six without a proportional increase in overhead.
How the Dimensional GL Makes This Work
The architecture that enables entity-level reporting in Sage Intacct is the dimensional general ledger. Rather than maintaining separate chart of accounts segments for every combination of entity, department, location, and service line, Intacct uses dimensions: tags applied to every transaction at the time it is posted.
A single transaction can carry dimensions for entity, location, department, project, and service line simultaneously. That means the same transaction that posts to the consolidated P&L also posts to the entity-level view, the department-level view, and the service line view at the same time. There is no secondary allocation process. There is no reconciliation between the entity GL and the consolidated GL. They are the same data, organized by dimension.
For a CFO, the practical effect is that the question “what is driving this result?” is answerable in minutes, not days. Drill-down from the consolidated view to the entity level to the department level is a click, not a request to the finance team.
The Reporting Position This Creates
The CFO who receives a consolidated report on day ten after close is in a reactive position by definition. The period has ended. The result is recorded. The analysis is a postmortem.
The CFO with real-time entity visibility is asking a different set of questions: which locations are trending ahead of budget this month, where is the anomaly in supply costs at the clinic level, and does the service line margin data support the expansion case that goes to the board next quarter. These are forward-looking questions. They require current data. Manual consolidation cannot support them.
Healthcare organizations that have made this transition describe the change not primarily in terms of hours saved on the close cycle, though those gains are real. They describe it as a change in what leadership is able to do. The CFO’s role shifts from reviewing history to managing performance in real time. That is not an efficiency improvement. It is a structural change in how the finance function supports decision-making.
What This Requires
Real-time entity-level reporting requires a few things to be in place:
- A single system of record across all entities. If each entity maintains its own instance of an ERP, or if some entities are still on spreadsheets, consolidation cannot be automated. The dimensional GL only works when all transactions flow through the same system.
- Dimension structure built for the organization’s reporting needs. The dimensions applied at transaction entry determine what questions can be answered in reporting. A dimension structure designed for the organization’s actual decision-making requirements, by location, service line, payer, project, and department, is what makes entity-level analysis genuinely useful rather than technically available.
- Access controls that reflect who should see what. Entity-level visibility does not mean everyone sees everything. Sage Intacct’s role-based access controls allow CFOs to see consolidated and entity-level data, while entity-level controllers see only their own entities. The same system supports both governance and transparency.
DSD’s consultants work with clients to design the dimension structure and chart of accounts configuration that matches how leadership actually makes decisions. The implementation is not just technical: it is a translation of the organization’s strategic reporting needs into a system that delivers them automatically.
Frequently Asked Questions
What is entity-level financial reporting in healthcare? Entity-level financial reporting shows the financial performance of each individual location, hospital, clinic, or business unit within a health system separately. It is distinct from consolidated reporting, which combines all entities into a single view. Entity-level reporting tells leadership which specific entities are driving performance, where variances are occurring, and how each location compares to its own budget, without requiring someone to manually pull and compare reports from each entity.
What is the difference between consolidated and entity-level financial reporting? Consolidated reporting combines results across all entities into a single view. It answers the question of how the overall organization performed. Entity-level reporting shows the performance of each individual entity and makes it possible to drill down from a consolidated result to its source. A consolidated P&L that shows a margin decline does not tell a CFO which location is responsible. Entity-level reporting does.
What is a dimensional general ledger? A dimensional GL is an accounting architecture that applies descriptive tags, called dimensions, to every transaction as it is recorded. In Sage Intacct, a single transaction can carry dimensions for entity, location, department, service line, and project simultaneously. This means the same transaction appears in the consolidated P&L, the entity-level report, the department budget comparison, and the service line margin analysis all at once, without manual allocation or reconciliation between reports.
Can Sage Intacct support a hospital network with multiple entities? Yes. Sage Intacct is built for multi-entity health systems. It supports multiple entities within a single system, with entity-level financial statements, intercompany transaction management, and a consolidated view available from the same platform. Each entity can maintain its own reporting structure while rolling up into the consolidated view automatically.
Does real-time consolidation require all entities to be on Sage Intacct? Yes. The real-time consolidated view requires all entities to record transactions in the same Sage Intacct system. Entities still operating on separate ERPs or spreadsheets cannot contribute to automated consolidation until they are migrated. DSD works with each organization to plan the migration sequence based on complexity, system readiness, and organizational priorities.
If your health system operates across multiple entities and leadership is still reviewing performance from a consolidated view that arrives after close, DSD Business Systems can walk you through what real-time entity-level visibility looks like in practice.
Douglas Luchansky
Director, Client Transformation
