Monthly Solar Asset Management Report: KPI Checklist & Template

Monthly reporting is the most common cadence in European solar asset management, and SolarPower Europe’s Asset Management Best Practice Guidelines treat it as the default: reporting can be set daily, weekly, monthly, quarterly or annually, with monthly being the most common and considered best practice, each frequency carrying its own defined content.

That last part is where most month-end packs go wrong. The frequency is settled. The content is not. Reports drift, either into a wall of every metric the monitoring platform can export, or into a thin generation summary that raises more questions than it answers.

The reusable eight-section report template is directly below, followed by a section-by-section guide to filling it: lock the scope, validate the data, review technical KPIs, add the operational explanation, connect performance to the financial position, explain variance, and close with a stakeholder-ready summary. A one-page month-end checklist is available to download at the end.

What should a monthly solar asset report include?

A monthly solar asset report should contain five layers: technical performance against expectation, operational activity that explains it, financial context appropriate to the stakeholder, variance commentary that connects the three, and a status and action list with named owners. The KPIs themselves are the smallest part of the job. Selecting the right ones, validating the data behind them, and explaining what moved is the work.

The organising principle is simple. A good monthly report is not every KPI you can calculate. It is the right technical, operational and financial information, validated properly, and presented at the cadence the relevant stakeholder actually needs.

Not every stakeholder needs the same pack, either. An O&M counterparty, an equity owner and a lender ask different questions of the same month. Build one consistent structure and vary the depth, rather than maintaining separate reports that will eventually disagree with each other.

Monthly solar asset report template

A reusable eight-section structure. Adjust the depth by stakeholder; keep the section order fixed.

As a rough guide to weighting, sections 3 to 6 carry the substance and typically run to a page or more each, while sections 1, 2, 7 and 8 should stay tight enough to read in a glance.

Appendices, kept out of the main pack: per-plant detail tables, incident log export, irradiance and weather detail, methodology and KPI definitions, contractual exclusions applied.

A note on the definitions appendix: write it once, attach it every month, and update it only when a definition genuinely changes. It ends most of the recurring arguments about whose availability number is right.

How to fill each section

The template above is the output. The seven steps below are the order in which to build it, and they explain why each section contains what it contains. Steps 1 and 2 produce section 2 of the report, steps 3 to 5 produce sections 3 to 5, step 6 produces section 6, and step 7 produces sections 1, 7 and 8.

1. Lock the reporting period, portfolio scope and source data

Before any number is calculated, fix five things. Getting this wrong is the most common reason two reports on the same portfolio do not reconcile.

Reporting period and cut-off. Define the exact start and end timestamps and the timezone, and confirm that every source system uses the same boundary. Monitoring platforms, meter data and accounting systems frequently disagree at month end, and a settlement meter reading taken three days late will not match a SCADA export cut at midnight on the 31st.

Portfolio scope. State which entities are in the report. In practice this means walking down the hierarchy: portfolio, then SPV, then plant or asset, then equipment. Assets acquired, divested, curtailed for grid works or still under EPC warranty during the period need explicit treatment, because a plant that joined the portfolio on the 14th will distort any portfolio-level average unless you say so.

Source-system consistency. Name the system of record for each number. Which meter is the revenue meter and which is the reference. Whether generation is reported at the inverter, the LV side or the grid connection point. Whether irradiance comes from an on-site sensor or a satellite dataset. If this is not written down, someone will silently substitute a source next month.

Reporting resolution. SolarPower Europe recommends that the spatial resolution of reports go down to inverter level, so that underperforming sections of a plant are visible rather than averaged away, and that detailed time-series data be reported or at least archived to support correct availability calculations.

Expected and budget source. Decide what "expected" means before you measure against it, and keep the definition stable. The P50 yield estimate, a simulation-model expected yield recalculated with actual weather, and the financial budget are three different baselines. They will give three different variance figures. Reports that quietly switch between them are the hardest to argue with, and the easiest to distrust.

2. Validate the data before you calculate the KPIs

A precisely calculated KPI built on poor input data is still poor reporting. It is worse than a missing number, because a missing number invites a question and a wrong number does not.

