Back to Blog

How do I handle state licensing rules in mortgage lead routing?

5 min read
How do I handle state licensing rules in mortgage lead routing?

State licensing is the single most consequential routing condition in mortgage lead distribution. Every lender must hold an active NMLS license in the state where the borrower is located before receiving that lead. Routing software that ignores this constraint doesn't just create inefficiency — it creates compliance exposure for the lead agency, not just the lender receiving the lead.

Getting the enforcement right requires more than a manual checklist. At any real lead volume, routing decisions happen in real time, and a spreadsheet state-check applied after delivery is already too late.

Why Manual State Filtering Fails

Most agencies start with a shared spreadsheet listing each lender's licensed states. A team member checks the incoming lead's state against the list before forwarding. This works at low volume — maybe 20-50 leads per day across 3-5 lenders. At any higher volume, the manual step introduces delay and errors. Leads arrive in parallel, the spreadsheet is not updated in real time, and unlicensed deliveries slip through whenever a lender's license list changes and someone forgets to update the sheet.

The compliance exposure from an unlicensed delivery is not hypothetical. State mortgage regulators track lead sources, and agencies that route to unlicensed lenders can be considered facilitators. Enforcement in the routing layer is the cleanest fix.

The Correct Setup Pattern

The pattern that works at scale has three parts. First, each lender profile in your router holds a state-license array — a list of two-letter state codes for the states they are currently licensed in. Second, every inbound lead carries a state field (from the lead form or webhook payload). Third, the routing engine evaluates state eligibility as the first filter before checking caps, credit range, or loan type — because there's no point evaluating downstream conditions for a lender who can't legally receive the lead.

When no eligible lender exists (all licensed lenders are capped, or none are licensed for that state), the lead should land in a dead-letter queue for manual review, not disappear silently. Silent drops are harder to audit than visible queued items.

Maintaining Your NMLS License Data

NMLS license status changes more often than most agencies expect. Lenders add states when they pass licensing exams and drop them when renewal costs or compliance overhead get too high. You can verify current license status at NMLS Consumer Access, which publishes real-time license data. A practical workflow: ask each lender to notify you within 24 hours of any NMLS status change, do a quarterly audit of all lender records against NMLS Consumer Access, and reflect changes in your router before the next lead batch runs.

Agencies that let lender state-license data go stale for months typically discover the problem after a disputed delivery, not before.

Combining State Filters with Other Mortgage Routing Conditions

State-license filtering rarely operates in isolation. A typical mortgage routing rule looks like: state match AND credit range AND loan type AND under daily cap. A jumbo lender in California only wants California purchase loans with 740+ FICO. A subprime lender might be licensed in 30 states but only accept FHA loans with 580-680 FICO. The router evaluates all conditions on each lead against each lender before deciding eligibility.

The order of evaluation matters for performance, not for correctness. State filtering first eliminates the most leads fastest, reducing the conditions that need to be evaluated downstream. Most dedicated routers evaluate filters in the order you define them; put state first.

Tool Support for State Licensing Rules

ToolState Filter SupportCombined with Credit/LOB RulesStarting Price
Sheets + ZapierManual onlyNo native support$50-300/mo + time
LeadProsperYes (Pro tier)Yes$499+/mo
LeadMoveYes (all plans)Yes$149/mo
BoberdooYes (via bid filter)Yes (ping/post)$1,000+/mo

Handling Edge Cases: Multi-State Lenders and License Gaps

Two edge cases come up regularly. First, multi-state lenders — licensed in 30+ states — need their full state list kept current, which means a reliable update workflow matters more than the initial setup. Second, license gaps: periods between a lender's license expiration and renewal where they technically have no active license in a state. During this period, the router should treat them as ineligible, even if they expect reinstatement in a week. License status is binary: active or not.

The mechanics of state-license filtering are straightforward; the discipline is keeping lender license data accurate and reacting quickly when it changes.

Frequently asked questions

do I need to check NMLS licensing before routing a mortgage lead?

Yes. Routing a lead to a lender who lacks an active NMLS license in the borrower's state creates compliance exposure for the agency, not just the lender. Your routing layer should enforce state-license filtering automatically on every delivery, rather than relying on lenders to self-report their licensed states after the fact.

how do I tag lenders with their licensed states in a lead router?

The typical setup is a multi-value field on each lender profile — a list of state codes (CA, TX, FL, etc.) they are licensed in. At routing time, the engine reads the lead's state field and checks whether it's in each lender's licensed-state list before making them eligible. You can verify current NMLS license status at nmlsconsumeraccess.org and update the list whenever a lender adds or loses a state license.

what happens if a lender is not licensed in the borrower's state?

If your router has no state-license filter, the lead routes to them anyway, which puts both parties at regulatory risk. A well-configured router simply marks that lender ineligible and moves to the next eligible lender in priority order. If no lender is eligible (all caps hit or none licensed), the lead should go to a dead-letter queue for manual review rather than being dropped silently.

how does LeadMove handle state-license filtering for mortgage leads?

LeadMove lets you define a state-license array per lender inside the buyer configuration. On every inbound lead, the router checks the lead's state field against each lender's licensed states before evaluating other rules like credit range or daily caps. This filter runs synchronously at ingestion so no unlicensed delivery happens, even at high volume. Available on the $149 Starter plan.

can state filters combine with credit score rules in the same routing rule?

Yes. Routing rules can stack multiple conditions — state match AND credit range AND loan type — so a lender only receives leads where all conditions are satisfied simultaneously. This is the standard mortgage routing pattern: a jumbo lender in California only receives California leads with 740+ FICO for purchase loans. Each condition is evaluated in sequence, and the first lender meeting all conditions receives the lead.

how often do NMLS license states change for a typical lender?

Lenders add or drop state licenses more often than most agencies expect — state licensing exams, renewals, and compliance costs cause active changes throughout the year. Quarterly audits of your lender state-license arrays are a reasonable minimum. Some agencies request a license update email from lenders whenever their NMLS status changes and reflect that in the router within 24 hours.

does LeadProsper support state licensing filters for mortgage routing?

LeadProsper supports state-level routing filters on Pro tier plans ($499+/mo). The filter works similarly — you configure accepted states per buyer and the router excludes ineligible buyers at delivery time. For agencies that also need competitive bidding (ping/post), LeadProsper applies state filters to the bid request so only licensed lenders receive the preview. LeadMove applies the same filter logic in rules-based mode starting at $149/mo.

Start distributing leads smarter today

Ingest. Score. Route. Track. One platform.