Statute of Limitations for Child Support Enforcement / Modification in Arizona

Overview

Arizona law sets time limits for when certain legal actions can be brought or pursued. For child support enforcement or modification activity, the “statute of limitations” concept can apply in some situations—especially when a party is trying to recover or enforce an old obligation or seek changes after a significant delay.

This page focuses on the general/default statute of limitations period Arizona applies under A.R.S. § 13-107(A) (the general criminal statute of limitations). Based on the jurisdiction data provided, no claim-type-specific sub-rule was found—so you should treat the period described below as the default/general period, not a tailored rule for every child support scenario.

For a practical next step, DocketMath’s statute-of-limitations calculator helps you translate dates (like the start date and the current date) into a “how much time is left / how long has passed” view.

Limitation period

General/default period: 2 years

The jurisdiction data provides a General SOL Period: 2 years and points to A.R.S. § 13-107(A) as the general statute.

Key takeaway:

• Default/general SOL period in this material: 2 years
• Default/general statute cited: **A.R.S. § 13-107(A)

Because no claim-type-specific sub-rule was found in the provided data, you should assume this 2-year period is the controlling time limit for the scenario being analyzed by this page—unless you identify a separate, more specific rule that applies to the precise enforcement or modification mechanism you’re dealing with.

How the 2-year window is typically evaluated (date mechanics)

In practical terms, most statute-of-limitations calculations boil down to:

1. Pick the relevant starting date
   Examples that often matter in SOL computations include:

   • the date an obligation accrued,
   • the date an enforcement right could first be pursued, or
   • the date of a triggering event.

2. Use today’s date (or the filing date)
   Many calculators use “today” as the comparison point so you can estimate risk early, then you can refine with the actual filing date.

3. Compute elapsed time

   • If elapsed time is less than or equal to 2 years, the claim may be considered timely under the default period.
   • If elapsed time is more than 2 years, the claim may fall outside the default period.

Practical inputs to gather before using DocketMath

To get the most accurate output from the DocketMath statute-of-limitations calculator, gather:

• Start date (clock start): the date you believe starts the 2-year period under the applicable rule you’re analyzing.
• End date: typically the current date (for planning) or the intended filing/enforcement date.
• Jurisdiction: select Arizona (US-AZ).

You’ll then see the elapsed time and how it compares to the 2-year general/default period used here.

Quick example (illustrative)

If the clock starts on January 15, 2022 and you’re evaluating as of January 16, 2024:

• elapsed time ≈ 2 years + 1 day
• under a strict 2-year default period, that would be outside the window.

Switch the end date to January 15, 2024:

• elapsed time = 2 years
• the result would be at the edge of the default period.

Key exceptions

This section is necessarily constrained by the provided jurisdiction data: it confirms the 2-year general/default SOL period and cites A.R.S. § 13-107(A), but it does not list claim-type-specific exceptions for child support enforcement or modification.

That means you should treat these as possible exception categories to investigate, not a guaranteed list of what applies to your fact pattern:

• Different triggering dates for the “clock start”
  Courts frequently focus on when the relevant right accrued or when enforcement could first occur.

• Tolling concepts
  Some statutes allow the clock to pause or reset based on specific circumstances. The jurisdiction data here does not specify tolling rules for the child support context, so you’d need to confirm applicability to the exact legal posture.

• A more specific statute than the general/default SOL
  Even when a general SOL exists, a specific Arizona statute sometimes controls for particular action types.

If you have documents showing the type of action (enforcement action vs. modification petition, and the procedural stage), you may need to confirm whether a more specific statute governs rather than the general/default period used here.

Statute citation

• A.R.S. § 13-107(A)
  Cited as the general/default statute of limitations period for this jurisdiction data.
  Reference material: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

Again, the dataset provided indicates:

• General SOL Period: 2 years
• No claim-type-specific sub-rule was found in the supplied information, so this 2-year rule is treated as the default/general period for purposes of this calculator workflow.

Use the calculator

Use DocketMath to convert your dates into a clear “time elapsed vs. 2-year default SOL” result.

What to enter in DocketMath (statute-of-limitations calculator)

1. Jurisdiction: Arizona (US-AZ)
2. Start date: the date you believe starts the 2-year clock
3. End date: today (for planning) or the date you plan to file/enforce (for a filing-focused view)

How outputs typically change when inputs change

• If you move the start date forward (more recent triggering event), the elapsed time decreases—raising the chance the claim falls within the 2-year default period.
• If you move the end date forward (later filing/enforcement), elapsed time increases—raising the chance the claim exceeds the 2-year default period.
• If the start date is uncertain, run multiple scenarios using different plausible start dates to see the range of outcomes.

Primary CTA: Use the calculator

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison