Bankable PVsyst Reports: What Lenders and Investors Require

Most solar projects do not fail financing because the site is bad. They fail because the yield report cannot survive an independent engineer’s review. The developer submits a PVsyst run with default losses, an undocumented meteo file, and a single P50 number. Six weeks later, the lender’s advisor cuts the P90 by 8%, the debt sizing collapses, and the deal reprices or dies.

We have seen this pattern across 1+ GW of delivered projects. The simulation itself is rarely the problem. The problem is what the report leaves undocumented.

PVsyst is the de facto standard for bankable yield assessment in utility-scale and large C&I solar. Lenders trust it because every assumption sits in the model — visible, editable, and auditable. But that transparency cuts both ways. A sloppy PVsyst report is worse than no report, because it shows the reviewer exactly where you cut corners.

This guide covers what lenders and investors actually require: how P50 and P90 drive debt sizing, which loss assumptions get challenged first, how to document meteo data and component files, what the independent engineer review looks for, and the specific red flags that stall or kill financing.

In this guide:

• What “bankable” means in practice for a PVsyst yield report
• How P50, P75, and P90 drive debt sizing and equity returns
• The loss assumptions lenders scrutinize line by line
• Meteo data, PAN/OND files, and site measurement requirements
• What the independent engineer review actually checks
• The 10 red flags that trigger re-runs, haircuts, or rejection
• A step-by-step checklist for a first-pass bankable report

What “Bankable” Means for a PVsyst Report

Bankability is not a software setting. A PVsyst report is bankable when a third party — someone who has never spoken to you — can open the project file, rerun the simulation, and reproduce your energy yield within a few tenths of a percent. That is the working definition every lender’s engineer applies.

The concept of bankability extends beyond the simulation. It covers the module and inverter manufacturers (are they on the lender’s approved vendor list?), the EPC and O&M counterparties, and the offtake contract. But the yield report is the piece the developer controls directly, and it is where most reviews start.

Three properties define a bankable report:

1. Reproducibility. The full PVsyst project file is shared, not just the PDF output. Every variant, shading scene, and batch of settings is intact.
2. Traceability. Every input has a documented source: a named meteo dataset, a manufacturer datasheet, a measured value, or a cited study. No “engineering judgment” without a basis.
3. Conservatism where it matters. Assumptions that drive revenue — soiling, availability, degradation — sit at or slightly below industry norms, and the report explains why.

PVsyst itself is accepted by lenders worldwide as the reference simulation tool, with the company reporting tens of thousands of licensed users across more than 100 countries, according to PVsyst SA (2025). That acceptance is earned: the software forces explicit loss modeling rather than black-box derate factors. For a broader introduction to the tool, see our guide on what PVsyst software is and how it works.

The distinction that matters: a correct simulation and a bankable simulation are different deliverables. Correct means the physics is right. Bankable means the physics is right, documented, conservative, and reproducible.

P50 and P90: The Numbers That Size the Debt

The P90 yield is the annual energy production the project will exceed with 90% probability. Lenders size debt on P90 — or occasionally P75 for investment-grade offtakes — because they get paid in bad years too. Equity investors model their returns on P50, the median expectation.

The spread between P50 and P90 determines how much debt the project can carry. A typical utility-scale project shows a P50-to-P90 gap of 5–12%, driven mainly by irradiance uncertainty and interannual variability. For a detailed breakdown of how these exceedance probabilities work, see our guides on P50 vs P90 in solar and solar probability of exceedance.

Here is how the numbers flow into financing, using a hypothetical 50 MWdc project:

A bankable report presents all exceedance levels, not just P50. PVsyst computes these from the uncertainty inputs you provide: meteo data uncertainty, model uncertainty, and loss variability. If you leave uncertainty at defaults, the report shows a P90 that no reviewer will trust.

