Why Alimony Child Support results differ in Michigan
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Alimony Child Support calculator.
If you’re comparing “alimony + child support” numbers from different Michigan runs of the DocketMath calculator, the mismatch usually isn’t the math—it’s the jurisdiction-aware inputs and how Michigan law is applied. Below are the top 5 reasons results differ in Michigan (US-MI).
Note: This is an educational walkthrough of common drivers of different calculator outputs. It’s not legal advice.
**Different time windows (start/end dates)
- DocketMath’s alimony-child-support output depends heavily on what months are included. Even a 1–2 month shift in dates can change totals materially.
- Michigan-related time assumptions also affect when support begins and ends in the calculation logic you select.
Income characterization and each line item’s treatment
- Two people can report the same “annual income” but with different components (e.g., overtime vs. regular pay; bonuses; business income).
- DocketMath’s jurisdiction-aware rules use the values you enter, so changing which income fields are populated changes the result—even if the headline number looks similar.
Child support variables tied to custody/parenting time
- Parenting time inputs (overnights/days) can shift the effective allocation that drives the child support calculation.
- If one run assumes different custody or time-sharing than another, child support will diverge quickly.
**Alimony input structure (type, duration assumptions, and whether alimony is included in the combined scenario)
- DocketMath can produce different “combined outcomes” depending on which scenario configuration you select (e.g., including or excluding alimony, or changing duration assumptions).
- Key point: two calculators can look comparable while actually running different scenario structures.
Michigan judgment timing vs. what you entered for enforcement period
- People often test with a “today-based” period in one run and a “judgment-based” period in another.
- That produces different totals and arrears projections, even with identical incomes.
A statute-driven reason you can verify (time horizon)
Michigan’s general default statute of limitations (SOL) is 6 years under MCL § 767.24(1). If you model recovery/enforcement windows, using different windows creates different totals.
Also, per your jurisdiction data: no claim-type-specific sub-rule was found, so this 6-year period is the general/default period (not claim-category-specific).
How to isolate the variable
Use a “single-change” diagnostic method with DocketMath so you can identify what moved the number.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
Step-by-step isolation checklist
- Run A: baseline
- Run B: change parenting time only
- Run C: change income line item only
- Run D: change alimony duration only
- Run E: change dates only
Quick comparison table (fill in your runs)
| Run | Dates used | Income entered | Parenting time inputs | Alimony settings | Result delta vs. baseline |
|---|---|---|---|---|---|
| A (baseline) | 0 | ||||
| B | (same) | (same) | changed | (same) | |
| C | (same) | changed | (same) | (same) | |
| D | (same) | (same) | (same) | changed | |
| E | changed | (same) | (same) | (same) |
If the delta shows up only when you adjust one specific input category, you’ve isolated the driver.
Why SOL matters to comparisons
If one run assumes a shorter enforcement/recovery horizon and another run uses the 6-year general default SOL, the totals will not match. Michigan’s general SOL period is 6 years under MCL § 767.24(1) (per your provided jurisdiction data sourced from the Michigan government).
Because there was no claim-type-specific sub-rule found in your jurisdiction data, treat this as the default time horizon when you’re comparing outputs.
Next steps
Open DocketMath and run a baseline scenario
Use: /tools/alimony-child-support
Choose the same date range and scenario configuration you’re trying to replicate.Re-check the “top 5” categories
Confirm: (a) dates, (b) income structure, (c) parenting time, (d) alimony scenario settings, (e) enforcement/recovery window.Align your time horizon with the general SOL (if you’re modeling it)
If your analysis depends on how long amounts can be pursued, model the horizon using Michigan’s 6-year general default SOL under MCL § 767.24(1).
And remember: your jurisdiction data indicates no claim-type-specific sub-rule found, so this is the default period.Rerun using locked inputs and the single-change method
Start from your baseline run and apply one change at a time until you reproduce the difference.
Warning: Even when two sets of numbers both “look Michigan,” different modeling choices—especially dates, parenting time, and alimony scenario structure—can produce materially different outputs. Don’t assume the difference is an error; it’s often a different assumption set.
For an audit trail, save the runs (screenshots or exported summaries) and label them by which single input you changed.