Statute of Limitations for Oral Contract in Indiana

7 min read

Published April 8, 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.

Overview

Indiana’s default statute of limitations for an oral contract is 5 years under Indiana Code § 35-41-4-2. No claim-type-specific oral-contract rule was found in the provided jurisdiction data, so this general period is the rule to use for this reference page.

An oral contract claim usually turns on the date the cause of action accrued, not the date the dispute became obvious. That means the clock typically starts when one party first fails to perform as promised, such as missing a payment, refusing delivery, or otherwise breaching the oral agreement.

For quick date-checking, DocketMath’s statute of limitations tool helps you compare the contract date, breach date, and filing date against the 5-year period.

Note: This page is a reference summary for Indiana’s limitations period on oral contract claims. It is not legal advice, and the exact accrual date can change the result.

Limitation period

The applicable limitations period is 5 years in Indiana. Under the jurisdiction data provided, Indiana does not have a separate, claim-type-specific oral contract rule, so the general/default 5-year period applies.

That means a lawsuit based on an oral contract generally must be filed within 5 years of accrual. In practice, the most important question is: when did the breach happen? Once that date is identified, the 5-year countdown is measured from there.

A simple way to think about it:

Event	Why it matters
Oral agreement made	Starts the relationship, but not always the clock
Performance due	Often the point when breach can first occur
Missed payment / refusal / nonperformance	Common accrual trigger
Complaint filed	Must fall within 5 years of accrual

Practical examples

If payment was due on March 1, 2020 and never made, the claim would generally need to be filed by March 1, 2025.
If the agreement was made in 2019 but performance was not due until 2021, the 5-year period usually runs from the 2021 breach-related date, not the date of the conversation.
If the parties kept performing over time, each missed installment or separate breach may create a new limitations issue.

What the calculator should check

DocketMath’s calculator is most useful when you enter:

the agreement date
the breach date or first missed performance date
the filing date
any later performance dates that may affect accrual

The output changes based on the date you choose as the trigger. A complaint filed inside 5 years of the correct accrual date is generally timely; a complaint filed after that period is generally outside the window.

Key exceptions

Indiana’s provided data does not identify a special oral-contract exception rule, so the main issue is accrual, not a shorter or longer contract-specific period. That said, several common timing issues can affect whether the 5-year period has expired.

Here are the most relevant timing considerations:

Issue	Effect on timing
Delayed accrual	The clock may start when breach first occurs, not when the agreement is made
Installment performance	Each missed installment may create its own deadline
Partial performance	Later acts can matter if they show the contract is ongoing
Acknowledgment or restart arguments	A later acknowledgment may affect timing analysis depending on the facts
Fraud or concealment allegations	May change when the claim is treated as discoverable, depending on the cause of action

A few practical checkpoints help avoid bad math:

Write down the first missed obligation. That is often the key date.
Separate one-time promises from recurring duties. They can have different deadline patterns.
Track each breach individually. If the oral contract involved monthly payments, don’t assume one missed installment controls all later ones.
Keep proof of when the other side refused performance. Emails, texts, invoices, and call logs often matter more than recollection.

Warning: If you use the wrong trigger date, you can make a claim look timely when it is not, or miss a deadline that still had time left. The filing date only matters after the correct breach date is identified.

For a reference-page workflow, DocketMath works best when you test multiple dates. Enter the initial promise date first, then compare it with the first breach date and any later nonpayment dates. That gives a more reliable deadline estimate than relying on the date the parties shook hands.

Statute citation

The jurisdiction data cites Indiana Code § 35-41-4-2 and sets the general limitations period at 5 years. Because no claim-type-specific oral-contract rule was found in the provided data, this citation is the one to use for the default period on this page.

For reference:

Statute: Indiana Code § 35-41-4-2
General limitations period: 5 years
Source: https://law.justia.com/codes/indiana/2022/title-35/article-4/chapter-4/section-35-41-4-2/?utm_source=openai

What to capture in a citation check

When you document a deadline, keep these fields together:

Field	Example
Jurisdiction	Indiana
Claim type	Oral contract
Statute	Indiana Code § 35-41-4-2
Period	5 years
Trigger date	First breach / missed performance
Filing deadline	Trigger date + 5 years

This format makes it easier to compare the date calculation against the rule used in the file. It also helps when the claim involves repeated obligations, partial payments, or disputes over when the breach actually occurred.

Quick filing math

If the breach date is known, the deadline is straightforward:

Breach date on June 10, 2021
Add 5 years
Deadline on June 10, 2026

If the breach date is uncertain, the safe approach is to test the earliest plausible breach date and the latest plausible breach date. DocketMath’s statute of limitations tool helps compare those scenarios quickly.

Use the calculator

DocketMath’s statute-of-limitations calculator shows whether the 5-year Indiana deadline is still open based on the dates you enter. It is designed for a fast, date-based check, which is especially useful when the oral contract was never reduced to writing.

Use these inputs:

Agreement date: when the oral deal was made
Performance due date: when the first obligation had to be completed
Breach date: when performance was missed or refused
Filing date: when the case was filed or will be filed
Recurring payment dates: if the contract involved installments or repeated duties

How the output changes

Input change	Result
Earlier breach date	Deadline moves earlier
Later breach date	Deadline moves later
Installment-based obligation	May produce multiple deadlines
Filing date after 5 years	Claim likely outside the period
Filing date within 5 years	Claim likely within the period

Best way to use it

Start with the first date performance was due.
Enter the earliest date the other party failed to perform.
Compare that date to the filing date.
If there were multiple missed payments, test each one.
Save the result with the file notes for later review.

This matters because an oral contract timeline can look simple but still turn on a narrow factual question. A single missed payment, a later refusal to perform, or an ongoing relationship can move the deadline.

Common user mistakes

Using the date of the conversation instead of the date of breach
Treating all missed payments as one event without checking each installment
Forgetting that the clock may begin before a demand letter is sent
Entering the filing date incorrectly by one year or one month

If you want a fast way to test the dates, use the statute of limitations tool before you rely on a deadline in your notes or draft.