HMDA data review
How do we check the HMDA reportable fields against the loan file and send discrepancies back for correction before the register is submitted?
Test the register against the file, not the file against the register. Callvu takes each reportable field from the loan application register, compares it with the source in the loan file (the application date, the action taken and date, the loan amount and terms from the note, the property data, the demographic information, the pricing fields from the Closing Disclosure, the automated underwriting result), flags each discrepancy with the source, routes it to the processor or compliance for correction in the Decision Desk, re-tests, and produces the submission-ready register with the edit results.
In scopeComplex: multi-party handoffsCallvu moves: classify, chase and verify, write back
Last updated November 7, 2026.
The problem today
The scrub is a spreadsheet of 110 fields per loan, and the resubmission threshold is a few errors away.
Every year compliance exports the loan application register and checks it, loan by loan, against the files, in a spreadsheet. The errors are in the usual places: the action taken date, the rate spread, the demographic fields, the loan purpose, the property type. Above the resubmission threshold, the register is resubmitted and the examiner's finding is written.
Each reportable field has a source document in the file. The comparison is mechanical, the sources are known, and the corrections belong to the people who made the entries. The hard part has always been doing it for every loan and every field before the deadline.
A register built from a file that was collected correctly needs a scrub that confirms, not reconstructs.
How it runs
From the requestto the system of record.
The scrub runs on the cycle the lender sets (monthly, quarterly, before submission) over the loans with reportable actions. Callvu opens the scrub with the register and the files.
- Compliance
- Owns the register, decides disputed fields and approves the submission in the Decision Desk.
- Processor
- Corrects the fields that are theirs from the discrepancy tasks.
- Callvu
- Compares, flags, routes, re-tests and produces the register.
Classify the fields and sources
Each reportable field is mapped to its source: the application date from the application record, the action taken and date from the decision or withdrawal record, the loan terms from the note, the property fields from the appraisal and the address, the demographic fields from the collection record, the pricing fields (rate spread, origination charges, discount points, lender credits) from the Closing Disclosure, the automated underwriting system result and the credit score from their records.
Chase and verify
Each register field is compared with its source for each loan; discrepancies are flagged with both values and the source document, and the submission edits (syntactical, validity, quality) are run. Each flagged field becomes a task for the party that owns the source entry, through the Decision Desk.
Decide and correct
The owner corrects the field at its source or explains it; compliance decides disputed fields and quality edits that need a justification; corrections are re-tested.
Write back and submit
The corrected register with the edit results and the justifications is produced for submission, the corrections are written back to the LOS, and the scrub record (fields tested, discrepancies, corrections, who) is kept for the examination.
Where it ends: Every reportable field was compared with its source for every loan, every discrepancy was corrected at the source or justified, and the register was submitted with the edit results and the scrub record. The Decision Trace shows the field mappings and each comparison; the Audit Trace shows each task, correction and the submission.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The scrub cycle over the register and the files.
The back office
Processors correct at the source from tasks; compliance decides disputes and submits from a tested register.
The Decision Desk
- A disputed field or a quality edit needing justification goes to compliance in the Decision Desk with both values and the source, and only correct, justify, or escalate as outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
What is compared?
Every reportable field on the register with its source document in the loan file, for every loan on the cycle, plus the submission edits.
Who corrects a discrepancy?
The owner of the source entry, at the source, from a task; compliance decides disputes and quality edits.
What does the examiner get?
The scrub record: the fields tested, the discrepancies, the corrections and who made them, with the submitted register.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.