IEA PVPS Task 13, in its 2024 best-practice guidelines on technical and economic KPIs, treats data quality and data cleaning as the decisive step in the whole processing cycle, and sets out five criteria to check: accuracy, completeness, consistency, timeliness and reliability. The same work notes that even the best gap-filling strategies increase uncertainty, and recommends recording every data-related step, from detected issues through filtering and imputation to aggregation.

What should be checked before calculating PV performance KPIs?

Work through these before anything is calculated:

• Generation and meter completeness. Are there missing intervals? What percentage of the period is covered? Gaps at inverter level can hide inside a plant total that looks complete.
• Irradiance and sensor quality. Confirm whether the reference is plane-of-array or global horizontal, since substituting one for the other changes performance ratio materially. Check pyranometer calibration dates and look for soiling or drift on the sensor itself. IEC 61724-1 sets the requirements for irradiance, module temperature and soiling measurement that these checks rest on.
• Missing periods and imputation. If gaps were filled, record how, and flag it in the report rather than presenting an imputed figure as measured.
• Obvious anomalies. Negative values, flatlines, values exceeding installed capacity, night-time generation. Each has a physical explanation and none belong in a KPI without one.
• Period consistency across systems. Reconcile the monitoring total against the settlement meter for the same window before either goes into the report.
• Hierarchy integrity. Confirm no plant is double-counted across SPVs and none has been orphaned by a structural change during the month.

One practical habit: keep a short, dated data-quality note in every report. Two or three lines stating coverage, any substituted sources and any filled gaps. It costs almost nothing and it is the difference between a report that survives lender scrutiny and one that does not.

3. Review the technical performance KPIs

Report the KPIs that let someone act. Each one below answers a different question, and quoting them together is what makes the section useful.

Actual generation versus expected or budget

The headline number, expressed in energy and as a percentage variance, at portfolio and plant level. On its own it says almost nothing, because a shortfall driven by a dull month is a different management problem from a shortfall driven by an inverter that was offline for eleven days. This is why the next three KPIs exist.

Performance ratio

Performance ratio expresses how effectively the plant converted the irradiance reaching the modules into delivered AC energy, relative to nameplate rating. It is defined in IEC 61724-1 and is the most widely used quality indicator in the industry, capturing the combined effect of temperature, soiling, degradation, inverter and transformer losses and downtime.

For monthly portfolio reporting, two points matter more than the formula. First, uncorrected PR is temperature-sensitive and will fall in summer and rise in winter for reasons that have nothing to do with plant health, so month-on-month comparison needs either temperature-corrected PR or a same-month-last-year comparison. Second, PR is conventionally reported over a month or a year in line with the O&M contract, so use the contractual definition in contractual reporting rather than inventing a house variant.

If you have a reliable simulation model, the energy performance index defined in IEC 61724-1 is a more season-stable alternative, though it is only as good as the model behind it, which is why PR remains the contractual default.

Specific yield (kWh/kWp)

Specific yield normalises energy output by installed capacity, which makes plants of different sizes directly comparable inside one portfolio table. It is the fastest way to spot the outlier site in a twenty-plant list.

It is also weather-dependent, so a low solar specific yield can mean a technical problem or simply a low-irradiance month. Always present it next to irradiance for the same period, or next to PR, so the reader can tell the two apart.

Availability

Availability tracks whether the plant was able to generate when it could have. It is standard in O&M contracts and it is where reporting most often goes wrong, because at least three related but distinct indicators travel under the same word: technical availability or uptime, contractual availability (which excludes agreed exclusions such as force majeure or grid outages), and energy-based availability (which weights downtime by the energy actually lost).

Label which one you are reporting, every time. A plant can show 99.2% contractual availability and still have lost a meaningful share of the month's revenue if the outage fell across the sunniest fortnight. Energy-based availability is what connects downtime to money.

Downtime, outage hours and energy lost

Report outage hours alongside estimated energy not delivered, attributed to cause where it is recorded. Energy lost is the figure that converts an operational event into a financial one, and it is the bridge into the next two sections.

Irradiance, curtailment and soiling where relevant

Include measured irradiance for the period against the long-term reference, so the reader can separate weather from performance without asking. Add curtailment volumes where grid or market curtailment applied, and soiling ratio where a soiling station or reference module is installed. Both suppress PR for reasons that are not equipment faults, and both need to be visible rather than buried.

