Why Closing Cost results differ in Utah

5 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

The top 5 reasons results differ

Run this scenario in DocketMath using the Closing Cost calculator.

If you’re seeing different Closing Cost outputs in Utah (US-UT) with DocketMath using the same general case inputs, the mismatch usually comes from jurisdiction-aware rules and input normalization. Utah is relatively straightforward on the basics, but small differences in what’s being counted (or how dates are treated) can change the results.

Below are the five most common causes we see when running closing-cost with Utah rules. (This is not legal advice—think of it as a practical checklist to help you reconcile tool outputs.)

Statute of limitations (SOL) timing assumptions
- Utah’s general SOL period is 4 years under Utah Code § 76-1-302.
- Utah courts also publish guidance reflecting this general/default approach for SOL calculations: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
- No claim-type-specific sub-rule was found in the provided jurisdiction data, so the 4-year general/default period is what DocketMath uses in this diagnostic.
- Outcome impact: if one workflow uses a different start date (for example, incident/act date vs. filing/served date), you can get different results—especially near the 4-year boundary.
Different “start date” for the same SOL calculation Even with a fixed 4-year rule, the anchor date matters. If one set of inputs uses:
- date of incident vs.
- date of discovery vs.
- date filed (or served)
…then Closing Cost results can diverge, sometimes noticeably.
Counting fees that may or may not be included Closing-cost models often depend on whether the run includes (and how it maps) items like:
- recording fees
- service/document costs
- administrative or processing fees
DocketMath’s calculator expects specific input fields. Two runs can produce different totals if the “same” closing-cost concept was entered differently across workflows (for example, one user enters a charge in one category; another leaves it in a different field or omits it).
Currency rounding and formatting differences Outputs can vary when inputs are entered with different precision or rounded at different stages, such as:
- amounts entered with cents vs. rounded to whole dollars
- percent-based line items rounded before summing vs. rounded after summing
Small rounding differences become more visible when there are many line items.
**Jurisdiction code not applied consistently (US-UT) DocketMath can apply jurisdiction-aware logic. If a run is accidentally made under a different jurisdiction code (or a dataset defaults to a non-UT rule set), the Utah-specific 4-year assumption won’t match, and results won’t reconcile.

Tip: Don’t assume two results “match” because both say Utah. If either run used a different jurisdiction code, a different anchor date, or different fee categories, the outputs can legitimately differ.

How to isolate the variable

To pinpoint what changed, treat this like a controlled troubleshooting session in DocketMath.

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.

1) Start with a baseline Utah (US-UT) run

Set Jurisdiction: US-UT
Use the same date fields you believe are correct
Confirm each fee/category is populated the same way in both runs

2) Lock the SOL rule and verify the anchor date

Utah’s general SOL period is 4 years under Utah Code § 76-1-302 (and Utah courts’ legal-help materials align with the general/default approach).
Also remember: no claim-type-specific sub-rule was found in the provided jurisdiction data—so the tool uses the 4-year general/default period.

Then verify:

Which date your two runs treat as the SOL start (the “anchor”)
Whether any upstream data prep shifted the date you thought you entered

3) Compare fee categories line-by-line

Use a “diff” mindset:

Are the same categories included?
Do the category amounts match exactly (including cents)?
Are any categories omitted because a field was left blank?

4) Normalize rounding inputs

If one run pre-rounded values:

Re-enter using the most precise values available (including cents)
Avoid rounding externally before entering into the tool
Let DocketMath compute totals based on the inputs it receives

5) Change one variable at a time

Run again with only one adjustment:

Move the anchor date by 1 day
Change one fee amount by $1.00
Adjust one percent input by 0.1%

This makes it much easier to identify whether the difference is driven by dates (SOL timing), fee inputs (categories/amounts), or rounding/formatting—which is especially important near SOL thresholds.

For the fastest iteration, open and use the calculator output flow from: /tools/closing-cost.

Next steps

Confirm Utah SOL setup
- Ensure the run is using Utah’s general 4-year SOL under Utah Code § 76-1-302.
- Re-check that the tool isn’t effectively using a different rule path due to missing/changed inputs.
- Again, no claim-type-specific sub-rule was found in the provided jurisdiction data—so treat 4 years as the default.
Reconcile date fields
- Create a quick checklist of the exact “SOL start” date used in each run.
- If one run uses “discovery” or “service” instead of the incident/act date, your results may differ for reasons unrelated to fees.
Export/compare the outputs
- Compare totals and the intermediate pieces tied to dates and fee categories.
- If DocketMath exposes line-item categories, match them one-by-one.
Validate with a single-variable test
- Adjust only one variable and ensure the result moves consistently in the expected direction.
- Example: shifting the anchor date closer to the 4-year mark should change outcomes consistently if SOL timing is the driver.