Renewable energy developers don't just have complex financials. They have complex structures. Hundreds of entities, layered intercompany transactions, tax equity partnerships, and ASC 842 lease obligations make consolidation a monthly operational crisis. Standard ERPs weren't built for this level of structural complexity, and the accounting teams carrying that load manually are paying for it every close cycle.
Multi-entity consolidation in energy breaks down because the structure of the industry makes it genuinely hard in ways that standard systems were never designed to handle. Every new solar project, wind farm, or tax equity partnership adds another entity to a hierarchy that already spans funds, holding companies, subsidiaries, and joint ventures. The math compounds fast.
For Controllers at renewable energy companies, month-end isn't just busy. It's a recurring test of how much manual work a lean team can absorb before something slips. The consolidation process sits at the center of that pressure, touching every entity, intercompany balance, and compliance obligation at once.
Understanding why this keeps happening requires looking at how these companies are actually built, not just how their accounting software is configured.
Energy Companies Are Built to Be Complex
The organizational structure of a renewable energy developer isn't a product of bad planning. It's the direct result of how the industry finances and operates projects. Each asset typically lives inside its own legal entity, a structure that protects investors, satisfies lenders, and isolates liability across a portfolio. That logic makes financial sense at the project level. At the consolidation level, it creates a problem that grows with every deal closed.
Project Finance Creates Entities by Design
When a developer brings a new solar or wind project online, it almost always does so through a newly formed LLC or special purpose vehicle. Tax equity investors, debt facilities, and production-based incentives like the Investment Tax Credit are all structured at the project entity level. A company with 50 operating assets doesn't have 50 entities; it may have two or three per asset once you account for holding companies, tax equity funds, and intermediate structures.
In practice, this means entity counts shift constantly. Holding companies make payments on behalf of subsidiaries, intercompany transactions run four to five layers deep, and the hierarchy changes with every new deal signed. That isn't unusual in renewable energy. It's how project finance is structured.
Holding Companies, Funds, and JVs Compound the Problem
Above the project entities sit fund-level holding companies that aggregate returns, manage investor distributions, and report across multiple projects simultaneously. Joint venture structures add another dimension, splitting ownership and economic interest in ways that require careful elimination at every consolidation level.
The intercompany activity flowing through this hierarchy, including loans, management fees, allocated expenses, and equity distributions, needs to be reconciled and eliminated before any consolidated financial statement means anything. In a structure with four or five integration tiers, one unresolved intercompany balance doesn't stay local. It ripples upward through every level above it.
What Multi-Entity Consolidation Actually Looks Like Across 280 Entities
Most accounting software vendors use the word "consolidation" to describe what happens when you aggregate a handful of subsidiaries into a parent report. That definition bears little resemblance to what Controllers at large renewable energy developers deal with every month. The scale is different, the depth is different, and the compliance obligations layered on top of the structural complexity make the whole process significantly harder to execute under time pressure.
Intercompany Eliminations at Depth
Green Street Power Partners (GSPP) operates across more than 280 entities, including LLCs, funds, and holding companies structured across multiple reporting tiers.
Before Nominal, preparing monthly financials meant days of manual work, tracking intercompany balances, eliminating transactions at each level, and reconciling the result before anyone could produce a fund report.
The complex entity structure meant consolidations took days of manual effort in spreadsheets. It was a constant struggle that cost us a significant amount of time and money. Efficiently consolidating reports and producing fund reports on a timely basis is a key factor for a company of our kind.
Josh Ramos, Controller, GSPP
The challenge goes beyond volume. Errors propagate upward through the hierarchy. A missed intercompany loan elimination between two project entities creates a discrepancy at the fund layer, which then surfaces again at the holding company. Finding and correcting it manually requires tracing the transaction back through every tier it touched.
The ASC 842 Problem No One Budgets For
Layered on top of the intercompany complexity is a compliance obligation that catches many renewable energy developers off guard at scale. ASC 842 requires operating and finance leases to appear on the balance sheet, and it applies directly to the land leases and equipment agreements that energy companies sign for every project.
A developer with 50 operating assets may be managing well over 100 active leases, each with its own commencement date, term, renewal options, and payment schedule. GSPP was tracking more than 115 leases under ASC 842 when it implemented Nominal. Doing that manually, across entities, while simultaneously running month-end close, is the kind of work that turns a five-day close into a ten-day one.
Why ERPs Weren't Designed for This
The instinct when consolidation breaks down is to look at the ERP configuration. In energy accounting, that instinct usually leads nowhere productive, because the limitation is architectural, baked into how these systems were designed from the start.
General ledger platforms are built to record transactions: what happened, where it happened, and when. They were not built to execute the consolidation logic that sits above the transaction layer, and most were not designed with multi-layer entity hierarchies in mind.
Recommended read: The ERP Accounting Gap: What Mid-Market Finance Teams Need to Know
ERPs Record, They Don't Consolidate.
NetSuite, for example, handles basic intercompany eliminations within its native multi-book setup, but the functionality breaks down quickly when consolidation hierarchies go beyond two or three tiers.
Non-standard fiscal years, multi-currency conversions at different consolidation points, and entity reporting requirements push most ERPs past their design limits. The result is that accounting teams export data, build the consolidation logic in separate files, and run the process outside the system of record every single month.
For most energy accounting teams, this is the process, repeated every close. The ERP produces the raw data; the actual consolidation work happens outside it.
What Accounting Teams Fill In Manually
The manual work in energy accounting is substantial. It typically includes building and maintaining the entity hierarchy as structures are added or restructured, tracking intercompany balances across the organization and ensuring they zero out at each reporting point, applying elimination journal entries for intercompany loans, management fees, and shared expenses, and reconciling the result against entity-level trial balances before producing any report.
Each of those steps requires human judgment, institutional knowledge about the entity structure, and careful version control across the files holding the process together. When a team member leaves or an entity structure changes mid-quarter, the fragility of that manual process becomes visible fast.
How Agentic Performance Management Addresses Energy Accounting Complexity
The answer to this complexity is Agentic Performance Management, an execution layer that sits above existing systems, connects to the data already living in the ERP and bank feeds, and performs the financial work that accounting teams currently handle manually.
Adding a new ERP or reconfiguring the existing one leaves the structural gap intact. Nominal's APM model deploys specialized agents that execute accounting workflows across entities, continuously, without requiring a system migration.
Agents That Run Eliminations Continuously, Not Monthly
The intercompany agents manage eliminations and cross-entity alignment in real time, not as a month-end batch process. Rather than waiting until close to discover that an intercompany loan balance doesn't reconcile, the agents flag the discrepancy when it appears. By the time month-end arrives, the work is substantially complete rather than just beginning.
For GSPP, that shift was immediate. The platform connected to their existing systems, handled intercompany eliminations across all 280-plus entities, and reduced a process that previously took days to something executed in a single action.
CFO Amir Richulsky summarized the outcome: "We're saving significantly, closing faster, and concentrating on analysis rather than leg work. It's elevated our whole team." The accounting team recovered more than 60 hours per month previously lost to manual reconciliations and lease tracking.
Audit-Ready by Default, Not by Effort
Every action Nominal's agents perform is logged, traceable, and reviewable. Elimination entries are documented. Journal entries carry the context of why they were prepared. Lease schedules are generated directly from agreement data and updated as terms change. The audit trail isn't something the team assembles after the fact; it exists as a byproduct of how the agents work.
For energy companies managing investor reporting, lender covenants, and regulatory compliance simultaneously, that default auditability changes the posture of the accounting function. Instead of spending close week reconstructing why a number looks the way it does, the team can show exactly how it was produced.
Helpful resource: Inside Nominal’s AI Agents: Embedded, Decision-Driven, and GL-Native
The Structural Problem Has a Structural Answer
Multi-entity consolidation in renewable energy is hard because the industry is structured to make it hard. Every project entity, every reporting layer, every ASC 842 lease is a product of rational decisions made at the deal level that accumulate into an accounting challenge at month-end.
The companies closing faster aren't simplifying their entity structures. They aren't hiring specialists for every fund. They're adding an execution layer that handles the volume their ERPs can't and their teams shouldn't have to. The accounting function in energy requires continuous execution across every entity, every month. Teams build for that reality are the ones delivering financials on time, with an audit trail already in place.
See how Nominal handles multi-entity consolidation for renewable energy developers: book a demo.
About the writer
