Why Closing Cost results differ in New Mexico
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
If you’re getting different Closing Cost results in New Mexico (US‑NM) using DocketMath (calculator: closing-cost), the cause is usually not math—it’s inputs or how timing is treated under the jurisdiction-aware rules.
Below are the most common drivers we see for New Mexico discrepancies.
Different “start dates” (and New Mexico’s 2-year general rule)
New Mexico’s general statute of limitations is 2 years under N.M. Stat. Ann. § 31-1-8. DocketMath can only compute closing-cost-related outcomes accurately if your dataset lines up on the intended event date (for example: contract execution vs. settlement vs. claim accrual).Pitfall: Two people can both say they’re using the “same” case, but one uses the signing date and the other uses the filing date—your outputs can diverge even if all monetary amounts match.
Jurisdiction-aware default timing applied to mismatched records
Important context: no claim-type-specific sub-rule was found. That means the 2-year general/default period is the basis referenced for New Mexico in DocketMath’s jurisdiction-aware logic (per N.M. Stat. Ann. § 31-1-8), rather than a different, shorter/longer claim-specific period.Inconsistent loan-cost components
Closing costs can be represented across multiple fields, and datasets sometimes differ on whether they’re recorded gross vs. net. If one dataset includes (or nets) items differently, totals will shift.Common examples:
- origination/processing fees
- escrow charges
- prepaid interest
- title/recording
- lender credits or seller credits
Amounts recorded in different units or bases
Even when the “numbers” look right, they may be on different bases:- percentages vs. dollars
- “estimated” vs. “final” settlement statement figures
- rounding differences (for example, converting 0.25% into dollars)
- taxes/fees attributed to different line items
Credits and concessions applied in opposite directions
A sign convention mismatch is a frequent culprit. For instance, a seller credit might be entered as a positive number in one run and as a subtraction in another. That single “+ vs. -” choice can materially change results.
How to isolate the variable
You can usually pinpoint the mismatch in 10–20 minutes by running controlled scenarios in DocketMath (changing one input 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 isolate workflow
Lock the jurisdiction
Confirm the tool is set to New Mexico (US‑NM) so the jurisdiction-aware baseline uses N.M. Stat. Ann. § 31-1-8 (2 years).Run multiple scenarios, changing only one variable per run
Keep all monetary inputs identical, then change only one of these at a time:- Scenario A: your current/original dataset
- Scenario B: update only the start date
- Scenario C: update only the fees/credits line items
- Scenario D: update only the loan amount / rate / percentage-to-dollar conversion
Compare sensitivity to timing
If updating the date changes results significantly while amounts are fixed, the issue is likely event-date alignment, not fee math.Compare sensitivity to credit/netting direction
If switching only how credits are represented (gross vs. net; sign direction) changes results, the issue is likely credit handling rather than jurisdiction timing.
A simple comparison table
| Variable changed | Kept constant | What you learn if results change |
|---|---|---|
| Start date | All fees/credits | Timing alignment vs. date selection |
| Fee categories | All dates | Missing or duplicated fee lines |
| Credit sign | All dates | Netting direction / sign convention |
| Unit basis (% vs $) | All else | Conversion or rounding mismatch |
| Rounding level | All else | Presentation vs. calculation mismatch |
Next steps
Once you identify the variable driving the spread, you can make results reproducible:
- Standardize date sourcing: choose one reference document (e.g., a specific settlement statement date or contract date) and use it consistently as the start date.
- Create a fee mapping rule: define which line items your workflow treats as “closing costs,” then apply the same mapping every time.
- Normalize credits: decide a single sign convention (e.g., credits entered as negative reductions) and document it for your team.
- Confirm the SOL assumption: for New Mexico, DocketMath’s jurisdiction-aware logic should rely on the general 2-year default in N.M. Stat. Ann. § 31-1-8 when no claim-type-specific sub-rule is applied.
If you want to reproduce the calculation with your inputs, use DocketMath here: /tools/closing-cost.
Note: This is a diagnostic workflow, not legal advice. If the timing or claim characterization is disputed or deadline-sensitive, consult your case team for legal strategy.
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
