5 Ways to Read Inverter Losses in PVSyst | Understanding Conversion Losses

When carrying out the design of photovoltaic systems and energy yield forecasting in practice, attention tends to focus on annual energy production and PR, while inverter losses are an item that is easily overlooked. However, no matter how good the irradiance or incidence conditions are, if losses are large at the stage of converting the power produced on the DC side to the AC side, the final amount of electricity sold and the amount effectively utilized will not increase. The official PVSyst documentation also explains that inverter efficiency is included in the system losses for grid-connected systems and that its impact is reflected in the PR.

Especially for practitioners searching for information on "how to read PVSyst", it is important not to treat inverter losses as merely a check of an efficiency value. In PVSyst, the global inverter loss called InvLoss is broken down into several factors — not only efficiency losses during normal operation but also output threshold, overload, MPPT voltage window, and nighttime consumption. In other words, inverter losses are not a single percentage but the result of several overlapping causes.

Also, how you interpret inverter losses changes which design items should be reviewed. Depending on whether it’s an efficiency-curve issue, an overload caused by the DC/AC ratio, a mismatched voltage window, or issues such as night-time consumption or minimum start-up power, the items that need to be rechecked differ. In PVSyst’s Inverter model: input and output, IL_Pmax, IL_Vmin, IL_Vmax, IL_Pmin, etc. are each explained as distinct behaviors, and it is assumed you will read them according to the underlying cause.

This article organizes and explains, from five perspectives, how to interpret inverter losses in PVSyst for practical use. First, it clarifies the role of inverter losses; next, it looks at where they are reduced within the energy flow; then it separates the meaning of each component in the breakdown; it checks how they manifest month by month; and finally it summarizes how to feed this understanding back into design. It also clarifies common points of misunderstanding and why the accuracy of assessing site conditions affects how convincing the inverter losses are.

Table of Contents

• Things to know before reading inverter losses

• How to read 1｜Understand that InvLoss is not just "efficiency loss"

• How to read 2｜Read in the flow from EArrMPP to EOutInv

• How to read 3｜Read by separating IL_Oper・IL_Pmax・IL_Vmin/Vmax・IL_Pmin・IL_Night

• How to read 4｜Read seasonal differences and output-condition tendencies from monthly results

• How to read 5｜Interpret inverter losses back in terms of DC/AC ratio and operating conditions

• Common misunderstandings

• The accuracy of site conditions influences the credibility of the inverter loss results

• Summary

What you should know before reading about inverter losses

When reading inverter losses in PVSyst, the first thing to grasp is that inverter losses are not just “losses that occur because the conversion efficiency is not 100%.” In the result variables, InvLoss is defined as the global inverter loss, and its breakdown is provided as IL_Oper, IL_Pmin, IL_Pmax, IL_Vmin, IL_Vmax, and IL_Night. In other words, although it may look like a single conversion loss, in practice multiple phenomena are managed separately, such as normal efficiency, minimum start-up power, overload, the MPPT voltage window, and nighttime consumption.

This clarification is important to avoid misinterpreting the numbers. For example, just because InvLoss is large you cannot immediately conclude that “the inverter is inefficient.” It could be that the DC-side capacity is too large, causing overload losses, or that the string voltage is outside the MPPT voltage window. Nighttime consumption may also have been added. In practice, it is important to first isolate which type of loss is contributing.

Also, in PVSyst, EArrMPP is the MPP energy after array losses, EArray is the array output including the deviation of the inverter operating point, and EOutInv is the energy available on the inverter output side. In other words, inverter losses act as the bridge to see how much of the "ideal power the array had" was delivered to the AC output. Understanding this makes it easier to position inverter losses as part of the system’s downstream section.

Furthermore, in PVSyst's definition of PR, PR explicitly includes system losses in addition to optical losses and array losses, and within that, for grid-connected systems, inverter efficiency is included. Therefore, inverter losses are also in the background when reading PR. Rather than judging a project's quality solely by PR, viewing inverter losses as part of the system losses that suppress PR makes it easier to trace the reasons for the results.

Interpretation 1｜Understand that InvLoss is not just 'loss of efficiency'

The first way to read this is not to interpret InvLoss solely as “efficiency degradation.” In PVSyst’s output variables, IL_Oper is separated out as the loss due to the efficiency curve during normal operation. In other words, this item mainly represents the pure deterioration of conversion efficiency. The overall InvLoss value additionally includes thresholds, overload, the voltage window, and nighttime consumption, so if you assume InvLoss is simply an efficiency-curve issue you will misidentify the cause.

In practice, when inverter losses appear large you may first be inclined to doubt the catalog conversion-efficiency values. However, in PVSyst’s model not only the usual losses based on the manufacturer’s efficiency data, but also losses caused by operating conditions are added separately. For example, IL_Pmin, which occurs when the inverter does not exceed its start-up threshold under low irradiance, and IL_Pmax, which occurs when the DC input exceeds the AC output limit, cannot be explained by catalog efficiency alone.

This way of interpreting things is useful because it makes it less likely to choose the wrong improvement measures. If IL_Oper is dominant, it is worth considering a review of the inverter's partial-load efficiency and selection. Conversely, if IL_Pmax is dominant, the DC/AC ratio and string configuration become more important. If IL_Vmin or IL_Vmax are having an effect, the voltage design should be reconsidered. Don’t dismiss InvLoss with the single word "efficiency"—confirming which type of loss is the primary cause is the first step to understanding conversion losses.

How to Read 2｜Read in the order from EArrMPP to EOutInv

The second interpretation is to read inverter losses not as a standalone rate but as part of the flow from EArrMPP to EOutInv. In PVSyst’s result variables, EArrMPP is described as the array MPP energy after all array losses, EArray as the effective energy at the array output including inverter operating point displacements, and EOutInv as the available energy at the inverter output. In other words, the energy the array could deliver at the ideal MPP, the energy actually received by the inverter, and the energy passed on to the output are separate stages.

Keeping this flow in mind makes the meaning of inverter losses much more concrete. Up to EArrMPP, it is the result of array-side losses. The difference from there to EArray includes the effects of the inverter’s operating point deviating from the ideal MPP. And between EArray and EOutInv, the actual conversion losses and behaviors such as thresholds, voltage windows, and overloads appear. In other words, inverter loss is easier to understand if read as “the intermediate loss from the array through the inverter to the output side.”

In practice, there are projects where the array side is neatly put together but the annual power generation does not increase as much as expected. In such cases, looking at the gap between EArrMPP and EOutInv makes it easier to see how much energy is being lost at the inverter stage. Conversely, if a project has already been significantly reduced by the time it reaches EArrMPP, examining inverter losses alone is unlikely to lead to substantive improvement. That is why inverter losses should always be interpreted together with the upstream array results.

Also, in older PVSyst tutorials the Loss Diagram is organized so that the flow is: after EArrMPP comes Inverter losses, then EOutInv, then AC losses, and finally EGrid. This remains a very clear and practical way to view it. In other words, understanding inverter losses as positioned "after the array losses and before the AC losses" stabilizes the reading order.

Reading Method 3 | Read IL_Oper, IL_Pmax, IL_Vmin/Vmax, IL_Pmin, and IL_Night Separately

The third way to interpret it is to read the breakdown of inverter losses individually. PVSyst explicitly lists IL_Oper, IL_Pmin, IL_Pmax, IL_Vmin, IL_Vmax, and IL_Night as result variables. Even though their names are similar, their meanings are completely different. In practice, whether you can distinguish and understand these separately will change the direction of countermeasures.

IL_Oper is the loss due to the efficiency curve during normal operation. This is generally the part that first comes to mind when you hear "conversion loss"—the energy the inverter loses when converting DC to AC. On the other hand, IL_Pmin is the energy lost when the inverter cannot start up at low-output conditions that do not exceed Pthresh. In the official documentation, Pthresh represents the power required for internal inverter circuit consumption and is treated as a loss in the low-output region.

IL_Pmax is the overload loss. The important point here is that PVSyst treats overload loss not as “the excess power being dissipated as heat inside the inverter,” but as “energy that the array theoretically could have produced but that was not extracted.” The official documentation also explicitly states that “overload mode does not mean the inverter dissipates excess energy; rather, this energy is not produced by the array,” and overload is treated as a safe operating condition. In other words, IL_Pmax should be read not as a “loss from overstraining that would break the system,” but as “energy uncollected due to clipping.”

