Why Alimony Child Support results differ in West Virginia
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 using DocketMath’s Alimony Child Support calculator for West Virginia (US-WV) and your results don’t match someone else’s, it’s usually because the two runs used different inputs, different timing assumptions, or different interpretations of how the calculator should treat those inputs. West Virginia’s jurisdiction-aware logic also incorporates timing concepts, including a general default statute of limitations that may affect how differences show up when people compare “what’s owed.”
Below are the top 5 reasons alimony/child support results can differ for US-WV users.
**Different income numbers (and how they’re entered)
- Net vs. gross pay (and whether the calculator fields are aligned)
- Overtime/bonus patterns (treated as steady vs. occasional)
- Commissions, second jobs, or variable income
Because support calculations are often proportional, even a small change in income assumptions can cause a noticeable output difference.
Parenting time and expense allocation aren’t the same
- A different assumed custody/parenting schedule (for example, a different number of overnights)
- Different assumptions about how costs are allocated in the model
In practice, if two people input different parenting-time assumptions, the monthly support output can shift even when both incomes look identical.
Alimony duration assumptions differ
- One person may assume alimony runs only for a fixed number of years
- Another may assume a longer end date or a different term used in the tool
Even when the monthly alimony figure looks similar, changing the term/end-date inputs can change totals and overall obligation outputs.
Existing obligations/deductions are entered differently
- Prior dependents (other children)
- Other court-ordered obligations that reduce “available income” in the calculator workflow
- Different treatment of what’s entered as a deduction vs. what’s treated as income
Two users can enter the same earnings but still get different results if their “other obligations” inputs don’t match.
**Timing and enforcement windows (statute-of-limitations mismatch)
- Sometimes people compare amounts as if every alleged arrearage is equally recoverable without considering time limits.
- For West Virginia, the general/default statute of limitations is 1 year, referenced in W. Va. Code § 61-11-9.
- Default/General clarity: the 1-year period is the general baseline; no claim-type-specific sub-rule was found in the provided jurisdiction data, so a different period could apply if a specific claim type has its own rule.
Note: DocketMath helps you model outcomes based on the inputs you enter. It’s not a substitute for reviewing the underlying order, pleadings, or the specific claim type with a qualified professional.
If you want to reproduce the workflow yourself, start at: /tools/alimony-child-support.
How to isolate the variable
The fastest way to figure out why results differ is to use a controlled test in DocketMath: keep everything the same except one input category.
Use this workflow:
Record both output sets
- Copy the key outputs (monthly alimony, monthly child support, and any total estimates shown).
- Write down the exact inputs from each run—especially income fields, parenting-time settings, and alimony term/date inputs.
Run a “single-change” test Change only one category at a time, then re-run:
- income (either parent)
- parenting time / schedule inputs
- alimony term or end-date inputs
- extraordinary expenses (if entered)
- other obligations/deductions
After each change, note whether the output shifts slightly or dramatically—and whether it moves higher or lower.
Keep a change log For each run, record:
- which field changed
- how much outputs changed
- direction of change (increase/decrease)
Check timing assumptions last Timing questions often explain why two people feel like the same “formula” should yield the same amount, but it doesn’t.
- West Virginia’s general default baseline referenced in W. Va. Code § 61-11-9 is 1 year when no claim-type-specific rule overrides the general period.
Reminder: Don’t compare outputs without confirming both runs used the same definitions (for example, whether income inputs are “monthly gross” vs. “monthly net after deductions”) and the same parenting schedule structure.
Next steps
Once you identify the mismatched input, you can move from “why are these different?” to “which one is correct for our facts?”:
Re-run DocketMath with harmonized definitions
- Use the same time window for income (for example, consistent monthly averaging).
- Enter parenting time using the same schedule format.
- Align alimony duration/term assumptions so the comparison is apples-to-apples.
Validate against the underlying order/record
- If you’re modeling an existing order, make sure the inputs reflect the actual terms (not a remembered summary).
- For timing or arrearage-related comparisons, remember the West Virginia general baseline is 1 year under W. Va. Code § 61-11-9 (with the caveat that a claim-type-specific rule—if one exists—could override the general period).
Create a “two-screenshot” comparison
- Screenshot your inputs and outputs.
- Screenshot the other run you’re comparing against.
- Then focus only on the changed fields—this is typically much faster than debating the entire result.