Closing Cost rule lens: Arizona

The rule in plain language

Run this scenario in DocketMath using the Closing Cost calculator.

In Arizona, the general statute of limitations (SOL) for criminal cases is 2 years. The governing provision is A.R.S. § 13-107(A).

Important boundary: this is the general/default SOL period, and it applies unless a different, claim-type-specific rule (or other recognized exception) is identified. In this article, no claim-type-specific sub-rule was found, so the content uses the 2-year default.

In plain terms:

• Start date (baseline concept): the timing typically ties to when the alleged criminal conduct/offense is treated as complete for SOL purposes—not when a case is filed.
• Deadline (baseline): Arizona generally must bring the case within 2 years under A.R.S. § 13-107(A).
• Scope of this lens: this is focused on the general SOL period only, because there is no additional sub-rule being applied here.

For jurisdiction-aware date calculations in DocketMath, this “2-year default SOL” is the core time boundary. It affects two practical questions:

1. What is the SOL deadline when you count forward from your chosen event/trigger date?
2. Does the filing/closing date you enter fall inside or outside that window?

Note (non-legal advice): This discussion uses the general SOL period stated in A.R.S. § 13-107(A) (2 years). If your facts involve a recognized exception, tolling concept, or an offense-specific SOL rule, the outcome could change—DocketMath can’t replace a tailored legal review.

Why it matters for calculations

When you use a closing-cost style “rule lens” together with SOL timing, the practical impact is mostly date math: translating key dates into a measurable “within/over” SOL window.

Here’s how that shows up in a workflow:

Small differences in the rule text can change the output materially. Using the correct jurisdiction and effective date ensures the calculation aligns with the authority that applies to your matter.

1) Your “elapsed time” drives the result

If you provide:

• an event/trigger date (a baseline date you treat as when the alleged offense/conduct is complete for SOL purposes), and
• a filing/closing date (a date you want to test for compliance),

then the calculator can determine whether that filing date lands within the 2-year default boundary.

Even though SOL isn’t a “cost,” the logic behaves like a constraint:

• You’re essentially asking: Is the filing within ~2 years (per A.R.S. § 13-107(A)) of the trigger date?

2) Counting method matters (and calculators make you choose)

Different tools and workflows can apply slightly different conventions, such as:

• whether the tool counts calendar days,
• how it treats the start date and end date (inclusive vs. exclusive),
• how it handles leap years and date transitions.

By using DocketMath, you’re prompted to provide inputs rather than relying on vague assumptions. That makes it easier to see how changing dates can flip the “within/outside” outcome.

3) Treat the 2-year period as a baseline screen—not a guarantee

Because the 2-year rule is the general/default period, it’s best used as a screening baseline and as a way to compare scenarios consistently.

A practical approach:

• Run Scenario 1 using the 2-year general SOL.
• If you later identify a reason an exception might apply, run a Scenario 2 using the adjusted timing logic (but only after you confirm the specific rule that changes the deadline).

Then compare side-by-side: it helps you identify which date assumption causes the biggest swing.

Use the calculator

Use DocketMath’s closing-cost tool and apply the Arizona (US-AZ) ruleset.

• Tool link: /tools/closing-cost
• Tool name: DocketMath
• Jurisdiction code: US-AZ
• SOL baseline used in this lens: 2 years under A.R.S. § 13-107(A) (general/default; no claim-type-specific sub-rule applied)

Inputs to focus on in DocketMath

Use these inputs to generate a jurisdiction-aware “deadline-window” comparison:

Quick scenario: watch the output change

Try two runs with the same trigger/event date, changing only the filing/closing date:

1. Scenario A (within window): Filing/closing date is within 2 years of the trigger date.
2. Scenario B (outside window): Filing/closing date is more than 2 years after the trigger date.

Expected directional result:

• Scenario A should indicate the filing is within the general 2-year SOL window.
• Scenario B should indicate the filing is outside that window.

Pitfall to avoid: If you accidentally plug in the wrong “filing/closing” date (for example, using a service date instead of an actual charging/filing date relevant to your timing assumption), you can flip the outcome. DocketMath helps because it is driven by your entered dates—so double-check which dates you’re using.

Sanity-check checklist (before you rely on results)

Sources and references

Start with the primary authority for Arizona and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

• Average closing costs in Alabama — Rule summary with authoritative citations
• Average closing costs in Alaska — Rule summary with authoritative citations
• Average closing costs in Arkansas — Rule summary with authoritative citations