Examiners are no longer treating the HMDA LAR and the NMLS Mortgage Call Report as independent filings. State financial regulators, the CFPB, and the prudential regulators now run cross-regime reconciliation as a standard exam procedure — and the findings they generate are some of the most common compliance deficiencies in mortgage lending today.
When your HMDA data and your MCR data tell different stories about the same loan portfolio, examiners treat the discrepancy as a risk signal. The conversation becomes about why your data is inconsistent, not whether you have a process at all.
This guide walks through the seven most common HMDA–MCR mismatches we see in mortgage compliance examinations, why each one happens, and how to build a reconciliation process that catches the issue before the examiner does.
Why Cross-Referencing Has Become a Supervisory Priority
Three forces have converged to make HMDA–MCR reconciliation an exam focus.
First, the data quality of HMDA filings has improved substantially since 2018, when the Bureau clarified its position that HMDA data is used for enforcement purposes. Examiners now trust HMDA as a reliable baseline.
Second, the MCR Form Version 7 (FV7) transition effective Q1 2026 has changed how origination and servicing data is structured, which creates natural reconciliation friction with HMDA fields that have not changed.
Third, the CFPB’s 2025–2026 supervisory priorities explicitly call out cross-regime data consistency as a focus area. Examiners have been directed to test HMDA–MCR reconciliation as a matter of routine.
The Seven Most Common Mismatches
1. Origination Count Differences
The single most common mismatch. Your HMDA LAR reports X originations; your MCR reports Y. The delta can be small (a handful of loans) or large (hundreds).
The root causes are usually scope differences: which legal entity is reporting (HMDA is at the institutional level, MCR is at the licensed-entity level); whether purchased loans are included (HMDA includes purchased loans, MCR typically does not); whether brokered-out loans are included (HMDA may include, MCR typically excludes); and how prequalifications are handled.
How to fix it: Document the scope rules for each filing. Build a reconciliation that adjusts each total to a common basis before comparison. If the adjusted totals still don’t tie, the difference is a data integrity issue.
2. Dollar Volume Mismatches
Origination dollar volume differs between HMDA and the MCR — often by a percentage that doesn’t match the count difference. This is a red flag for examiners because it suggests inconsistent loan-level data across regimes.
Common causes include: rounding differences (HMDA reports in thousands, MCR reports in dollars); purchased loan amount handling (HMDA includes premium, MCR may not); and treatment of construction loans (HMDA reports the permanent financing amount, MCR may report a different basis).
How to fix it: Document the reporting basis for each regime. Convert both totals to the same unit (whole dollars) before comparison. Reconcile at the loan level, not the aggregate level.
3. Geographic Distribution Differences
The state-level distribution of originations differs between HMDA and the MCR. This is a higher-risk mismatch because it can imply different operational footprints or different definitions of where business is conducted.
Common causes include: property location vs. branch location reporting (HMDA uses property location, MCR uses branch location); treatment of loans originated through remote channels; and treatment of wholesale loans (whose branch is the loan attributed to).
How to fix it: Document the geographic attribution rule for each filing. Make sure your internal operating data uses a single attribution rule and that both filings are built from that single rule.
4. Loan Purpose Mismatches
The split between purchase, refinance, and home improvement differs between HMDA and the MCR. This is one of the more revealing mismatches because it can point to inconsistencies in how your team classifies loans.
Common causes include: cash-out refinance vs. rate-and-term refinance classification; home equity loans treated as home improvement in one regime but not the other; and construction-to-permanent loan staging.
How to fix it: Build a single loan-purpose classification matrix that maps to both HMDA and MCR definitions. Train your origination team on the matrix. QC a sample of loans against the matrix before each filing.
5. Servicing Portfolio Mismatches
The MCR Expanded filers report servicing portfolio volumes. HMDA does not, but examiners pull servicing data from other filings (servicing system reports, investor remittances, custodial accounts). When the MCR servicing figure doesn’t reconcile against these other sources, it generates findings.
Common causes include: portfolio transfer timing (loans sold during the reporting quarter); treatment of subserviced loans (the subservicer vs. the portfolio owner); and treatment of loans in forbearance.
How to fix it: Build a servicing data lineage that ties MCR reporting to your servicing system and your investor reporting. Reconcile monthly, not just at filing time.
6. Reporting Period Mismatches
HMDA is filed annually with a March 1 deadline covering the prior calendar year. The MCR is filed quarterly. When examiners compare a quarterly MCR to the corresponding quarter of the HMDA LAR, the numbers should match — but they often don’t.
Common causes include: cut-off date differences (HMDA uses application date, MCR uses settlement date); treatment of loans that crossed quarter-end; treatment of loans that were withdrawn after cut-off but before settlement; and amendment timing.
How to fix it: Document the cut-off convention for each filing. Make sure both filings use the same cut-off when reconciliation is the goal, or document the adjustment needed to reconcile.
7. Reporting Entity Mismatches
The legal entity reporting differs between HMDA and the MCR. HMDA is filed by the institution as defined in Regulation C. The MCR is filed by each licensed entity on NMLS. When a single holding company has multiple licensed entities, the aggregation can produce different totals.
This is one of the most common sources of mismatch and one of the most difficult to remediate, because the regulatory definitions don’t fully align.
How to fix it: Maintain a legal entity mapping that ties each HMDA reporting unit to the corresponding MCR filing entities. Adjust each total to a common scope before comparison. Document the adjustment methodology.
Building a Reconciliation Process That Works
A defensible HMDA–MCR reconciliation process has five elements.
1. Common Source of Truth
Both HMDA and MCR should be built from a single loan-level data store. This is the architectural foundation. If your HMDA pipeline and MCR pipeline are built separately from the operating system, you will always have reconciliation friction.
2. Documented Scope Rules
Write down the scope rules for each filing: who is in, who is out, what is included, what is excluded. The rules should be detailed enough that an examiner could replicate your filing from your operating data.
3. Pre-Filing Reconciliation Step
Build a pre-filing reconciliation step into both pipelines. For HMDA, this means reconciling your draft LAR against the MCR for the corresponding quarters (if available) and against your operating system totals. For the MCR, this means reconciling your draft MCR against the prior HMDA LAR (if available) and against your operating system totals.
4. Reconciliation Tolerance and Exception Documentation
Set a reconciliation tolerance (we recommend 0.5% or tighter at the aggregate level) and document any exceptions. Exceptions should be tied to specific loans or categories, with a written explanation of why the difference exists.
5. Continuous Reconciliation, Not Filing-Window Reconciliation
The worst time to discover a reconciliation issue is during the filing window. Run reconciliation monthly (or more frequently for high-volume originators). The reconciliation should be a standing report, not a filing-day activity.
What Examiners Actually Look At
In a typical MCR examination, examiners will:
- Pull your MCR for the period under exam
- Pull the corresponding HMDA LAR
- Compare aggregate origination count and dollar volume at the legal entity level
- Compare state-level geographic distribution
- Compare loan purpose distribution
- Compare servicing portfolio volume (for Expanded MCR filers) against your servicing system
- Sample loan-level records and compare the HMDA record, the MCR record, and the loan file
- Ask you to explain any mismatch with supporting documentation
The conversation escalates from a procedural question to a substantive finding when the explanation is unsatisfactory. “We didn’t reconcile” is a process finding. “We reconciled but the difference is real and we don’t know why” is a substantive finding. “We reconciled, here’s the documented reason, and here’s how we’re fixing it” is a defensible answer.
What an Examiner-Ready Reconciliation Binder Looks Like
When the examiner asks for your reconciliation documentation, you should be able to produce:
- The current period MCR and the current period HMDA LAR (or the most recent filed LAR)
- Reconciliation worksheets showing aggregate count, volume, geographic distribution, and loan purpose at the legal entity level
- Identified variances with root cause and remediation status
- Documented scope rules for each filing
- Loan-level reconciliation samples for high-risk categories (large loans, geographic outliers, loan purpose transitions)
- Evidence that reconciliation runs on a continuous basis, not just at filing
A binder that can be produced within an hour of an examiner request is a defensible binder. A binder that takes a week to assemble is a process finding waiting to happen.
The Role of the MCR Form Version 7 Transition
FV7 introduced structural changes to the MCR that materially affect reconciliation. Three changes in particular require attention.
Consolidated filing structure: FV6’s separate Standard and Expanded MCR forms were replaced with a single filing with conditionally required fields. Companies that haven’t updated their internal mappings are reporting data under old category assumptions.
New Ginnie Mae Issuer fields: FV7 introduced new conditional fields for Ginnie Mae Issuers that did not exist in FV6. If your compliance team built your FV7 template from FV6 documentation, these fields may be missing.
Texas supplemental filings: The Texas SSSF is a separate filing from the NMLS MCR but captures related data. Texas-licensed companies need to reconcile SF600 and SF610 against their MCR origination volume to avoid a different set of mismatches.
Frequently Asked Questions
How Often Should We Run Reconciliation?
Monthly at minimum. Quarterly is acceptable for low-volume originators, but monthly is better. Continuous reconciliation is the gold standard.
What Tolerance Should We Set?
Tighter is better. We recommend 0.5% at the aggregate level. Any variance above that should be documented with a root cause and a remediation plan.
What If Our Operating System Doesn’t Have a Single Source of Truth?
This is a common problem, especially for lenders that have grown through acquisition or operate multiple legacy systems. The first step is to map each filing pipeline back to its underlying data source and identify where the divergence occurs. Then prioritize a single source of truth for the highest-risk data elements first.
What If We Discover a Mismatch After Filing?
File an amendment. For HMDA, submit a revised LAR. For the MCR, file an amended MCR through NMLS. Document the amendment internally. Self-discovered and promptly amended errors are treated more favorably by examiners than errors discovered during an examination.
Need help building a reconciliation process or preparing for an upcoming exam? Synergy supports mortgage lenders with reconciliation design, pre-filing QC, and exam-readiness reviews for HMDA, MCR, and the Texas SSSF. Book a 30-minute reconciliation review.
