HMDA and Reg C

The Home Mortgage Disclosure Act, HMDA, at twelve U-S-C twenty-eight-oh-one, and Regulation C at twelve C-F-R part ten-oh-three, require many lenders to collect and publicly report data on the mortgage applications they receive and the loans they make. Why? So regulators, communities, and the public can see lending patterns, who's applying, who's getting approved, at what price, and in which neighborhoods.

HMDA is a data rule, not a substantive lending rule; it doesn't tell you whom to lend to. But it's the fuel for fair-lending and Community Reinvestment Act analysis, which is why the exam pairs it with Reg B and the C-R-A. Think of HMDA as the spotlight that makes discrimination visible.

Coverage depends on a mix of factors: the institution's asset size and location, whether it's federally related, and crucially, its mortgage-loan volume. The rule sets loan-count thresholds, separately for closed-end mortgages and for open-end lines of credit, below which a smaller lender is exempt from collecting and reporting. These thresholds have been adjusted over time, so the exam tests the concept that volume drives coverage rather than any single current number.

Both depository institutions and certain non-depository mortgage lenders can be covered. When a question describes a small lender doing only a handful of mortgages, ask whether it even crosses the reporting threshold, sometimes the answer is that HMDA doesn't apply. It also matters what kind of loan is involved: HMDA generally covers closed-end mortgages and open-end lines of credit secured by a dwelling, and it captures applications, originations, and purchases of covered loans.

Certain transactions, like temporary financing or some business-purpose loans not secured by a dwelling for consumer purposes, fall outside coverage. So before you analyze the data, confirm two things: is this institution covered, and is this particular loan a reportable transaction?

Covered lenders compile a Loan Application Register, the L-A-R, recording each application and loan. The data points are extensive: the applicant's demographic information, race, ethnicity, sex, and age, collected as government monitoring information; the action taken, originated, approved-not-accepted, denied, withdrawn; the property location; and a range of loan-level details like loan amount, rate spread and other pricing data, loan type, and lien status. For denials, certain reasons may be reported.

The exam may test what's collected and how monitoring information is gathered, including the rule that if an applicant declines to provide it for an in-person application, the lender notes it based on visual observation or surname, a detail candidates often miss.

Covered institutions submit their Loan Application Register annually, generally by early in the following year, to their federal regulator, and the data is compiled and released publicly through the F-F-I-E-C. The institution must also make a modified version of its register available to the public on request, with certain fields removed to protect privacy. Data accuracy matters: examiners test HMDA data for errors, and significant error rates can trigger resubmission and, in some cases, penalties.

For the exam, remember the annual submission cycle and the public-availability requirement. The takeaway is that HMDA's power comes from making the data both standardized and public.

Here's why HMDA matters beyond the data exercise. Because the register captures demographics, geography, and pricing, analysts can detect potential disparities, are applicants of one group denied more often, or priced higher, than similar applicants of another? That analysis feeds disparate-impact reviews under ECOA and redlining reviews under the Community Reinvestment Act.

So HMDA, Reg B, and the C-R-A form a fair-lending triangle, and the exam expects you to see the connections. Poor HMDA data quality is itself a compliance risk, because errors distort the fair-lending picture and draw examiner scrutiny. When a question links mortgage data to discrimination analysis, HMDA is the source.

It's worth appreciating why public data matters so much: a single bank can't see whether its denial rates for one group are out of line with the rest of the market, but aggregated, public HMDA data makes those comparisons possible for regulators, researchers, and community groups alike. That transparency is the whole point, sunlight as a fair-lending tool. For the compliance manager, the practical takeaway is to scrub HMDA data for accuracy before submission and to use it proactively in the bank's own fair-lending self-assessment, rather than waiting for an examiner to find the disparities first.

Recap. HMDA and Regulation C, at twelve C-F-R ten-oh-three, require covered lenders to collect and report mortgage application and loan data on the Loan Application Register. Coverage turns on asset size, location, and loan volume, with exemptions for low-volume lenders.

The register captures applicant demographics, the action taken, pricing, and property location, and it's submitted annually and made public through the F-F-I-E-C. Its real purpose is fair-lending and C-R-A analysis. Go test yourself, then we'll cover the Community Reinvestment Act itself.