Historical Context & Motivation
The Home Mortgage Disclosure Act (HMDA) was enacted in 1975 as a direct legislative response to decades of discriminatory lending practices—most notably redlining—that systematically denied mortgage credit to minority and low-income communities across the United States. Prior to HMDA, there was no standardized mechanism for collecting and publicly disclosing mortgage lending data, which made it virtually impossible for regulators, community organizations, or the public to evaluate whether financial institutions were serving the credit needs of all neighborhoods equitably. Congress recognized that transparency was a prerequisite for accountability, and HMDA was designed to bring lending patterns into the light by requiring covered institutions to report detailed information about the mortgage applications they received and the loans they originated.
Over the decades, HMDA has undergone significant amendments that expanded both the scope of reportable data and the universe of covered institutions. The regulatory framework implementing HMDA is codified primarily in Regulation C, which was originally issued by the Federal Reserve Board and transferred to the Consumer Financial Protection Bureau (CFPB) following the Dodd-Frank Act of 2010. The 2015 HMDA Rule, finalized by the CFPB, represented the most sweeping modernization of HMDA data collection since the statute's original enactment, adding dozens of new data points and refining reporting thresholds. Understanding this evolution is essential for mortgage professionals preparing for the NMLS examination, as the reporting obligations, institutional coverage tests, and data field requirements reflect layers of legislative and regulatory activity spanning nearly five decades.
The central question HMDA addresses remains as relevant today as it was in 1975: Are financial institutions serving the housing credit needs of their communities in a fair and equitable manner? By mandating standardized data collection and public disclosure, HMDA enables regulators, researchers, and advocacy organizations to identify disparate lending patterns, assess compliance with fair lending laws, and evaluate whether public funds deposited in financial institutions are being reinvested in the communities that generate them.
Core Principles & Definitions
HMDA reporting rests on several foundational principles that govern who must report, what data must be collected, and how that data is ultimately used. These principles operate in concert to create a comprehensive disclosure regime that serves multiple policy objectives simultaneously—from fair lending enforcement to community reinvestment analysis to housing market research. Mastering these principles is essential because the NMLS exam frequently tests candidates on the specific thresholds, definitions, and obligations embedded in Regulation C.
Institutional Coverage
Transactional Coverage
Data Points & Fields
Public Disclosure & Reporting
Purposes of HMDA
Visual Explanation — HMDA Coverage & Reporting Flow
As illustrated in the diagram, the HMDA reporting framework operates as a multi-stage filter. The first gate is the institutional coverage test, which varies depending on whether the entity is a depository or nondepository institution. Depository institutions must meet a combined asset-size, geographic-presence, and regulatory-status test, while nondepository institutions are covered based primarily on origination volume thresholds. Once an institution is determined to be a covered financial institution under Regulation C, it must then evaluate each transaction against the transactional coverage test to determine whether that particular loan or application triggers a reporting obligation. The final stage involves compiling the required data fields into the LAR format and transmitting it electronically to the CFPB.
How HMDA Reporting Works — Coverage Tests & Data Fields
Institutional Coverage Tests
Regulation C defines two separate institutional coverage frameworks—one for depository institutions and one for nondepository institutions. A depository institution (bank, savings association, or credit union) is covered if it meets all of the following conditions: (1) it has total assets above the CFPB's annually adjusted threshold (for example, $56 million for 2024 reporting), (2) it has a home or branch office in a Metropolitan Statistical Area (MSA), (3) it originated at least one home purchase loan or refinancing secured by a first lien on a one-to-four-family dwelling during the preceding calendar year, and (4) it is federally insured or regulated. Nondepository institutions follow a different path: they are covered if they originated at least 100 closed-end mortgage loans or at least 200 open-end lines of credit in each of the two preceding calendar years.
Transactional Coverage
Not every loan made by a covered institution triggers HMDA reporting. The transactional coverage test requires that the loan be a closed-end mortgage loan or open-end line of credit that is (a) secured by a dwelling and (b) falls into one of the covered purposes: home purchase, home improvement, refinancing, or other purpose. Certain transactions are excluded, including loans made primarily for commercial or business purposes (unless secured by a dwelling), temporary financing such as bridge loans and construction-only loans, and purchases of partial interests in pools of loans. Additionally, the property securing the loan must be a dwelling, which Regulation C defines broadly to include single-family homes, condominiums, cooperatives, multifamily residential properties, manufactured homes, and even houseboats or RVs used as a residence.
Key Data Fields (Regulation C §1003.4)
| Category | Selected Data Fields | Purpose |
|---|---|---|
| Application/Loan | ULI, application date, action taken, action taken date, loan type (conventional, FHA, VA, RHS), loan purpose, pre-approval status | Track each application through the pipeline and identify loan product mix |
| Applicant Demographics | Race, ethnicity, sex, age, income of applicant and co-applicant (collected per government monitoring information) | Enable fair lending analysis and identify potential discrimination |
| Loan Terms | Loan amount, interest rate, rate spread, loan term, introductory rate period, balloon payment indicator, interest-only indicator, negative amortization indicator | Evaluate pricing fairness and identify potentially predatory loan features |
| Property | Property address, census tract, county, state, property type (site-built, manufactured), occupancy type, property value | Map lending patterns geographically for CRA and redlining analysis |
| Underwriting | Credit score model used, DTI ratio, combined LTV, denial reasons, automated underwriting system (AUS) results | Analyze underwriting standards and identify disparate treatment in credit decisions |
Detailed Breakdown — Reporting Actions & Exemptions
One of the most frequently tested areas of HMDA on the NMLS exam involves the action taken codes that institutions must assign to every reported application or loan. Regulation C specifies eight possible action taken codes, each representing a distinct disposition of the application or loan file. These codes are critical because they form the basis for analyzing approval rates, denial rates, and withdrawal patterns across different demographic groups—which is precisely the kind of fair lending analysis HMDA was designed to facilitate.
Partial Exemptions Under the Economic Growth Act
The Economic Growth, Regulatory Relief, and Consumer Protection Act of 2018 (EGRRCPA) introduced partial exemptions from certain HMDA data field requirements for institutions that originate fewer than 500 closed-end mortgage loans or 500 open-end lines of credit in each of the two preceding calendar years and satisfy additional criteria. Institutions qualifying for the partial exemption are relieved from reporting approximately 26 of the newer data fields added by the 2015 rule—such as property value, credit score, DTI ratio, and automated underwriting system information—but must still report the remaining core data fields. It is important to note that the partial exemption does not relieve institutions from HMDA reporting entirely; it merely reduces the number of data fields they must report for each covered transaction.
Worked Example — Determining HMDA Reporting Obligations
HMDA vs. Related Federal Reporting Requirements
HMDA does not exist in a regulatory vacuum. It intersects with several other federal laws and reporting obligations that collectively shape the data infrastructure of the mortgage industry. Understanding how HMDA differs from—and complements—these related requirements is essential for both exam preparation and professional practice. The most commonly confused frameworks are the Community Reinvestment Act (CRA) and the Equal Credit Opportunity Act (ECOA) / Regulation B government monitoring information requirements.
| Dimension | HMDA / Regulation C | CRA | ECOA / Regulation B |
|---|---|---|---|
| Primary Purpose | Public disclosure of mortgage lending data; fair lending analysis | Evaluate whether depository institutions meet community credit needs | Prohibit discrimination in all credit transactions (not just mortgages) |
| Covered Institutions | Depository and nondepository mortgage lenders meeting volume/asset thresholds | Depository institutions only (banks, thrifts, credit unions) | All creditors extending credit to natural persons |
| Data Collected | ~48 fields per application including demographics, loan terms, property info, underwriting data | Small business, small farm, and community development lending data; investment and service data | Applicant race, ethnicity, sex, marital status, age (for dwelling-secured credit) |
| Reporting To | CFPB via the HMDA Platform | Federal banking regulators (OCC, FDIC, Fed, NCUA) | Retained in lender files; no public submission required |
| Public Disclosure | Yes — modified LAR available to public | CRA ratings publicly available | No — data retained internally |
Connection to Advanced Regulatory Concepts
HMDA data serves as a foundational input into more sophisticated regulatory frameworks that mortgage professionals encounter at advanced stages of their careers. Two particularly important connections are the use of HMDA data in fair lending examinations and in disparate impact analysis. Federal regulators—including the CFPB, DOJ, and prudential banking agencies—routinely screen HMDA data to identify statistical outliers in denial rates, pricing spreads, and loan product steering across racial, ethnic, and gender lines. When an institution's HMDA data reveals significant disparities, it may trigger a targeted fair lending examination that involves a deep dive into individual loan files, underwriting policies, and compensation structures.
| Concept | HMDA Foundation | Advanced Application |
|---|---|---|
| Fair Lending Screening | HMDA data provides denial rates and pricing data segmented by applicant demographics and geography | Regulators use regression analysis on HMDA data to identify statistically significant disparities that warrant further investigation |
| Disparate Impact | HMDA captures loan features (rate spread, balloon payments, negative amortization) alongside demographics | Facially neutral policies that produce statistically adverse outcomes for protected classes may be challenged under disparate impact theory |
| CRA Performance Context | HMDA's census-tract-level data maps lending activity to CRA assessment areas | Examiners compare an institution's HMDA lending patterns to peer institutions and aggregate market data in CRA evaluations |
| CFPB Market Monitoring | Aggregated HMDA data provides a national picture of mortgage market trends | The CFPB uses HMDA data to identify emerging risks in mortgage products, monitor market concentration, and shape supervisory priorities |
As data science capabilities continue to evolve, the analytical uses of HMDA data are expanding rapidly. Machine learning models can now process millions of HMDA records to detect subtle patterns of discrimination that traditional statistical methods might miss. The CFPB has also signaled interest in requiring additional data points—such as more granular credit score information and automated valuation model data—in future rulemaking cycles. For professionals entering the mortgage industry, understanding HMDA's current reporting obligations is the foundation upon which advanced compliance, risk management, and fair lending analytics skills are built.
Practice Problems
Lesson Summary
The Home Mortgage Disclosure Act (HMDA), implemented through Regulation C, requires covered financial institutions to collect and publicly disclose detailed data about mortgage lending activity. Institutional coverage depends on whether the entity is a depository institution (meeting asset, MSA presence, origination, and regulatory tests) or a nondepository institution (originating at least 100 closed-end loans or 200 open-end lines of credit in each of the two preceding calendar years). Transactional coverage applies to closed-end mortgage loans and open-end lines of credit secured by a dwelling for purposes of home purchase, refinancing, home improvement, or other covered purposes—with exclusions for commercial-purpose loans, temporary financing, and partial pool interests.
Covered institutions must collect approximately 48 data fields per application—including applicant demographics, loan terms, property information, and underwriting data—and submit a Loan/Application Register (LAR) to the CFPB by March 1 of the following calendar year. Each transaction is assigned one of eight action taken codes representing its disposition. HMDA data serves three statutory purposes: evaluating whether institutions serve community credit needs, assisting in public investment decisions, and identifying potentially discriminatory lending patterns for enforcement action. This data forms the evidentiary backbone for CRA evaluations and ECOA/fair lending examinations.