Spreadsheet checks before running Alimony Child Support in Idaho

What the checker catches

Run this scenario in DocketMath using the Alimony Child Support calculator.

Running an alimony or child support calculation without verifying the “plumbing” can lead to avoidable errors—especially in Idaho, where the timing of actions and the lookback/retro period you model can hinge on a short limitation period. DocketMath’s alimony-child-support checker helps you catch spreadsheet issues before you run numbers.

Here are the most common problems the checker is designed to surface for Idaho (US-ID) workflows, with attention to limitations timing under Idaho Code § 19-403.

1) Date-driven eligibility mistakes (the #1 spreadsheet failure point)

Support calculations often depend on correct dates (for example: filing date, service date, and the start/end of the period you’re calculating). If those cells are off by even one day—or placed in the wrong “role” (start vs. end vs. filing date)—downstream totals can still look plausible while being wrong.

The checker prompts you to verify that the dates you’re using match the period logic in your spreadsheet.

In Idaho, the general/default statute of limitations period is 2 years under Idaho Code § 19-403. If your worksheet uses a limitations-based approach for retroactive periods, offsets, or review of accrued amounts, this baseline matters.

2) Off-by-one month errors when converting dates

Many spreadsheets convert dates to month buckets (e.g., using DATEDIF, end-of-month logic, or custom rounding). That can create subtle mismatches:

• A period that starts on the 15th may be counted as a full month.
• A period ending on the 1st may disappear if the range is treated as “end-exclusive.”

The checker helps you validate the period boundaries you’ve defined so the spreadsheet’s month conversion doesn’t quietly drift from your intended start/end.

3) Income fields that are present but not normalized

Alimony/child support inputs commonly come from paystubs, tax returns, or prior-year averages. Spreadsheet pitfalls include:

• Mixing gross vs. net income across different rows
• Leaving “annual” income labeled as “monthly” (or vice versa)
• Importing values as text (e.g., "3500" instead of 3500)

These issues often lead to outputs that don’t match your expectations, even when there’s no obvious error message.

The checker looks for patterns like:

• Inconsistent frequency (weekly + annual blended)
• Values that won’t sum cleanly
• Basic numeric validation failures (including text-to-number mismatches)

4) Unit mismatches in assumptions

A typical worksheet includes toggles like:

• health insurance included/excluded
• childcare included/excluded
• tax-related assumptions

Even if the final output changes only slightly in a single month, a unit mismatch can compound over a longer modeled window. The checker helps you confirm that the assumptions being applied match what you intended.

5) Spreadsheet range drift (rows move; formulas don’t)

If you copy a template and later insert or delete rows, formulas can end up pointing at the wrong cells while still calculating without errors.

The checker checks that:

• the expected input ranges are actually feeding the calculation block, and
• the period section is aligned with the output section.

When to run it

Run the checker before you run the full calculator, and rerun it whenever any date, income, or period input changes.

A practical Idaho-focused workflow looks like this:

1. Finalize key dates first

   • Choose the period start and period end you intend to evaluate.
   • If your sheet uses a limitations-based lookback, anchor it to the general 2-year baseline under Idaho Code § 19-403 (and remember: the guidance provided is general/default, not claim-type-specific).

2. Enter income in a consistent frequency

   • Decide whether you’re entering monthly or annual figures and keep it consistent across sources and rows.

3. Update assumptions last

   • Only after dates and income are locked should you adjust items like insurance, childcare, or other add-ons.

4. Run the checker, then run the calculator

   • Treat DocketMath’s checker as a “preflight” step.

5. Repeat after corrections

   • If you change one date cell (even slightly), rerun the checker. Small changes are exactly where off-by-one logic and range drift show up.

Quick checklist (Idaho workflow)

Gentle reminder: This is a spreadsheet QA step, not legal advice. If you’re unsure whether a different limitations rule applies to your specific situation, consider verifying it with a qualified professional.

Try the checker

If you want a fast way to validate your spreadsheet setup before running outputs, start here: /tools/alimony-child-support.

In DocketMath:

• Enter or upload your inputs exactly as your spreadsheet would use them
• Run the checker first
• If it reports date-range or normalization issues, correct those inputs, then re-run
• Only after the checker looks clean should you run the full calculator

How outputs tend to change when the checker finds issues

When errors are corrected, you’ll usually see one or more of these shifts:

• Total period amount changes (from corrected date boundaries)
• Monthly vs. annual totals realign (from unit/normalization fixes)
• Retro/accumulation periods compress (from applying limitations logic using the correct Idaho 2-year general baseline under Idaho Code § 19-403)
• Component totals move (from insurance/childcare assumption toggles or numeric casting fixes)

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado