Statute of Limitations for Common Law Fraud / Deceit in Poland
6 min read
Published March 22, 2026 • By DocketMath Team
Overview
In Poland, claims framed as common law fraud / deceit generally fall within the Polish Civil Code rules on tort (czyn czynu niedozwolonego) or unlawful enrichment / other civil-law remedies, depending on how the claim is pleaded and what facts are alleged. The “fraud” label you might see in other common-law systems does not translate 1:1 into a single Polish cause of action. Practically, though, plaintiffs commonly rely on Polish provisions that address:
- Fault-based liability for harm caused by an unlawful act (often where deceit is used to induce conduct), and/or
- General contractual and pre-contractual liability concepts where relevant (for example, misrepresentations in transactions).
DocketMath’s statute-of-limitations calculator helps you model the timing question: when does your limitation clock start, and when does it expire? For this blog post, the focus is on the limitation period treatment that most often applies to civil claims grounded in a fraudulent/deceptive act.
Note: This page is about limitation rules for civil claims in Poland—not criminal fraud charges. Criminal limitation periods are different and not covered here.
Limitation period
Typical structure: start date + deadline
Polish limitation rules commonly use a two-step pattern:
- The clock starts at a defined point (often tied to when the injured party knew—or reasonably could have known—about the harmful conduct and the person liable).
- A deadline runs after that start point, with possible “long-stop” dates (absolute outside limits) for some claim types.
Common approach for fraud/deceit-like civil claims
For civil claims that are treated as tort-based liability (i.e., harm caused by an unlawful act with fault), the frequently used Polish limitation structure is:
- A short limitation period that depends on knowledge (subjective element), and
- A long-stop limitation period that prevents claims from being brought indefinitely (objective element).
The result is that two inputs usually matter most for a fraud/deceit-style claim in Poland:
- When the claimant actually learned of the fraud/deceit (knowledge of the act and the wrongdoer), and
- The outer “absolute” limit running from the event.
Practical timing examples (how outputs change)
Example A: Late discovery
If the claimant discovers the deceit 2 years after the fraudulent conduct, the short knowledge-based clock starts at discovery. Depending on the exact limitation regime applicable, the claim may still be timely even though the event happened years earlier—until the long-stop date.Example B: Immediate discovery
If the claimant learns about the deceit shortly after it occurs, both the short period and the long-stop period are likely to expire sooner relative to the claim filing date.Example C: Uncertain knowledge date
Where the “knowledge” date is disputed, limitation outcomes often turn on what the claimant knew or should have known in light of reasonable diligence. DocketMath helps you run “what-if” scenarios using different knowledge dates so you can see sensitivity.
Key exceptions
Polish civil limitation rules include important exceptions and modification mechanisms. These can be outcome-determinative for fraud/deceit-like claims.
1) Discovery-based limitations can shift the start date
For many claim categories, the limitation period does not run from the date of the deceit itself. Instead, it may run from when the claimant learned of the relevant facts (harm + wrongdoer). That means the most practical “exception” is often not a special fraud rule, but rather the knowledge trigger.
2) Interruptions (e.g., by formal action)
Certain procedural steps can interrupt the limitation clock (for example, by filing a claim or taking steps that are legally recognized to stop time). The effect is that the clock may reset or restart depending on the statute and procedural context.
3) Long-stop limits still cap claims
Even when a knowledge-based trigger helps, many regimes still have an absolute long-stop date. That long-stop operates as a hard ceiling—so arguing delayed discovery cannot extend the claim indefinitely.
4) Wrong cause of action can change the limitation analysis
Because Polish law organizes claims differently than “common law fraud / deceit,” the label alone may not determine the limitation regime. The limitation clock can change depending on whether the claim is treated as:
- tort-based, or
- contract-related, or
- another civil-law theory tied to a different limitation provision.
Warning: If a claim is pled under the wrong legal theory, courts may apply a different limitation provision than you expected. DocketMath can help you compare scenarios, but it cannot replace legal pleading strategy.
Statute citation
The key Polish Civil Code limitation provision commonly relied upon for civil claims based on unlawful acts (tort) is:
- Polish Civil Code (Kodeks cywilny), Article 442¹ — limitation periods for claims arising from harm caused by a prohibited act, including the structure involving a knowledge-based period and an absolute long-stop period.
When you use DocketMath, the statute citation you select should align with the theory you’re modeling (tort/unlawful act framework for deceit-based harm).
Use the calculator
Open DocketMath’s statute-of-limitations tool here: /tools/statute-of-limitations.
What to enter (inputs that actually change the output)
Typically, you’ll be prompted for inputs such as:
Date of harmful conduct / deceit (event date)
Used for the absolute long-stop component (where applicable).Date of discovery (knowledge date)
Used to trigger the knowledge-based limitation window.Claim theory / limitation regime selector
This determines which statutory rule is applied (for example, a tort/unlawful act regime aligned with Civil Code Article 442¹).Target filing date (optional, if the tool supports “is it timely?” outputs)
Lets you compare expiration dates to a specific filing date.
How output results should be interpreted
After entering the inputs, DocketMath generally produces:
- A calculated expiration date for the applicable limitation period(s)
- If the regime includes both a short (knowledge-based) period and a long-stop (absolute) period, you’ll typically see:
- an expiration date tied to knowledge, and
- an outer “cap” date tied to the event.
That lets you run sensitivity checks:
- If you move the knowledge date forward by 30, 90, or 180 days, does the expiration date cross your planned filing date?
- If you move the event date (e.g., based on evidentiary disputes about when the deception occurred), does the long-stop cap become decisive?
A quick scenario run-through
- Event (deceit) date: 2021-05-10
- Knowledge (discovery) date: 2023-08-20
- Filing date to test: 2024-09-01
When you change only one input (like knowledge date), the calculator output will show whether the claim is still within the knowledge-based window and whether the long-stop cap is already reached.
Pitfall: Don’t enter “knowledge” as the date you suspected wrongdoing without evidence. Many limitation triggers are tied to when the claimant knew or could reasonably know the relevant facts—using a too-late or too-early date can shift the computed deadline.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
