Automate your HMDA LAR scrub
Compare each HMDA LAR line to the loan file and run the published edits before filing. We automate extraction, comparison, and exceptions. A reviewer resolves each exception, and an authorized person certifies and files.
| LAR field | Loan file | Result |
|---|---|---|
| Loan Amount | 251500 | Over $1,000 |
| Application Date | 20260107 | Within 3 days |
| Action Taken Date | 20260322 | Over 3 days |
| Interest Rate | 6.250 | Match |
| Property Value | 415000 | Reviewer checks |
Tolerances from FFIEC's 2017 examiner testing guidelines.
| Edit | Type | Result |
|---|---|---|
| V677 | Validity | Pass |
| Q607 | Quality | Lien 2 over $250K |
| Q635 | Macro | Run from FIG |
Edit IDs from the 2026 FIG. Macro edits are not in CFPB's public API.
How it runs.
Passing the platform's edits does not prove a LAR entry matches the loan file. Hand sampling against the March 1 deadline leaves field errors for examiners to find.
LAR and loan file
Your LAR, plus Closing Disclosure, note, application, and appraisal.
Your dataCompare and edit
Fields compared to documents. LAR checked with published edit logic.
AutomatedReviewer resolves
A reviewer decides each exception against the loan file.
A personCorrected LAR
Ready for your filer. An authorized person certifies and submits.
Automated
HMDA Platform / Pipe-delimited LAR .txt / CFPB public verification API / Closing Disclosure and note / Loan origination system
The rules and limits.
- Edit logic source
- FFIEC's Filing Instructions Guide Section 5 lists syntactical, validity, quality, and macro edits. CFPB publishes the platform code under CC0.
- Public checks
- CFPB's public verification API parses and validates TS, LAR rows, and files with no login. Macro and institution-dependent edits are not run there.
- Who files, and when
- Regulation C coverage includes at least 25 closed-end loans or 200 open-end lines in each of two preceding years, with other tests. Annual data due March 1.
- Examiner tolerances
- FFIEC's 2017 guidelines do not count differences of three calendar days or less in application or action date, or $1,000 or less in loan amount.
- File format
- A pipe-delimited .txt file. A TS row starts with 1, then one row per loan or application starts with 2.
What a person does.
- A reviewer decides each field exception against the loan file.
- Compliance confirms or corrects every quality and macro edit.
- An authorized representative with knowledge of the data certifies the submission.
Where we stand: we have not shipped this. It uses the same pattern as our document extraction and review-queue work.
Common questions.
Does this make us compliant?+
No. It finds likely errors before you file. Accuracy stays with the institution, and an authorized representative with knowledge of the data must certify it.
Can it file for us on the HMDA Platform?+
No. CFPB's filing API has a sign step, but certification and submission stay with your people. HMDA accounts are tied to your institution's registered email domain.
Does passing the edits mean the LAR is right?+
No. Edits test format and expected values. They cannot show whether a field matches the loan file. That is what the comparison step is for.
Sources
- FFIEC Filing Instructions Guide 2026
- CFPB HMDA Public Verification API
- CFPB HMDA Platform Filing API
- CFPB HMDA platform source
- 12 CFR 1003.5
- 12 CFR 1003.2
- FFIEC HMDA Examiner Transaction Testing Guidelines
General information, not legal, tax, or compliance advice. Rules change; confirm against the current source and your own advisers.
Bring us your version of this.
Intro calls are 30 minutes, free, and useful even if we never work together. We'll be honest about whether this is the right fit for your finance team.