Compare HMDA Mortgage Rates Without Letting Loan Mix Pick the Winner
A fictional two-lender example shows how loan mix reverses overall averages. Recalculate with shared weights and plan a transparent comparison.
Estimated reading time: 8 minutes
HMDA mortgage rates can change with the mix of loans in the comparison. Hold the comparison groups and exclusions visible before describing one lender as cheaper.
A lender can have a lower average rate within every group you compare and still have a higher average across all its loans. The missing ingredient is the mix of loans in each average.
This guide uses invented lenders and numbers to show the arithmetic, then gives you a plan for a reproducible HMDA comparison. No real lender records were downloaded or analyzed. None of the example rates is a mortgage offer.
HMDA mortgage rates: start with four fictional groups
L and H are abstract labels in this classroom exercise, not HMDA codes, actual products or measured risk categories. Every loan within a cell has the stated invented rate.
| Invented group | Lender A: loans | Lender A: rate | Lender B: loans | Lender B: rate |
|---|---|---|---|---|
| L | 90 | 6.0% | 10 | 5.8% |
| H | 10 | 8.0% | 90 | 7.8% |
Within L, B is 0.2 percentage point lower than A. Within H, B is also 0.2 percentage point lower. Now calculate the overall arithmetic mean, giving each loan equal weight:
- A: (90 × 6 + 10 × 8) ÷ 100 = 6.2%.
- B: (10 × 5.8 + 90 × 7.8) ÷ 100 = 7.6%.
B’s overall mean is 1.4 percentage points higher. Nothing in the arithmetic contradicts the group comparisons: 90% of A’s loans are in L, while 90% of B’s are in H. The two overall means describe different compositions.
These are loan-count-weighted arithmetic means. They aren’t medians, dollar-weighted means, APRs or approval rates. The example establishes no reason why real borrowers receive different rates.
HMDA mortgage rates: give both lenders the same mix
Try a second question: what would each summary be if L and H each received half the weight? This changes the calculation’s target, not the loans in the first table.
- A: 0.5 × 6 + 0.5 × 8 = 7.0%.
- B: 0.5 × 5.8 + 0.5 × 7.8 = 6.8%.
| Summary | A | B | B minus A |
|---|---|---|---|
| Original mix; 100 invented loans each | 6.2% | 7.6% | +1.4 percentage points |
| Hypothetical 50% L / 50% H mix | 7.0% | 6.8% | −0.2 percentage point |
The common-weight results are hypothetical standardized summaries, not either lender’s original overall mean. In this invented example, B stays 0.2 point below A under any identical L/H weights because its difference is identical in both groups. That property doesn’t establish a real-world lender ranking.
Missing-group test: suppose B has no observations in H. You can’t compute its 50/50 summary without supplying an unsupported H rate. Mark that target unavailable, or explicitly choose a different target using only the shared group. Don’t fill an absent group with zero.
What the HMDA mortgage rates fields can tell you
HMDA, the Home Mortgage Disclosure Act, provides information reported by many financial institutions, with modifications to protect privacy. It doesn’t represent every lender or mortgage. See the CFPB’s HMDA overview.
For 2025 reporting, action code 1 identifies an origination; code 6 identifies a purchased loan. A reported rate of 4.125 means 4.125%. A genuine zero, NA (not applicable) and Exempt (reporting exemption) have different meanings. These conventions are field-specific. Check the 2025 Filing Instructions Guide before interpreting a file.
The public HMDA field reference treats interest rate and rate spread as separate measures. Rate spread compares APR with an applicable average prime offer rate; it isn’t the interest rate itself. Loan term is recorded in months, and some borrower measures appear in bands rather than exact values.
Regulation C’s reporting instructions address adjustable-rate loans too. A reported interest rate shouldn’t automatically be read as a fixed rate for the entire loan.
Write the comparison plan before calculating
The following is a proposed analysis design, not an executed extraction or a regulator-endorsed method.
- Freeze the input. Record the activity year, dataset product, official URL, retrieval time, revision label, public schema, file checksum and code version. Another analyst should be able to identify the same input.
- Define the population. Choose a geography, purpose, loan type, lien position and occupancy. Set rules for construction, unit count, open-end lines, reverse mortgages, business-purpose lending and loan term. Verify those fields against the public schema for the selected year. Keep lender identifiers explicit; don’t combine institutions just because their brand names look related.
- Fix the grouping and weights. Write down boundaries before looking for a preferred result. Choose one common reference distribution and explain whom it’s intended to describe. Show the original composition alongside the shared-weight result.
- Publish the denominator. Show retained loan counts, group counts and rate availability for each lender. Use the same retained records in the counts and means. Prevent repeated file ingestion, but don’t delete records merely because their public fields look identical.
- Test stability. Try defensible alternative groupings and report meaningful changes. Don’t hide an unavailable positive-weight group or quietly substitute a different target.
Keep an exclusion log that adds up
Apply the scope tests in a fixed order: activity year; origination status; purpose; loan type; lien position; occupancy; remaining product and geography rules; rate availability; shared-group support.
For each lender and each step, record the starting count, the count removed and the count retained. Assign each removed row its first failed test so the flow reconciles. Keep overlapping quality flags separately; adding those flags together can double-count exclusions.
Record NA, Exempt, blank and unparseable rate entries separately. Don’t replace them with zero. Preserve a valid numeric zero; investigate unusual values rather than silently changing them.
Keep original values and add separate eligibility and reason columns. The final retained count must equal the denominator used for that mean. This fictional exercise has no unavailable rates by construction; it supplies no real-world exclusion counts.
HMDA mortgage rates: change the common weights transparently
Use another reference mix for the same invented cells: 75% L and 25% H for both lenders. A’s standardized summary becomes 0.75 × 6 + 0.25 × 8 = 6.5%. B’s becomes 0.75 × 5.8 + 0.25 × 7.8 = 6.3%. The gap is still minus 0.2 percentage point.
These results differ from the earlier 50/50 summaries because the target population changed. They also differ from the original observed-composition means. Keep three labels distinct: original mix, hypothetical 50/50 mix and hypothetical 75/25 mix. None replaces the others silently.
The stable gap follows from this exercise’s identical within-group difference. It isn’t evidence that all possible groupings or real datasets produce stable rankings. An analyst needs to inspect actual group results and common support before making that claim about observed data.
HMDA mortgage rates: make the exclusion flow reproducible
Consider a separate invented count ledger for one lender. Start with 120 records. Suppose 10 first fail the selected action-status rule, eight of the remaining records first fail the product scope and seven then lack usable rate information. The retained denominator is 95: 120 minus 10 minus eight minus seven.
These mutually assigned first-failure counts reconcile because each excluded row appears once. They aren’t extracted HMDA counts. The interest-rate mean for this hypothetical retained population must use those same 95 records. Dividing their summed rates by 120 would mix a retained numerator with the original input count.
Suppose a separate quality flag marks four records already removed at an earlier scope step. Keep that flag in a diagnostic column; don’t subtract another four from 95. A record can carry several issues while contributing only once to the exclusion flow.
For missing-rate categories, retain the original code and the reason for the selected analysis treatment. A rule that excludes NA from an interest-rate mean shouldn’t rewrite it as zero in the source column. If a positive-weight comparison group becomes unavailable after exclusions, show that missing support rather than inventing a group mean.
Save the counts, retained-row rule and common weights with the output. A second analyst should be able to distinguish a changed dataset, a changed denominator and a changed target mix. That reproducibility supports interpretation; it doesn’t make the standardized summary a causal estimate or an individual loan quote.
A common mix is still not a causal price comparison
The CFPB’s 2018 disclosure guidance excludes credit scores and application/action dates from public loan-level data and limits precision in some other fields.
Matching the fields you can observe doesn’t make borrowers, underwriting, timing or pricing concessions identical. Neither the raw mean nor the standardized summary proves discrimination, predicts an individual approval or identifies the best lender for a particular borrower.
For an actual borrowing decision, compare your own offers and their costs using the Loan Estimate comparison worksheet. The useful research habit here’s narrower: inspect group counts, distinguish original from common-weight means, and make exclusions reproducible before trusting an overall-rate headline.
For other comparison pitfalls, review mortgage quotes against Freddie Mac’s average and who is included in SCF debt medians. An average or median only answers the question defined by its underlying population.


