Contractual Penalties in Switzerland | Magic Heidi

The project suits you, the fee looks right, and then you read this in the draft contract: "For each breach, the contractor owes CHF 10,000.00." Should you sign because surely that's only meant for serious cases? This is precisely where it's worth pausing. Contractual penalties in Switzerland aren't just another bill: they're a contractual risk in their own right for your business.

A contractual penalty can be due even without proven damage. What matters includes the obligation it protects, the trigger and the agreement on further claims. This guide helps you, as an independent professional, ask the right questions before signing. It provides general information about the Swiss Code of Obligations, not individual legal advice.

The essentials at a glance

• Clarify the trigger: If CHF 10,000.00 is due "per breach", you need to know what counts as one breach and whether the amounts can add up.
• Separate damage from the penalty: Under OR 161, an agreed penalty of CHF 3,000.00 doesn't necessarily require financial loss.
• No automatic exit: Paying CHF 5,000.00 doesn't, on its own, release you from performing the contract.
• Negotiate the overall risk: Even with a fee of CHF 8,000.00, there's no statutory percentage limit that automatically makes a clause safe.

Contractual penalties in Switzerland: Which obligation are you securing?

A contractual penalty is an agreed sanction for a specified breach of contract. Its purpose is to support compliance with the contract, and it can spare the creditor having to prove actual damage when claiming the penalty. It isn't a fine imposed by the state, nor is it automatically a fee for extra work.

Independent professionals encounter these clauses in confidentiality agreements, project contracts and delivery deadline provisions. An agency might require you to keep customer data confidential. A website might have to go live for a campaign launch. There can be a legitimate commercial interest behind this; the wording still needs to fit your work.

Read the obligation first, not the franc amount. "Breach of material confidentiality obligations" and "any breach of this contract" aren't equally precise. On its wording, the second version could also cover minor obligations. You can't reliably tell from a single line whether, or how, a clause would be interpreted in a dispute.

So ask: What conduct should this prevent? Who can control that conduct? When does the obligation start and end? For a delivery deadline, the contract should also cover customer approvals and duties to cooperate. Don't silently take on a deadline risk when the main conditions for meeting it are outside your control.

Illustrative, entirely fictional example: Lea and the postponed launch

Lea is a freelancer building an online shop for CHF 8,000.00. The draft specifies a CHF 2,000.00 penalty for late publication but doesn't require the customer to approve products on time. Lea raises this before signing. Together, they add which content the customer must provide by when, and how a late approval affects the publication date.

This story doesn't say how a court would rule. It shows the better moment to negotiate: before anyone misses a deadline. A clearly documented process won't prevent every dispute, but it makes clear who must put which conditions in place. Lea is negotiating not just the amount of the penalty, but when it actually applies.

Also check in what capacity you're signing. This article covers independent contractual relationships, not leaving employment early. Employment contracts can be subject to specific protective provisions and rules of their own. A freelance agreement isn't governed by employment law simply because it contains a non-compete or confidentiality clause. Equally, its heading doesn't conclusively determine the contract's status.

Especially when you're starting out, it helps to consider your contracting partners, business structure and personal risks together. Our guide to setting up an Einzelfirma, a Swiss sole proprietorship provides that business context. If you're unsure how your particular engagement should be classified legally, have that assessed separately.

OR 160–163: Separate penalties, performance and damages

The central question isn't only: "Do I have to pay?" It's also: "What else can the other party demand?" The law distinguishes different situations. Mixing them up means either overestimating your protection or underestimating your obligations following a breach of contract.

Under OR 160 on Fedlex, the basic rule for a penalty covering non-performance or improper performance is this: unless otherwise agreed, the creditor can demand either performance or the penalty. That's the statutory starting point, not a guarantee that your contract adopts that relationship unchanged.

OR 160 paragraph 2 has a different rule for failure to meet the agreed time or place of performance. Here, the penalty can be demanded alongside performance, unless the creditor expressly waives it or accepts performance without reservation. If you accept late work, the question of a reservation therefore deserves particular attention. Have its wording and timing checked for your specific case.

Payment isn't an automatic licence to walk away, either. Under OR 160 paragraph 3, the debtor retains the right to prove that they were intended to be free to withdraw by paying the penalty. You can't simply assume that this exit option exists. If you need it, it must be deliberately agreed in clear terms.

On damage, OR 161 on Fedlex makes another important point: a contractual penalty can become payable even if the creditor has suffered no damage. The agreed breach and the other requirements still need checking. "No damage" doesn't automatically mean "no penalty"; equally, "a penalty in the contract" doesn't automatically mean "a valid claim".

If the damage suffered exceeds the penalty amount, OR 161 paragraph 2 allows the creditor to claim the excess only to the extent that they prove fault. You don't simply add the penalty to the full amount of damage without further scrutiny. Any claim beyond the penalty needs its own legal and factual assessment.

