HMDA Reportability Determination Checklist

It helps you decide whether a transaction is reportable under HMDA Regulation C. The checklist covers institution threshold testing, whether the file is a dwelling-secured loan or application, whether an exclusion applies, and whether the final action is reportable. It is meant to produce a documented yes/no determination with a clear rationale.

It is usually completed by compliance, lending operations, or a HMDA reporting analyst who understands the institution's reporting profile. A second-level reviewer or compliance manager should sign off when the transaction is unusual, incomplete, or close to a coverage threshold. The person completing it should have access to the loan file and the institution's current origination counts.

Use it for each application or origination that could fall within HMDA scope, especially when the product type, purpose, or collateral is unclear. It is also useful during monthly or quarterly quality control reviews to catch missed reportable files before year-end submission. Institutions often use it as part of their ongoing HMDA file review process rather than only at reporting time.

No. It is a decision aid, not a substitute for the underlying rule set in Regulation C and your institution's HMDA procedures. The checklist works best when paired with internal policy, product mapping, and a current interpretation guide for covered and excluded transactions. It should be updated when your product mix or reporting threshold status changes.

Common misses include dwelling-secured credit that was treated as non-HMDA because the file was incomplete, applications with unclear action taken, and products that changed status after underwriting or closing. Open-end lines of credit and transactions near the institution threshold are also frequent problem areas. The checklist is designed to surface those edge cases before they become reporting errors.

It creates a consistent record of how the reportability decision was made, including the rule or exclusion relied on. That makes internal testing, audit review, and regulator questions easier to answer because the file shows both the conclusion and the reasoning. It also helps demonstrate that ambiguous cases were escalated instead of being decided informally.

Yes. You can add product-specific prompts for construction-to-permanent loans, HELOCs, business-purpose dwelling-secured credit, or portfolio products that create recurring questions. Many institutions also add fields for reviewer name, source system, and links to policy references so the checklist fits their reporting workflow.

An ad hoc review often leaves the decision buried in email or a comment field, which makes it hard to reproduce later. This checklist standardizes the sequence: identify the transaction, test institution coverage, screen for covered loan/application status, and record the final determination. That structure reduces missed steps and makes the review easier to audit.