A PVsyst report that fails independent engineer (IE) review delays financial close by weeks and signals project quality concerns to lenders. Most rejection comments are not about simulation errors — they are about missing documentation, undefended parameter choices, and incomplete uncertainty budgets. This guide gives you the validation checklist that Heaven Designs applies to every bankable yield report before submission, covering simulation inputs, meteorological data, loss parameters, uncertainty budget, and report structure.
Key Takeaway: Independent engineers review documentation quality as much as simulation accuracy. A technically correct PVsyst simulation with poor documentation will fail IE review. A well-documented report with conservative, defensible parameters passes on first submission. Follow this checklist before you send anything to a lender.
Why Reports Fail IE Review
The most common IE rejection reasons are procedural rather than computational. Based on our experience supporting yield report preparation across India, the US, and sub-Saharan Africa, the top five rejection triggers are:
- Missing or undocumented uncertainty budget — the most common reason, accounting for approximately 40 % of first-round IE comments
- Single meteorological data source without cross-validation — IEs expect at least two sources compared
- Unexplained or aggressive loss parameters (soiling, mismatch, availability) — parameters that differ from IE expectations without written justification
- Module or inverter parameters not matching manufacturer datasheets — outdated database records or incorrect binning assumptions
- Report structure that does not follow IE expectations — missing appendices, simulation files not attached, inconsistent numbers between sections
All five are correctable before submission. None requires re-running the core simulation from scratch. The investment in pre-submission validation saves weeks of back-and-forth during a financially critical period.
Phase 1 — Simulation Input Audit
Before examining outputs, verify that simulation inputs are defensible and traceable to source documents.
Module parameters: Open the PVsyst module database record used in the simulation. Verify that Pmax, Voc, Isc, alpha (temperature coefficient of Isc), beta (temperature coefficient of Voc), and gamma (temperature coefficient of Pmax) match the module manufacturer’s current datasheet. Manufacturers update datasheets periodically — a module database record from two years ago may not reflect current binning. If the project uses a module not in the PVsyst database (common for newer Chinese and Indian manufacturers), document the source of parameters used for the custom module file, and attach the datasheet as an appendix.
Inverter parameters: Verify that the inverter efficiency curve and rated power match the manufacturer’s technical datasheet. Confirm that the inverter file in PVsyst is the correct model (not a similar model from the same manufacturer with different rated power or efficiency curve). Inverter database records are updated regularly; if the PVsyst version is older than the inverter specification, discrepancies may exist.
DC/AC ratio (ILR): Confirm that the DC/AC ratio (Inverter Loading Ratio) falls within the range 1.10–1.35. Ratios below 1.10 leave inverter capacity underutilised and may indicate a suboptimal design. Ratios above 1.35 trigger significant clipping losses and may indicate an optimistic simulation assumption. Document the rationale for any ratio above 1.25, including the expected clipping percentage.
String sizing: Verify that the string configuration (modules per string, strings per MPPT, total DC capacity) is consistent with the equipment specifications in the design drawings and the inverter MPPT voltage window. Mismatches between the simulation string configuration and the actual design are a common source of post-commissioning yield discrepancies.
Degradation rate: Confirm that the annual degradation rate used in the simulation (typically 0.45–0.60 %/year for mono PERC and TOPCon modules) matches the module manufacturer’s warranty schedule. Using a lower degradation rate than the warranty implies inflates long-term production projections.
Phase 2 — Meteorological Data Audit
Source documentation: The report must name the meteorological data source (Meteonorm, Solargis, NSRDB, or other) with the specific version or dataset reference. “PVsyst default” is not an acceptable source citation. The report should state: “Meteonorm 8.1 data for the period 1996–2015, accessed via PVsyst 7.4 embedded database” or equivalent specificity.
Cross-validation: Confirm that the report includes a comparison of at least two independent meteorological datasets. The comparison table should show annual GHI (kWh/m²/year) for each source, the percentage difference, and the selected reference with written justification. This table is what the IE reviewer looks for first in the meteo section.
Historical period: Confirm the dataset covers at least 10 years of historical data. For sites in high-variability regions (monsoon-influenced India, inter-tropical convergence zone Africa), 20+ year datasets are preferred for accurate IAV calculation. Document the historical period covered by each source used.
IAV documentation: The interannual variability (IAV) component must be calculated from the historical dataset. Acceptable approaches: standard deviation of annual GHI values from the long series, or the dataset provider’s stated IAV for the location. Generic IAV assumptions (e.g., “IAV = 4 % assumed”) without site-specific derivation will attract IE comments requesting the calculation basis.
GHI plausibility check: Verify that the reference annual GHI value is consistent with published values for the region. For Rajasthan utility-scale sites, GHI should be 1,800–2,100 kWh/m²/year. For Tamil Nadu coastal sites, 1,750–1,950 kWh/m²/year. Values outside expected regional ranges warrant explanation in the report.
DNI/DHI consistency: For tracker projects, verify that the DHI fraction is reasonable for the location. High-DNI, low-DHI sites (Rajasthan, Middle East) will show DHI fractions of 15–20 %. High-DHI sites (monsoon regions, coastal fog zones) will show 25–35 %. DHI fractions are critical for tracker yield accuracy, as discussed in our PVsyst tracker yield study methodology.
Phase 3 — Loss Parameter Audit
Loss parameters are where simulation optimism most frequently hides. IEs know the typical ranges for each market and flag outliers. A loss parameter that is outside the expected range without written justification is a certain IE comment.
| Loss Category | Typical Range | Flag If |
|---|---|---|
| Soiling losses | 1–5 % (region dependent) | < 1 % or > 6 % without documented justification |
| Module mismatch | 1–3 % | < 1 % without power sorting or flash test documentation |
| DC wiring losses | 0.5–2 % | < 0.5 % or > 3 % without wiring calculation |
| AC transformer losses | 0.5–1.5 % | < 0.5 % without transformer specification review |
| Availability (DC + AC combined) | 97–99 % | > 99 % without contractual O&M SLA documentation |
| LID (Light-Induced Degradation) | 0.5–2 % for mono PERC | 0 % for mono PERC without LID-free certification letter |
| Module degradation (year 1) | 1–2 % | 0 % or > 3 % without manufacturer documentation |
| Snow losses | Site-specific | 0 % for high-altitude or northern sites without local data |
Soiling justification: If soiling is set below 2 % for an Indian or African site, the report must include documentation: nearby plant soiling measurement data, cleaning frequency schedule from the O&M contract, or water availability assessment confirming wet cleaning feasibility. Dry-climate sites without documented cleaning schedules should use 3–5 % minimum soiling loss.
Availability documentation: If availability is set above 98.5 %, it must be supported by the O&M contract SLA terms. Generic “98 % availability assumed” without contractual backing will attract IE pushback, particularly for projects in markets with unreliable grid connectivity or remote locations where response times are longer.
LID for mono PERC: PVsyst’s default LID for mono PERC is often set at zero or 0.5 %. Industry data suggests mono PERC LID is typically 1–2 % without active LID mitigation. If the module manufacturer provides a LID-free certification (some Tier 1 suppliers offer this for PERC through specific manufacturing processes), attach it as documentation. Otherwise use 1 % minimum.
Phase 4 — Uncertainty Budget Review
The uncertainty budget is the section most commonly missing or incomplete. It must appear as a formatted table with component-by-component breakdown, not as a paragraph in the report body.
A complete uncertainty budget table includes all five components:
| Uncertainty Component | Value (1-sigma %) | Source/Justification |
|---|---|---|
| Meteorological data source | X.X % | Provider stated accuracy or inter-source comparison |
| Interannual variability | X.X % | Derived from N-year historical dataset |
| PVsyst model uncertainty | 3.0–4.0 % | IEC 61724-3 reference |
| Soiling uncertainty | X.X % | ± range around soiling assumption |
| Equipment performance | X.X % | Module tolerance + inverter curve accuracy |
| Combined 1-sigma (RSS) | X.X % | √(sum of squares of all components) |
| P90 calculation | P50 × (1 − 1.282 × sigma) | — |
| P99 calculation | P50 × (1 − 2.326 × sigma) | — |
Common errors in the uncertainty budget:
Omitting the IAV component is the largest and most common error. IAV is typically 3–5 % for a 10-year dataset and is the second-largest uncertainty component after data source uncertainty.
Adding components linearly instead of using root-sum-of-squares (RSS) overstates total uncertainty and produces a P90 that is more conservative than the data justifies. The RSS combination assumes the uncertainty components are statistically independent, which is a reasonable approximation for the five standard components.
Not distinguishing one-year P90 from ten-year P90. If the lender requests ten-year P90, IAV is reduced by √10 before the RSS combination. Presenting one-year P90 when ten-year is requested will cause confusion during debt sizing.
Using model uncertainty without an IEC or published reference. The IEC 61724-3 standard provides the authoritative reference for PVsyst model uncertainty. Citing it explicitly prevents IE questions about the model uncertainty assumption.
The Heaven Designs PVsyst Report Validation Checklist — The 8-Point Pre-Submission Gate
This is the checklist Heaven Designs applies before delivering any bankable yield report to a client for lender or IE submission. Each gate must pass before the report is released.
Gate 1 — Simulation File Completeness PVsyst .PRJ file and simulation variant file (.VCi) are included in the deliverable package. The IE can reopen the simulation and verify all inputs without requesting additional files. Missing simulation files are an automatic IE comment.
Gate 2 — Module/Inverter Datasheet Match Module and inverter parameters match the manufacturer’s current datasheet. If custom database records are used, the source datasheet is attached. Parameter discrepancies > 2 % from the datasheet are flagged and explained.
Gate 3 — Dual Meteo Source Comparison Two independent sources have been compared. The GHI comparison table appears in the report body. The reference dataset has been selected with written justification. The historical period for each source is documented.
Gate 4 — Loss Parameters in Defensible Range All loss parameters are within IE-accepted ranges or documented with project-specific justification. No loss parameter is left at PVsyst default without confirmation that the default is appropriate for the site. Soiling, LID, and availability are reviewed against site-specific evidence.
Gate 5 — Uncertainty Budget Table Complete All five components (source, IAV, model, soiling, equipment) are quantified and documented with source references. RSS combination is shown. P90 and P99 are calculated and labelled. One-year vs ten-year distinction is addressed if relevant to the lender’s requirements.
Gate 6 — DSCR Cross-Check P90 annual energy is cross-checked against the project’s financial model to confirm P90 DSCR ≥ 1.25×. If DSCR is marginal (1.25–1.30×), the transmittal letter notes it proactively so the lender is not surprised during financial model review.
Gate 7 — Report Structure Follows IE Standard Report sections are present and complete: Executive Summary, Site Description, Meteorological Data (with comparison table), Simulation Methodology, Loss Analysis (with loss cascade table), Energy Yield Summary (P50/P90/P99 with annual and monthly tables), Uncertainty Analysis (with budget table), Appendices. Missing sections are added before release.
Gate 8 — Sensitivity Analysis Included A ±10 % GHI sensitivity table and ±5 °C temperature sensitivity table are included. These confirm P90 DSCR robustness under stress scenarios and are increasingly required by DFI lenders as standard disclosure.
Transmittal Letter Best Practices
The transmittal letter (cover letter) accompanying the yield report is the first thing a lender or IE reads. It sets the frame for review and signals the quality of the engineering team behind the report.
A strong transmittal letter includes:
- Project name, location, and rated capacity (DC and AC)
- Report version and date
- Summary of P50, P90, P99 annual energy (in GWh) and the uncertainty sigma
- Summary of meteorological sources used and the cross-validation result
- One-line description of any non-standard assumptions and their justification
- Confirmation of simulation file attachment
- Contact details for the yield study author for IE queries
A weak transmittal letter says only “Please find attached the PVsyst report for Project X.” IEs who receive vague transmittal letters approach review with lower confidence, which means they scrutinise every parameter more carefully and are more likely to issue comments on borderline issues they might otherwise accept.
When to Get an External Review Before IE Submission
If your project meets any of the following criteria, consider having Heaven Designs review your PVsyst report before you submit to the IE. The time and cost of pre-submission review is far less than the delay and rework associated with a formal IE rejection.
- First utility-scale project for your organisation (no established track record with the assigned IE)
- Project in a country or climate zone where your team has limited simulation experience
- Project using non-standard technology (bifacial + tracker combination, agrivoltaic, floating PV)
- DSCR at P90 is below 1.30× (limited headroom above minimum)
- Lender has specified a particular IE firm known for detailed review (DNV, Black & Veatch, UL)
- Timeline is critical — financial close date is fixed and revision cycles cannot be absorbed
An external pre-submission review typically takes 3–5 business days and identifies the specific comments most likely from the IE, allowing them to be addressed before formal submission.
Connecting Validation to the Full Yield Report Ecosystem
Yield report validation sits within a broader bankability preparation workflow. The uncertainty budget draws on the P50/P90/P99 methodology. The meteo source choice follows the Meteonorm vs Solargis vs NSRDB decision framework. The simulation itself may involve comparison with PVsyst vs SAM if the lender requests a dual-model cross-check.
For projects using single-axis trackers, the PVsyst tracker yield methodology covers the additional simulation parameters specific to tracker projects, including backtracking algorithm selection and GCR-dependent shade modelling. For bifacial modules, the PVsyst bifacial gain modeling tutorial provides the albedo and row spacing inputs needed to produce a defensible bifacial P50.
Heaven Designs delivers complete lender-ready yield report packages via our solar feasibility study service and PVsyst simulation service. Every report exits our 8-point validation checklist before delivery, meaning clients submit with confidence that IE first-round approval is the expected outcome, not a hopeful one.
For developers who need consulting support on strengthening an existing report rather than producing a new simulation, our solar engineering consulting service covers pre-submission review, uncertainty budget construction, and transmittal letter drafting.
Stats Grid
FAQ
What does an independent engineer look for in a PVsyst report? IEs verify: meteorological source quality and cross-validation, loss parameter defensibility, uncertainty budget completeness (all five components), simulation file consistency, and report structure. They also cross-check that P90 DSCR is adequate given the stated parameters and that P50 production aligns with regional irradiance benchmarks.
Can I submit a PVsyst report without an uncertainty budget? No. An uncertainty budget is required by all major IEs and is referenced in IEC 61724-3 and IFC Performance Standards. A report without an uncertainty budget will receive a formal IE comment requiring one before a final letter can be issued. This comment alone can delay financial close by 2–4 weeks.
How conservative should loss parameters be? Loss parameters should reflect realistic project conditions, documented with evidence — not be artificially conservative or optimistic. A well-justified realistic loss assumption is more defensible than a conservative assumption presented without evidence. Using O&M contracts, soiling data, and equipment guarantees to support specific loss values demonstrates engineering rigour.
What is the fastest way to fix a rejected PVsyst report? Address IE comments systematically: add the uncertainty budget table first (most common comment), then document meteo sources and cross-validation, then justify any flagged loss parameters. Attach simulation files if missing. Most reports can be revised to address all comments within 3–5 business days. Contact Heaven Designs for rapid turnaround support through our solar engineering consulting service.
Do lenders read the PVsyst report directly or only the IE letter? Lenders primarily rely on the IE letter and executive summary, but credit analysts at larger institutions or DFIs will review the report directly. The report must be clear and self-contained because it may be reviewed by non-engineers in the lender’s credit team who are assessing documentation quality rather than simulation methodology.
Should I submit the PVsyst .PRJ file to the lender? Submit the .PRJ file to the IE, not directly to the lender. The IE needs the simulation file to verify all inputs match what is stated in the report. The lender typically receives the PDF report and IE letter only. If the lender’s term sheet requires the simulation file, confirm what format they need before submission.
What happens if P90 DSCR is below 1.25× after the yield report is complete? Options include: increase DC capacity (raise P50 production), negotiate a higher PPA tariff, reduce debt gearing, extend debt tenor, or reduce O&M cost assumptions with contractual backup. The yield report engineer cannot adjust simulation inputs to fix a marginal DSCR — the underlying project economics must change to support the target debt structure.
How does pre-submission validation differ from IE review? Pre-submission validation is conducted by the engineering team (or an external consultant like Heaven Designs) before the report reaches the IE. It identifies and corrects likely IE comments before formal submission. IE review is conducted by the independent engineer appointed by the lender and results in a formal review letter that becomes part of the financing documentation.