As a calculation only: with a CHF 3,000.00 penalty and CHF 4,500.00 in proven damage, the damage exceeding the penalty is CHF 1,500.00. That doesn't establish a right to payment of that excess. In particular, the required proof of fault and the contractual provisions must be considered. The figure illustrates the distinction, not the outcome of a legal case.

OR 162 is easy to overlook in a quick contract review. It says that an agreement allowing the creditor to retain part payments on withdrawal is also assessed under the rules on contractual penalties. A clause saying "the deposit is always forfeited" therefore deserves a second look. Calling a payment a reservation fee or a fixed charge doesn't, by itself, settle its legal treatment.

Contractual penalties in Switzerland: How much risk can you carry?

There's no general rule that a contractual penalty up to a particular percentage of the project value is always permissible. Nor does a high penalty become invalid simply because you'd struggle to afford it. You need to consider the legal assessment and your business's own risk limit separately.

OR 163 on Fedlex first states that the parties can freely determine the amount of a contractual penalty. Paragraph 3 requires the court to reduce excessive penalties at its discretion. No universal table can predict how that will turn out in an individual case.

So don't plan on the basis of: "I'll sign; the court will sort it out later." A dispute takes time and money. A court-ordered reduction isn't a discount you can choose for yourself, either. If a clause could endanger your business, the risk limit belongs in the contract wherever possible, not just in your defence later.

OR 163 paragraph 2 sets further limits. A penalty can't be claimed if it is intended to reinforce an unlawful or immoral promise. Unless otherwise agreed, the same applies where performance has become impossible because of a circumstance for which the debtor isn't responsible. Don't equate mere difficulty or an inconvenient schedule with that situation.

Illustrative, entirely fictional example: Karim and confidentiality

Karim is asked to prepare a market analysis for CHF 6,000.00. The confidentiality agreement specifies CHF 15,000.00 "for each individual breach". He asks whether a document accidentally sent to the wrong recipient, with multiple attachments, would be treated as one incident or multiple breaches. He also wants to know whether the same information remaining accessible would trigger repeated penalties.

Karim and the client negotiate a more precise definition and an overall cap on contractual penalties. They decide the amount of that cap based on their project; the example deliberately gives no supposedly legally safe standard rate. The cap also needs to be aligned with the damages provisions. Otherwise, it might not limit the total financial risk.

Work through scenarios, not just individual amounts. Check a single breach, multiple independent incidents and an ongoing situation. If CHF 1,000.00 is specified for each day, a prolonged outage has a different financial impact from a one-off sanction. Ask when such claims start, when they end and whether there's an overall cap.

Consider your margin and cash flow, too. A fee of CHF 12,000.00 doesn't mean CHF 12,000.00 in freely available profit. Subcontracted services, time already spent and running costs don't disappear. Check any insurance you have against its actual terms; don't assume that penalties you've agreed to in a contract are automatically covered.

Before you sign: A contract checklist in six questions

A useful negotiation doesn't start with "We're deleting this penalty altogether." It starts with understanding the legitimate interest being protected and identifying excessive or unclear risks. When both sides can describe the same incident, it's easier to find a suitable arrangement. Record changes in the final contract document, not just in a friendly phone call alongside it.

1. Can the protected obligation be checked? A specific delivery deadline is easier to establish than "the best possible cooperation at all times". Describe services, acceptance and cooperation in concrete terms. For confidentiality, the scope, permitted recipients and any exceptions should be clear. Have legally demanding definitions tailored to your project.

2. What triggers the sanction? Distinguish late delivery, defective performance and failure to perform. Clarify what requirements concerning responsibility should apply. Any opportunity to remedy defects or a period for putting things right must also be expressly agreed if you want that option. It doesn't arise just because you'd consider it fair.

3. How are breaches counted? The words "each", "per case", "per document" and "per day" can make a big financial difference. Insist on a shared understanding of related incidents. A cap should make clear whether it applies per event, per project or for the entire contract term.

4. What other claims remain available? Ask expressly about performance, damages, withdrawal and other contractual sanctions. A limit on the penalty alone isn't necessarily a comprehensive liability cap. Provisions scattered across the main contract, general terms and confidentiality agreement should be reviewed together. Contradictions don't disappear because each individual clause looks short.

5. Can both sides document the relevant conditions? Set out approval channels, responsible people and how deadline changes will be handled. A version history and confirmed acceptances are more useful in a dispute than memories of a conversation. Keep only the necessary records, though, and respect the agreed confidentiality requirements in your internal documentation too.

6. Are you consciously accepting the remaining risk? A firm deadline for a trade fair appearance might genuinely be central to the project. In that case, realistic resources, reserves and a suitable fee belong in your calculations. If you can't control or financially carry the risk, a clear refusal is wiser than signing and hoping for goodwill.

