Statute of Limitations for Common Law Fraud / Deceit in Arizona

5 min read

Published April 8, 2026 • By DocketMath Team

Overview

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

In Arizona, the statute of limitations (SOL) for common law fraud / deceit is 2 years under the general/default rule provided for this jurisdiction: A.R.S. § 13-107(A).

DocketMath’s statute-of-limitations calculator uses that default 2-year timeframe for common law fraud/deceit in Arizona because a fraud/deceit-specific sub-rule was not found in the jurisdiction data provided. Practically, that means your deadline is generally measured from the legally relevant start/accrual date (often tied to when the claim accrued, which may depend on discovery timing depending on the facts and theory).

Note: This page describes the general/default SOL based on the Arizona jurisdiction data supplied. If your matter involves a different cause of action (for example, a claim labeled as fraud but governed by a distinct statutory scheme), the applicable SOL may differ.

Limitation period

General SOL period: 2 years
Source used for the general/default rule: **A.R.S. § 13-107(A)

Because the brief specifies no claim-type-specific sub-rule was found, the 2-year period is the baseline period DocketMath applies in this calculator flow. If your inputs or scenario raise additional timing concepts (like discovery or tolling), the calculator may provide options—but the core limitation period remains 2 years under the default approach.

What the 2-year SOL means in practice

Most SOL calculations follow this structure:

  1. Pick the accrual/start date (the date the clock starts running for the claim).
  2. Add 2 years to that date.
  3. The result is your deadline, subject to any exceptions/tolling rules the calculator allows based on the facts you enter.

For example, under a simple 2-year add:

  • If the start/accrual date is January 10, 2023, the baseline deadline is January 10, 2025.
  • If the start/accrual date shifts to March 1, 2023, the baseline deadline shifts to March 1, 2025.

Inputs that typically matter for SOL deadlines

In Arizona (US-AZ), the calculator flow you’re using is anchored to:

  • Jurisdiction: Arizona (US-AZ)
  • Default/general SOL: 2 years
  • Start/accrual date: the date you select (this drives most changes in the outcome)

Because the default SOL is fixed at 2 years, the start/accrual date is usually the biggest driver of the output.

Key exceptions

Even with a default 2-year baseline, deadlines can move because of exceptions—including how the law treats when a claim accrues (often tied to discovery concepts) and tolling (pauses or adjustments to the clock).

Because the jurisdiction data provided does not identify a fraud/deceit-specific exception sub-rule, the calculator is best understood as: apply the general baseline, then use any available options it provides that reflect general timing principles (to the extent the tool supports them and your facts match).

1) Accrual/discovery timing

In many fraud-related disputes, the “start” of the limitations period can depend on when the claimant knew (or reasonably should have known) of the relevant wrongdoing and injury.

  • If your facts support a later accrual/discovery date, the SOL deadline may move later.
  • If the law ties accrual to an earlier event (for example, earlier notice or earlier knowledge), the deadline may move earlier.

2) Tolling (pauses in the clock)

Tolling generally refers to situations where the SOL clock may pause for a period due to an external circumstance recognized by law.

Your DocketMath calculation may offer tolling-related choices depending on how the tool is configured. If it does, use them only when your facts plausibly fit the tolling basis.

Practical pitfall: In a 2-year SOL regime, even a timing difference can matter. Double-check that the start/accrual date you input reflects the best-supported accrual theory for your situation.

3) Matching the scenario to the “general/default” rule

Since this is explicitly a default 2-year approach, treat your result as a baseline unless you confirm that your specific claim is governed by the same default framework.

Checklist to keep your inputs aligned:

Practical disclaimer

This page and the calculator are tools to help you model timing. They are not legal advice and can’t replace a careful review of the underlying pleadings, governing law, and factual timeline. If you’re making filing decisions, consider having the computation reviewed for your specific context.

Statute citation

The general/default SOL period used here is 2 years, based on the provided jurisdiction data referencing:

  • A.R.S. § 13-107(A)General SOL Period: 2 years (as stated in the provided Arizona jurisdiction data)

Source context provided: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

Use the calculator

Use DocketMath’s Statute of Limitations calculator here:

  • /tools/statute-of-limitations

Steps to get a usable deadline

  1. Choose jurisdiction: Arizona (US-AZ)
  2. Confirm the calculator uses the default limitation period of 2 years tied to **A.R.S. § 13-107(A)
  3. Enter the start/accrual date
    • This is the key input that starts the 2-year countdown.
  4. Review any optional adjustments
    • If the calculator provides toggles/options for concepts like discovery timing or tolling, apply them only if your facts support those timing adjustments.

How output changes when inputs change

With a default 2-year SOL, the output typically changes as follows:

  • Changing the accrual/start date generally changes the deadline by the same amount of time.
  • The SOL length remains 2 years under the default rule.

Quick example table (2-year baseline):

Assumed accrual/start dateBaseline deadline (2 years)
2023-01-102025-01-10
2023-06-152025-06-15
2024-02-012026-02-01

Because the SOL length is fixed at 2 years in this default approach, getting the accrual/start date right for your fact pattern is usually the most important step.

Related reading