6 steps to check report outputs in the PVSyst manual

Table of Contents

• Roles you should understand first in PVSyst report output

• Step 1 Decide the purpose of submitting the report and its audience

• Step 2: Organize projects and variants before output

• Step 3 Confirm the key values on the simulation results screen

• Step 4 Select content to include in the report preview

• Step 5: Check to ensure you haven't misread the loss plot and key metrics

• Step 6 Manage in preparation for PDF saving, comparison, and resubmission

• Common mistakes in report output and how to prevent them

• Summary

Roles to Understand First in PVSyst Report Output

When preparing report output while referring to the PVSyst manual, the first thing to understand is that the report is not merely a printout but a technical document for explaining to third parties the photovoltaic system’s design conditions, simulation settings, energy production forecasts, and loss factors. Even if it looks on-screen like you are simply filling in input fields in sequence, the final report reflects meteorological data, azimuth, tilt, modules, inverters, shading, losses, and output results as an integrated whole. Therefore, rather than assuming you can just run the report output at the end, it is important from the input stage to be mindful of whether the conditions are set in a way that can be explained later.

In PVSyst’s official documentation, project design and simulation are described as the core functions for detailed study, including the selection of meteorological data, system design, shading analysis, loss settings, and economic evaluation, and the simulation results are compiled into a printable Report. Because the Report includes the parameters used in the simulation and the main results, it should be treated not merely as a table of results but as a document for verifying the link between input conditions and outcomes.

Especially when search users look up "PVSyst manual", they often want not only where in the software to click to produce the PDF, but also which pages to check, which parts of the generated report to review to judge its validity, and how to prepare it for client or internal approval. Report output is a step seen at the end of the design process, but in practice it directly ties into estimates, feasibility evaluations, internal reviews, pre-construction considerations, explanations for financial institutions, and materials for the project owner. For that reason, verification procedures before and after output are as important as the output operation itself.

PVSyst reports can easily be misunderstood if you extract and read only the generation figures. For example, if the annual energy production is lower than expected, the cause might be the solar irradiance conditions, or it might be temperature losses, wiring losses, inverter capacity, shading effects, or differences in module settings. Conversely, even if the energy production appears high, the report’s reliability is reduced if the input conditions are more optimistic than reality. Therefore, in this article we organize the sequence of report outputs you should check in the PVSyst manual into six steps that are commonly confusing in practice.

Step 1: Determine the purpose of submitting the report and its intended readers

The first step in producing a report is not an operation in PVSyst, but deciding who the report is for and what it should explain. Whether it’s for an internal design review, the owner/client, financial institutions or investment decisions, or for sharing conditions with the contractor, the pages to review and the metrics to emphasize will differ. For internal reviews, the validity of input conditions, loss assumptions, and comparison of variants are emphasized. For owners/clients, annual energy production, monthly trends, the main loss factors, and the ease of explaining the assumptions are important.

PVSyst reports contain a lot of specialized information, so readers may not understand every item. For checks among engineers, it is necessary to examine details such as module configuration, inverter oversizing, wiring losses, temperature conditions, and shading conditions. For explanations aimed at non-technical audiences, you may prepare a separate explanatory note apart from the main report so you can briefly explain not only the energy generation results but also why those results occur. A practical approach is to use the PVSyst report itself as an objective output document and to organize the key points in the explanatory materials.

When deciding the purpose for submission, it is also important not to narrow the role you expect from the report down to a single function. PVSyst output reports can serve as evidence of the design, confirmation of conditions, explanation of results, and a foundation for comparison and review. For example, in the initial study phase they can be used to check approximate conditions, in the basic design phase to verify the consistency of input conditions, and in the final proposal phase to be stored as PDFs and linked to estimates and contract terms. Because the same PVSyst report can carry different meanings depending on which stage it was produced, it is safer to be conscious of file naming and version control from the outset.

Deciding on the intended reader also affects how you format elements in the report such as the language, company name, comments, logo, and date display. In PVSyst’s print settings you can configure the company logo, header title, comment lines, date format, output language, color display, and other items, enabling you to tailor the presentation to the recipient.

What you want to avoid at this stage is the "generate the PDF first and think later" approach. PVSyst reports, once generated, can look like plausible documents, but if you share them with a page layout that doesn't match the purpose or with insufficient explanations, you'll later get queries such as "what are the assumptions?", "have shadows been taken into account?", and "why is the loss rate set to this value?". Positioning report generation not as the final action but as a step for fulfilling accountability will reduce rework.

Step 2: Organize the project and variants before output

The second step is to clarify the relationship between the project and its variants before generating the report. In PVSyst, a project contains basic conditions such as site and weather data, and you can create multiple variants within it to run simulations while changing module configuration, inverters, tilt angle, shading, loss conditions, and so on. It is crucial to know which variant the report corresponds to. Even with the same project name, different variants will yield different outputs.

