Archives

Regulatory Updates

HMDA and Mortgage Call Report Cross-Referencing

Leave a comment

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:

  1. Pull your MCR for the period under exam
  2. Pull the corresponding HMDA LAR
  3. Compare aggregate origination count and dollar volume at the legal entity level
  4. Compare state-level geographic distribution
  5. Compare loan purpose distribution
  6. Compare servicing portfolio volume (for Expanded MCR filers) against your servicing system
  7. Sample loan-level records and compare the HMDA record, the MCR record, and the loan file
  8. 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:

  1. The current period MCR and the current period HMDA LAR (or the most recent filed LAR)
  2. Reconciliation worksheets showing aggregate count, volume, geographic distribution, and loan purpose at the legal entity level
  3. Identified variances with root cause and remediation status
  4. Documented scope rules for each filing
  5. Loan-level reconciliation samples for high-risk categories (large loans, geographic outliers, loan purpose transitions)
  6. 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.

Regulatory Updates

CFPB Section 1071 Small Business Lending Data Collection

The CFPB’s Section 1071 rule reshapes how mortgage lenders collect, store, and report data on credit applications from small businesses. For Tier 1 filers — the largest originators — the compliance date is July 1, 2026. For most mortgage lenders operating in the small business and commercial space, this is the most consequential data collection rule since HMDA.

On October 2, 2025, the CFPB finalized an interim final rule extending compliance dates for Section 1071 of the Dodd-Frank Act. Under the revised schedule, Tier 1 filers — those originating 2,500 or more covered small business credit transactions in each of 2024 and 2025 — must begin collecting and reporting data on or before July 1, 2026, with first filings due June 1, 2027.

For mortgage lenders, this is a meaningful expansion of the data collection perimeter. Until now, HMDA has been the dominant data regime. Section 1071 extends a parallel reporting requirement to small business lending, and the two regimes are designed to work together — examiners will increasingly look for consistency between them.

This guide walks through what Tier 1 status means for mortgage lenders, what counts as a covered application, the data points required, and how to build a Section 1071 program that holds up under CFPB examination.

Who Counts as a Tier 1 Filer

The CFPB’s tier structure is based on originator volume, not portfolio or servicing. Under the 2025 interim final rule, tiers are:

Tier 1: 2,500+ covered transactions in each of 2024 and 2025 — compliance date July 1, 2026 — first filing June 1, 2027.

Tier 2: 500–2,499 covered transactions in each of 2024 and 2025 — compliance date January 1, 2027 — first filing June 1, 2028.

Tier 3: 100–499 covered transactions in each of 2024 and 2025 — compliance date October 1, 2027 — first filing June 1, 2029.

Exempt: Fewer than 100 covered transactions in each year — not required to file.

Volume is measured at the legal entity level, not the holding-company level — though there are aggregation rules for commonly controlled entities. The CFPB has signaled that aggregation will follow Regulation B’s control-person framework, with limited exceptions for certain minority-owned institutions and CDFIs.

The threshold applies to covered credit transactions, not portfolio or servicing. If your institution has any commercial or small business lending activity and your overall originator volume puts you in any tier, you must include that activity in your Section 1071 count. The threshold is firm-wide, not line-of-business.

What Applications and Loans Are Covered

Section 1071 covers applications for credit from a small business. The CFPB’s definition of “small business” is the SBA’s size standard for the applicant’s industry — generally a business with $5 million or less in gross annual revenue (calculated across the applicant’s three most recent fiscal years) and 500 or fewer employees.

A “covered credit transaction” is a closed-end or open-end credit product originated for a small business, including:

  1. Commercial mortgages and refinances
  2. Commercial real estate loans
  3. Working capital lines of credit
  4. SBA-guaranteed loans
  5. Equipment financing
  6. Business credit cards (with limited exceptions for corporate cards)
  7. Merchant cash advances (treated as credit under the rule)

