How to run Closing Cost in DocketMath for New Mexico

Step-by-step

Here’s a practical walkthrough for running a Closing Cost calculation in DocketMath for New Mexico (US-NM) using jurisdiction-aware rules. This guide focuses on how to set up the run inside DocketMath and how to interpret the output for New Mexico.

1) Start the right calculator and confirm the jurisdiction

1. Open DocketMath → Closing Cost.
2. Use the primary call-to-action: /tools/closing-cost.
3. Select/confirm the jurisdiction as New Mexico (US-NM).

DocketMath uses the jurisdiction code so it can apply the correct set of assumptions. For New Mexico, one high-impact rule to remember is that New Mexico has no state real estate transfer tax. Instead, the recording-related costs are handled under New Mexico’s recording fee framework.

2) Enter the core financial inputs

Most closing-cost calculators work from a few key underwriting-style inputs. In DocketMath, provide the values that match your transaction:

• Purchase price / loan amount (depending on how your closing-cost model is structured)
• Down payment (if the calculator uses loan-to-value logic)
• Property type / occupancy (if the tool asks)
• Loan type / term (commonly affects lender-side items)
• Estimated interest rate and/or points (if the tool includes them)

If you’re unsure whether DocketMath expects purchase price or loan amount for a specific fee field, align your entries with how your lender’s Loan Estimate (LE) breaks out charges. The goal is to mirror the same categories the calculator is designed to estimate.

3) Populate fee categories that are transaction-specific

In most closing-cost models, you’ll see categories like:

• Title & escrow fees
• Lender fees (processing, underwriting, doc prep)
• Recording-related items
• Prepaids (taxes/insurance/escrow-related)
• Owner’s policy / lender’s policy (if included)

Because DocketMath is jurisdiction-aware, the New Mexico run should apply recording-related mechanics consistent with New Mexico’s approach. The key New Mexico-specific point is:

• No state real estate transfer tax is imposed.
• Instead, the relevant “recording cost” concept is connected to recording statutes and fees—commonly referenced here as recording fees under NMSA § 14-8-15.

4) Apply the “no real estate transfer tax” baseline

When you run the calculation for New Mexico, make sure your fee selections and scenario do not effectively create a transfer tax line item.

DocketMath’s output should reflect that New Mexico has no real estate transfer tax. For reference, New Mexico’s recording framework and the recording-fee concept under NMSA § 14-8-15 are part of the property recording context. Source for the statutory navigation: https://nmonesource.com/nmos/nmsa/en/nav.do

If you enter inputs or select options in a way that assumes a transfer tax exists (for example, by choosing a “transfer tax” style line item), the result can become overstated versus New Mexico practice.

5) Check the amortization/points logic (if the tool asks)

Some closing-cost calculators incorporate lender points (or similar percentage-based lender costs) either directly or through percentage-based fee assumptions. If DocketMath includes points:

• Enter points as a percentage (e.g., 1.0%) if that’s how the UI is designed.
• If you enter a dollar amount, confirm whether the tool converts it or expects it in a specific format.

A mismatch here can change the “lender charges” portion significantly even if other fees remain the same.

6) Review the breakdown table and totals

After inputs, DocketMath typically provides:

• Category subtotals
• Total estimated closing costs
• Sometimes, buyer-paid vs. seller-paid splits

Use the breakdown to see what changed when you adjust assumptions. For example, changing the purchase price (e.g., $250,000 → $275,000) can cause scaling in items that are tied to purchase price or value-based fee bases. Conversely, items tied to loan amount should scale differently if down payment changes.

7) Run multiple scenarios (fast comparisons)

To understand sensitivity (and catch issues early), run at least two “what-if” scenarios:

• Scenario A: Baseline purchase price and rate/points
• Scenario B: Change down payment and/or points
• Scenario C: If available, change owner’s policy option or title/escrow selections

This helps you identify which categories are most sensitive to your inputs—especially important in New Mexico, where the absence of a state transfer tax can make certain categories comparatively more noticeable.

Common pitfalls

New Mexico closing cost calculations can go wrong in predictable ways—mostly due to importing assumptions from other states.

• Including a real estate transfer tax line item
  New Mexico does not have a state real estate transfer tax. In a New Mexico run, your calculation should not assume a transfer tax percentage. Recording fees are the relevant recording cost concept, tied to NMSA § 14-8-15 (recording fee framework).
  Reference (statutory navigation): https://nmonesource.com/nmos/nmsa/en/nav.do

• Overstating recording costs by double-counting
  If your input selections include both:

  • a “recording fee” category, and
  • a broader “title/closing” category that already includes recording,
    you might accidentally double-count. Use the breakdown table to check whether recording appears in more than one line.

• Misinterpreting “default period” settings
  If DocketMath includes a time-related assumption (for example, default coverage period settings for prepaids, taxes, or escrow), understand that the tool may use a general/default period when it cannot detect a claim-type-specific sub-rule.
  In this guide, no claim-type-specific sub-rule was found, so the tool behavior should be treated as general/default period logic for New Mexico unless the UI provides a more specific selector.

• Using loan amount where purchase price is required (or vice versa)
  Percentage fees (such as points or other lender % charges) often attach to the loan amount, while other items attach to purchase price or property value. Confirm how DocketMath defines each field and what base each percentage uses.

• Assuming statutory tax behavior that doesn’t exist in New Mexico
  Some users expect a state-level transfer tax similar to other jurisdictions. That expectation conflicts with New Mexico’s structure (recording fees rather than state transfer tax).

  Warning: A “looks reasonable” total can still be wrong if the model silently includes a transfer tax assumption that New Mexico doesn’t impose. Always sanity-check the category breakdown for a tax line that should not be present.

Try it

You can run the New Mexico closing-cost estimate directly in DocketMath here: /tools/closing-cost.

To get the most accurate estimate during your first run, use this quick checklist:

A quick “sanity test” for New Mexico

After you run, scan the totals:

• If your breakdown includes a state transfer tax percentage or a transfer-tax-specific category, review your inputs and selections—New Mexico does not impose that tax.
• If recording costs seem unusually high, check for double-counting (recording in more than one category).

Then rerun with one change at a time (for example, adjust points from 0.0% to 1.0%) and confirm the output changes proportionally in the expected lender-related lines.

Related reading

• How to calculate Closing Cost in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Closing Cost in Philippines — Worked example with real statute citations
• Inputs you need for Closing Cost in Philippines — Input checklist with sourcing guidance