Solar Asset Valuation: Deal Comp Checklist

Bad solar comps can distort value fast. If I’m screening a deal, I want a comp set that matches on project stage, market, interconnection, contract setup, tax credit timing, and near-term capex before I trust any $/MW figure.

Here’s the short version: I separate operating assets, late-stage development, and solar-plus-storage first. Then I check a few deal-breakers: MW-AC vs. MW-DC, ISO/RTO, queue and GIA status, PPA tenor, offtaker credit, and any inverter, augmentation, or upgrade costs that would shift net value. I also treat a project with a merchant tail very differently from one with long-term contracted revenue.

A few numbers matter right away:

• 0.3%–0.5% annual degradation is common, though some audits find up to 0.8%
• I want at least 12 months of production data, and 24–36 months is better
• A gap of more than 5% between modeled P50 and actual output is a warning sign
• Comps with less than 2 years of PPA tenor left need extra caution
• Post-January 1, 2025 tax credit rules and the December 31, 2027 completion timing can affect price

How to Value Solar Energy Assets.mp4

sbb-itb-e766981

Quick comparison

If I can’t verify the core fields, I leave the deal out. That’s the simplest way to keep a solar comp set tight and usable.

Checklist 1: Core Asset Fields to Capture for Every Comp

Use the same field screen for every comp. If a property has a physical or market mismatch, handle that outside the comp set. If it fails this screen, cut it before you get into cash flow or tax structure.

Screen comps in this order: asset, market, then contract.

Asset Age, COD, and Operating History

Vintage matters because it shapes degradation and availability. Group comps by COD band. Older assets bring more degradation into cash flow, with typical annual output loss of 0.3%–0.5%, though technical audits sometimes find rates as high as 0.8% ^[4][5].

Use at least 12 months of actual production data. 24–36 months is better if you want to check degradation trends and availability with more confidence ^[4]. If the seller can't provide that, ask for direct SCADA or inverter platform access.

One red flag stands out: a gap of more than 5% between P50 and actual output. That can point to yield issues or construction problems ^[4].

Market, Interconnection, and Project Configuration

Market and interconnection differences can move price enough to knock out weak comps. ERCOT, PJM, and CAISO each have their own nodal pricing patterns and congestion issues. So a comp from one market doesn't carry over neatly to another unless you normalize it.

For interconnection, zero in on status and upgrade cost exposure. Queue position, study phase, POI, and GIA status can all change how usable a comp is.

For solar-plus-storage comps, record battery MW and MWh capacity, plus the exact use case. That matters because ancillary services and capacity contracts follow different revenue models and different augmentation schedules ^[3].

On the physical side, capture tracker type and DC/AC ratio. If the setup differs, document the output adjustment for tracker configuration.

Once the asset screen clears, move to PPA terms, counterparty support, and storage revenue.

Checklist 2: Contracted Cash Flow and Risk Screens

Once the asset screen clears, the next step is revenue durability. This is where you figure out how steady the cash flow is and where the risk actually lives.

PPA Tenor, Pricing, and Merchant Tail Exposure

Start with the contract basics: length, start date, end date, and remaining tenor. Then record how the project gets paid. Is pricing fixed, or does it move with an index? Is there an escalation schedule?

Some details look small on paper but can change revenue in a big way. If the contract includes time-of-delivery (TOD) multipliers or shaping provisions, break those out on their own. They can change realized revenue in a material way compared with nameplate output. Also flag curtailment compensation and basis risk, especially in congested nodes where actual settlement prices can come in below the hub price used in the model ^[7][1].

One clean way to think about it: contracted PPA cash flow and merchant tail cash flow are not the same animal. Merchant tail exposure should be isolated and discounted at a higher rate than contracted PPA revenue ^[7].

Counterparty Risk and Security Support

After term and pricing, look at who pays and what backs the payment.