Key exclusions include trade credit (credit extended for the purchase of goods and services from the creditor itself), public utilities, securities transactions, credit to financial institutions, credit to governments, and credit extended to a business with gross revenue above the size standard.

The 19 Data Points You Must Collect

For every covered application, the rule requires collection of 19 data points organized into three categories.

Applicant-Identifying Data

1. Legal name

2. Trade name (if different)

3. Address (physical, not PO Box)

4. Taxpayer Identification Number (TIN / EIN)

5. Application date

6. Application method (in-person, phone, online, mail)

7. Application recipient (where the application was submitted)

Application Characteristics

1. Application type (covered application, prequalification, or incomplete)

2. Action taken (approved, denied, withdrawn, incomplete)

3. Action date

4. Denial reason(s) — enumerated list (main reason + up to four additional)

5. Credit type (closed-end vs. open-end)

6. Credit purpose (working capital, equipment, real estate, etc.)

7. Amount applied for

8. Amount approved or originated

9. Term

Pricing Data

1. Interest rate

2. Total origination charges

3. Broker fees and lender compensation

Demographic data on the applicant’s principal owners (race, ethnicity, sex) is collected on a voluntary basis, consistent with the rule’s fair-lending intent.

Pricing data sensitivity: The pricing fields (interest rate, origination charges, broker fees) are the most contested parts of the rule. For mortgage lenders, these overlap with HMDA rate spread reporting. Treat 1071 pricing data as separate and validate at the loan level — examiners will compare 1071 pricing against HMDA LAR, internal loan files, and the closing disclosure.

Where Section 1071 Meets Mortgage Lending

For most residential mortgage lenders, Section 1071 will be a peripheral obligation. But the rule applies where the lines blur — and for diversified lenders, the overlap is significant.

Residential Mortgages That Touch 1071

  1. Investment property mortgages held in the name of a small business entity (LLC, corporation, partnership) — not in the borrower’s personal name. These are commercial loans, even if secured by 1–4 family residential property.
  2. Mixed-use property loans where the borrower is a small business.
  3. Construction loans to small business developers, including single-purpose entity (SPE) borrowers.
  4. Diversified lenders with both consumer mortgage and commercial / small business lending arms, where total originator volume pushes the institution into a tier.

Residential Mortgages That Do NOT Touch 1071

  1. Personal mortgages on a borrower’s primary residence (HMDA-only)
  2. Personal second homes and vacation homes (HMDA-only)
  3. Refinances of personal mortgages (HMDA-only)
  4. Reverse mortgages for individuals (HMDA-only)

The test is who the applicant is, not what the property is. Loans to individuals — even on non-owner-occupied investment property — are generally HMDA territory. Loans to small business entities are 1071 territory.

HMDA and 1071: The Overlap You’ll Want to Plan For

This is the part of Section 1071 that gives mortgage compliance officers heartburn — and the part examiners will look at most closely.

HMDA and Section 1071 both collect credit-application data. For the small (but growing) population of loans that could plausibly be reported under either regime, you need a clear written policy on which regime applies and why. Examiners will compare:

  1. Total application counts under HMDA vs. 1071
  2. Volume consistency between HMDA LAR and 1071 data
  3. Denial reason patterns across both regimes
  4. Pricing data, where both regimes capture rate-related fields
  5. Demographic data handling (both are voluntary but collected separately)

The CFPB and prudential regulators have signaled that cross-regime consistency will be a supervisory priority beginning in 2027. Build the policy now, while you have time.

Building a Single Source of Truth

For institutions in scope for both HMDA and 1071, the right architecture is a single application-level data store that feeds both regimes — not two parallel pipelines. This reduces data integrity risk, simplifies examiner requests, and improves your ability to identify and remediate discrepancies.

Building a Defensible Compliance Program

A Section 1071 program that will survive CFPB examination has five moving parts.

1. Written Policies and Procedures

