HMDA · Denial reasons

What mortgage denial reasons mean—and what they do not

A public denial-reason category can help describe patterns across past records. It is not a complete underwriting explanation and cannot tell a future applicant why they will—or will not—qualify.

10 minute readReviewed September 1, 2026Sources: CFPB / FFIEC

The short answer

HMDA denial reasons are lender-reported categories attached to denied applications in a past activity year. More than one can be reported for one decision, some institutions are exempt from reporting them, and the public field is not a substitute for the specific adverse-action explanation owed to an applicant.

01 · Separate the records

Public HMDA data and an applicant notice serve different jobs

HMDA fieldA coded category reported for public analysis of historical mortgage activity.
Adverse-action noticeA communication about the creditor's action on a specific person's application.

Do not use an aggregate HMDA chart to diagnose an individual application. The public record does not include the full file, every underwriting factor, the lender's complete policy, or the correspondence sent to that applicant.

02 · Read the label

The categories are broad reporting codes

Debt-to-income ratio
Reported obligations were high relative to income under the lender's evaluation.
Employment history
The lender reported employment history as a principal reason.
Credit history
A broad category that can cover several credit-file or payment-history issues.
Collateral
The value or type of property collateral did not support the requested credit.
Insufficient cash
Available funds for the down payment or closing costs were reported as insufficient.
Unverifiable information
The lender could not verify information used in the credit decision.
Application incomplete
The application did not contain the information needed for the decision.
Mortgage insurance denied
Required mortgage insurance was not approved.
Other
A principal reason outside the standard listed categories was reported.
A category is not a diagnosis.

“Credit history,” for example, can represent different facts in different files. HMDA does not establish the precise item, threshold, or weight used in an individual decision.

03 · Count decisions first

Reason shares need a denial-decision denominator

MortgagesVine county pages divide each reported reason count by all application and preapproval denial decisions in the displayed cohort. This answers: “Among denied decisions, how often was this category reported?”

The HMDA filing instructions permit up to four principal reasons for one denial. One decision can therefore contribute to several reason counts, so reason shares can add to more than 100%. That is expected and is not a calculation error.

04 · Preserve uncertainty

Not every denied record has a usable public reason

The public fields include values for “not applicable” and “exempt,” and reporting can also be incomplete. An institution eligible for an exemption may not report denial reasons at all. Missing categories must remain missing rather than being guessed from income, credit, loan, or property fields.

  • Do not treat a blank reason as “other.”
  • Do not treat fewer reported reasons as fewer underwriting concerns.
  • Do not compare reason shares without checking reporting coverage.
  • Do not expose unstable small counts as precise local evidence.

05 · Compare with limits

A reason-share difference does not identify its cause

Applicant, product, geography, channel, property, and lender mix can all differ. Reporting practices and exemptions can differ too. A raw gap is descriptive evidence worth a closer look; it is not proof of underwriting quality, discrimination, or how a lender would treat another applicant.

  • Use the same activity year and geography.
  • Align loan purpose, product, and action codes.
  • Show denied decisions and reason counts together.
  • Disclose exemptions, missingness, and suppression.
  • Avoid causal or predictive language.

06 · Your application

Your adverse-action notice is the relevant starting point

Regulation B requires the reasons for adverse action to be specific and tied to the factors the creditor actually considered. A notice may state the principal reasons or explain the right to request them. Generic statements about internal policy or merely failing to reach a score are not sufficient.

  • The action the creditor took
  • The creditor's name and contact information
  • The specific principal reasons, or instructions for requesting them
  • Information about the federal law prohibiting credit discrimination
  • Credit-report and credit-score information when those requirements apply

If the notice says to request the reasons, follow its instructions promptly. CFPB explains that the request right generally applies within 60 days of receiving the notice.

07 · Act on the record

Use the explanation to decide what to verify next

  1. Read the notice and request the specific reasons if they are not included.
  2. Ask the lender to explain which documented facts drove each reason.
  3. If a credit report was used, obtain the free report identified in the notice and check it for errors.
  4. Dispute inaccurate credit-report information with the reporting company and information provider.
  5. Ask whether a different loan amount, product, timing, or documented change would affect a new application.
  6. Consider a HUD-approved housing counselor for independent help.

Another lender may reach a different decision, but submitting a new application is a personal financial choice. Compare the costs and terms rather than assuming that approval alone makes an offer suitable.

08 · Go to the record

Official sources and next steps

Keep categories in context

Use public reasons for research—not personal diagnosis.

Review the HMDA basics