1 SolutionVisit Website →
← Back to blog

Avoid Rejected Files: Map FFIEC Rules to HMDA Reporting for Lenders

September 7, 2026
Avoid Rejected Files: Map FFIEC Rules to HMDA Reporting for Lenders

If your institution meets the Regulation C coverage thresholds, you must collect, record, and submit Loan/Application Register data through the HMDA Platform between January 1 and March 1 for the prior calendar year. Start with three moves: run a formal coverage test, secure your Legal Entity Identifier and institutional email domain for platform access, and begin mapping LAR fields against the Filing Instructions Guide.

TL;DR:

  • Run the coverage test annually and save calculations to ensure compliance with asset size, loan volume, and partial exemption criteria.
  • Map all LAR fields from a single source system and embed validation rules early to prevent formatting and data errors that cause rejections.
  • Validate and certify your file well before March 1 using the HMDA Platform’s tools, with special attention to rate spread calculations and file format checks.
  • Secure institutional email access and your LEI at least a month in advance to avoid last-minute delays during registration and validation steps.
  • Document every decision, correction, and validation step to build an audit trail that supports your compliance efforts during examinations.
1 Solution Mortgage Software
Bring Mortgage Workflows Together
1 Solution connects pricing, CRM, compliance, marketing, and operational tools in one platform built for independent mortgage professionals.
Explore 1 Solution

Table of Contents

Key Requirements at a Glance: Your Filing Checklist

