Common Closing Cost mistakes in New Mexico

The top mistakes

Run this scenario in DocketMath using the Closing Cost calculator.

Closing costs in New Mexico aren’t just “fees at the end.” Small errors in how costs are calculated, categorized, or disclosed can ripple into your transaction—especially when the documents you receive don’t match the numbers you expected.

Below are common closing cost mistakes when using DocketMath (closing-cost) for New Mexico (US-NM). This is a practical checklist, not legal advice.

1) Mixing up prepaids vs. lender/service fees

A frequent issue is treating prepaids (like escrow deposits for taxes/insurance) as if they were the same type of charge as lender or third-party fees. That can change how your modeled total behaves in DocketMath.

Common misclassifications:

• Prepaids entered as lender fees
• Lender fees entered as escrow deposits
• Leaving “unknown” amounts in the wrong category

How it shows up in outputs: your cash-to-close number can swing by hundreds of dollars, because prepaids are typically deposited for a future period rather than paid for a one-time service.

2) Getting interest start date, payoff timing, or proration assumptions wrong

Another common problem is using incorrect assumptions for interest start date, proration, or payoff timing.

Typical triggers:

• Closing date entered correctly, but settlement date or interest accrual start date doesn’t match what the lender will use
• Using an outdated payoff estimate instead of the lender’s statement figures

How it shows up in outputs: the “cash to close” number changes after the lender recalculates interest and proration items.

3) Double-counting lender/origination-related charges

Some fees look similar across documents (names vary), and borrowers or closers sometimes enter the same concept twice—once under lender fees and again under other charges.

Common patterns:

• Origination fee plus “processing” added separately when the statement effectively combines them
• Loan discount/points entered again under a different line item

How it shows up in outputs: totals inflate, and you may have to reconcile discrepancies with the settlement agent.

4) Using a non–New Mexico rule set for timeframe reminders

DocketMath is jurisdiction-aware. If you select the wrong jurisdiction or rely on generic assumptions, your modeled timeline and any downstream “timing” prompts can drift out of alignment.

For New Mexico, the baseline general statute of limitations is:

• General SOL period: 2 years
• General statute: N.M. Stat. Ann. § 31-1-8

Key point: based on the jurisdiction data provided, no claim-type-specific sub-rule was found. So treat § 31-1-8’s 2-year period as the baseline, not a tailored guarantee for every dispute scenario.

How it shows up in outputs: if your workflow flags deadlines based on timing, incorrect jurisdiction inputs can cause follow-ups to be scheduled too late or too early.

5) Leaving blanks or using rough “best guess” for tax/insurance prepaids

Prepaids often drive the biggest swings. Entering estimated annual property tax/insurance amounts without aligning them to the coverage period can distort results.

Common mistakes:

• Putting estimated annual property taxes in without prorating to the required months
• Entering insurance as a full year even though the closing timeline implies fewer months
• Using last year’s figures instead of the settlement statement’s estimates

How it shows up in outputs: cash-to-close becomes less reliable, and the discrepancy may surface only after you receive final settlement documents.

6) Entering credits as charges (or using the wrong sign)

Credits can include seller credits, lender credits, or other adjustments. When credits are entered like charges (or vice versa), the direction of the change flips.

How it shows up in outputs: cash-to-close looks higher or lower than reality. On a practical level, it can also affect day-of wire instructions and cash requirements.

How to avoid them

Use these steps to reduce errors—before finalizing inputs and after you get updated lender numbers.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Confirm each line item’s type (prepaid, fee, or credit)

For every entry you make in DocketMath, sort it into one bucket:

• Prepaids (deposited for future periods—often taxes/insurance escrow-style amounts)
• Fees (one-time services, lender charges, third-party settlement services)
• Credits (amounts that reduce what you pay)

Checklist:

Step 2: Tie interest and proration to the dates your lender will use

Before running DocketMath:

• Use the actual closing date reflected in your settlement documents.
• Ensure interest accrual and proration assumptions match how the lender calculates them.
• If you’re modeling before you have the final statement, treat proration/payoff items as provisional and rerun once updated figures arrive.

Checklist:

Step 3: Use New Mexico timing reminders consistently (baseline SOL)

If your workflow includes timing reminders, anchor them to the New Mexico baseline:

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

Because no claim-type-specific sub-rule was identified in the provided data, treat § 31-1-8 as the baseline reference point.

Checklist:

(Again: this is modeling hygiene and risk-awareness, not legal advice.)

Step 4: Reconcile DocketMath outputs to the settlement statement format

DocketMath can calculate totals, but reconciliation is where mismatches are found.

Quick checks:

• Compare DocketMath categories to the settlement statement sections.
• Watch for “same concept, different label” duplication (especially lender-related items).
• Verify credits reduce totals and charges increase totals.

Tip: scan for outliers:

• A single fee category that jumps unexpectedly
• Prepaids that don’t look prorated to the closing month range
• “Other charges” that could be duplicating items already captured elsewhere

Step 5: Prorate tax and insurance prepaids to the required period

Don’t enter raw annual estimates as-is. Align them to the deposit/coverage period the transaction requires (and to whatever start/end period your workflow uses).

Checklist:

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