Here’s the paradox: The system Finance needs most isn’t a finance system.
Finance teams in energy companies usually have strong systems. Accounting knows the SPVs, treasury knows the bank accounts, the ERP knows the invoices and the models know the assumptions. And yet one important piece of information often arrives indirectly: what is actually happening in the projects.
Luis Cabello5 min read
Bring governed project information into financial forecasts and capital decisions.
Finance teams in energy companies usually have strong systems.
Accounting knows the SPVs.
Treasury knows the bank accounts.
ERP knows the invoices, purchase orders and payments.
Financial models know the assumptions behind valuation, funding and returns.
And yet one important piece of information often arrives indirectly:
What is actually happening in the projects?
That gap becomes increasingly important as portfolios grow.
Finance sees SPVs. The business executes projects.
The legal and financial structure of an energy company is usually built around SPVs.
But the operational structure does not always match it one-to-one.
This is becoming particularly visible with BESS.
One SPV may own both a PV plant and a battery project, while those assets have different schedules, permits, risks, procurement plans and commercial assumptions.
From an accounting perspective, the SPV is perfectly clear.
From an execution perspective, there may be two projects moving at different speeds.
Finance needs both views.
The legal entity tells you where the money belongs. The project tells you what is happening to it.
Connecting the two becomes essential when forecasts and capital decisions depend on project reality.
Too much financial forecasting still starts with: “Can you update this template?”
This is one of the patterns I have seen repeatedly.
Finance prepares a forecasting template.
Execution teams are asked to update it.
The deadline approaches.
Project Managers already have their own workload, so the file gets completed quickly, often by manually transferring information that already exists somewhere else.
A milestone date.
An EPC payment schedule.
A revised CapEx assumption.
A commissioning forecast.
Then Finance consolidates those inputs and builds the corporate forecast.
The process may work.
But it creates an uncomfortable question:
How much of the financial forecast is based on governed project information, and how much has just been reconstructed for reporting?
That distinction matters.
Because a financial model can be mathematically perfect while one of its operational assumptions is already outdated.
Financing depends on milestones that Finance does not control
This becomes even more important when project finance enters the picture.
Senior debt from commercial banks, institutional lenders or organizations such as the European Investment Bank can depend on specific project conditions being achieved.
RtB.
NtP.
Construction progress.
COD.
Those milestones are not simply project-management dates.
They may determine when capital can be drawn, when equity is required, when covenants become relevant or when repayment assumptions need to change.
Yet the milestone often travels to Finance through several layers before it reaches the forecast.
Project reality changes.
Someone updates a tracker.
Someone prepares a report.
Finance receives the new date.
The model is updated.
By then, the project team may already have known about the change for weeks.
The issue is not that Finance needs another reporting process.
It needs a closer connection to the governed operational source behind the financial assumption.
And sometimes the dependency is not even inside your company
Energy projects rarely operate in isolation.
A project may depend on a shared substation or transmission infrastructure developed by another SPV, a joint venture or even a third party.
That creates an uncomfortable situation for Finance.
The financial forecast may assume a commercial-operation date that depends on infrastructure the project does not directly control.
If the dependency exists only in somebody’s project plan or in the knowledge of the development team, Finance cannot properly understand the confidence behind the date.
The forecast sees:
COD: 30 June
The operating model should also know:
COD depends on a third-party substation currently expected on 15 May.
That context changes the quality of the financial information enormously.
When the project moves, Finance should know what moves with it
Imagine NtP moves by three months.
Execution immediately understands some of the consequences.
The EPC mobilization changes.
A procurement payment may move.
A capital requirement may shift.
But if project governance and financial planning live as completely separate realities, those consequences have to be discovered and rebuilt manually.
A better model connects them.
A forecast payment can be linked to a milestone.
An EPC payment schedule can remain connected to the project that originated it.
A financing assumption can be checked against the latest governed project commitment.
The goal is not to automate every financial decision.
It is to make sure Finance starts those decisions with better operational context.
Navorda should not become your accounting system
This distinction is important.
Navorda does not need to replace ERP.
It does not need to replace Treasury.
It does not need to replace the financial model.
And it certainly does not need to become the general ledger.
Those systems already have jobs they are very good at.
Navorda’s role is different.
It governs the project reality those systems often need but do not naturally contain:
Which project belongs to which SPV, what milestones and dependencies are moving, and which financial commitments are connected to them.
That information can then flow into Finance instead of being reconstructed every reporting cycle.
Bring project reality closer to the capital decision
A CFO should be able to look at a forecast and understand more than the number.
Where did the assumption come from?
Which project commitment supports it?
Has that commitment changed?
What dependency threatens it?
Who owns the next action?
That is where project governance and financial governance begin to meet.
And that is the opportunity I see for Navorda:
Not to become the system of Finance. But to become the governed operational context Finance can trust.
Because the closer financial forecasts are to project reality, the less effort Finance has to spend reconstructing that reality — and the more confidence it can have when allocating capital.
Bring governed project information into financial forecasts and capital decisions.
Bring one project — and its financial context
For a Navorda Fit Review, bring one representative project.
We can look at how its SPV, milestones, dependencies, procurement commitments and financial assumptions currently connect — and identify where Finance is still rebuilding information that already exists elsewhere in the organization.
Bring one project. Start from your reality.
Navorda for CFOs & Finance Leaders — the role page behind this article
Navorda Finance — forecasts, commitments and funding status on the project they belong to
External Models Governance — keep the financial model in Excel, govern its assumptions and outputs
What’s in Navorda for me? — one operating model, five very different reasons to care
Enter it once. Use it yourself. Trust what gets reported. — the Project Manager chapter
