Statute of Limitations for Written Contract in Louisiana

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Louisiana’s statute of limitations for an action “on a written contract” is generally 1 year under La. Rev. Stat. Ann. § 9:2800.9. Because your contract-based claim is not limited by a separate, contract-specific sub-rule in the general/default rule set described in the jurisdiction data, this page uses that general rule as the starting point.

When people search for “written contract SOL Louisiana,” they’re usually trying to answer one question: How long do I have to file after the breach or nonpayment? In Louisiana, the answer depends on which statute applies to your claim type. This page focuses on the general/default period associated with § 9:2800.9 as provided in the jurisdiction data.

Note: DocketMath is designed to help you compute time windows from key dates (like breach or demand). It doesn’t replace a case-specific legal analysis, but it can help you avoid missed deadlines caused by date errors.

For a direct calculation, you can start at: /tools/statute-of-limitations

Limitation period

The general limitations period shown for this written-contract rule is 1 year.

Under La. Rev. Stat. Ann. § 9:2800.9, the clock runs for 12 months from the triggering date used by the applicable rule (often the date of breach or the date the claim becomes actionable, depending on the facts).

To use this period practically, you’ll want to identify at least one anchor date:

  • Date of breach (e.g., the day performance was due and not provided)
  • Date of nonpayment (e.g., the invoice due date plus the first day payment wasn’t received)
  • Date notice was given / demand made (useful where the claim’s “actionable” moment is fact-dependent)

Because limitations rules operate on dates—not “when you finally realized”—working backward is usually safer:

  1. Pick the most defensible anchor date in your records.
  2. Add 1 year to determine the outside filing date.
  3. Subtract a buffer for real-world steps (drafting, service, filings).

Here’s a simple timeline illustration for a claim using the general 1-year period:

Anchor date (example)Add 1 yearPractical “file by” takeaway
2026-01-15 (breach)2027-01-15Aim to file well before 2027-01-15
2026-03-01 (nonpayment starts)2027-03-01If you can document this date, it controls the window

What changes the output?

Your DocketMath result typically changes based on:

  • Which date you choose as the trigger (breach vs. nonpayment vs. demand)
  • Whether tolling or exceptions apply (see next section)
  • The date format you enter (to avoid off-by-one or timezone issues when converting documents)

Pitfall: Choosing the wrong anchor date can cut your usable time dramatically. If your records show multiple “possible breach dates,” document why you selected the one used for the SOL calculation.

Key exceptions

No claim-type-specific sub-rule was found for written-contract actions in the provided jurisdiction data, so the general/default 1-year period applies as the baseline. Still, exceptions and tolling concepts can materially change the end date.

Because you’re working from a general rule rather than a claim-specific map, treat the items below as an issue checklist to validate whether any adjustment is even plausible—not as automatic edits to your deadline.

Here are the main categories to look for when validating a SOL window (without taking legal position on your facts):

  • Tolling (pause of the clock)
    Some scenarios can delay when the limitations period starts running or pauses it after it begins.
  • Accrual disputes (when the claim became actionable)
    The outcome may turn on whether the claim is treated as becoming actionable on the first missed payment vs. later steps (like notice, refusal, or a contractually required cure period).
  • Repudiation vs. default
    In some contracts, the “breach” date for limitations purposes can depend on whether the other side repudiated the agreement or simply failed to perform according to a schedule.
  • Fraud or concealment theories
    Certain allegations can, in some contexts, affect when a claim is deemed discoverable or actionable. Those issues can be fact-heavy and document-driven.

A practical way to validate whether an exception might matter:

  • [ ] List the contractual payment/performance schedule (due dates, milestones, cure periods)
  • [ ] Gather proof of the first nonperformance/nonpayment date
  • [ ] Save written communications (emails, letters, notices) that show when the dispute matured
  • [ ] Confirm whether you have a reason to argue the claim was not actionable immediately (e.g., conditions precedent)

Warning: Deadlines are unforgiving. Even if you suspect an exception might apply, don’t wait to “see what happens” near the end of the one-year period—use DocketMath to compute a conservative filing deadline while you evaluate the facts.

Statute citation

The general/default statute of limitations period stated for this written-contract rule is:

This page uses the general/default period of 1 year because the provided jurisdiction data did not identify a separate written-contract-specific sub-rule.

If you’re building a litigation timeline, keep the statute citation tied to your chosen trigger date:

  • Document why your trigger date matches the “accrual/actionable” event you’re relying on.
  • Keep the calculation trail (anchor date → 1-year deadline → draft filing target).

Use the calculator

Use DocketMath to compute your Louisiana 1-year SOL window under the general rule tied to La. Rev. Stat. Ann. § 9:2800.9.

  1. Go to /tools/statute-of-limitations
  2. Enter the trigger date you’re using (commonly one of the following):
    • Breach date
    • First missed payment date
    • Date the contract required performance and it did not occur
  3. Select the jurisdiction: **Louisiana (US-LA)
  4. Review the computed outside filing date (the end of the 1-year period)

Inputs and how outputs change

  • Change the trigger date → the deadline shifts accordingly (because the calculator adds 12 months).
  • Use a different trigger hypothesis (breach vs. nonpayment vs. refusal) → compare outputs side-by-side to see which deadline is earliest. For safety, treat the earliest computed deadline as the conservative benchmark.
  • If you’re considering an exception/tolling theory → you may need to re-run the calculation using adjusted effective dates (for example, a later start date if tolling applies). Since this page does not provide a tolling formula, base adjustments on your documented facts.

If your earliest computed deadline is approaching, prioritize a “move from calculation to action” workflow:

  • [ ] Confirm the date you’ll use as the trigger
  • [ ] Gather supporting contract and payment records
  • [ ] Prepare a filing plan that doesn’t rely on perfect timing

For direct access, start here: /tools/statute-of-limitations

Related reading