HMDA Edit-Check Validator
Paste a single Loan/Application Register record and see which FFIEC edits it would fail, with the edit number, the rule as the Filing Instructions Guide states it, and what to change.
Nothing leaves your browser. This page has no backend and makes no network request with your data. The record you paste is parsed and checked by JavaScript running on your own machine, it is never uploaded, never logged and never stored. You can confirm that by opening your browser’s network tab, or by disconnecting from the network and using the page anyway — it will still work.
Run a record
Paste one pipe-delimited LAR row. Field order follows the 2026 Filing Instructions Guide, in which the register carries 110 fields beginning with the record identifier. If you would rather not paste a real record, use the sample.
What it checks, and what it deliberately does not
This tool implements a named subset of the FFIEC edits: the syntactical and validity checks that can be judged on one record in isolation. That is the honest boundary of what a single-row tool can do, and it is worth being explicit about the three things on the other side of it.
- Edits that compare your record to your transmittal sheet — the LEI on a row against the LEI on the first row of the file, for instance — need the file, not the row.
- Edits that compare records to each other, such as duplicate ULI detection, need the whole register.
- Quality (Q) and macro-quality edits are outside this subset entirely. They flag values that are unusual rather than invalid, and most of them only mean something across a population.
So a clean result here means “this record does not fail the subset below”. It does not mean the record will file. For that you need a full submission pass against the complete edit set, which is what Comply HMDA/CRA/SBL does against your own data before the filing window opens.
If you want the failures that recur most often in practice and the fix for each, we set those out in how to fix the ten most common HMDA edit check errors.
Methodology
The edit numbers, the data fields each edit names and the rule text quoted in the results are read from the FFIEC Filing Instructions Guide, 2026 edition (released October 2025, covering data collected in 2026), published by the CFPB at ffiec.cfpb.gov. Nothing in the checks is our interpretation of what an edit ought to say.
Where an edit states several numbered conditions and only some of them can be judged on a single record, this tool implements the ones that can and says so in the result rather than implying the edit passed in full. Field positions follow the guide’s Loan/Application Register specification.
The plain-language remediation line under each failure is ours, not the FFIEC’s. It reflects what the fix usually is at the origination step rather than at the filing step, which is the part a rule text does not tell you.
Rules last checked against that edition: August 25, 2026. If the FFIEC publishes a newer guide, treat the edition named above as the authority for what this page currently implements.
Cite this page
Republish or quote this page freely, with attribution and a link back.
Plain text
RATA Associates. “HMDA Edit-Check Validator.” Rules read from the FFIEC Filing Instructions Guide, 2026 edition. Last checked August 25, 2026. https://rataassociates.com/hmda-edit-check-validator/
Link
<a href="https://rataassociates.com/hmda-edit-check-validator/">HMDA Edit-Check Validator</a> — RATA Associates</a>
Who built this
RATA Associates has prepared HMDA and CRA submissions for banks and credit unions continuously since 1987. The ordering of the checks below, and the remediation notes, come from that rather than from the guide: which failures actually send a filing back, and where in the process they are cheapest to fix. The full edit set, run against your own register before the filing window, is Comply HMDA/CRA/SBL; the geography fields behind several of these edits are compliance-grade geocoding.