IL_Vmin and IL_Vmax are losses that occur when optimal operation could not be achieved outside the MPPT voltage window. The official documentation explains that if the true MPP voltage is outside VmppMin or VmppMax, the inverter clips the voltage to the window, and the difference becomes IL_Vmin or IL_Vmax. Therefore, if these losses appear, you should suspect the number of modules or the string voltage design. The final IL_Night is nighttime energy; it is usually small but reflects standby consumption and assumptions about nighttime operation. ([turn452899search0], [turn452899search1])

What is useful in practice is to develop the habit of always returning to the breakdown when you see InvLoss. Whether IL_Oper is the main cause, IL_Pmax is the main cause, or whether IL_Vmin/Vmax is hidden, the design conditions that need to be reviewed will be completely different. Once you can separate these, inverter loss becomes not just a "conversion loss" but a diagnostic for design checks

Interpretation 4 | Interpreting seasonal differences and tendencies in output conditions from monthly results

The fourth way to interpret it is to read inverter losses not as a single annual rate but within monthly results and seasonal differences. In PVSyst's Array and system losses description, the effects of each loss can be used as hourly, daily, and monthly values, and can also be checked in the Loss Diagram. Therefore, the thing to check is inverter losses not only as an annual value but in which months and under what conditions they are increasing

In practice, there are cases where IL_Pmax stands out only in midsummer. This tends to occur when the DC/AC ratio is relatively high and the AC output limit is easily reached during periods of strong solar irradiance. Conversely, IL_Pmin can be more apparent in winter or during low-irradiance periods. Viewing by month makes it easier to see which losses are affecting which times—information that can be obscured when looking at annual totals. These seasonal differences, with a single annual InvLoss

Also, IL_Vmin and IL_Vmax related to the voltage window manifest in combination with monthly weather conditions and variations in array operating voltage. String voltage tends to be higher in cold periods and lower in hot periods, so looking at monthly data makes it easier to identify the seasons when problems are more likely to occur. In PVSyst's Inverter model, the relationship between array voltage and the acceptable operating window is also considered to generate losses, so check not only the annual average but also seasonal differences.

Reading by month makes it easier to prioritize improvements. If clipping occurs only in mid-summer, acceptance may be an option, whereas if a voltage-window problem appears year-round, design modification should be given higher priority. For inverter losses, it is more practical to interpret them by which months and under what conditions they occur than by “what percentage per year” in practical work.

Reading 5｜Re-examining inverter losses in terms of DC/AC ratio and operating conditions

The fifth way of interpreting this is not simply to view inverter losses as a result, but to trace them back to the DC/AC ratio and operating conditions. PVSyst's Inverter model: input and output shows that the inverter's behavior is determined by conditions such as PnomDC, Pnom(AC), VmppMin, VmppMax, and Pthresh. In other words, inverter losses are not just the efficiency figures in equipment catalogs, but the very way the array and inverter are combined?

In particular, IL_Pmax is strongly linked to the DC/AC ratio. According to PVSyst’s description, when the input-side MPP power exceeds the acceptable input power an overload loss occurs, and in Limitation mode power is clipped to the level corresponding to Pnom(AC). Therefore, how to evaluate clipping losses should be judged not simply by thinking “losses are bad,” but by taking into account what DC/AC ratio the design is targeting.

Similarly, IL_Vmin/IL_Vmax are matters of string design, while IL_Pmin is linked to the concept of low-irradiance operation. In other words, inverter loss is not a figure that is finalized on the result screen; it is a number that should be read back against design conditions such as the number of modules in the array, number in series, number in parallel, the input window, and the expected output range. In practice, when reviewing projects with large inverter losses, you need to be able to return to the design intent — for example, “how was this DC/AC ratio considered?” and “is this string voltage design reasonable?”

Also, because PR includes system losses, bringing inverter losses back into the design conditions helps to understand the reasons for PR differences. If inverter losses stand out in projects with low PR, that may be a sign to review the inverter-side design conditions rather than a site problem. In practice, after confirming inverter losses as part of the final results, always return to the DC/AC ratio, string configuration, voltage window, and input conditions when making your assessment.

Common Misunderstandings

The most easily misunderstood aspect of inverter losses is thinking of all InvLoss as "poor efficiency." In fact, besides IL_Oper it also includes thresholds, overload, voltage window, and night-time consumption. Therefore, a large InvLoss does not necessarily mean you have chosen an inefficient inverter. If you don't read the causes separately, the countermeasures will also be wrong

Another common misconception is to think of clipping loss as "the inverter is overworking and dumping it as heat." In PVSyst's description, overload loss is not "excess energy dissipated in the inverter" but "energy not produced from the array." This is an important distinction: clipping is not a malfunction of the equipment but a normal behavior corresponding to the output limit and

Also, it's dangerous to feel reassured or worried based only on the annual InvLoss. When viewed month by month, you may see biases such as IL_Pmax occurring only in midsummer, IL_Pmin occurring only during low-irradiance periods, or IL_Vmax occurring in cold periods. With annual values alone, it's difficult to determine which design conditions are problematic. The reason PVSyst allows losses to be viewed as monthly values is ma

Furthermore, it is incorrect to view inverter losses in isolation. PR includes system losses, and after EOutInv there are further losses such as AC wiring and transformer. Therefore, inverter losses are a central part of the system loss, but they do not, by themselves, represent the entire system. They should also be read together with the upstream EArrMPP and the downstream EOutInv onward

Accuracy of on-site conditions determines confidence in inverter loss estimates

At first glance, inverter losses may seem to be an issue of equipment specifications and the DC/AC ratio, appearing unrelated to site conditions. However, in practice the accuracy of understanding site conditions also greatly affects how convincing the inverter loss estimates are. The reason is that the array’s actual irradiance conditions, the way shadows occur, cable lengths, installation azimuth, and the configuration up to the point of injection ultimately influence the array voltage and current and how downstream losses manifest. Even in PVSyst’s output variables, EArrMPP, EArray, EOutInv, EacOhmL are in a continuous flow

For example, if the shading-condition inputs are inadequate, the estimated amount of midsummer clipping may also change. If the positional relationship among the AC route, the panel, and the injection point is ambiguous, it becomes difficult to separate those losses from the losses after EOutInv. In other words, even if you think you are isolating and reading only the inverter losses at your desk, they are actually influenced by both the upstream on-site conditions and the downstream layout conditions. This is why the accuracy of on-site understanding is the convincingness of inverter losses

In that sense, in practical work where you want to grasp on-site positional relationships with high precision, you naturally come to LRTK for iPhone-mounted GNSS high-precision positioning devices. By making it easier to perform high-precision on-site position checks, understand clearances from obstacles, and organize the layout of panels and equipment, you can more tightly define the assumptions for array conditions and system conditions. If you want to understand inverter losses not merely as equipment numbers but as the result of design conditions tied to the site, this level of accuracy in on-site understanding will be a great help.

Summary

When reading inverter losses in PVSyst, first understand that InvLoss is not just "efficiency reduction," then place it within the flow from EArrMPP to EOutInv, and on that basis read IL_Oper, IL_Pmax, IL_Vmin/Vmax, IL_Pmin, and IL_Night separately; check seasonal differences and quirks of output conditions in the monthly results; and finally return to consider the DC/AC ratio and operating conditions. Just mastering these five ways of reading makes conversion losses quite practically understandable

What is important is not to dismiss inverter losses as a single rate. As the PVSyst documentation shows, they encompass different factors such as nominal efficiency, startup threshold, overload, voltage window, and night consumption. That is why you need to do more than just look at the numbers—you must trace which design conditions produced them. Understanding conversion losses is not about evaluating the inverter in isolation, but about reading them in the context of the array and the entire system

And to make that reading even more reliable, it is indispensable to grasp on-site positional relationships with high precision. If you want to organize shadows, layout, and route conditions more accurately, the perspective of utilizing the iPhone-mounted GNSS high-precision positioning device LRTK is also effective. By combining the ability to correctly interpret inverter losses in PVSyst with the ability to accurately capture the site, you can reach a more convincing evaluation of conversion losses and design decisions to

It will become easier.