A contractual mechanism, not a statutory rate

Polish law does not set a general IT supplier liability cap of one year's remuneration. In commercial B2B contracts, parties may allocate liability within the limits of contractual freedom. A clause is not necessarily enforceable simply because both parties signed it.

Read the financial ceiling alongside the grounds for liability. A cap does not create a claim: first establish whether the supplier is liable for the event. Conversely, accepting responsibility for a very broad range of events may increase exposure substantially despite an apparently reasonable maximum amount.

Fees paid and fees payable are different bases

The calculation may use amounts actually paid or remuneration payable for a defined period. In the first case, late customer payments can reduce the calculated cap. In the second, clarify whether only amounts already due count, or also fees earned for services but not yet invoiced.

Identify which price components count. One-off implementation, subscriptions, additional work and third-party licence charges may receive different treatment. State whether figures include VAT. Under a master agreement with several orders, decide whether the base covers the entire relationship or only the order giving rise to the claim.

Address the first year expressly

The parties can agree a floor or a separate first-year calculation. That is a risk-allocation decision, not a statutory requirement. The supplier should check the result against the contract value and the exposure it can bear. The customer should check that protection is not merely nominal during a particularly risky launch period.

PRACTICE

How the issue appears in practice

Example

Hypothetical example: an annual figure that exists only in assumptions

A supplier maintains a system for PLN 6,000 a month. The draft caps aggregate liability at fees actually paid in the 12 months preceding the event. An outage occurs after three paid months. The customer expected a PLN 72,000 cap, but the formula produces PLN 18,000, assuming the claim falls within it. Before signing, the parties can agree a PLN 72,000 floor if they genuinely intend annual-fee protection from the outset. They should also specify that this floor applies to aggregate liability over a defined period, rather than resetting for each claim. The solution is to fix the mechanism, not merely add the word “annual”.

The calculation period is not the reset period

“Fees for the previous 12 months” describes the calculation base. It does not explain how claims are aggregated. A cap may apply over the entire contract, each contract year or each event. These approaches have different consequences. For a supplier, a per-claim cap may create much greater total exposure than the headline figure suggests.

Specify the reference date: the event, the loss or notification of the claim. If a claim is notified after the relationship ends, a rolling window may include months with no fees. Also decide how related claims are assigned to one event and one period, rather than leaving open whether each subsequent demand triggers a fresh cap.

In particular, the agreement should specify which period applies to claims arising from one incident if losses emerge in later years. An annual reset does not resolve that question by itself.

Penalties and exceptions can change the result

State whether contractual penalties count towards the aggregate cap. The right to recover damages above a penalty is a separate question: Article 484 § 1 of the Polish Civil Code requires an appropriate agreement between the parties. That reservation should also make clear whether the additional damages remain capped.

A Polish contractual penalty secures a non-monetary obligation. A claim for payment must be distinguished from a request for judicial reduction under Article 484 § 2 where performance was substantial or the penalty is grossly excessive. The guide to contractual penalties explains these mechanisms further.

Article 473 § 2 does not permit an effective exclusion of liability for loss intentionally caused to the creditor. A financial cap cannot be used to achieve that exclusion either. Other exceptions, such as confidentiality or software IP, require deliberate negotiation: they may create uncapped exposure or a separate, higher cap. Those are different outcomes.

Exclusions of particular types of loss also need separate consideration. Lost profits are not simply another name for “indirect loss”. In a Polish-law agreement, define the intended scope rather than assuming an English label has one obvious legal effect. A well-chosen financial ceiling does not resolve an ambiguous exclusion.

LEGAL BASIS

Legal basis

  • Polish Civil Code of 23 April 1964, particularly Articles 58, 65, 353¹, 361, 471-473 and 483-484; official consolidated text available through ELI.
Explore this areaE-commerce and technology ↗

This article provides general information and does not constitute legal advice for a specific matter. The appropriate solution depends on the facts, documents and business objective.

Summary

A fee-based cap requires agreement on the entire mechanism: the base, first year, reference date, aggregation and exceptions. Only then can supplier and customer assess the level of liability they are actually accepting.