The offtaker has a huge effect on cash flow stability. Record the offtaker type - utility, cooperative, or corporate - and pull the credit rating. Investment grade is generally defined as BBB or higher (S&P/Moody's) ^[4]. If the rating falls below investment grade, flag a higher discount rate and tighter payment security.

If the offtaker is a subsidiary, confirm whether a parent guarantee exists. Without one, you're taking the subsidiary's standalone credit risk, and that can be much weaker ^[4]. Also check for letters of credit or other collateral.

Curtailment terms matter here too. Record who pays when the grid forces a shutdown. A contract with no economic compensation for curtailment can cut into P50/P90 revenue certainty, even if the headline PPA rate looks fine ^[4].

Storage Attachment and Revenue Stacking

Storage can make the revenue picture a lot more complicated. The first thing to pin down is simple: Is storage bundled into the solar PPA, or priced on its own? That one distinction changes how you model revenue durability and which discount rate applies to each stream.

Check whether storage economics sit under a separate agreement, such as a tolling agreement, resource adequacy contract, or standalone merchant setup ^[1]. Each use case - energy arbitrage, ancillary services, or capacity payments - runs on a different revenue model and a different augmentation schedule ^[3].

Model each revenue stream on its own before tax, leverage, and capex adjustments. If a comp has several contracted streams mixed with merchant exposure, probability-weight each stream separately instead of rolling everything into one revenue figure ^[1].

Carry these cash-flow assumptions into tax credit, capital structure, and capex adjustments.

Checklist 3: Tax Credits, Capital Structure, and Capex Adjustments

Observed transaction prices can send you in the wrong direction if you don't strip out tax attributes, financing structure, and near-term capex.

Tax Credit Vintage and Tax Equity Timing

Start by recording whether the project used the Investment Tax Credit (ITC) or the Production Tax Credit (PTC). Starting January 1, 2025, technology-neutral credits replaced legacy PTC and ITC structures ^[6].

You should also log the credit regime, development stage, tax-equity flip status, sponsor buyout rights, and placed-in-service date.

That timing matters. Projects that miss the December 31, 2027, completion deadline can lose federal tax credits, and 2026 construction starts often trade at a discount because buyers price in that risk ^[6].

Once you've pinned down the tax treatment, move to the balance sheet and purchase structure.

Debt, Deal Structure, and Enterprise Value Normalization

Record whether the deal was an asset sale, an equity sale, or a portfolio/platform trade. Those structures shift which liabilities move with the deal, so mixing them together can warp your comp set ^[1][2].

Then capture:

• Project debt
• Cash
• Reserve accounts
• Whether pricing was cash-free/debt-free or included assumed financing

The goal is simple: get from the headline number to a clean enterprise value basis.

Near-Term Capex, Repowering, and Equipment Replacement Costs

This is one of the easiest places to get fooled. If one deal comes with near-term inverter replacements and another has newer equipment, the raw EV/MW figures are not apples to apples.

Flag costs tied to inverter replacements, tracker repairs, module remediation, storage augmentation, repowering, and GIA-driven upgrades. Treat immediate costs as purchase-price deductions or escrow items ^[4]. Then subtract those costs from the headline value before you compare comps.

Here's a simple way to think about the adjustment stack:

Pull the GIA and confirm who bears post-close upgrade costs ^[1].

Normalize these items before source-quality scoring.

Checklist 4: Data Source Quality Checks and Comp Set Governance

Even a well-normalized comp set can fall apart if the data underneath it is shaky. Before you lock in any valuation, you need to know where each number came from and how much trust it earns.

Source Reliability, Disclosure Depth, and Normalization Rules

Transaction data does not come with the same level of confidence across the board. Some numbers come straight from signed documents. Others come from press releases, teasers, or secondhand reports. That gap matters. A weak data point can throw off an otherwise usable EV/MW comp.

A simple way to handle this is to sort each comp by source tier: primary documents, secondary research, or unverified claims.

Standardize currency in USD, capacity in MW-AC or MW-DC with the conversion stated, and transaction dates in U.S. format. For the final database entry, use as-built drawings instead of early project designs. If a deal structure is unclear or pricing looks estimated, either exclude that comp or push it down in rank before it gets into the benchmarking pool.

When documentation is incomplete or the sources don’t line up, ask for direct access to SCADA or inverter platforms to check actual operating data ^[4]. If two sources still conflict, use 12–36 months of monitoring-system output as the tie-breaker ^[4].

Use that scoring step to decide whether a comp is audit-ready or not.

Quality Scoring, Outlier Review, and Workflow Ownership

Once you classify the source, score the comp before it makes the final cut. Rate it on two things:

• Source quality
• Normalization completeness

That score helps separate clean, audit-ready comps from low-confidence entries.

Outlier review matters just as much. Flag any comp with a production deviation of more than 5% versus modeled P50 before adding it to the set ^[4]. Do the same for any unexplained production decline or year-over-year performance drop ^[4]. If a comp looks off, don’t just wave it through and hope the average smooths it out. That’s how bad inputs sneak into a valuation.

Workflow ownership should also be clear. Assign one person to handle data updates, outlier review, and stale-comp removal. And watch PPA tenor closely: flag comps with less than two years of remaining PPA tenor unless a renewal is documented ^[4].

Conclusion: The Minimum Fields That Make a Solar Comp Set Defensible

A solar comp set is only as good as the rules behind it. Those checklists draw the line between deals that belong in the set and deals that don't.

Before you rely on any comp, check the fields that shape price normalization. A defensible comp set needs clear documentation on asset vintage, market, interconnection, contract terms, counterparty credit, tax treatment, and any capex or structure adjustments that change value. Those are the minimum fields for a defensible comp set. If a transaction can't support them, leave it out.

The best comps come from the best-documented transactions. Weak source reliability, incomplete normalization, or missing disclosure in any of these areas makes the comparison harder to defend. If a deal can't support the minimum fields, don't use it as a comp.

FAQs

Which mismatches make a solar comp unusable?

A solar comp stops being useful when the project is so different that it can’t serve as a fair benchmark anymore.

Some common deal-breakers are:

• Project size differences above 25%
• Different technology types
• Major regional differences in resource availability or grid interconnection costs
• Data older than 24 months
• Incompatible revenue structures
• Major differences in development stage

At that point, you’re no longer comparing like with like. The comp may still look close on the surface, but the numbers can point you in the wrong direction fast.

How should I adjust comps for merchant tail risk?

Use a risk-adjusted discounted cash flow method instead of simple capacity-based multiples. It gives you a much better read on value, especially when cash flows don’t all carry the same level of risk.

When you look at comps, line them up with assets that have similar revenue mixes and similar regulatory exposure. That part matters more than it may seem at first glance. An asset with merchant exposure should not be valued the same way as one with fully contracted cash flows, because the risk profile is different.

You’ll also want to apply a specific risk premium to merchant tail years. Those later-year cash flows are more exposed to market swings, so they need a tougher discount treatment.

Then stress-test the model against current power curve forecasts. That helps reflect price volatility, congestion, curtailment, and long-term market expectations, instead of assuming a smooth path that rarely shows up in practice.

What documents matter most for audit-ready solar comps?

Put the highest priority on documents that confirm both the financial case and the system’s actual output:

• Executed PPAs with term, pricing, and counterparty details
• Operating reports, maintenance logs, and actual capacity factors
• Engineering records, including PVSYST files, equipment invoices, and system layouts
• Legal and regulatory filings, such as land leases, permits, interconnection agreements, and tax credit certifications

Just as important, spell out every adjustment and assumption in plain language. That paper trail makes the work easier to audit and easier to defend if someone later asks, “How did you get this number?”

Related Blog Posts

• Cash Flow Analysis in Solar System Valuation
• Market Comparables for Renewable Energy Valuation
• Valuation Methods for Solar Energy Projects
• Ultimate Guide to Solar Asset Valuation with Degradation