Government monitoring information capture
How do we collect the HMDA demographic information in the required form, record refusals correctly, and keep it out of the credit decision?
Ask the questions the way the rule prescribes, once, in the application. Callvu presents the ethnicity, race and sex questions with the disaggregated categories and the option to decline, records the answers or the refusal with the method of collection, captures the loan officer's visual-observation entries where the rule requires them for in-person applications, keeps the data separate from the underwriting view, and writes it to the LOS for the loan application register. Live at Bank Leumi, under national rules outside the US.
Live at Bank LeumiSimpleCallvu moves: prefill, write back
Last updated November 7, 2026.
The problem today
The demographic section is skipped on the phone, guessed on the form, and corrected at the HMDA scrub.
A loan officer takes an application by phone and leaves the demographic section blank. An online form asks the questions without the subcategories. A broker's form uses last year's version. At year end the compliance team scrubs the loan application register and finds hundreds of fields to fix, which they can only do by guessing.
Regulation C prescribes the questions, the disaggregated categories, the option to decline, the instruction to collect on the basis of visual observation or surname when the applicant does not provide the information in a face-to-face application, and the fields to report. Errors above the resubmission thresholds mean a resubmitted register and a finding. The data also must not reach the credit decision.
The fix is to ask correctly at the one moment it is natural: in the application, on the borrower's screen.
How it runs
From the requestto the system of record.
The application process reaches the demographic section for each applicant and co-applicant. Callvu presents the questions in the required form for the channel.
- Borrower
- Answers the questions or declines, on their own screen.
- Loan officer
- For a face-to-face application where the borrower declines, records visual observation or surname entries as the rule requires.
- Callvu
- Presents the prescribed form, records answers and refusals with the collection method, separates the data from underwriting, writes to the LOS.
Prefill nothing, ask correctly
The demographic questions are never prefilled from prior data. Each applicant sees the ethnicity, race and sex questions with the aggregate and disaggregated categories, the free-text options the rule allows, and the option to decline, in the prescribed wording, on their own screen or read by the loan officer from the same screen.
Record the collection method
The answers or the refusal are recorded with how the information was collected (provided by the applicant, or collected on the basis of visual observation or surname) and whether the application was taken in person, by phone, online or by mail, which decides whether the loan officer must complete the observation fields.
Decide: observation entries
For a face-to-face application where the applicant declines, the loan officer completes the observation entries in the Decision Desk as the rule requires; for other channels, the refusal stands. The data is stored outside the underwriting view.
Write back
The demographic fields are written to the LOS in the register's format for each applicant, with the collection method and the channel, ready for the HMDA scrub and the submission.
Where it ends: Every applicant was asked in the prescribed form, every answer or refusal is recorded with the collection method and the channel, the observation entries exist where required, and the data is in the LOS for the register without reaching the credit decision. The Decision Trace shows the form and the method; the Audit Trace shows each entry and who made it.
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
Inside the application, on each applicant's screen, in every channel.
The back office
Compliance scrubs a register that was collected correctly, not reconstructed; underwriting never sees the fields.
The Decision Desk
- For a face-to-face application where the applicant declines, the loan officer completes the observation entries in the Decision Desk as the rule requires.
Proof
Live at Bank Leumi.Published results only.
Each result is a published claim, with its code on agents.callvu.com, where its status, source and last verified date are kept.
Bank Leumi runs its home lending (mortgage) workflows on Callvu, under national lending rules outside the US.
MTG-01 · Self-asserted · verified 2026-11-06
Bank Leumi cut data errors by 77%.
BNK-03 · Customer-attested · verified 2026-11-02
Bank Leumi reached a 94% average completion rate.
BNK-16 · Customer-attested · verified 2026-11-02
Questions
What buyers ask next,answered plainly.
What if the borrower declines?
The refusal is recorded with the collection method and the channel. For a face-to-face application the loan officer completes the observation entries as the rule requires; otherwise the refusal stands.
Can underwriting see the answers?
No. The data is stored outside the underwriting view and written to the LOS in the register format for compliance.
Are the questions the same in every channel?
Yes, in the prescribed form, with the disaggregated categories and the decline option, never prefilled.
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.