Statute of Limitations for Child Support Enforcement / Modification in Illinois

5 min read

Published March 22, 2026 • Updated April 8, 2026 • By DocketMath Team

Overview

Illinois generally uses a 5-year statute of limitations framework for enforcing or seeking modification of certain child support obligations, using the general/default period under 720 ILCS 5/3-6.

Because your goal may be either (1) enforcement (collecting past-due amounts) or (2) modification (changing a future obligation), the deadlines can feel confusing. This page focuses on the general statutory time limit Illinois applies under its default rule and explains how to estimate timing using DocketMath’s statute-of-limitations calculator.

Note: This page describes the general/default period found in 720 ILCS 5/3-6. The jurisdiction data you provided indicates no claim-type-specific sub-rule was identified for a shorter/longer period in Illinois beyond this general framework.

(General information only—not legal advice.)

Limitation period

Illinois’ general SOL period for many actions is 5 years, using 720 ILCS 5/3-6 as the default time limit.

What the “5 years” typically means in practice

For statute-of-limitations questions in family-law enforcement contexts, the practical timing question is usually:

  • When did the underlying obligation become due?
  • When did you file the action (or take the relevant enforcement/relief step)?

DocketMath’s calculator is designed to help you compare a trigger/due date against a filing/action date.

A quick timeline example (how the math works)

Assume:

  • A child support amount became due on January 15, 2020
  • You filed an enforcement/relief request on January 10, 2025

Under a 5-year rule, January 10, 2025 is within the 5-year window from January 15, 2020.

Swap the filing date to January 16, 2025, and it moves beyond the 5-year mark by one day—so the result can flip depending on the exact dates.

A checklist to set up your dates

Before running DocketMath, gather:

  • The date the support amount became due (or the date you want to treat as the “trigger”)
  • The date you filed the enforcement or modification request
  • Whether you’re working with a single missed month or a range of months

If you have multiple missed months, you’ll often get the best clarity by running several calculations—one per due date—rather than trying to force everything into one estimate.

Key exceptions

Illinois’ general/default SOL period is 5 years, but timing outcomes can change depending on facts that affect what date counts (and whether any timing-related doctrines apply).

Because your jurisdiction note indicates no claim-type-specific sub-rule was found, the “exception” planning focus here is usually not a different SOL length—it’s the dates being compared to the same 5-year baseline.

Common timing pitfalls to check

Even when the baseline is still 5 years, these issues can shift results:

  • Due vs. assessed date: Support is often calculated monthly, but the exact “became due” date for a specific unpaid amount matters.
  • Multiple unpaid installments: Each missed installment can have its own due date, so the 5-year analysis may need to be evaluated separately for different months.
  • Effective timing of steps: Some matters don’t move instantly—what counts as the relevant “filing/action” date can affect whether you’re inside or outside the window.

Warning: Using an incorrect due/trigger date (for example, using a rough month date instead of the actual due date) can move the deadline result by months or flip the outcome.

What to do if you’re unsure about the due dates

If you don’t have a clean list of due dates:

  1. Start with the earliest missed amount date you can document.
  2. Run the calculator.
  3. Add later missed months and re-run until you see where results begin to move from “likely within” to “likely outside.”

This “boundary mapping” approach is often more reliable than guessing a single deadline for everything.

Statute citation

The general/default statute of limitations framework referenced here is:

For deadline calculations, you can treat 720 ILCS 5/3-6 as the default “time limit” unless you have a specific reason to believe a different rule applies. Per your jurisdiction note, no claim-type-specific sub-rule was identified beyond this general framework—so this page stays within the general approach.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to estimate whether a given due/trigger date and filing/action date fall within Illinois’ general 5-year framework.

Primary CTA: /tools/statute-of-limitations
Direct link: **/tools/statute-of-limitations

Inputs that matter

In DocketMath’s tool, you’ll generally work with:

  • Jurisdiction: Illinois (US-IL)
  • Statute length: choose the 5-year default aligned with 720 ILCS 5/3-6
  • Trigger / due date: the date the support amount became due (or the date you’re using as the key start point)
  • Filing date: the date you filed the enforcement or modification request

How outputs change when inputs change

With a 5-year baseline, a common rule-of-thumb is:

  • If the filing date is before the 5-year anniversary of the due/trigger date, the claim is likely within the window (under this general framework).
  • If the filing date is after that anniversary, it’s likely outside the window under the general SOL rule.

To handle multiple missed months:

  • run one calculation per missed month (most precise), or
  • run enough consecutive months to identify the approximate expiration boundary.

Step-by-step workflow

  1. Choose the earliest missed payment due date you want to evaluate.
  2. Enter that due date and your filing date in DocketMath.
  3. Review whether it falls inside vs. outside the 5-year period.
  4. Repeat for later due dates until you see results flip.

This creates a practical map of which missed amounts may fall within the SOL window under the general/default framework.

(If you have unusual procedural facts or mixed dates, consider using the calculator multiple ways—e.g., testing nearby due dates—to see how sensitive the result is.)

Related reading