Spreadsheet checks before running Alimony Child Support in South Dakota

5 min read

Published April 15, 2026 • By DocketMath Team

What the checker catches

Before you run an alimony or child support calculation in South Dakota with DocketMath, a “spreadsheet checker” helps you catch issues that commonly derail results—especially when you’re entering inputs across a spreadsheet.

This jurisdiction-aware checklist focuses on South Dakota’s general statute of limitations (SOL) rules. South Dakota uses a general/default SOL period of 3 years, under SDCL 22-14-1. No claim-type-specific sub-rule was identified for this content, so you should treat 3 years as the general period.

Here’s what the checker is designed to flag.

  • Dead-on-arrival worksheet dates

    • Missing date fields (start date, end date, or payment period).
    • Dates entered in mixed formats (for example, 01/04/2025 vs 2025-01-04).
    • End dates that precede start dates.
  • **Out-of-window lookback problems (SOL-aware)

    • If your spreadsheet is being used to estimate back-owed amounts, the checker checks whether your “lookback window” fits the 3-year general SOL period under SDCL 22-14-1.
    • If the worksheet implicitly includes payments older than the general 3-year window, the tool can flag the mismatch so you can adjust inputs (rather than unknowingly inflating totals).
  • Missing or inconsistent payment frequency

    • Weekly vs biweekly vs monthly amounts entered inconsistently.
    • Period totals that don’t match the frequency implied by your date range.
  • Conflicting numeric fields

    • Income or deductions entered as both annual and monthly (double-count risk).
    • Negative values where you intended zeros (for example, -1000 treated as a deduction rather than a “correction” entry).
  • Worksheet logic issues that distort outputs

    • Cells left blank that formulas assume are present.
    • Tax/adjustment fields that are referenced but not updated for the current period.
  • Alimony + child support interaction errors

    • Accidentally routing child-support-related inputs into alimony fields (or vice versa).
    • Reusing a number that represents “income after deductions” in a place where the calculator expects a different category (such as gross or another designated input).

Note (not legal advice): DocketMath’s jurisdiction-aware checks won’t replace legal judgment. They help you reduce spreadsheet errors and keep your worksheet’s time window consistent with the general 3-year SOL described in SDCL 22-14-1. If your goal is anything beyond budgeting, consider getting guidance on how the rules apply to your specific situation.

When to run it

Run the checker before you calculate totals, and again after you update dates or income assumptions. This prevents the common “I fixed the numbers but not the period” problem.

A practical workflow:

  • Step 1 — Create your period timeline

    • Define the period you want to model (start date and end date for calculations).
  • Step 2 — Run the spreadsheet checker

    • Confirm formatting, frequency, and date consistency.
    • Verify that any back-owed lookback window you’re modeling aligns with the 3-year general SOL under SDCL 22-14-1.
  • Step 3 — Adjust inputs based on flags

    • Fix date formats.
    • Repair missing fields.
    • Correct payment frequency.
    • If you intended a lookback of “up to 3 years,” update your worksheet so it actually reflects that period.
  • Step 4 — Run DocketMath’s alimony/child support calculator

    • Then store outputs (and, if helpful, screenshots or exported reports) for your records.
  • Step 5 — Re-run after changes

    • Any time you:
      • update income,
      • switch payment frequency,
      • change the modeling period,
      • or modify the assumed lookback window.

Pitfall to watch: The biggest spreadsheet failure mode isn’t usually the arithmetic—it’s the period. If your worksheet includes payments older than 3 years when you intended a general SOL-limited lookback under SDCL 22-14-1, your totals can look inflated even if every numeric input is correct.

Try the checker

You can test the workflow directly using DocketMath’s tool for South Dakota. Start here:

Before you run it, open your spreadsheet and check the items below—these are the most common “checker” triggers for US-SD.

Quick input checklist (South Dakota / US-SD)

How output changes when the checker finds problems

Below is a practical way to think about what typically changes after you correct issues.

Spreadsheet issueWhat the checker flagsTypical downstream impact on results
Start/end dates reversedDate order and period inconsistencyOutputs may become zero or mis-calculated for the intended months
Mixed date formatsDate parsing/format mismatchPeriod length may change, affecting totals
Lookback window exceeds 3 yearsSOL-aware window mismatch (SDCL 22-14-1)Back-owed totals may reflect more than the general period intended
Frequency mismatchInconsistent payment cadenceTotals multiply incorrectly (for example, weekly treated like monthly)
Annual vs monthly income mixDuplicate or wrong scaleSupport amounts can be materially overstated/understated

If your worksheet passes the checker, proceed to /tools/alimony-child-support and run your calculation.

Related reading