Your 1071 policy should document tier classification and how it was determined; scope (which products, which channels, which entities are included); application intake process; data storage and retention (3 years from application date); reporting process; quality control; exception handling; training requirements; and oversight and audit cadence.

2. Application Intake Controls

Capture the data points at the point of application, not after origination. The intake controls should include LOS / origination system integration that captures the data at submission, validation rules at the field level, required-field enforcement on the controlled fields, and a demographic data collection workflow.

3. Data Quality Controls

Pre-submission QC is the single biggest determinant of exam-readiness. At minimum: reconciliation against origination system totals, reconciliation against HMDA LAR (for any overlap), denial reason accuracy check on a sample basis, pricing data validation against closing disclosures, and edit checks before submission.

4. Filing Platform Readiness

The CFPB is building a dedicated filing platform for Section 1071 (parallel to the HMDA Platform). Confirm your institution’s readiness to integrate with the platform ahead of your first filing deadline.

5. Exam-Readiness Documentation

Maintain an exam binder that includes the Section 1071 written policy, tier classification analysis with supporting data, data lineage documentation (where each field comes from), QC results for the most recent filing, reconciliation against HMDA LAR for overlap period, and any voluntary demographic data collection materials.

Compliance Timeline and What to Do by July 1

If you’re a Tier 1 filer with a July 1, 2026 compliance date, the clock is short. Here’s the practical action sequence:

  1. Now: Confirm tier classification using 2024 and 2025 originator volume.
  2. Now – end of month: Stand up the written policy and get it approved by compliance committee.
  3. Next 60 days: Map current data capture against the 19 data points; identify gaps.
  4. Next 90 days: Update LOS / origination systems to capture missing fields.
  5. Next 120 days: Train intake and operations staff.
  6. By July 1, 2026: Begin collecting all 19 data points on every covered application.
  7. By Q4 2026: Run your first pre-submission QC cycle.
  8. By Q1 2027: Validate the full pipeline end-to-end with test data.
  9. June 1, 2027: First filing due.

Frequently Asked Questions

Do I Have to Collect Demographic Data on the Applicant’s Owners?

No — demographic data (race, ethnicity, sex) is collected on a voluntary basis. You must offer the applicant the opportunity to provide it, but you cannot require it, and you must clearly disclose that providing the information is voluntary.

What If My Institution’s Originator Volume Was Above the Tier 1 Threshold in 2024 but Below in 2025?

You must meet the threshold in both years to qualify for Tier 1. If you drop below in either year, you move down a tier (or become exempt).

How Does Section 1071 Interact With State-Level Small Business Reporting?

Several states have their own small business lending reporting requirements (notably California and New York). Section 1071 is federal and preempts conflicting state requirements. You still need to file state reports, but Section 1071 is the floor, not the ceiling.

Can I Use Third-Party Vendors to Handle Section 1071 Compliance?

Yes — most lenders will use LOS providers, compliance platforms, or specialized 1071 vendors to handle data capture, validation, and filing. Vendor selection and oversight is itself an exam topic, so document your due diligence and ongoing monitoring.

What Records Must I Retain?

Three years from the date of application. Records must be sufficient to reconstruct the application data as it was reported, including the response to any voluntary demographic question.

Ready to review your Section 1071 readiness before July 1? Synergy supports mortgage lenders with policy drafting, data-mapping, QC buildout, and pre-filing readiness reviews. Book a 30-minute readiness call.

Q&A

Mortgage Call Report Q&A: Servicing Data and Expanded Filers

Q1: What Is the Actual Enforcement Pattern for MCR Non-Compliance Across Major States?

Enforcement varies significantly by state regulator — which is one of the most underappreciated aspects of MCR risk management for multi-state lenders.

The SAFE Act mandates MCR filing as a condition of license maintenance, but the enforcement mechanisms are state-designed:

