Self-consumption, batteries and solar subsidies: what do you actually need to understand?

Self-consumption changes the economic and practical logic of the project first. It affects how production is read against building use, whether storage makes sense, and sometimes whether a collective setup is relevant. It does not replace the need to separate federal support, local schemes and grid-related questions. In other words, it is a project steering concept, not a subsidy in itself.

Once self-consumption becomes the reference point, the project is no longer assessed only by installed capacity. It is also read through the rhythm of consumption, the profile of the building and the share of energy that can be used immediately. That is why self-consumption is often the first useful lens when a solar project becomes more than a simple production estimate.

This distinction matters because it changes the order of analysis. Before asking whether an incentive exists, you need to know what the project is trying to do: reduce purchases from the grid, increase on-site use, support a shared model, or simply export a larger share of production. Each of those aims leads to a different reading of the file.

For that reason, official support logic should not be compressed into one generic label. According to the official framework used by sources such as Pronovo and SwissEnergy, the project structure, the use of the electricity and the type of support are separate questions, even when they interact in practice.

A battery can transform the project, but it should never be added as a marketing reflex. It changes the reading of sizing, the real use of electricity, the self-consumption rate and, in some cases, the support available. In certain situations, local aid may target the battery. In others, the battery adds value in a different way or must be analysed separately from the main photovoltaic support.

The trap is to treat storage as if it were automatically the logical next step after panels. That assumption is often too fast. A battery is not just a technical accessory; it changes the operational logic of the whole installation. It can smooth consumption peaks, shift usage into other time slots and reduce the part injected into the grid, but it also introduces a separate investment logic.

This is why battery analysis should begin with the building’s actual consumption profile. If consumption is already well aligned with daytime production, the added value of storage may be limited. If usage is concentrated in the evening or on another schedule, the battery may change the project meaningfully. The point is not to decide in advance that a battery is good or bad, but to read what it changes in context.

It is also important not to confuse battery support with photovoltaic support. A subsidy for the production system does not automatically mean the storage element is covered in the same way. Where a local scheme exists, it may focus on storage specifically; where it does not, the battery must be read as a separate economic and technical layer. That is the official logic to keep in view: production, storage and support are related, but they are not merged into one category.

Individual self-consumption describes the use of electricity by one site or one building. Collective models such as RCP or ZEV concern several consumers around the same production source. Grid injection, by contrast, is the share that is not used locally and is sent back to the network. The distinction is decisive because it changes how the project is presented, notified and understood in support terms.

This table is useful because these terms often appear together in the same discussion, even though they belong to different layers. Self-consumption is a use logic. Battery is a storage logic. Injection is a network logic. RCP and ZEV are organisational logics. If you collapse them into one another, you lose the ability to read the project properly.

In practical terms, the distinction also changes what must be said about the installation. A purely individual project can often be described from the point of view of one user and one roof. A collective project needs another reading: who consumes, who benefits from the production, how the shared arrangement is structured and how the electricity is allocated. Grid injection then sits alongside that structure as the part that remains outside local use.

This is why the project narrative matters as much as the equipment list. Two installations may look similar technically and yet belong to completely different reading frameworks. One may be a straightforward self-consumption case with some injection. Another may be a collective structure with shared use and a different distribution logic. That is not a detail; it is the starting point for understanding the file.

The most frequent confusion is to ask for a “battery subsidy” when the real issue is the overall balance of the project. Another common mistake is to talk about self-consumption as if it removed the question of grid injection or the grid operator. Finally, some files mix Pronovo, local aid, battery and collective models without saying which layer finances what. That lack of separation makes the decision harder before the administrative phase even starts.

The first misunderstanding is structural: a support mechanism is often read as if it covered the whole system in one block. In reality, each layer has its own reading. The federal support framework, local programmes, grid relations and internal project logic are not the same thing. If they are merged too early, the file becomes unclear even when the technical project is sound.

The second misunderstanding is semantic. People often use self-consumption as a catch-all word for the entire project. But self-consumption does not mean “no injection” and it does not mean “battery present.” It means that the electricity is used locally, at least in part. That is a narrower and more useful definition.

The third misunderstanding is procedural. Some dossiers present the equipment, the economic aim and the support request in the same sentence, as if they were interchangeable. They are not. A good reading separates what the system does, what the installation stores, what the network receives and what the subsidy actually covers. That separation is what keeps the project intelligible.

A simple way to avoid confusion is to read the project in this order:

• Use logic: who consumes the electricity, and when?
• Storage logic: does a battery change the timing of use?
• Network logic: what is injected, and under what conditions?
• Support logic: which programme or scheme applies to which layer?
• Organisation logic: is the project individual or collective?

That order does not replace the administrative file, but it prevents the most common category errors.

You should move down to a procedure as soon as the topic touches documents, grid notification, the Pronovo timeline or the risk of blockage. You should move down to the glossary as soon as the words themselves become the point of friction, especially between self-consumption, RCP, ZEV and injection. That is usually the moment when a concept is no longer enough and the file needs a precise term.

If the issue is operational, go to the procedure. If the issue is semantic, go to the glossary. That distinction is useful because many solar files fail not for technical reasons, but because the project was described with the wrong layer of language. A good procedure answers “what must be done?” A glossary answers “what does this term mean in the Swiss solar context?”

This article has deliberately stayed one level above the administrative file. It is meant to help you read the project correctly before you commit to a form, a support request or a network exchange. Once that reading is clear, the next step becomes much easier.

• Pronovo
• SwissEnergy
• the relevant grid operators and suppliers