The PVSyst tutorial explains working with a workflow structured in a Project-and-Variant hierarchy. A Project includes general conditions such as the geographic location, meteorological data, albedo, and so on, while a Variant contains the detailed definitions used for the simulation calculations, such as the selection of modules and inverters, the geometric layout, shading, electrical connections, and economic scenarios.

A common mistake when outputting reports is exporting while a variant that is not the latest design is still open. For example, if there are multiple proposals—VC0 as the initial plan, VC1 with a corrected azimuth, VC2 with a revised inverter capacity, and VC3 with reset shading conditions—failing to make clear which variant is intended for submission can lead to a PDF with outdated conditions being shared. Because names can look similar on the PVSyst screen, including the date and the key points of the conditions in the variant name for submission makes it easier to verify.

When organizing variants, we verify at least the project name, site name, weather data, module model, inverter model, array capacity, azimuth, tilt, shading settings, and loss settings before producing the output. The purpose here is not to memorize the numbers perfectly, but to be able to explain, when reading the report, under which conditions the results were calculated. Because simply checking the results after generating the report makes it difficult to notice differences in input conditions, organizing variants before output is indispensable.

Furthermore, because PVSyst reports are often retained as technical documentation, consistency between the variant name and the PDF file name is also important. For example, even if the variant name shown on the screen is something like "VC2_final", if the PDF file name still uses an old design name, it can be difficult later to determine which is correct. Before exporting, ensure the project name, variant name, export date, and main conditions match, and it is advisable to have a common internal naming convention.

Organization of projects and variants tends to be overlooked by beginners who are not familiar with operating PVSyst. However, in practice it is the most basic check that determines the reliability of the report. Even when consulting the PVSyst manual, you should not simply look for the location of the Report button; you need to first confirm whether the currently open Project and Variant are the ones intended for submission.

Step 3 Confirm the key values on the simulation results screen

The third step is to check the key values on the simulation results screen before exporting the report. PVSyst’s report organizes the simulation results for printing or PDF, but the pre-export results screen brings together the information you should verify. If you identify the annual energy production, specific yield, Performance Ratio, major loss items, and monthly trends at this stage, reviewing the PDF afterward will go much more smoothly.

On PVSyst's results screen, you can work with many variables related to the simulation and display or export them as monthly, daily, hourly, or sub-hourly values. The results also include detailed energy loss charts, normalized indicators, the Performance Ratio, input/output charts, incident energy, and array output distributions.

The first items to check before output are the annual energy production and the monthly balance. In solar power systems, the distribution of generation varies with seasonal solar irradiance, temperature, shading, snowfall, and the effects of azimuth and tilt. Even if the annual values look reasonable, if a particular month is extremely low or high you should review the shading settings, weather data, azimuth angle, tilt angle, and loss settings. Because being notified after a report is generated causes major rework, it is important to catch any anomalies on the results screen first.

Next, what I want to check is the Performance Ratio. The Performance Ratio is a representative indicator for getting a sense of a system’s efficiency, but it is dangerous to judge the quality of a project by this alone. Even with the same Performance Ratio, its meaning changes if the assumptions about meteorological data, temperature conditions, shading conditions, inverter settings, or wiring losses are different. When reading a PVSyst report, you should not treat the Performance Ratio as a standalone score, but read it together with the loss diagram and the input conditions.

Also, check whether any warnings or cautions appear in the simulation results. If you issue a report while warnings related to module string count, inverter input range, oversizing, temperature conditions, or voltage range remain, the recipient will be more likely to question the validity of the design conditions. Warnings do not necessarily mean the design is infeasible, but you need to be in a position to explain why you judged those conditions to be acceptable.

PVSyst's report output can be completed quickly. However, if you export to PDF without checking the results screen beforehand, you will need to recalculate, re-export, and re-share when you discover an error later. Because the impact of corrections grows with the number of recipients, verifying the key values before output is a step you should always take.

Step 4: Select the content to include in the report preview

The fourth step is to check the content and formatting in the report preview. In PVSyst, you can review the output in a preview screen before printing or saving as a PDF. It is explained that when the simulation report is displayed, the preview opens automatically. The preview screen also provides functions such as saving as PDF, printing, copying to the clipboard, exporting results, comparing with another project or another variant, navigating pages, and zooming.

At this stage, the important thing is to check whether the pages required for submission are included before saving the PDF. In PVSyst’s print settings, you can select which display data to include depending on the output target, and in the simulation report you may be able to choose which pages to include. The official documentation also shows an example in the Displayed data tab of selecting the pages to include in the simulation report.