California (DFPI): DFPI has been increasingly active in examining MCR data against branch license activity. We’ve seen examination findings issued where branch-level MCR submissions showed activity inconsistent with the company’s NMLS licensing map.

New York (DFS): DFS takes a hard line on late or missing filings, and has included MCR non-compliance as a factor in consent order negotiations with mortgage servicers — even when the underlying issue was unrelated to call reporting.

Texas (SML): The new Q1 2026 supplemental filing requirement has caught several mid-sized servicers off guard. SML has signaled through industry communications that they will be actively validating supplemental submissions against RMLA data.

Washington (DFI): Washington DFI has issued fines for incomplete MCR filings — not just late ones — where companies filed but left required fields blank or submitted obviously rounded figures that suggested incomplete data collection.

The pattern across all states: regulators are using MCR data as a primary source for examination planning. A clean MCR history doesn’t just avoid penalties — it shapes which companies get examined and how intensively.

Q2: How Should Servicers Handle Loss Mitigation and Workout Data in the Expanded MCR?

For Expanded MCR filers — those approved by Fannie Mae, Freddie Mac, or Ginnie Mae — the servicing data section is where most reconciliation errors occur. With FHA’s revised loss mitigation waterfall (effective October 2025 under ML 2025-06 and subsequent revisions) adding new workout options including Payment Supplements and modified COVID-era relief transitions, the MCR servicing categories are under pressure to reflect activity that previous form versions didn’t anticipate.

Specifically:

  1. Payment supplement activity needs to be properly categorized — this is a relatively new tool in the FHA servicing waterfall, and companies that haven’t updated their internal reporting taxonomies are classifying it inconsistently
  2. COVID-era loss mitigation transitions are winding down under the updated permanent waterfall, but the activity is still appearing in MCR data under legacy categories, creating inconsistencies
  3. Modifications vs. forbearance re-defaults — there is genuine ambiguity in how to report certain workout scenarios, and companies making conservative assumptions may be underreporting while aggressive classifications create regulatory exposure

The practical recommendation: before each quarterly filing, your servicing data team and your compliance team need to review the categorization decisions together — not hand off data in a one-way process.

Q3: How Does MCR Data Interact With HMDA LAR — and Where Do the Reconciliations Break Down?

The intersection of MCR and HMDA reporting is where experienced compliance teams still make errors — not because the concepts are difficult, but because the two datasets use different segmentation logic and deadlines that create plenty of room for inconsistency.

Key reconciliation challenge: loan count segmentation. HMDA requires reporting of originated loans, purchased loans, and in some cases applications that didn’t close. The MCR RMLA captures origination activity by product type and purpose. When a company is active in both HMDA-reportable and business-purpose lending, the segmentation of the MCR data must align with the same population that drives HMDA reporting.

The “no activity” problem. Companies that originate no HMDA-reportable loans in a quarter still have MCR filing obligations — but the RMLA data must reflect zero origination activity consistent with what HMDA would show. If the company had any activity at all and is claiming zero in both, regulators will cross-reference and find the discrepancy.

Annual LAR reconciliation. HMDA’s annual submission deadline (March 2 for 2025 data) creates a natural reconciliation point with the four quarterly MCR submissions. Companies that perform this reconciliation annually rather than quarterly frequently discover errors that have compounded across multiple quarters.

Q4: What Documentation Do You Need to Survive an MCR Examination?

State examiners don’t just ask for your NMLS submission. They ask for the supporting documentation — and if you can’t produce it, the filing itself becomes a compliance issue.

The audit trail for a defensible MCR filing should include:

  1. Source system reconciliation reports showing how origination, servicing, and accounting data fed into each MCR field
  2. Data classification logic — documented rationale for how you categorized each loan type, product, and activity line
  3. Internal review sign-off — a named compliance officer or CFO who reviewed and approved the filing before submission
  4. Correction log — if prior quarters were amended, the documentation of what changed and why
  5. State-specific supplemental data — stored separately from the NMLS submission with its own supporting documentation

