Infrastructure Lender's Base Case DCF Diverges from Sponsor Case Over Merchant Price Risk
Executive Summary
Illustrative Scenario
This case study is a composite, educational scenario built from patterns commonly observed in financial model reviews. It does not describe a specific, identifiable client engagement, and any resemblance to a particular transaction is coincidental.
Background¶
A lender was evaluating a term financing for a renewable energy project with a hybrid revenue structure: approximately 70% of output was sold under a long-term, fixed-price power purchase agreement, and the remaining 30% was sold at prevailing wholesale merchant prices. The sponsor's financial model presented a single-discount-rate DCF cross-check supporting the project's base case valuation and debt capacity, alongside the primary coverage-ratio-based project finance metrics.
The Problem¶
The lender's independent advisers, cross-checking the sponsor's project IRR against the DCF-implied value as described in the DCF Valuation pillar's treatment of project finance applications, noted that the sponsor's model applied a single blended discount rate to the entire revenue stream, derived primarily from the contracted portion's risk profile.
Findings¶
Recalculating the DCF with the merchant-exposed 30% of revenue discounted at a materially higher rate — reflecting its genuine exposure to wholesale power price volatility, distinct from the fixed-price contracted portion — produced a lower overall project value and a less favorable implied debt capacity than the sponsor's single-rate base case had shown. The gap was concentrated entirely in how the merchant-exposed cash flow was discounted, not in any disagreement over the underlying merchant price forecast itself, which both parties' advisers had estimated similarly.
Root Cause¶
The sponsor's model had been built by extending the discount rate methodology used for the project's original, fully-contracted structure to the revised structure once a merchant component was added during later-stage negotiations. The model's discount rate section had not been restructured to split contracted and merchant cash flows into separately discounted components, leaving a uniform rate applied across cash flows with genuinely different risk profiles — a structural gap rather than a disagreement over the merchant price forecast itself.
Risk¶
Had the lender relied on the sponsor's single-rate base case without an independent cross-check, the financing could have been sized against a project value and implied debt capacity that did not adequately reflect the additional risk carried by the merchant-exposed portion of revenue, potentially leaving the facility undercollateralized relative to the project's true risk-adjusted value.
Resolution¶
The lender's advisers presented the split-discount-rate DCF alongside the sponsor's original single-rate version, and the parties agreed to restructure the discount rate methodology to apply a contracted-revenue rate and a separate, higher merchant-revenue rate, consistent with each cash flow stream's actual risk. The revised project value and coverage-ratio-based debt sizing were used as the basis for the final facility terms.
Lessons Learned¶
- A single blended discount rate applied uniformly across cash flows with materially different risk profiles — contracted versus merchant exposure — can understate risk in the exposed portion, even where the underlying revenue forecast itself is not disputed.
- Discount rate methodology should be revisited whenever a project's revenue structure changes materially, not carried forward unchanged from an earlier, structurally different version of the deal.
- Splitting cash flows by risk profile and applying a rate matched to each component is the correct structural response to a hybrid contracted/merchant revenue structure, addressed generally in the DCF Valuation pillar's discount rate coverage.
- Independent DCF cross-checks in project finance lending add value precisely where a sponsor's model methodology has not kept pace with a change in the underlying deal structure.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
Related Glossary¶
Related Industries¶
- Financial Modelling Best Practices for Infrastructure — see its DCF Application section
Related Checklists¶
Related Products¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
Is this a real client engagement?
No. This is an illustrative, composite scenario built from patterns commonly observed in project finance model reviews. It does not describe a specific, identifiable transaction.
What is merchant price risk in a renewables financing?
The risk that a portion of a renewable energy project's revenue is sold at prevailing wholesale market prices rather than under a fixed-price offtake agreement, exposing that revenue to power price volatility that a contracted, availability-style payment stream does not carry.
Why does discount rate selection matter for merchant-exposed cash flows specifically?
Because the discount rate is meant to compensate the capital provider for the risk of the cash flow actually materializing as forecast. A merchant-exposed cash flow carries meaningfully more volatility risk than a contracted, fixed-price cash flow, and applying the same discount rate to both understates the compensation required for the merchant-exposed portion.
How is this different from a dispute over the revenue forecast itself?
The underlying merchant price forecast was not in dispute in this scenario; both the sponsor and the lender's advisers used a similar central price forecast. The issue was that the discount rate applied to that forecast did not differentiate between the contracted and merchant portions of revenue, a structural, not a forecasting, issue.
How could this have been avoided at the outset?
Splitting the discount rate (or the cash flow stream itself) into a contracted-revenue component and a merchant-revenue component, each discounted at a rate reflecting its own specific risk, rather than applying a single blended rate uniformly across both.