One way to open the conversation is: "I understand your interest in delivery on time. Let's clarify the trigger, the customer's contributions and the overall financial exposure." This isn't a ready-made contract clause and doesn't replace legal drafting. It does move the conversation away from abstract mistrust and towards processes you can check.

Don't rely solely on a later invoice or quotation to change contract terms you've already signed. Which agreement takes priority, and how changes are made, is a contractual question in its own right. A Swiss invoice template helps structure your normal billing documents; it doesn't determine whether a penalty clause is valid.

When a contractual penalty is claimed: Check before rushing to offset

An email with a payment deadline creates pressure, but it doesn't answer the legal question. First, secure the signed contract and its attachments, the agreed changes and the relevant correspondence. Put together a factual timeline: What was owed, what actually happened, and when was each service offered or accepted?

Ask the other party to identify the clause, the specific breach and the calculation. Where multiple breaches are alleged, it should be clear which amount relates to which event. Don't just deny "everything" if individual facts are clear. Equally, you don't have to accept a legal claim without checking it simply because you confirm a missed deadline.

Illustrative, entirely fictional example: Nora and the fee deduction

Nora has completed a design project worth CHF 9,000.00. The customer pays CHF 5,000.00 and says the remaining CHF 4,000.00 has been deducted as a contractual penalty for late delivery. Nora separates the fee invoice from the alleged counterclaim. She asks for the exact contractual basis and documents delayed approvals rather than quietly reducing the price of her original work.

Nora has a legal professional check whether the penalty is due and whether the set-off is valid. The story promises neither a certain court victory nor any particular payment outcome. Its practical point is this: a reduced payment received is initially a transaction you need to explain and allocate, not an automatically agreed price reduction.

Keep different amounts separate when a claim is disputed: the agreed fee, the payment actually received and the alleged contractual penalty. Any settlement should also state clearly which claims it resolves. A vague statement such as "that settles everything" can itself become a new interpretation problem later.

Don't confuse a contractual penalty with costs arising from late payment. For that different situation, the guides to reminder fees in Switzerland and late-payment interest in Switzerland provide the relevant detail. A penalty clause for confidentiality breaches doesn't, on its own, establish additional reminder fees on an ordinary customer invoice.

If a claim remains unpaid, taking a debt collection step is another decision, not legal confirmation that the claim is justified. The process for initiating debt enforcement in Switzerland should therefore be kept separate from checking the claim beforehand. Especially with disputed contractual penalties, discuss the evidence, costs and potential opposing arguments before escalating.

Act promptly if you've already received formal correspondence or official documents. Which deadlines apply and what response is needed depend on the document and the procedural situation. This overview can't replace an individual check of deadlines. Negotiating calmly and protecting your rights in time aren't mutually exclusive.

Documentation, taxes and a clear end to the project

The most important rule for your administration is to describe transactions according to what they actually are. A payment for a service delivered, a payment to settle a dispute and a contractual penalty can have different underlying bases. Recording everything as a "project flat fee" loses distinctions that may matter later for advice and bookkeeping.

Tax treatment doesn't depend on the label alone. Whether a payment constitutes genuine compensation for damage, for example, or is connected to an exchange of services must be assessed according to its economic and legal character. Don't add VAT to every contractual penalty as a matter of course. Equally, don't automatically assume that every payment with that label falls outside VAT.

Give your fiduciary adviser the contract, the grounds for the claim and any settlement agreement. A single bank entry for CHF 4,000.00 doesn't explain whether it settled a fee, a penalty or multiple items. For a mixed payment, a clear breakdown helps. The correct accounting entry and tax treatment require a specific assessment.

Close the project from an organisational perspective too. Document the handover, outstanding items and agreed follow-up work. Clarify which confidentiality duties continue after the project ends and which data must be returned or deleted. A paid final invoice doesn't necessarily end every ancillary contractual duty; the agreement remains decisive.

For ordinary service billing, you can create invoices with Magic Heidi. That doesn't replace a review of your contractual penalty or a legal assessment of a set-off. Its useful role is to bill clearly for your actual services and keep your records organised while you resolve disputed contractual questions separately.

Before your next engagement, start with three things on the table: the complete draft contract, your realistic project plan and a calculation of the maximum possible risk. If those three don't fit together, renegotiate before committing. A good project shouldn't just promise revenue; it should be manageable under its actual terms.

Your next step: In the next draft, highlight the triggers, counting rules and possible additional claims. Have uncertainties involving large amounts checked by a qualified professional. If you'd then like to simplify your day-to-day invoice administration, explore Magic Heidi's current plans. You make conscious decisions about contractual risks yourself; your invoicing software doesn't make them for you.

This overview is based on OR 160–163 in the version published on Fedlex as at 1 October 2026. All three short stories are entirely fictional illustrations. For specific disputes, employment-law questions or tax uncertainties, consult an appropriately qualified professional.