Which KPIs should solar asset managers track?

For a monthly portfolio report, the working set is: generation versus expected or budget, performance ratio, specific yield, availability (stating which definition), downtime and energy not delivered, and measured irradiance as the context for all of them. Curtailment, soiling ratio and degradation indicators are added where the plant or the contract makes them relevant. Everything else is analysis, and analysis belongs in an appendix or a separate review, not in the monthly pack.

What is the difference between performance ratio, availability and specific yield?

They answer three different questions and are not interchangeable.

• Performance ratio asks: how efficiently did the plant convert the sunlight it received? It is weather-normalised, so it isolates plant quality.
• Availability asks: was the plant able to operate? It measures uptime, not efficiency. A plant can be fully available and still perform poorly.
• Specific yield asks: how much energy did each installed kWp actually deliver? It is not weather-normalised, so it reflects both plant health and the month's resource.

A month can show high availability, falling PR and normal specific yield at the same time. That combination points at gradual efficiency loss (soiling, degradation, sensor drift) rather than an outage, and no single one of the three would have told you.

4. Add the operational explanation behind the numbers

This is the section that separates a report from a data export. Numbers describe what happened. Operational records explain why, and they are the only part of the pack that tells the reader whether anything is being done about it.

SolarPower Europe's guidance is explicit that the individual monthly report should include relevant operational incidents, corrective maintenance interventions and, where the supplier provides them, security incident statuses.

Include for the period:

• Incidents opened, closed and still open, with age on the open items
• Corrective maintenance carried out, with the associated downtime and energy loss
• Preventive maintenance completed against plan, and anything deferred
• Root cause where it has been recorded, and an honest "not yet determined" where it has not
• Energy lost by cause, which is what makes the technical section legible
• Warranty and contractual events: claims raised, claims in progress, SLA breaches, response and resolution times against contract
• Open actions carried forward, with owners

The discipline that makes this work is linkage. Each material variance in section 3 should trace to an operational record here, and each operational record with energy or cost impact should appear in section 5. Where the incident, work order, downtime, energy loss and cost are captured against the same asset record, that linkage is a query. Where they sit in a monitoring platform, a ticketing tool and three spreadsheets, it is a week of reconciliation, which is the single largest hidden cost in most month-end cycles.

Organisations differ here. Some asset managers hold incident data directly, some receive it from an O&M contractor on a contractual reporting schedule, and the level of root-cause detail varies with the contract. Say in the report which applies, rather than presenting partial data as complete.

5. Connect operating performance to the financial position

Financial content belongs in the monthly report, but not all of it, and not all at monthly cadence. SolarPower Europe's guidance describes financial information as incorporated into the individual monthly report, usually centred on a cost structure analysis, with a consolidated report produced in addition where required. Statutory financial statements, valuation work and lender packs follow their own schedules, set by the financing structure and the reporting obligations in the relevant agreements.

For a standard monthly pack:

• Revenue actual versus budget, split where possible into a volume effect and a price effect. A revenue shortfall caused by low generation and one caused by a fall in captured market price require completely different responses, and reporting them as one number hides that.
• OPEX against budget, with commentary on material variances rather than a full line-by-line table
• Material service and corrective maintenance costs for the period, tied back to the incidents in section 4
• Cash position and reforecast where the stakeholder or the financing structure requires it
• Covenant and lender reporting according to the obligations that actually apply to the SPV
  

  Should DSCR, IRR and NPV appear in a monthly solar report?

Usually not all three, and rarely as standing monthly KPIs.

DSCR is relevant where the asset is financed and the facility agreement requires it. Where it applies, report it on the schedule the agreement specifies, which is often quarterly or at defined calculation dates rather than monthly, and report it against the covenant threshold rather than in isolation.

IRR and NPV are investment and valuation measures. They are calculated over the asset life, they move mainly with assumptions rather than with last month's operations, and recalculating them every month produces noise that reads as precision. They belong in valuation cycles, budget resets, refinancing, disposal processes or a board-mandated review, and they should be presented with the assumption set that produced them.

The general rule: report a financial metric at the cadence the obligation or the decision requires, and say which obligation it serves. A monthly report that carries an unchanged IRR figure month after month trains its readers to skip the financial section.