The math is unforgiving. On that hypothetical 50 MWdc project selling at $50/MWh, a 7.4% P90 haircut removes roughly $540,000 of annual revenue from the debt case. At a 1.20 DSCR covenant, that translates to several million dollars less debt.

Loss Assumptions Lenders Scrutinize Line by Line

The loss waterfall is where bankability reviews spend the most time. Lenders compare every line of your PVsyst loss diagram against industry norms, and any line that sits materially below the norm needs documented justification. The typical pre-injection loss budget for a utility-scale project totals 15–25% from nominal to meter.

The lines that get challenged first:

Soiling deserves special attention because it is the most site-dependent loss. Dust-heavy markets like India, the Middle East, and North Africa routinely justify 3–6% with cleaning schedules, per project data compiled by the Global Solar Atlas (World Bank ESMAP) (2024). A 0.5% soiling assumption in Rajasthan will get flagged in the first read.

Degradation is the second battleground. Module degradation assumptions have tightened as TOPCon and HJT displaced PERC; first-year light-induced degradation plus annual rates now typically total 2–2.5% in Year 1 then 0.4–0.45%/year for n-type modules, according to IEA PVPS reporting (2025). Anything better than the manufacturer’s warranted curve needs a cited third-party study.

Our own practice on EPC projects: we itemize every loss with a basis column — “measured,” “contract,” “datasheet,” or “study [citation].” Lines marked “assumed” get pre-negotiated with the IE before submission. That one habit has cut our review cycles roughly in half.

Input Documentation: Meteo Data, PAN Files, and Site Measurements

A bankable report is only as strong as its inputs, and lenders rank inputs by quality. The hierarchy runs: on-site measured data, then site-calibrated satellite data, then uncorrected satellite data, then interpolated ground-station data. Where you sit on that ladder directly moves your P90.

Meteo data. Acceptable sources for most lenders include Solargis, Meteonorm, and NASA POWER for early-stage work, with a strong preference for site-specific satellite time series of 15+ years. Interannual variability of solar irradiance runs roughly ±3–6% at most sites, which is why single-year TMY files draw scrutiny, per Solargis methodology documentation (2024). For projects above 20 MW, expect a requirement for 12+ months of on-site measured global horizontal irradiance to bias-correct the satellite series.

Component files. The PAN file (module) and OND file (inverter) must match the exact equipment in the supply contract, with versions traceable to manufacturer datasheets or third-party lab measurements. Reviewers check:

• PAN file source: manufacturer-provided, or built from a certified datasheet (IEC 61215/61853).
• Inverter efficiency curve at your actual operating voltage and temperature, not the European-efficiency headline number.
• Bifacial parameters, if claimed, backed by the manufacturer’s bifaciality coefficient.

Site and layout documentation. The 3D shading scene must reflect the as-designed layout: row pitch, tracker or fixed tilt, terrain, and near obstructions. A shading scene that differs from the layout drawing is an instant credibility hit. Physics-based shading models — the same class of analysis behind solar shadow analysis software — are what reviewers expect to see reproduced.

NREL’s free PVWatts tool applies a default 14.08% system loss, which is useful for sanity checks but far too coarse for financing, as documented by NREL PVWatts (2024). If your itemized PVsyst losses total well under that benchmark, expect to defend every line.

The Independent Engineer Review

The independent engineer (IE) — also called the lender’s engineer or owner’s technical advisor — is the reviewer who stands between your report and financial close. The IE does not audit your PDF. The IE rebuilds your yield estimate from raw inputs and issues its own P50/P90. Financing closes on the IE’s numbers.

The review follows a predictable sequence:

1. Data room intake. PVsyst project file, meteo files, PAN/OND files, layout drawings, shading scene, offtake term sheet, O&M and cleaning contracts.
2. Independent model build. The IE constructs its own PVsyst variant using its preferred meteo data and its own loss benchmarks.
3. Variance analysis. Line-by-line comparison of the developer’s and IE’s loss diagrams. Any gap over roughly 0.5% per line gets queried.
4. Sensitivity runs. Soiling ±1%, availability ±1%, meteo uncertainty, and degradation rate variations to bound the P90.
5. Report issuance. The IE’s P50/P90/P95, plus conditions precedent for close.

Timeline reality: 4–12 weeks for utility-scale, and the schedule slips mostly because of missing inputs, not modeling disputes. The role and selection of this advisor is covered in our post on the solar independent engineer.

One nuance: the IE is not your adversary. IEs benchmark against public datasets — global cumulative PV capacity passed 2.2 TW in 2024, according to IEA PVPS Trends in Photovoltaic Applications (2025) — and against hundreds of reviewed projects. If your assumptions sit inside the observed distribution with documentation, review is fast. Outliers without evidence are what stall deals.

The 10 Lender Red Flags That Kill or Reprice Deals

Most rejected or repriced reports fail on a short list of recurring problems. If you fix nothing else, fix these:

1. P50-only reporting. No exceedance table means no debt case. Instant re-run request.
2. Undocumented meteo file. “Meteonorm TMY, default” with no station list, no time period, no bias correction.
3. Round-number losses. Soiling exactly 2.0%, availability exactly 2.0%, wiring exactly 1.0%. Round numbers signal untouched defaults.
4. Missing 3D shading scene or a scene that does not match the layout drawing.
5. PAN/OND files that do not match contracted equipment, or generic library files for a Tier-2 module.
6. Optimistic degradation below the manufacturer warranty curve without a cited study.
7. Zero curtailment in a market with known grid constraints or PPA caps.
8. No uncertainty inputs behind P90 — the number exists but cannot be defended.
9. Version ambiguity. Report generated in an old PVsyst version with different bifacial or shading models, not disclosed.
10. Inconsistent horizons. Year-1 P90 quoted for debt sizing but degradation applied inconsistently across the tenor.

For teams working across India and similar markets, detailed-engineering specialists publish lender-focused checklists worth reading — see Heaven Designs’ guide to bankable PVsyst reports and their companion piece on validating a PVsyst report for lenders.

Myth: A Higher P50 Wins the Deal

The most persistent misconception in solar development is that squeezing the yield model — lower soiling, hotter bifacial gain, aggressive availability — improves financing outcomes. It does the opposite.

Aggressive P50 numbers trigger deeper IE scrutiny, wider uncertainty bands, and a lower P90. The lender prices the deal off P90, so an inflated P50 often reduces the debt you can raise. We have watched a developer’s optimistic 1,820 kWh/kWp P50 come back from the IE at 1,710 with a fatter uncertainty band — a double hit that a conservative, well-documented 1,750 would have avoided.

The tradeoff is real: conservative inputs lower your equity case on paper. But equity investors apply their own haircuts to developer models anyway. The optimal strategy is a P50 that sits at the center of the defensible range, with tight, documented uncertainty. Tight uncertainty is worth more than a high median.

There is one legitimate exception: measured performance data. If you operate a sister plant 50 km away with 3 years of metered production, that evidence can justify assumptions better than industry norms — and IEs accept it. Evidence beats optimism every time.

Building a Bankable Report: Step-by-Step Checklist

Here is the sequence we run before any report leaves the building:

1. Lock the design first. Layout, row pitch, tilt or tracker configuration, DC/AC ratio, and equipment selection frozen before simulation. Yield reports on unfrozen designs waste review cycles.
2. Source 15+ years of site-specific satellite meteo data. Add on-site measurements where the project scale justifies a met station.
3. Build the 3D shading scene from the actual layout drawing. Export the drawing, import the scene, cross-check module counts.
4. Use contract-exact PAN and OND files. Verify against datasheets; document the source of every parameter.
5. Itemize losses with a basis for each line. Measurement, contract, datasheet, or cited study. Nothing “assumed” without a number behind it.
6. Fill in uncertainty inputs deliberately. Meteo, model, and loss uncertainties documented, then P50/P75/P90/P95 computed and tabulated.
7. Apply degradation consistently across Year 1 and the full debt tenor.
8. Self-review against the 10 red flags above before submission.
9. Package the data room. Project file, meteo files, component files, drawings, contracts, and a one-page assumptions memo.

