Statute of Limitations for Consumer Fraud / Deceptive Trade Practices in District of Columbia

5 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

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

In the District of Columbia, the statute of limitations (SOL) for consumer-fraud–type claims is 3 years under D.C. Code § 23–113(a)(1) (the provision’s general/default rule). This page focuses on that default limitations period, because no claim-type-specific sub-rule (e.g., shorter/longer periods depending on the exact theory) was identified in the information reviewed for this reference.

In practice, your deadline is usually driven by two timing questions:

When the claim “accrued” (often tied to the consumer’s knowledge or when they reasonably should have known, depending on the claim’s legal theory)
Whether tolling or an exception concept applies (which can pause or extend the time to sue)

Note: This is a reference workflow and calculator guidance—not legal advice. Always confirm how the rule applies to the specific claim elements and timeline in your situation.

Limitation period

The general SOL period is 3 years, governed by D.C. Code § 23–113(a)(1).

What “3 years” means in real-world deadlines

When you’re turning the SOL into a calendar deadline, you generally use:

Start date (accrual / access-to-knowledge date): the date the law treats the claim as having accrued
End date (SOL expiration): the start date plus 3 years, subject to any tolling/exception arguments

Because the accrual trigger can vary depending on facts (for example, when the consumer discovered— or should have discovered—an alleged deceptive act), the same “3 years” can produce different expiration dates across cases.

How DocketMath helps you calculate the expiration date

Use DocketMath to convert the “3 years” rule into a specific expiration date.

In most workflows, you’ll enter (or select) inputs such as:

Relevant event dates (e.g., purchase date, misrepresentation date, or other conduct)
Accrual date / discovery date (if you track it separately in your process)
Whether you intend to model tolling (if your internal process flags a credible tolling basis)

DocketMath then applies the default 3-year SOL from the start/accrual date you provide for the US-DC jurisdiction setting.

Practical checklist for inputs

Before running DocketMath, gather:

If you don’t yet have a discovery/accrual date, you may need to make a best-supported estimate for early planning. Once you identify a more reliable accrual trigger, rerun the calculator.

Key exceptions

Important baseline: This page is built on the general/default 3-year rule in D.C. Code § 23–113(a)(1). Since no claim-type-specific SOL length change was identified in the underlying review, “exceptions” here are best understood as fact-dependent arguments about:

How accrual is determined (e.g., discovery/access-to-knowledge concepts tied to your legal theory)
Whether tolling applies (equitable or other recognized tolling concepts)

Common exception categories to check (non-exhaustive)

Rather than assuming a different SOL length, evaluate whether the deadline may shift due to:

Accrual/discovery variations: some legal frameworks treat accrual as starting when a consumer knew (or should have known) the deception, rather than the transaction date.
Equitable tolling concepts: if circumstances prevented timely filing despite reasonable diligence, a court may consider tolling-related arguments.
Tolling due to special circumstances: certain events or procedural circumstances can affect timing, depending on the governing doctrine.

Warning: Don’t rely on fairness alone. Tolling and accrual disputes typically turn on what you can document about notice, diligence, and timing.

What to do operationally (two-pass approach)

To keep your process practical and defensible, run two scenarios in DocketMath:

Baseline run: use your best estimate of the accrual/discovery date → apply the default 3-year period.
Exception/tolling run (if warranted): adjust your start/end logic based on a specific, documented theory for why the clock should pause or start later.

Even a modest shift can matter for filing strategy, document preservation, and settlement posture—especially when you are near the end of the SOL window.

Statute citation

Primary SOL (District of Columbia): **D.C. Code § 23–113(a)(1)
General/default SOL period: 3 years
Source used for this reference: https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

Use the calculator

Use DocketMath’s /tools/statute-of-limitations calculator to turn D.C. Code § 23–113(a)(1)’s 3-year rule into an actual expiration date.

Recommended workflow

Step 1: Open /tools/statute-of-limitations
Step 2: Enter the accrual/discovery date you plan to treat as the SOL “start”
Step 3: Confirm the tool is applying the default 3-year SOL for US-DC
Step 4: Review the computed SOL expiration date
Step 5: If you have a basis to argue a different accrual trigger or tolling, run a second scenario and compare the outcomes

How outputs change with different inputs

Common input changes you can model to see how the deadline moves:

Scenario input change	Typical impact on SOL expiration
Later accrual/discovery date	Expiration moves later by the date difference
Earlier accrual/discovery date	Expiration moves earlier
Switching date basis (event date vs. discovery/accrual date)	Can materially shift the deadline, especially when deception was discovered later
Tolling/extension modeled (only if you have a specific basis)	Expiration may move later, depending on your modeled logic

If you’re building a conservative filing calendar, treat the earliest credible accrual/discovery date as the safer assumption until you can support a later discovery trigger.

Primary CTA: /tools/statute-of-limitations