Why Closing Cost results differ in Kansas

The top 5 reasons results differ

If your DocketMath Closing Cost results don’t match another estimate in Kansas (US-KS), the difference usually comes from inputs or timing assumptions that the calculator has to operationalize. Kansas applies a general/default statute of limitations (SOL) period of 0.5 years (6 months) under K.S.A. § 21-6701. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found, so the guidance below treats this general period as the default.

Here are the top 5 reasons results differ in Kansas:

1. Different “lookback” window caused by the SOL start date

   • DocketMath must anchor the SOL window to a particular start date. If one workflow uses a filing date while another uses an event/transaction date, the 0.5-year (6-month) window shifts—changing which closing-cost items fall inside the counted period.

2. Different treatment of “closing cost” components

   • Closing costs are rarely a single line item. They can include lender fees, escrow/title charges, and prepaid items. Even if both runs are “Kansas,” a mismatch in which categories are included (or excluded) can change the total significantly.

3. **Different assumptions for cost timing (paid vs. incurred)

   • Two estimates can use the same fee amounts but disagree on whether a fee should be evaluated using the paid date or the incurred date. With Kansas’s short 6-month SOL under K.S.A. § 21-6701, that boundary decision can flip whether costs are counted.

4. Different jurisdiction settings or US-KS selection

   • DocketMath is jurisdiction-aware. If the calculation isn’t truly running under US-KS, the SOL window logic and date handling may differ, leading to a different included-cost set.

5. **Different normalization of dates (date-only vs. exact timestamps)

   • If one system records exact timestamps and another records only dates, the “within 0.5 years” determination can behave differently around the cutoff. Those small differences matter more in a 0.5-year framework.

Practical warning: Because Kansas’s default SOL is 0.5 years (6 months) under K.S.A. § 21-6701, small interpretation differences about dates (even without changing dollar amounts) can materially change which costs are included.

How to isolate the variable

Use this checklist to identify the single input (or timing rule) that explains the mismatch. The fastest method is “change one thing at a time.”

• 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 workflow (practical)

• Make sure both runs use Kansas (US-KS).

  • Decide which date field is treated as the SOL “start” (for example: transaction date vs. demand date vs. filing date), and make sure both runs use the same convention.
  • Kansas default SOL period: 0.5 years (6 months) under K.S.A. § 21-6701 (and no claim-type-specific sub-rule was identified in the provided jurisdiction data).
  • Compare the included categories line-by-line so you’re not comparing different fee sets.
  • Ensure both estimates use the same timing field when determining whether costs fall within the 0.5-year window.

Quick comparison table (fill in from both runs)

If you want the quickest path: run a second DocketMath calculation and change only one variable at a time—typically start with date fields, since Kansas’s short 0.5-year SOL is sensitive to boundary interpretations.

Next steps

Once you isolate the driver of the difference, capture it so your future runs stay consistent.

1. Document the date convention

   • Write down the exact date field used as the SOL anchor (because the default is 6 months under K.S.A. § 21-6701).

2. Create a fixed “closing cost component policy”

   • Maintain a consistent inclusion/exclusion list for what counts as “closing cost” in your inputs.

3. Re-run DocketMath with locked inputs

   • Keep the same US-KS selection, the same SOL anchor date convention, and the same paid/incurred approach. If results still differ, focus on how each run treats the cutoff boundary around the 0.5-year mark.

4. Use the tool directly

   • Primary CTA: /tools/closing-cost

Gentle note: This is guidance to help you reconcile calculator inputs and outputs; it isn’t legal advice.

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