6. Explain variance instead of only reporting it

Most monthly reports state variance. Fewer explain it. This section is what stakeholders actually read, and it is the cheapest place to improve the quality of your reporting.

Use a fixed five-question structure for every material item, so the format is predictable and comparable across months:

1. What changed? State it in energy and in money. "Portfolio generation 6.2% below budget, equivalent to 412 MWh and approximately EUR 38k of revenue."
2. Why did it change? Decompose it. Irradiance 3.1% below the long-term reference accounts for roughly half. An inverter failure at one site accounts for most of the rest. A residual remains unexplained.
3. What was the operational or financial consequence? Energy not delivered, revenue impact, cost incurred, any contractual or covenant implication.
4. What has been done? The intervention, when it happened, and the current status.
5. What remains open? With an owner and a date.

Two things make this section credible.

Separate weather from performance every time. A shortfall against budget in a low-irradiance month is a forecasting outcome. The same shortfall in a normal-irradiance month is an operational one. Presenting generation variance without irradiance variance next to it forces the reader to assume the worse of the two, and they usually will.

Set a materiality threshold and apply it consistently. SolarPower Europe suggests a useful anchor: a loss due to a fault is considered major when PR or availability is affected by more than roughly 1% within a one-month reporting period, and best practice is to issue an intermediate operational report when that happens rather than waiting for month end. Whatever threshold you adopt, publish it in the report so readers know that silence on an item means it fell below the line, not that it was missed.

Also carry forward last month's open items and state their status. A variance section that never references the previous month is a series of unrelated documents rather than a record.

7. Finish with a stakeholder-ready summary and sign-off

The executive summary is written last and read first. It should be readable on its own by someone who will never open the appendices.

Include:

• Executive summary: three to five sentences covering portfolio performance against budget, the single most material issue, and whether it is contained
• Material exceptions: the items that crossed your materiality threshold, and nothing else
• Portfolio changes: acquisitions, disposals, entities entering or leaving operations, structural changes affecting comparability
• Unresolved risks and issues: including items outside your control, such as grid constraints or pending warranty determinations
• Open actions: action, owner, status, due date, one line each
• Next-period priorities: three to five items, not a work plan
• Report metadata: preparer, reviewer, date of issue, data cut-off, and the data-quality note from section 2

Keep the structure identical month to month. SolarPower Europe's guidance notes that report content is expected to be consistent, and that any change in content or format should be explained by the provider. Consistency is what makes trends visible and what allows a reader to find the one thing they came for in fifteen seconds.

Download the one-page month-end reporting checklist

The seven steps above, condensed to a single page you can print or keep open while you work. Same order, same logic.

Making the cycle repeatable

Most of the effort in month-end reporting is not analysis. It is assembly: pulling generation from monitoring platforms, incidents from a ticketing system, costs from accounting, and reconciling them into one consistent view before the thinking can start. The larger and more dispersed the portfolio, and the more monitoring systems it spans, the more of the month that assembly consumes.

That is the problem ACTIS ERP was built around. Because monitoring data, incidents, work orders, contracts, costs and financial records sit in one platform against the same portfolio, SPV, plant and equipment hierarchy, the linkage between a KPI and the operational event behind it is already in place when reporting starts. The Power BI layer on top produces the technical, operational and financial reports, with a report generator that takes an asset and a time period and produces a downloadable report.

A documented ACTIS ERP implementation at Nautilus Solar, a US asset management company managing more than 200 solar projects across a dispersed portfolio with multiple monitoring systems, recorded a 77% reduction in time spent on reporting after monitoring data, operational data and reporting processes were consolidated onto one platform. That result reflects that organisation's starting point, portfolio and implementation scope. Results vary with portfolio size, existing systems and configuration.

ACTIS ERP is developed by Alectris, a renewable energy services company, and has been in field use for over a decade, which is why the hierarchy and the workflows follow how operators actually work rather than how software prefers data to arrive.

To be clear about the boundary: ACTIS ERP does not replace SCADA, your monitoring platform or your accounting system. It centralises the data those systems produce and connects it to the operational and financial records that explain it.

See how ACTIS ERP connects technical, operational and financial reporting across a renewable portfolio.