Projects

Cantonal, municipal and utility incentives for solar: how do you check them?

Local solar incentives do not follow the same logic as Pronovo. This guide explains how to identify whether support belongs to the canton, the municipality, or the utility, in what order to verify it, which territorial signals require a finer check, and how to avoid publishing a misleading cumulative benefit claim.

Published on 02/05/2026
Reviewed on 02/05/2026
Reading ~7 min
Frequently asked questions 3

The safest method is to verify local support only after the solar project has been framed and the Pronovo layer has been positioned. Local incentives do not obey a single grid or a universal filing order. They may depend on the canton, the municipality, the energy supplier, the grid operator, the type of installation, or a specific project component such as the battery. In other words, the right check is territorial and contextual, not generic.

Why should local incentives be checked separately from Pronovo?

Pronovo gives you the federal baseline. Local incentives follow different logics: a top-up amount, a battery bonus, a supplier rebate, a territory-based condition, or a network-related rule. If you mix those layers too early, you easily end up with a false promise of stacking. The local check therefore has to be treated as an independent layer, not as an extension of the federal one.

That separation matters for editorial accuracy as much as for project design. A reader who sees “solar incentive” assumes one scheme, one rule set, and one straightforward eligibility path. In reality, the official logic is often split across multiple public or semi-public actors, each with its own scope. Pronovo does not tell you whether a municipality adds a local bonus, whether a canton supports a battery, or whether a supplier applies a specific tariff or rebate.

The practical consequence is simple: first identify what is already covered at federal level, then check whether any local support exists at all, and only then assess whether the two layers can coexist. That order prevents the most common mistake, which is to present a local aid as if it were automatically available nationwide.

Subsidy simulator

Move from reading to a concrete simulation

We prefill the simulator with the useful context from this page so you can move faster and check the subsidies that fit your situation.

Solar

What can fall under a canton, a municipality, or a utility?

Cantons, municipalities, and utilities do not necessarily support the same thing. A canton may support a photovoltaic measure or one component of the project. A municipality may add a very local lever. A supplier or grid operator may offer a specific bonus, a battery-related incentive, or a buyback logic that changes the project economics. None of these layers should be assumed from the others.

ActorWhat it may coverWhat to verifyCommon trap
CantonA photovoltaic measure or a project componentTerritorial scope, eligible technology, component covered, compatibility with federal supportAssuming a cantonal rule applies everywhere in the country
MunicipalityA local supplement or targeted local measureExact municipality, eligibility limits, wording of the local decisionTreating a municipal page as if it applied to the whole canton
Utility / grid operatorA bonus, a battery-related support, or a buyback logicNamed provider, service area, technical conditions, whether it concerns installation, battery, or injectionConfusing a supplier-specific offer with a public subsidy

The key editorial discipline is to name the actor behind the support. “Local solar aid” is too broad to be reliable on its own. An official source must tell you whether the measure comes from the canton, the municipality, or the utility. If it does not, the statement is not ready for publication.

This is also where wording matters. A “bonus” is not necessarily a “subsidy”; a “buyback rule” is not the same as an installation grant; a battery incentive is not the same as a PV installation grant. The more precisely you identify the object of support, the fewer false expectations you create.

What order should you follow to check local support?

The safest order is: first the location, then the actor, then the project component, and only after that the cumulative logic with Pronovo. Starting from a prize name found elsewhere is riskier, because you may end up trying to match a territorial rule to a project that was never eligible in the first place.

  • Confirm the canton and, if relevant, the municipality.

This establishes the territorial frame. Without it, no local incentive can be safely described.

  • Identify the actual provider or grid operator.

Some offers are tied to a named supplier or network area. The official source must make that link explicit.

  • Check what the measure covers.

Is it the installation itself, the battery, injection into the grid, or another component? The answer changes the economic interpretation.

  • Only then assess stacking with Pronovo.

A local support may complement the federal layer, but this must be confirmed by the relevant official source rather than assumed.

This order is more reliable than jumping straight to “how much can be combined?” because the question of combination only makes sense once the local support has been identified precisely. In practice, the search should start from official territorial pages, not from generic lists or copied summaries.

A good editorial process mirrors that logic. You should be able to answer, for each claim: who issues it, where it applies, what it covers, and whether its compatibility with Pronovo has been explicitly stated. If one of those four points is missing, the information remains incomplete.

Which signals require a stricter territorial check?

As soon as a measure mentions a precise territory, a named provider, a limited envelope, a launch date, a battery, or a power category, the check has to become more granular. The same phrase “solar bonus” can hide very different mechanisms. That is why a territorial clue is not a detail; it is a warning that the rule may be highly specific.

Typical signals that call for a finer check include:

  • a named canton, municipality, or service area
  • a utility or grid operator mentioned by name
  • a limited budget or envelope
  • a start date or launch window
  • a battery-specific condition
  • a power class or output band
  • a measure that seems linked to a particular technology or project component

These signals matter because they change the scope of the claim. If a page says “there is a solar incentive,” the reader may assume that the incentive exists everywhere. Official sources often prove the opposite: the measure is only valid in one municipality, on one network, or for one category of installation.

For publishing, this means you should never generalise from a single local page to the entire country. The official logic is territorial before it is solar. A support measure is not “Swiss” merely because it exists in Switzerland; it remains local if the source ties it to one territory or one network.

When in doubt, the safest editorial posture is to say that the incentive must be checked at cantonal or municipal level, or directly with the relevant supplier, before any claim of availability is made.

How do you avoid publishing a false cumulative claim or a false promise?

You avoid it by separating what is verified, what is conditional, and what still needs confirmation. A serious page does not simply say “stackable” or “not stackable.” It states which level of support is being discussed, which actor controls it, and which territorial or technical conditions still govern the file.

A practical way to write safely is to use three layers of certainty:

StatusHow to phrase itWhat it means
Verified“The canton / municipality / utility states that…”The official source clearly confirms the rule
Conditional“This may apply if…”The rule exists, but only under specific territorial or technical conditions
To confirm“Please check with…”The source is incomplete or too local to publish as a general statement

This approach prevents two common errors. The first is overstating cumulative support by presenting a local bonus as if it were automatically compatible with Pronovo. The second is promising availability without naming the territory or the actor responsible for the measure. Both errors weaken trust and can mislead readers who are trying to size a solar project.

In practice, every local support sentence should answer four questions:

  • Who provides it?
  • Where does it apply?
  • What does it cover?
  • Is its relationship with Pronovo explicitly confirmed?

If the answer to any of those questions is missing, the claim should remain conditional. That discipline is especially important when you are publishing a guide, a project page, or a pre-sales explanation. Readers need direction, but they also need honesty about what has been verified.

A final safeguard is to use the official source language as closely as possible when the rule depends on a public body. If the canton, municipality, or utility defines the scope narrowly, the article should mirror that narrowness. That is how you avoid turning a local exception into a general promise.

Official sources cited

  • Cantonal energy services
  • Concerned municipalities
  • Relevant energy suppliers and grid operators
  • Pronovo

Frequently asked questions

Does a supplier bonus follow the same logic as a cantonal incentive?+

No. You need to check who actually issues the measure, which territory it applies to, what it covers, and its own conditions.

Can you announce a local incentive without naming the territory?+

No. Without the territory, the actor, and the date or validity context, the information is too fragile to guide a solar file.

Is “local solar support” enough as a description?+

Not really. It is better to name the canton, municipality, utility, or grid operator, and to specify whether the support concerns installation, battery, injection, or another component.

Ready to discover your subsidies?

Run a free simulation and get the list of subsidies available for your project.

Start simulation