Before you assign tasks across your compliance and operations teams, get everyone aligned on what actually needs to happen. We build for brokers who juggle a dozen priorities at once, so here's the short version you can hand off today:

  • Confirm coverage. Run the asset-size, loan-volume, and location tests under Regulation C, and check for partial exemptions tied to state law.
  • Collect LAR fields. Pull every required data point using FIG formatting rules, not your best guess at formatting.
  • Register on the HMDA Platform. You'll need your institution's Legal Entity Identifier, tax ID, and an institutional email domain (personal email won't authenticate).
  • Run pre-submission tools. Use the file-format verification tool, rate spread calculator, and check-digit validator before you certify anything.

Miss any one of these and you're looking at rework during the exact week you have the least time for it.

Who Must Report: Coverage, Thresholds, and Partial Exemptions

Regulation C defines a "financial institution" broadly, but coverage still comes down to a specific test tied to asset size, loan volume, and location. Depository institutions generally need to meet asset-size thresholds plus a minimum count of closed-end mortgage loans or open-end lines of credit in each of the two preceding calendar years. Non-depository institutions face a different volume trigger, independent of asset size.

The FFIEC's Getting It Right guide walks through both tests with worked examples, and it's worth running the numbers even if you were covered last year. Thresholds don't reset automatically, and a slow year in originations can actually change your status.

Partial exemptions complicate things further. Some institutions qualify for reduced reporting under state law exemptions tied to insured depository institutions and credit unions, which shrinks the field set you owe but doesn't eliminate the obligation entirely.

  • Run the coverage test annually, even if you filed last year.
  • Save your calculations and source data. Examiners will ask.
  • Document any partial exemption claim with the specific criteria you relied on.

What to Collect: Core LAR Fields and Common Pitfalls

Your Loan/Application Register needs data across roughly a dozen categories: applicant demographics, loan terms, property information, action taken, and pricing details like rate spread. The FFIEC guide and the FIG both contain field-by-field definitions, but they serve different jobs. Getting It Right explains what a field means; the FIG tells you exactly how to format it for submission.

Formatting mistakes cause more rejected files than actual data errors. APR gets entered to two decimal places. Rate spread needs leading and trailing zeros, so 3.5 becomes 03.50, not 3.5 or 3.50.

Knowing when to enter "NA" trips up even experienced filers. Certain HELOCs and purchased loans qualify for NA treatment on fields like rate spread, but only under specific conditions the FIG spells out. Guessing wrong here generates blocking edits you'll have to chase down later.

  • Map every LAR field to a single source system. Pulling the same field from two databases invites mismatches.
  • Build validation rules into your intake process, not just at submission time.
  • Run sample audits on a subset of records each quarter instead of waiting until February.

Filing Process and Deadlines: Registration, Cadence, and Resubmissions

The annual filing window runs January 1 through March 1 for the prior year's data, per the FIG. Institutions that originated a high volume of covered loans in the prior year face quarterly reporting obligations on top of the annual submission, so check your volume early rather than assuming annual filing applies.

  1. Register on the HMDA Platform using your institution name, LEI, tax ID, agency code, and an institutional email domain. The platform authenticates against that domain, so a personal email address will lock you out.
  2. Validate your LAR file using the platform's built-in checks well before the deadline, not the week of.
  3. Certify the submission. A designated official signs off that the data is accurate and complete.
  4. Watch for resubmission windows. If edits surface after certification, the platform allows corrections within a defined period, and the FIG outlines the mechanics.

Give registration and validation at least a few weeks of runway. IT provisioning for institutional email access is the most common last-minute holdup, and it's entirely avoidable.

Tools and Calculations: Rate Spread, APOR, and File Validation

Rate spread calculation isn't optional guesswork. It depends on choosing the correct Average Prime Offer Rate table (fixed versus adjustable), matching amortization type, lock-in date, and lien status, then applying the APR consistently before formatting the result. The OCC's 2024 bulletin treats this as a deterministic process: same inputs, same output, every time.

Certain loans, including specific HELOCs and purchased loans, qualify for "NA" on rate spread instead of a calculated figure. Getting this wrong is one of the most common causes of rejected LAR entries.

  • Generate rate spread and ULI/check-digit values through the HMDA Platform's own tools rather than manual formulas.
  • Run the File Format Verification Tool before every submission attempt, not just the first one.
  • Batch-process calculations where your volume allows it, but spot-check individual records for edge cases like adjustable-rate HELOCs.

Pro Tip: Run your rate spread calculations in a sandbox environment weeks before the deadline. Catching a formatting error in February costs you an afternoon. Catching it on March 1 costs you a missed deadline.

Preparing Files and Resolving Validation Edits

The FIG specifies a pipe-delimited LAR format with defined valid values for every field, and the platform checks your file against those rules the moment you upload it. Most blocking edits trace back to missing required fields, invalid codes, or ULI and check-digit mismatches that a quick regeneration would have caught.

  1. Pre-validate your file in the HMDA Platform's sandbox environment before your real submission window opens.
  2. Fix errors at the source system, not by patching the export file.
  3. Re-run file-format verification after every correction round.
  4. Document each fix for your audit trail, then submit and certify.

Assign clear roles before this process starts: a data owner responsible for source accuracy, a technical owner who manages file generation, and a certifying official who signs off on the final submission. Blurring those roles is how errors slip through twice.

Practical Compliance Checklist and Operational Advice

Treat coverage testing and LAR preparation as two separate workstreams with a documented handoff between them. One team confirms whether you're covered; another builds the file. Combining these into one rushed process in February is how institutions miss things.

Get institutional email access and your LEI locked down well ahead of the filing window. Use the HMDA Platform's sandbox to pre-validate files and keep a written record of every edit and decision your team makes.

  • Assign a single owner for coverage determination and a separate owner for data preparation.
  • Provision institutional email access at least a month before registration.
  • Retain every validation report as part of your audit trail.

Pro Tip: Independent brokers rarely have a compliance department the size of a bank's. That's exactly why documenting decisions as you go, rather than reconstructing them under exam pressure, matters more for smaller shops than larger ones.

What This Guide Gets Right (and What Most Advice Misses)

Most HMDA guidance treats coverage testing and LAR preparation as one continuous task. They aren't, and conflating them is where a lot of filers lose weeks they didn't need to lose. Coverage is a legal determination you make once a year, backed by asset and volume math. LAR preparation is an ongoing operational discipline that should run monthly, not just in the six weeks before the deadline.

What This Guide Gets Right (and What Most Advice Misses) — overview diagram

The conventional advice also underrates how often institutional email authentication trips up otherwise well-prepared teams. It's not a compliance question. It's an IT provisioning question, and it needs to be on someone's calendar in the fall, not the first week of January.

If you're prioritizing one thing, prioritize documentation. Examiners and auditors care less about whether you got every field right on the first try and more about whether you can show your reasoning when something needed a fix. A mortgage-technology platform like 1 Solution Mortgage Software that keeps compliance data, communication logs, and loan records in one connected system makes that documentation trail far easier to produce when you need it. Build the habit now. The filing window won't wait for you to catch up.

— Omar Khamisa

Sources

For coverage questions, start with the FFIEC Getting It Right guide. For file specs and valid values, the Filing Instructions Guide is definitive. The CFPB's HMDA resources page links to the platform, reportable-data charts, and current filing dates. The platform itself hosts the rate spread calculator, file-format verification tool, and ULI/check-digit generator you'll use during preparation.