Statute of Limitations for Written Contract in Poland

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Poland, the statute of limitations (prescription) for claims arising from a written contract is governed primarily by the Polish Civil Code (Kodeks cywilny). If you’re using DocketMath’s statute-of-limitations calculator, you’ll be translating a contract type and key dates into a limitations timeline—typically to answer: when does the claim become time-barred if it hasn’t been brought to court?

This guide focuses on the common scenario where a creditor wants to enforce a monetary claim under a written agreement (for example, a signed supply agreement, services agreement, or loan agreement documented in writing). It also covers the main situations that can extend, pause, or otherwise change the limitations analysis.

Note: Poland’s limitation rules are legal mechanics, not just “timing.” Even after a limitation period expires, the claim may still be disputed in court unless the defendant raises the statute of limitations defense.

Limitation period

1) The baseline rule for written contracts

Under Polish civil law, a claim connected to a contract typically falls under the general limitation framework. For claims arising from a contract, the standard limitation period is commonly 6 years for claims other than those specifically listed for different durations.

For written contracts, the key takeaway for many practical contract disputes is that documentation in writing helps establish:

  • the contractual basis of the claim, and
  • the date from which the limitation period may start (depending on the obligation’s maturity).

In other words, the “written” attribute is usually not a separate limitations duration by itself; instead, it affects how you prove the obligation and its due date, which then affects the timeline.

2) When the clock starts

A frequent trigger is the time the obligation becomes due. Practical examples:

  • Payment due on an invoice date: limitations often start when the payment is contractually due (or when it becomes due after notice/conditions).
  • Deliveries or milestones: limitations can start for each installment/milestone when that part becomes due.
  • Termination and acceleration clauses: the due date of remaining payments can change if the contract makes them immediately payable upon a defined event.

If the contract specifies a maturity date, that date is usually central to the “start” of the limitations analysis.

3) How to estimate with DocketMath

When you input details into DocketMath’s statute-of-limitations calculator, your outputs will generally shift based on:

  • the claim category you select (e.g., contract claim),
  • the date the claim became due (or due date of performance),
  • whether the calculator has options for interruptions/pauses (often reflecting events like formal demands or court actions, depending on what you choose to track).

The more precisely you define the “due” date (and any later maturity events), the more reliable the calculated end date becomes.

Checklist: inputs that usually matter

Key exceptions

Polish limitations are not always a straight line. Certain legal events can extend the period or stop/interrupt it. You should model these scenarios carefully because they can change the “final day” when a claim becomes time-barred.

1) Interruption of the limitation period

Some procedural or formal actions can interrupt the limitations running such that the time is recalculated. Common examples in Polish civil practice include:

  • filing a lawsuit,
  • certain formal acts that law treats as interrupting the period.

Because interruption rules can depend on the type of action and timing, the most practical approach is to:

  • record the exact date the interrupting act occurred, and
  • ensure you select the matching option (if available) in DocketMath.

Warning: A rough date (e.g., “around July 2023”) can move the computed deadline by months. For limitation timing, courts often rely on the actual calendar date of the due event or procedural act.

2) Claims with different limitation periods

Not every contract-related claim uses the same baseline. Some claims are governed by different statutory durations (for example, certain claims tied to specific performance types or special legal regimes). If you select the wrong claim category in a calculator, you may get a misleading end date.

How this shows up in real work:

  • A claim labeled “contract” in a workflow may actually fall into a special category due to the nature of the obligation.
  • The invoice and payment terms might support the due date, but the legal characterization of the claim determines the duration.

3) Morality/consumer and other specialized regimes (scope check)

Some disputes involve legal frameworks that can affect:

  • how obligations are interpreted, or
  • whether particular procedural steps are required before enforcement.

These issues rarely change the written-contract “baseline” directly, but they can affect when an obligation becomes enforceable, which then affects limitation start timing.

Statute citation

The principal statutory basis for limitation periods for contractual claims in Poland is found in:

  • Polish Civil Code (Kodeks cywilny), Article 118 — sets the general limitation period of 6 years for certain claims, including many contract-based claims, and distinguishes categories with other periods.

Additional provisions can govern start rules, suspension, and interruption (often addressed in adjacent Articles within the Civil Code). If you’re using DocketMath, the calculator typically focuses on the most relevant variables for the chosen scenario and will assume standard rules unless you indicate events that affect running time.

Use the calculator

To estimate your limitations end date with DocketMath, start with the Primary CTA and then map your facts to the calculator’s fields.

Open the DocketMath tool:
/tools/statute-of-limitations

What you’ll generally enter

  1. Jurisdiction: Poland (PL)
  2. Claim type: choose the option that corresponds to written contract / contract claim (wording may vary)
  3. Due date: the date the payment/performance became due under the written contract
  4. Time-impacting events (if the tool supports them):
    • interruption events (e.g., lawsuit filing date) or other calculator options that reflect changes to the running period

How outputs change based on your inputs

Use the calculator like a “what-if” engine:

  • If you move the due date forward by 30 days, the calculated end date usually moves forward by about the same amount (because the baseline period is calculated from due date).
  • If you input an interrupting event, the calculator’s output may:
    • reset the running period, or
    • compute a new end date reflecting the reset/changed timeline.

Practical workflow tip:

  • Confirm the due date from the contract’s payment clause (e.g., “pay within 14 days of invoice receipt” usually requires an invoice-receipt date to determine the due date precisely).

Outputs to watch for

Even when the calculator returns one end date, it’s useful to capture:

  • the start date used by the tool,
  • the limitations duration applied (e.g., 6 years),
  • any adjusted end date after interruptions/pauses (if applicable).

Pitfall: Selecting “written contract” while using a “due date” that reflects invoice issue rather than contractual maturity can artificially shorten (or extend) the timeline. Build your due date from the actual contract trigger.

Related reading