For Expanded MCR filers, the documentation burden is higher. Servicing portfolio data should tie to investor statements; loss mitigation figures should tie to your loss mitigation workflow system; delinquency and default data should tie to your default management reporting.

Q&A

Mortgage Call Report Q&A: What Examiners Want to See

The Mortgage Call Report is one of the most examined regulatory filings in mortgage lending — and most compliance teams are treating it like a simple data submission exercise. Regulators are treating it as a risk signal. Here’s what every Mortgage Call Report filer needs to understand about how examiners actually review your submission.

Q1: What Are Examiners Actually Looking for When They Review Our MCR?

Most compliance teams treat the MCR as a data submission exercise. Regulators treat it as a risk signal.

State financial examiners don’t just check whether you filed — they cross-reference your MCR data against your HMDA submissions, your BSA/AML filings, your licensed MLO count on NMLS, and your audited financial statements. When those numbers don’t reconcile, you get an examination finding — not a conversation, a finding.

Specifically, examiners are flagging:

  1. Servicing portfolio totals that don’t match investor reporting — the most common Expanded MCR trigger
  2. MLO headcount that diverges from state licensing records — particularly after a layoff round or MLO migration
  3. Denial rate spikes without accompanying explanation — regulators are acutely focused on adverse action patterns
  4. Origination volume that doesn’t correlate with your stated product mix — a lender claiming $200M in originations but only two loan products raises questions

The takeaway: your MCR shouldn’t be assembled in the filing window. It should be reconciled continuously against your other regulatory outputs throughout the quarter.

Q2: What Actually Changed With MCR Form Version 7 — and What Filers Are Getting Wrong?

Starting Q1 2026, MCR FV7 replaced FV6 as the mandatory submission format. The headline change was structural consolidation — FV6 eliminated the separate Standard and Expanded MCR forms in favor of a single filing with conditionally required fields based on company type and license profile. But the practical implications run deeper than the form redesign.

The most common FV7 filing errors we’re seeing:

Servicing portfolio segment misclassification. FV7 restructured how servicing activity is reported across investors. Companies that didn’t update their internal data mappings before the Q1 2026 window opened are reporting data under old categories — meaning the numbers don’t align with what state regulators are now expecting to see.

Ginnie MaeIssuer-specific data gaps. FV7 introduced new conditional fields for Ginnie Mae Issuers that weren’t present in FV6. If your compliance team built your FV7 filing template from FV6 documentation rather than the current NMLS field definitions and instructions, you’re almost certainly missing required fields.

State-specific supplemental attachments. Texas’s new supplemental filing requirement — effective Q1 2026 for companies engaged in third-party processing or underwriting — is a separate submission from the NMLS MCR. Several lenders treated it as part of the MCR filing and either missed it entirely or submitted incomplete data.

Q3: How Do You Handle MCR Reporting When You Have both State-Licensed and Federally Chartered Entities?

This is one of the most complex MCR scenarios in the industry, and it’s becoming more common as large bank mortgage subsidiaries and credit union service organizations navigate dual chartering structures.

When a company operates both state-licensed entities and federally chartered affiliates, the MCR reporting obligations do not consolidate at the parent level — they file separately through NMLS for each licensed entity. The data must reflect only that entity’s activity, not the consolidated group.

The practical compliance challenge is cost allocation and data allocation. State regulators have increasingly scrutinizing whether shared services (compliance technology, QC staff, accounting functions) are being allocated appropriately across entities — particularly when one entity appears unprofitable while the parent is profitable. examiners are beginning to ask for supporting documentation on cost allocation methodologies.

Additionally, if your state-licensed entity services loans for your federally chartered affiliate, you may have MCR servicing data that needs to be reconciled against a separate federally required reporting framework — and the numbers must match.

© Copyright 2017 Synergy. All Rights Reserved. - Designed by MPP Freelance
Web Statistics