Why Closing Cost results differ in South Dakota

The top 5 reasons results differ

If you’re seeing different Closing Cost outputs in South Dakota (US-SD) when using DocketMath, the differences usually come from inputs and how the calculator applies jurisdiction-aware rules. For South Dakota, the default timeframe backdrop is the 3-year period under SDCL 22-14-1—and importantly, no claim-type-specific sub-rule was found, so the calculator uses this general/default period.

Here are the top 5 reasons results differ:

1. Different recording/settlement timing assumptions

   • Closing cost schedules often depend on when events occur (e.g., settlement date vs. recording date). Even a 1–2 day shift can change which line items fall inside the calculator’s lookback window tied to the 3-year general period in SDCL 22-14-1.

2. Mismatch in property and transaction type inputs

   • DocketMath’s closing-cost calculations can respond to transaction context (e.g., purchase vs. refinance, different payee categories). If one run includes items that another run excludes (or reclassifies), the totals will diverge.

3. Inconsistent lender/party fee mapping

   • Lender-related fees may be entered under different labels across two runs (for example, “lender fee” in one case and a more generic category in another). When the same real-world fee is mapped differently, DocketMath can aggregate it under different buckets.

4. Rounding and fee decomposition

   • Some users enter fees as a single amount; others input fees as multiple components. Depending on how the calculator totals those components, rounding (or subtotaling) can create visible differences.

5. Jurisdiction context not applied uniformly across runs

   • If one run was created under a non–South Dakota context (or if jurisdiction settings were changed), the default period logic can shift. In South Dakota, that baseline logic is the 3-year period under SDCL 22-14-1, which affects whether items are counted within the analysis window.

How to isolate the variable

Treat the discrepancy like a controlled diagnostic. The goal is to change one input at a time until you see exactly where the output changes.

• Step 1: Lock the jurisdiction

  • Confirm you’re running South Dakota (US-SD) in DocketMath.
  • DocketMath’s SD behavior uses the 3-year baseline under SDCL 22-14-1. If jurisdiction settings differ, outputs may change even if the fee amounts look identical.

• Step 2: Use the same set of dates

  • Keep settlement/recording (or any relevant event dates you input) identical between runs.
  • If you’re comparing two versions, change only one date at a time (settlement first, then recording) and re-check the totals.

• Step 3: Normalize fee categories

  • Make sure the same charges are mapped to the same categories across runs.
  • Quick checks:

    • Are lender fees entered as “lender” in both runs?
    • Are third-party fees grouped consistently?
    • Did any line items get reclassified between runs?

• Step 4: Compare totals at each aggregation layer

  • In DocketMath, don’t only compare the final grand total. Compare intermediate subtotals (e.g., lender-related vs. third-party-related).
  • If the difference shows up only in one subgroup, it strongly suggests either fee mapping or rounding/subtotal structure, not the time window.

• Step 5: Perform a “single-fee toggle”

  • Temporarily remove or adjust one fee item while keeping everything else the same.
  • If the result jumps exactly when that item changes, the discrepancy is input-driven. If it changes even when inputs look stable, it may be a jurisdiction-aware timeframe inclusion effect.

If you want to reproduce the issue quickly, start from /tools/closing-cost and re-enter only the fields you suspect changed. Use /tools/closing-cost as your “gold run” reference, then iterate.

Next steps

Use this checklist to turn confusion into a reliable result:

Gentle disclaimer: This is an output-diagnostics guide for how DocketMath inputs can affect results. It’s not legal advice. Real-world outcomes in disputes may depend on additional factual or procedural details beyond what a calculator can model, even with the SDCL 22-14-1 baseline logic.

Related reading

• Average closing costs in Alabama — Rule summary with authoritative citations
• Average closing costs in Alaska — Rule summary with authoritative citations
• Average closing costs in Arizona — Rule summary with authoritative citations