When choosing what to include, it's important to leave readers with the information they need and not to add too much unnecessary detail. While internal technical reviews require detailed configuration pages, including every detailed page in explanations for clients can actually make them harder to read. However, cutting too many pages can make the basis for the calculation conditions unclear. In particular, it's safer to keep pages related to modules, inverters, meteorological data, azimuth, tilt angle, major losses, and power generation results so they can be verified later.

In the preview, we also check the visual presentation. We verify whether the company name, contact person's name, comment lines, date, language, and color display are appropriate for the submission's purpose. Formatting mistakes such as an outdated date, comments left over from a previous project, a language that does not match the intended recipient, or a missing logo are not part of the technical content itself, but they do affect the document's credibility. Because PVSyst's print settings allow adjustment of the company logo, header title, comments, date format, output language, and color or grayscale, we tidy these up before saving the PDF.

Also, the report preview is not merely a pre-print check; it can also serve as the starting point for preparing explanatory materials. The preview screen includes functions to save as PDF and to copy to the clipboard, and can be used to paste the displayed material into other software. However, when pasting a screen or page into another document, take care to ensure that the content matches the original PDF and that the pasted charts and tables are not presented out of context. Extracting only the charts or tables can omit input conditions and notes, making misunderstandings more likely.

The ideal in this procedure is to determine, while viewing the preview, "under what minimum conditions the person who receives this PDF can confirm what results were obtained and which losses are in effect." Leaving verifiability — not just visual neatness — is the key to making a PVSyst report a document that can be used in practice.

Step 5 Confirm you are not misreading the loss plot and key metrics

The fifth step is to correctly read the loss diagram and the key indicators in the report. In PVSyst reports, the Loss diagram is particularly important. The Loss diagram is a figure used to visually confirm where energy is being lost in a photovoltaic system, and it helps to identify weaknesses in the design. The official documentation also describes the Loss diagram as a means to quickly assess the quality of a system design and to identify the main loss factors.

The loss diagram is one of the most persuasive pages in a report. Because it allows you to see the flow of energy from solar irradiance to effective irradiance, array output, inverter output, and output to the grid, it makes it easier to explain which factors are reducing generation. Displaying temperature losses, wiring losses, mismatch, IAM, shading, inverter losses, and so on makes it easier to explain the background behind the results than simply stating “the generation is this value.”

However, when reading the Loss diagram, be careful not to simply add the loss percentage figures. The official PVSyst documentation explains that each loss is defined as a percentage of the energy remaining at the previous stage, so percentage values cannot be summed. This is a very important practical point. Looking at multiple loss items and simply saying "they total X%" is an inaccurate way to read the report.

For example, if temperature losses are large, you should check the mounting method, ventilation conditions, ambient temperature data, and the module temperature model. The PVSyst tutorial also explains that the effect of thermal losses is displayed in the array loss diagram of the final report. If wiring losses are large, review the DC- and AC-side wiring lengths, conductor cross-sections, connection configurations, and transformer-related settings. If shading losses are large, verify the treatment of near-shading and far-shading, the construction of the 3D scene, and how the monthly impacts manifest.

When checking the key indicators, we look at annual energy production, specific yield, Performance Ratio, monthly energy production, and the balance of loss items as a set. If you isolate just one of them, you risk drawing incorrect conclusions. For example, even if the Performance Ratio appears high, if the underlying irradiation data are conservative, a different interpretation is required. Likewise, even if the energy production looks high, if shading or temperature conditions are modeled more favorably than reality, the reliability of the proposal documentation is reduced.

Loss diagrams are useful for engineers, but they can appear difficult to non-technical audiences. When explaining to owners or sales representatives, it is easier to understand if you separate "which losses are large," "which losses have room for improvement," and "which losses are difficult to avoid due to site conditions." For example, temperature losses caused by ambient temperature are often unavoidable as regional conditions, whereas wiring losses and some shading losses can sometimes be reduced through design improvements. If you can explain this distinction, a PVSyst report will function not merely as a record of results but as a document to support design decisions.

Step 6: Save the PDF, compare, and manage in preparation for resubmission

The sixth step is management after saving the PDF. PVSyst’s preview screen includes a feature to save documents as PDFs. Additionally, when previewing simulation reports you can use the result export feature and the comparison feature with other projects or other variants.

When saving as a PDF, include the project name, variant name, output date, and main conditions in the file name to make management easier. For example, if there are versions of the same project with a changed azimuth, a changed module capacity, or updated shading conditions, the risk of later referencing the wrong PDF increases if the file name alone does not make the differences clear. Since PVSyst reports are often treated as proof of the design conditions, it is desirable to save not only the latest version but also to keep them in a way that clearly shows the change history.

When comparing multiple options, PVSyst’s comparison feature is also useful. The official documentation explains that you can compare the report you are currently previewing side by side with reports from other projects or variants, and highlight the differences in yellow. This helps you check which conditions or results changed due to design modifications. It is especially handy for seeing how changes in the number of modules, inverter capacity, tilt angle, shading conditions, or loss settings are reflected in energy production.

When preparing for resubmission, organize and retain not only the PDF but also the original PVSyst project and its variants. PDFs are convenient as submission documents, but the original data are necessary to modify conditions later. If only the PDF remains and it is unclear which variant it was generated from, reproducibility suffers. Linking the report output date with the variant name in PVSyst and establishing internal storage rules will make it easier to respond to inquiries at a later date.

When handling a large number of simulations, there is also a way to automatically generate PDF reports in Batch mode. The official documentation explains that on the definition screen for running multiple simulations, you can automatically generate PDF reports for each simulation by using the Create PDF report checkbox in Save mode. For projects that compare many variants, this makes it easier to reduce missed outputs and the mixing of conditions compared to exporting each one manually.

However, automatically generated PDFs may not be ready for submission as-is. Batch mode is useful for improving efficiency, but before submitting you should always open a representative report to confirm it was generated under the intended conditions. When producing large numbers of outputs, a wrong setting could be applied to all files, so it's safer to check the first few files and organize the naming rules and save locations before running a full-scale export.

Common Mistakes in Report Output and How to Prevent Them

One common mistake in PVSyst report output is looking only at the result numbers and not checking the input conditions. Annual energy production and the Performance Ratio are conspicuous, so attention inevitably focuses on them. However, a PVSyst report only makes sense when inputs and results are considered together. Unless you verify that the meteorological data are appropriate, that the azimuth and tilt match the site plan, and that the module and inverter settings match the estimated specifications, you cannot judge the validity of the reported numbers.

Another common mistake is exporting an old variant. During design studies, multiple variants are created by slightly changing the conditions. If initial, revised, and final proposals are mixed together and you rely only on the visible file name when exporting, you may end up submitting an outdated proposal. To prevent this, it is important to clearly specify the variant for submission and to make the name in PVSyst match the PDF file name.

Formatting failures can also occur. If the company name, date, comments, language, or color settings do not match the intended recipient’s requirements, the overall quality of the document is reduced. PVSyst’s print settings allow you to configure the logo, header, comments, date format, language, and color display, so it’s a good habit to check the preview before saving as a PDF.

Also, inadequate explanations of the loss diagram frequently occur. The Loss diagram is useful, but explanations become inaccurate if one does not understand that loss rates cannot simply be added, or which stage’s energy each loss is a proportion of. The official documentation also explains that each loss is a proportion of the energy amount of the previous stage, and that the percentage values cannot be added. When submitting reports, including a brief note on how to read the loss diagram will help prevent misunderstandings by the recipient.

Furthermore, if the storage rules after outputting PDFs are unclear, it will more easily lead to problems later. If you cannot tell which PDF is the final version, under what conditions it was produced, or which original PVSyst data it corresponds to, resubmissions and corrections will take time. By linking and managing the PDF, the PVSyst project, the variant name, the output date, and the submission destination, you can ensure the reproducibility of the report.

When using the PVSyst manual, it is important to understand not only the operating procedures but also how to use the outputs. Report output is not a simple PDF save at the end of the design work; it is a process of reviewing input conditions, results, losses, formatting, and version control together. Simply adopting this awareness will greatly improve the quality of the materials you submit.

Summary

The report output workflow you want to verify in the PVSyst manual does not end with simply looking for the PDF save button. To produce a report that can be used in practice, you first need to determine the submission purpose and the intended reader, organize the project and its variants, check the key values on the simulation results screen, refine the content and layout in the preview, confirm you do not misinterpret the loss diagram and main indicators, and carry out comparisons and version control after saving the PDF.

The PVSyst report is a document that summarizes the parameters used in the simulation and the main results, and is intended to link the design conditions with the outcomes. For that reason, if pre-output checks are insufficient, the report may look well-presented yet be unreliable. Conversely, if input conditions, variants, loss diagrams, key indicators, formatting, and saving rules are carefully checked, the report becomes easy to use for internal review, client presentations, business viability assessments, and comparative evaluations.

What is particularly important is to treat the report not as a "deliverable of results" but as the "basis for design decisions." Rather than showing only the annual energy production, the value of a PVSyst report is enhanced if it enables you to explain why that production is achieved, which losses are affecting it, and under what conditions the calculations were performed.

When working while reading the PVSyst manual, don't just follow the steps mechanically—be aware, for each screen, of what the operations are intended to check. Before generating the report, set the conditions; after generation, verify the contents; and keep the project in a state where you can compare or regenerate outputs as needed so that design changes or additional explanations can be handled more easily. PVSyst report output is the final step for correctly conveying the results of a photovoltaic simulation. By accumulating careful checks, you can produce a technical document that communicates clearly to the reader and is usable in practice.