Inputs you need for Statute Of Limitations in Brazil

6 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Inputs you will need

To calculate a statute of limitations (prescrição) timeline in Brazil using DocketMath (jurisdiction BR), you’ll typically provide case inputs that determine: (1) when the clock starts, (2) which limitation window applies, and (3) whether any events interrupt or suspend the running period.

Use the checklist below as your input checklist for the Statute Of Limitations calculator.

Input checklist (Brazil / BR)

Note: Brazil’s limitation periods depend heavily on the substantive category of the claim and on procedural timeline events that can interrupt or suspend the running of time. If you enter only dates but choose the wrong claim category, the output can be materially off.

Where to find each input

Below is a practical “where to look” guide so you can collect what DocketMath needs quickly. The goal is to identify the exact date your team treats as legally relevant (for example, filing/protocol date vs. receipt date).

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Claim category / legal basis

Look for facts that establish the relationship and track of the dispute:

Contracts & demand letters: identify whether the issue is a contractual breach and whether it’s consumer vs. non-consumer.
Pleading drafts or case notes: note whether the matter is treated as civil, labor, or another track.
Invoices and service records: help determine whether the obligation is installment-based (which can change how you think about accrual).

What to capture: a short label you’ll map to the calculator’s claim type options.

2) Date the claim accrued

Find the event that marks when the claimant could have sued (the “right to sue” start date). Common examples:

Contract: the maturity date, the delivery/acceptance timeline, or the breach date specified in the agreement.
Unpaid debt: the due date of the invoice/obligation; for installments, the due date of each installment can be important.
Tort / damages: the date of the harmful act and/or the point when damages became reasonably ascertainable, depending on how your case team treats accrual.

What to capture: a specific calendar date (YYYY-MM-DD).

3) Interruption events (and their dates)

Brazil recognizes that certain events can interrupt prescription. Your task is to identify the event you actually have and then enter its date(s):

Filed court action: typically the date of filing (protocol/filing date is often the relevant operational date).
Formal judicial or procedural acts: check docket entries and case movement logs.
Documented notices/demands: if your workflow treats a particular demand as interruption, record the exact dispatch/receipt date your team uses consistently.

What to capture: for each event, the event type and the relevant date.

4) Suspension events (and their dates)

Some events can suspend the running of the clock. Gather the period boundaries:

Settlement negotiations / agreed standstills: confirm whether there’s a written agreement and its start/end dates.
Procedural halts: check court docket events indicating the timeline was paused.
Legal impediments documented in the case file: capture the period the impediment was in effect.

What to capture: suspension start date and end date (or the end condition, if your process represents it that way).

5) Status details affecting accrual

This is where many “almost right” timelines fail. Gather facts that affect when the claim is treated as accruing:

Installments: confirm whether the obligation is a single due date or a series of payments.
Continuing harm: document whether harm persisted beyond the first act.
Condition precedents: if performance is conditional, note the date the condition was satisfied.

What to capture: a one-line narrative + the date that changes your accrual analysis.

6) Jurisdiction context inside Brazil

DocketMath mapping for BR may rely on the operational track you select. Collect enough information to align your inputs:

Civil track vs. labor track
Consumer angle vs. non-consumer

What to capture: your track selection that matches the claim category and event logic you intend to model.

Run it

Open DocketMath → Statute Of Limitations (Brazil / BR) via:

Primary CTA: /tools/statute-of-limitations

Enter the inputs in DocketMath and run the Statute Of Limitations calculation to generate a clean breakdown: Run the calculator.

Step-by-step: enter inputs

Select jurisdiction: Brazil (BR).
Choose claim category/legal basis that matches the matter you’re analyzing.
Enter the accrual date (the start date for the “right to sue”).
Add interruption events
- For each event: add event type + date.
Add suspension events
- For each period: add start date and end date (or end condition as reflected in your workflow).
Review the computed prescription timeline
- Confirm it reflects your case theory of accrual and the effects of interruptions/suspensions.

How outputs change when inputs change (quick reference)

Input you adjust	Typical impact on results
Accrual date earlier by 30 days	Deadline shifts earlier by ~30 days (unless event logic recalibrates)
Wrong claim category	A different limitation window may apply → potentially a major deadline change
Add an interruption event	The clock may reset/restart depending on how the event is mapped
Add a suspension period	The deadline moves out by the suspension duration
Change installment treatment	Accrual may shift per installment vs. one global start date

Pitfall: If you provide only one “accrual date” for an installment obligation, you may accidentally model the clock as if all installments matured together—your deadlines can be significantly wrong.

Output interpretation checklist

After you run the calculation, confirm you have:

If something doesn’t match your case file, update the relevant input and rerun.

Gentle disclaimer: This tool output is for planning and timeline awareness, not legal advice. If your case turns on nuanced accrual or event effects, consider confirming the approach with qualified counsel.