A Building Programme subsidy and a tax deduction can sometimes coexist, but they do not follow the same logic. One is a funding decision tied to an eligible measure and the correct procedure. The other is a tax reading of renovation expenses under the applicable tax rules for your file.
That distinction matters because many renovation budgets are presented as if “subsidy + tax saving” were one simple stack. In reality, the subsidy is a concrete amount awarded and paid if the measure qualifies. The tax effect is separate, often later in time, and depends on the way the expense is documented, allocated and read by the competent authority. The safest method is therefore to treat them as two different questions from the outset.
Can a Building Programme subsidy and a tax deduction be combined?
Yes, a subsidy from the Building Programme can be combined with a tax deduction in principle, but not through a single automatic formula. The subsidy is judged under programme rules; the deduction is judged under tax rules. To combine them correctly, you must check the measure, the canton, the timing of the file and the documents kept for both readings.
The first useful reflex is to stop thinking in terms of “stacking percentages”. A subsidy is not the same thing as a tax reduction, and it is not read by the same authority for the same purpose.
In practice, you are dealing with two layers:
- Subsidy layer: is the measure eligible under the competent Building Programme rules, and was the correct process followed?
- Tax layer: how will the renovation expense be treated in the tax return once the real invoices and any subsidy information exist?
That means you should not promise yourself a combined savings figure on the basis of a commercial quote alone. A quote may describe the works, but it does not by itself settle eligibility under the programme or deductibility for tax purposes.
A simple way to handle the decision is this:
- Identify the exact measure and the canton concerned.
The Building Programme is implemented through cantonal practice, so the measure must be read in the correct place.
- Check the subsidy procedure before committing irreversibly.
If the measure requires a particular order of application, offer, approval or completion, that order matters.
- Complete the works with clean, traceable documentation.
Final invoices, payment proofs and the grant decision will later matter more than a rough sales simulation.
- Only then estimate the tax effect.
Tax treatment should be read from the final file, not guessed at the start as if it were part of the subsidy.
Used this way, the combination is possible to assess without confusion: first confirm whether the project receives funding, then analyse how the remaining expense is treated for tax purposes.
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.
Why distinguish the subsidy from the tax effect?
The subsidy and the tax effect answer different questions, happen at different moments and produce different outcomes. A subsidy is a paid contribution linked to an approved measure. A tax deduction is a later fiscal treatment of expenses. If you merge them too early, you risk budgeting with a number that neither the programme nor the tax authority has actually confirmed.
This is the core distinction on the page. If you understand it, most “Can I combine them?” questions become much easier.
| Point of analysis | Building Programme reading | Tax reading |
|---|---|---|
| Main question | Is this measure fundable under the applicable programme rules? | How is this renovation expense treated in the tax file? |
| Usual basis | Measure, building, canton, procedure, completion proof | Invoices, payment proof, subsidy information, tax year, owner situation |
| Outcome | Grant decision and, if approved, payment | Deduction accepted, adjusted or refused according to the tax reading |
| Typical mistake | Assuming the commercial scope automatically matches an eligible measure | Treating the expected tax benefit as a fixed cash rebate |
| Good budgeting reflex | Separate the potential grant from the owner’s remaining cost | Estimate tax only after the real net file is documented |
The distinction also helps with timing.
A subsidy becomes concrete when there is an official decision and, ultimately, a paid amount. The tax effect usually becomes meaningful only when the work has been invoiced and you can document what was actually paid, what was subsidised and which year or filing period is concerned.
A practical example makes the difference clearer. Imagine a project that includes envelope work and heating improvements. The installer may present one overall savings narrative. But the programme may only fund certain measures under certain conditions, while the tax reading may focus on how each cost item appears on the invoices and whether the file is complete. The correct combined answer therefore comes from two separate validations, not from one brochure number.
This is why maprime’s route structure starts from the programme itself before moving to tax optimisation. If you have not yet clarified the funding scope, begin with the Building Programme overview. Tax logic becomes more reliable once the subsidy logic is already under control.
Which documents should be kept for both readings?
The strongest files keep the subsidy trail and the tax trail aligned. At minimum, keep the application record, grant decision, payment confirmation, final invoices, proof of payment and any technical or administrative document that explains what was actually done. The goal is not volume; it is traceability between the funded measure, the paid expense and the final tax reading.
Documents are where many apparently simple cases become difficult. The programme and the tax return may look at the same renovation through different lenses, but both still rely on evidence.
For a robust file, keep these items together:
- The subsidy application file
Submission confirmation, portal exports, attachments and any official correspondence.
- The grant decision
This shows what was accepted, under which conditions, and for which measure or scope.
- Proof of subsidy payment
A grant decision is not the same thing as a paid amount. Keep the payment notice or account evidence if available.
- The final contractor invoices
Prefer detailed invoices over broad package descriptions. The more precise the line items, the easier both readings become.
- Proof of payment for each invoice
Bank records or equivalent proof help match the expense to the owner’s actual outlay.
- Technical descriptions or completion documents
If the programme required specific proof of completion, keep it with the invoices.
- A clean separation of cost categories
If one invoice mixes subsidised work, non-subsidised work and unrelated extras, ask for a split or an annex.
That last point is often decisive. A tax reading is much harder when one invoice covers several different realities at once. The same is true on the subsidy side when the funded measure cannot be isolated from the rest of the project.
Good document handling also means preserving chronology. Keep the original offer, the accepted version, the final invoice and the relevant dates. If there were changes in scope, keep those changes visible rather than relying on oral explanations months later.
If your project is part of a broader renovation, a separate project summary can help: one page listing the works, contractor, invoice date, payment date, subsidy file reference and whether the item is linked to the Building Programme. This is not mandatory in every case, but it makes later tax review far easier.
Which stacking cases require particular caution?
The riskiest situations are not ordinary one-measure files but mixed or phased projects: one invoice covering several types of work, several subsidies touching the same project, or a renovation spread across time. These are the cases where “subsidy plus tax deduction” stops being a sales argument and becomes a file-structure problem that may require canton-specific tax advice.
Most misunderstandings come from one of four situations.
1. Mixed invoices
A single invoice may include:
- an energy measure that may be subsidised,
- other renovation work that is not part of that measure,
- and extras that are commercially linked but administratively different.
If these elements are merged into one undifferentiated amount, both readings become weaker. The programme wants to know what measure was actually funded. The tax reading may also depend on how the expense is allocated. Clean invoice separation is therefore a practical safeguard, not an administrative luxury.
2. Global or phased renovations
A wider renovation can include several measures, several contractors and several moments of completion. That changes the file structure.
If your project is broader than one isolated measure, the useful next step is often the global renovation route. It helps you think in terms of project sequencing rather than one invoice or one grant line.
3. Multiple incentives around the same works
If the same project also involves another public or private incentive, the combined reading may become less intuitive. The safe approach is to verify, measure by measure, what is funded, what is paid and what remains as the owner’s expense to be analysed for tax purposes.
This does not mean combination is impossible. It means the file must be read with more discipline.
4. Advice imported from the wrong canton
A common error is to rely on a friend’s result, an installer’s example or a case from another canton. That shortcut is risky. The Building Programme is implemented through cantonal practice, and the tax reading is also not something you should generalise from a different local context.
If your property or project is in a specific canton, move to the corresponding canton route rather than applying a generic answer. For example, if Vaud is your relevant reference point, start from the Vaud page.
When is tax advice needed instead of a commercial reading?
A commercial estimate is useful for understanding the project. It is not the same thing as tax advice.
Professional tax review becomes especially worthwhile when:
- the project is large enough that the tax effect materially changes the decision,
- the invoices mix several categories of work,
- ownership is shared or the file is otherwise structurally complex,
- the renovation is spread across periods,
- or there is real doubt about how the expense should be classified.
In those cases, the best question is no longer “Can I stack these benefits?” but “How should this exact file be read?” That is a tax question, not a sales question.
What should you read next for your project?
The right next page depends on what is still unclear. If you have not yet validated the programme side, return to the parent Building Programme page. If the project combines several works, go to the global renovation route. If your uncertainty is local, move to the relevant canton page before trying to estimate a tax result.
Use the cluster in this order:
- Start with the parent programme page
Go to /en/programs/building-programme if you still need to confirm how the programme is organised and where the cantonal reading begins.
- Move to the project route if works are bundled
Go to /en/projects/global-renovation if your case is not a single isolated measure but a broader renovation with several moving parts.
- Finish with the canton page that matches the real file
Use the relevant canton route, for example /en/cantons/vaud, when the practical answer depends on local procedure or authority.
That reading order keeps the logic clean: first subsidy scope, then project structure, then canton-specific interpretation. Only after that does a tax estimate become worth trusting.
The short version is simple: yes, the Building Programme and tax deductions can be combined in some cases, but the correct method is not additive marketing. It is a two-step reading supported by clean documents and, where needed, canton-specific tax advice.