For early-stage screening and C&I projects below utility-finance scale, a cloud solar design software workflow is faster than a full PVsyst data room. SurgePV’s solar designing module handles 3D layout and string sizing, while the generation and financial tool produces yield simulation and payback, IRR, and NPV in the same workspace — enough for most commercial offtake conversations. When the project graduates to project finance, the PVsyst discipline above takes over, and the two outputs should agree within a few percent.

Once financing closes, the same yield model feeds the offtake-facing documents. Teams using solar proposal software can carry the production estimates straight into branded proposals without re-keying numbers between tools.

Conclusion

A bankable PVsyst report is a documentation exercise as much as a modeling exercise. Lenders do not ask for the highest yield — they ask for the most defensible one. The developers who close financing fastest are the ones whose reports a stranger can reproduce on the first pass.

Three actions to take before your next submission:

• Audit your loss waterfall against the ranges in this guide. Flag any line without a measurement, contract, or citation behind it, and fix it before the IE finds it.
• Build the full exceedance table. P50, P75, P90, and P95 for Year 1 and the debt tenor, with documented uncertainty inputs. If your P90 cannot be defended, your debt sizing is fiction.
• Package the data room with the report. Project file, meteo data, PAN/OND files, layout drawings, and an assumptions memo in one submission. First-pass completeness is the single biggest schedule lever you control.

If you are building yield and financial models for C&I projects, book a demo to see how SurgePV connects design, shading simulation, and financial outputs in one cloud workspace.

Frequently Asked Questions

What is a bankable PVsyst report?

A bankable PVsyst report is an energy yield assessment that a lender’s independent engineer can independently verify and reproduce. It uses documented weather data, itemized loss assumptions, valid component files, and a full probability-of-exceedance analysis (P50, P75, P90). The report must disclose every input so a third party can rerun the simulation and get the same result.

Do lenders use P50 or P90 for solar project finance?

Most lenders size debt service on the P90 annual energy yield, sometimes P75 for strong offtakes. Equity investors model returns on P50. The gap between the two — typically 5–12% depending on resource uncertainty — determines how much debt a project can carry. A report that only shows P50 will not pass credit review.

Which meteo data sources do lenders accept in PVsyst?

Lenders generally accept satellite-derived datasets with 15+ years of data, such as Solargis, Meteonorm, and NASA POWER, with preference for site-specific satellite data validated against nearby ground stations. For utility-scale projects, at least 12 months of on-site measured irradiance is often required to calibrate the satellite data and reduce uncertainty.

What loss assumptions raise red flags in a PVsyst report?

Red flags include soiling losses under 1% without a cleaning plan, DC/AC mismatch losses below 1%, zero availability loss, combined degradation under 0.4%/year without manufacturer backing, and round-number defaults copied from PVsyst presets. Every loss line needs a documented basis: measurement, contract, or cited study.

What is the role of the independent engineer in solar financing?

The independent engineer (IE), also called the lender’s engineer or technical advisor, reviews the yield assessment on behalf of the debt provider. The IE reruns the PVsyst simulation, checks meteo data and losses, verifies component datasheets, and issues its own P50/P90 estimates. Financing closes on the IE’s numbers, not the developer’s.

How long does bankability review of a PVsyst report take?

Expect 4–12 weeks from submission to IE report issuance for a utility-scale project. Missing documentation — invalid PAN files, undisclosed shading scenes, missing uncertainty tables — is the main cause of delay. Developers who submit a complete data room with the PVsyst project file typically clear review in the first pass.