HMDA Reportability Determination Checklist
Use this HMDA Reportability Determination Checklist to decide whether a mortgage transaction is reportable under Regulation C and document the basis for inclusion or exclusion before filing.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Mortgage Lending · Credit Unions · Community Banks · Nonbank Lenders
Overview
This HMDA Reportability Determination Checklist is a decision record for deciding whether a transaction belongs in your HMDA file under Regulation C. It guides the reviewer through the facts that matter most: what the transaction is, whether the institution is covered, whether the credit is secured by a dwelling, whether the purpose is covered, and whether any exception or exclusion applies.
Use it when a file could be reportable but the answer is not obvious, when you need a documented basis for exclusion, or when you want a consistent pre-filing review process across multiple reviewers. It is especially useful for mixed or borderline files, incomplete applications, unusual collateral, open-end lines of credit, and transactions that may affect filing deadlines if the determination is made late.
Do not use it as a substitute for legal review when the facts are highly unusual or when your institution’s coverage status is uncertain. It is also not the right tool for non-mortgage consumer credit, general loan booking, or operational reviews that do not require a HMDA reportability decision. The checklist is most effective when the reviewer has the application file, property details, product type, and institution-level coverage data in hand before making the final determination.
Standards & compliance context
- This checklist supports HMDA Regulation C coverage analysis by documenting institution coverage, transaction coverage, and the basis for inclusion or exclusion.
- It aligns with examiner expectations for a defensible audit trail and consistent treatment of reportable and non-reportable mortgage transactions.
- For institutions subject to broader compliance management expectations, it also supports governance practices consistent with consumer compliance programs and quality control review.
- If your file involves unusual property types or mixed-purpose credit, route the determination through your internal compliance policy before finalizing the HMDA status.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Transaction Intake and Context
This section captures the facts needed to start the coverage analysis, including the transaction type, action date, and source documents.
-
Transaction type and application stage identified
Confirm whether the file is an application, origination, purchase, refinance, home improvement, or other transaction type relevant to HMDA analysis.
-
Action date documented
Capture the application date, action taken date, or closing date used for HMDA determination.
-
Property location and occupancy information available
Confirm the file contains sufficient information to evaluate whether the dwelling is located in a HMDA-reportable geography and whether the purpose is dwelling-related.
-
Supporting source documents reviewed
Identify the documents used to determine HMDA reportability.
-
Reviewer notes and rationale captured
Summarize the key facts supporting the HMDA determination, including any ambiguity or exception handling.
Institution Coverage Test
This section confirms whether the institution is covered under Regulation C before any transaction-level decision is made.
-
Institution is a covered financial institution under Regulation C
Confirm the institution meets HMDA coverage criteria for the relevant reporting year.
-
Closed-end mortgage loan volume threshold met
Document the number of closed-end mortgage loans originated in the prior two calendar years.
-
Open-end line of credit volume threshold met
Document the number of open-end lines of credit originated in the prior two calendar years.
-
Coverage determination source verified
Identify the source used to confirm institutional coverage and volume thresholds.
Transaction Coverage Under Regulation C
This section tests the file against dwelling-secured, purpose, and exception rules that determine whether the transaction is reportable.
-
Transaction is secured by a dwelling
Determine whether the transaction is secured by a dwelling as defined for HMDA purposes.
-
Transaction purpose is covered
Identify whether the purpose is home purchase, home improvement, refinance, cash-out refinance, or another covered purpose.
-
Dwelling-related property type confirmed
Confirm the collateral or property type for HMDA analysis.
-
Loan purpose exception or exclusion reviewed
Check whether any HMDA exclusion applies, such as a transaction that is not reportable despite being mortgage-related.
-
Borderline or ambiguous coverage escalated
Confirm that any uncertain coverage determination was escalated for compliance review before final disposition.
Final HMDA Determination and Filing Readiness
This section records the final decision, documents any non-reportability reason, and flags filing or follow-up impacts.
-
Final determination recorded
Document the final HMDA reportability outcome.
-
Reason for non-reportability documented
If the transaction is not reportable, explain the basis for exclusion with enough detail for audit trail and QC review.
-
HMDA filing deadline impact considered
Confirm whether the determination affects current-cycle HMDA reporting readiness and whether the file must be resolved before filing.
-
Corrective action or follow-up owner assigned
Enter the person or team responsible for resolving missing data, exceptions, or escalation items.
-
Inspector signature
Compliance reviewer attests that the HMDA reportability determination is complete and supported by the file record.
How to use this template
- 1. Open the transaction file, identify the application or action type, record the action date, and attach the source documents that show property, occupancy, and product details.
- 2. Confirm whether the institution meets HMDA coverage thresholds for the relevant loan type and document the source used for that coverage determination.
- 3. Test the transaction against Regulation C by verifying that it is secured by a dwelling, has a covered purpose, and does not fall into an exclusion or exception.
- 4. Escalate any ambiguous or borderline file for compliance review before marking it reportable or non-reportable, and capture the reviewer rationale in the notes field.
- 5. Record the final determination, state the reason for any non-reportability decision, assign any follow-up action owner, and confirm whether the filing deadline is affected.
Best practices
- Document the action date and review date separately so late determinations do not obscure filing timing issues.
- Verify dwelling-secured status from source documents, not from assumptions in the loan summary.
- Treat mixed-use, investment, and vacant-property files as escalation candidates until the coverage facts are clear.
- Capture the exact reason for exclusion or non-reportability in plain language so a second reviewer can follow the logic.
- Use the same decision sequence for every file to reduce inconsistent treatment across branches, channels, and reviewers.
- Assign a named owner for follow-up when a file is pending clarification, rather than leaving it in an informal hold status.
- Keep supporting documents linked to the checklist so examiners can trace the determination without searching across systems.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this HMDA reportability checklist determine?
It helps you decide whether a transaction must be reported under HMDA Regulation C and records why it was included or excluded. The checklist walks through institution coverage, transaction coverage, and final filing readiness. It is designed to create a clear audit trail for borderline cases and non-reportable decisions.
Who should complete this checklist?
It is typically completed by compliance staff, mortgage operations reviewers, or a designated HMDA analyst who understands Regulation C coverage rules. In smaller institutions, a loan compliance manager or secondary reviewer may own the final determination. The key is that the reviewer has access to the application file, underwriting notes, and institution-level volume data.
How often should this checklist be used?
Use it for each transaction that could fall within HMDA scope, especially applications, originations, purchases, and other reportable actions. It is most useful at intake or pre-filing review, before data is finalized for submission. Many institutions also use it during quality control sampling to confirm that exclusions were applied consistently.
What kinds of transactions does it cover?
It is meant for mortgage-related transactions that may be reportable under Regulation C, including closed-end loans and open-end lines of credit when the institution meets the applicable coverage thresholds. It also helps flag transactions that are excluded because they are not secured by a dwelling, do not meet the purpose test, or fall within a recognized exception. If the facts are unclear, the checklist prompts escalation rather than a guess.
How does this help with borderline or ambiguous files?
The checklist includes an explicit escalation point for ambiguous coverage questions, which is where many HMDA errors start. That makes it easier to pause on unusual property types, mixed-use collateral, or incomplete occupancy information until the file is reviewed. Documenting the rationale reduces inconsistent treatment across reviewers.
What are the most common mistakes this checklist helps prevent?
Common mistakes include assuming every mortgage is reportable, skipping the institution coverage test, and failing to document why a transaction was excluded. Another frequent issue is not verifying the property type or dwelling-secured status before making the determination. The checklist also helps prevent missed filing implications when a late decision affects the reporting deadline.
Can this checklist be customized for our institution?
Yes. You can add your internal coverage thresholds, review approvals, document links, and exception codes without changing the core decision path. Many teams also add fields for loan channel, product type, and reviewer escalation notes so the checklist matches their workflow and HMDA controls.
How does this fit into a broader compliance workflow?
This checklist works well alongside loan origination, QC review, and HMDA data validation processes. It can be paired with document management, task assignment, and filing calendars so non-reportable decisions and follow-up actions are tracked in one place. That makes it easier to show how each determination was made if an examiner asks.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Learn how hospitality teams use internal communication, employee training, and engagement tools to turn negative hotel reviews into opportunities for growth.
Ready to use this template?
Get started with MangoApps and use HMDA Reportability Determination Checklist with your team — pricing built for small business.
