Development Happens in Days and Euros

Ask a development team when NtP is expected and you get a date. Ask finance what the EPC payment forecast looks like and you get a number in a month. Ask what happens to that number if the date moves, and the honest answer is usually a meeting.

The two questions are answered from two systems. Schedule lives in the development tracker, with its permits, land and milestones. Money lives in the forecast file or the ERP, organized by account and by month. Both are maintained carefully. Neither knows the other exists.

Money is causally linked to development events

Very little project money is scheduled independently. A permit is granted and a fee becomes payable. NtP triggers the first EPC payment, and the ones that follow are defined relative to it. Ready-to-build closes a transaction. Commercial operation starts a supply obligation and the revenue that comes with it. The date on a financial forecast is rarely a date in its own right — it is the consequence of a project event that has to happen first.

Development teams know that chain. Finance teams know the amounts. The link between them lives in somebody's head, or in a comment cell that says NtP plus thirty days, which nobody reads when NtP moves.

Milestones tell you when development is expected to happen. Finance tells you what money moves with it. Most organizations keep the two in systems that cannot reference each other.

Two versions of reality

The result is not dramatic. It accumulates. NtP slips by three months in April; the forecast still shows the EPC payment in June because nobody has yet found the rows that depend on it. The monthly close preserves the project's new dates and the forecast's old ones, side by side, both officially approved. Management receives two reporting processes — one that explains why the project changed, one that says what is forecast — and reconstructs the relationship between them by hand.

That reconstruction is where the cost sits. Not in the delay itself, which is a development fact, but in the weeks between the date moving and the money moving, when capital calls, cash planning and lender reporting are built on a forecast the project has already contradicted.

The problem is not that finance lacks data. It is that project reality and financial reality are held apart, so every schedule change becomes a reconciliation exercise instead of a number.

What connecting them actually looks like

It is less ambitious than it sounds, and it does not require finance to leave its systems. It requires the amount to know which project it belongs to and which event it depends on.

• Every financial record — a forecast, a commitment, a cost — is posted against a project, a finance figure and a ledger account, so it can never be a loose row in a tracker.
• An amount can be linked to the milestone or permit that drives it. When that milestone moves, the linked date can move with it — if the people who own the forecast decide it should. The link is a choice, not an automation imposed on them.
• The record carries its own status, in the vocabulary the organization already uses: forecast, capital call, purchase order, goods receipt, payment. What the ERP records as an accounting event, the project record shows as a stage in a commitment's life.
• When a reporting period closes, the money is preserved with the milestones, permits and risks management saw at the time. A locked month cannot quietly change later, so the project's history and the financial history stay explainable together.

None of this predicts anything. It removes the excuse that the information was somewhere else — which is, in practice, why the conversation about a moved payment happens late.

Where this stops

Worth being precise about the boundary, because this territory has good specialist systems in it. Connecting project money to project events is not accounting. The general ledger, invoicing, payments, tax, treasury, consolidation and statutory reporting belong in the ERP and the finance stack, and they should stay there. The ERP records the accounting truth.

The question worth owning is narrower and, for a developer, more urgent: when the project moves, what money moves with it — and can the organization see that on the day the date changes, rather than at the next close? That is a question about milestones, permits and risk, with a financial commitment attached to the answer. Development happens in days and euros. It deserves to be governed in both.

Navorda Finance — every euro, on the project it belongs to

The Cost of Delay: Why Energy Development Needs Economic Visibility

Your Milestones Aren’t Dates. They’re Commitments.

Contracted MW Is Not Delivered MW