How to run Closing Cost in DocketMath for New Mexico

Step-by-step

This guide walks you through running Closing Cost in DocketMath for New Mexico (US-NM), using jurisdiction-aware rules and the general statute of limitations framework that applies in New Mexico.

1) Open the Closing Cost calculator

1. Go to the DocketMath Closing Cost tool: /tools/closing-cost.
2. Confirm you’re using the correct calculator (Closing Cost). Don’t use the general credit, foreclosure, or lending tools—this walkthrough is specifically for Closing Cost.

2) Set the jurisdiction to New Mexico (US-NM)

In the jurisdiction selector (or jurisdiction field), choose:

• Jurisdiction: US-NM (New Mexico)

DocketMath uses jurisdiction-aware defaults so you don’t have to manually manage every rule. For this workflow, New Mexico’s key timing input uses the general statute of limitations.

3) Understand the timing rule DocketMath is using (default SOL)

For New Mexico, the applicable general statute of limitations period is:

• 2 years under N.M. Stat. Ann. § 31-1-8

Be clear on this important point: our jurisdiction data did not identify a claim-type-specific limitations sub-rule. So, the tool is using the general/default period.

• No claim-type-specific sub-rule was found in the jurisdiction data provided.
• Therefore, DocketMath is using the general/default 2-year SOL under § 31-1-8 for this setup.

If your scenario involves a different claim type with a different limitations period, the tool’s timing-related output may not capture that nuance.

4) Enter the inputs DocketMath needs for “Closing Cost”

In the Closing Cost calculator, you’ll typically provide:

• Cost components (fees, charges, or expenses you want to model)
• Any options related to how you want the amounts treated (for example, costs paid at closing vs. costs net of credits, depending on what the calculator asks)
• Any dates required to evaluate whether timing-related assumptions fall within the SOL window

Practical input guidance:

• If you’re analyzing what was paid at closing, enter those amounts as paid (and do not omit them).
• If you’re analyzing net amounts after credits/offsets, include credits/offsets anywhere the tool expects them, so you don’t overstate net totals.

5) Set dates carefully (when the tool asks)

If the calculator requests one or more dates (for example, a transaction/closing date and/or a “start” or “relevant event” date), enter them consistently and deliberately:

• Use the actual closing date if you’re modeling charges tied to closing.
• Use the correct event/relevant start date if the tool provides a dedicated field for when the “clock starts.”
• When the tool uses SOL logic, remember it’s applying the general 2-year period from N.M. Stat. Ann. § 31-1-8.

If you have both a closing date and an event/start date, avoid swapping them—SOL-based flags can change when the “start” date shifts.

6) Review the outputs and how changes affect them

After you run the calculation, review each output block DocketMath provides—commonly including:

• Total closing cost (sum of included cost lines)
• Net closing cost (if credits/offsets are modeled)
• Timing/eligibility indicators (if SOL logic is used in this calculator)

Quick sanity checks for what typically drives the results:

• Increase any fee line → the total generally rises, and net usually rises too (unless offset by credits).
• Add a credit/offset → net should decrease, while gross/total may remain the same (depending on how the tool separates those concepts).
• Move a date by months/years → timing indicators may flip if they cross the 2-year threshold associated with § 31-1-8.

7) Export or capture the result for your records

If DocketMath offers a way to download, share, or export results, use it to keep your work reproducible. A useful workflow is saving snapshots for different assumptions, such as:

• Scenario A: include all recorded closing charges
• Scenario B: exclude disputed fees or handle credits/offsets differently (as your workflow requires)

This makes it easier to compare how sensitive the outputs are to individual entries—especially dates and credits.

Common pitfalls

New Mexico users often run into the same issues when using the Closing Cost calculator with jurisdiction-aware defaults:

• Using the wrong jurisdiction code

  • Selecting anything other than US-NM can change how timing defaults (including SOL logic) are applied.

• Forgetting the SOL basis is the general/default period

  • The tool is applying a 2-year general statute of limitations under N.M. Stat. Ann. § 31-1-8 because no claim-type-specific sub-rule was found in the jurisdiction data provided.
  • If your situation calls for a different limitations period, the tool’s timing output may not match that nuance.

• Mixing “closing date” and “event date”

  • If the tool asks for both, ensure you enter the correct date into the correct field.
  • Swapping fields can make a scenario look timely or untimely incorrectly.

• Leaving out credits or offsets

  • Closing cost results often hinge on net amounts.
  • If credits exist but you omit them where the tool expects them, you can overstate net closing cost.

• Double-counting costs

  • Some charges may appear as standalone line items and also as part of a bundled component.
  • If you’re importing from a statement, verify each line’s inclusion status in the tool.

• Assuming calculator outputs replace legal analysis

  • DocketMath can help organize calculations and apply structured timing checks, but it doesn’t provide legal advice.
  • Use the results as decision-support for your own review process.

Try it

To validate the workflow quickly, run a mini check using controlled changes.

1. Select US-NM in DocketMath.
2. Enter a baseline set of closing cost line items.
3. Capture:

   • Total and net outputs
   • Any timing/eligibility indicator tied to the 2-year general SOL under N.M. Stat. Ann. § 31-1-8

Then adjust only one variable at a time:

• Change one fee line (watch total/net changes)
• Change one relevant date to move the scenario across the 2-year window (watch timing indicator behavior)
• Add or remove one credit/offset (watch net changes)

Suggested quick scenarios:

• Scenario 1: Base costs + base dates
• Scenario 2: Same costs, later date (e.g., shift by ~6–18 months)
• Scenario 3: Same costs and dates, but add/remove a single credit

When comparing results:

• If net changes but gross/total doesn’t, you’re likely inputting credits correctly.
• If the timing indicator flips near the 2-year mark, that aligns with the tool using the general/default 2-year SOL under § 31-1-8.

Ready to run it now? Use the primary call to action:

• **/tools/closing-cost

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