Fair lending software reads an institution’s loan application register and tests it for outcome differences between borrower groups, geographies and price points, then reports each disparity alongside the loan documentation that supports it.
This article covers what the category includes and excludes, what the analysis does to a register, how peer benchmarking works, what the output must contain to survive an examination, and how the approach is implemented.
What Fair Lending Software Covers
US banks and credit unions supervised by the OCC, FDIC, Federal Reserve or NCUA need a register large enough to analyse statistically before any of this applies. The work is then bounded twice:
- By the risk factor categories named in the Interagency Fair Lending Examination Procedures published by the FFIEC
- By which of those risk factor categories application data can measure
The software does not determine whether a measured disparity constitutes discrimination, it does not replace comparative file review and it reaches none of the risk factors that live in documents and conduct.
One distinction separates fair lending testing from HMDA testing, which uses the same input file. HMDA testing asks whether each field on a loan is accurate before the register is filed, while fair lending testing takes the register as filed and asks what it shows across groups.
What the Analysis Does to a Loan Application Register
The loan application register goes in with supporting loan documents attached, and analysis runs across three dimensions the examination procedures already name as risk factors:
- Underwriting outcomes
- Pricing
- Geographic distribution
Each risk factor category sets its own limit on what fair lending software can measure, what data the measurement demands, and what stays a human judgment.
| FFIEC risk factor | What the software measures | Data required | Judgment left to a person |
|---|---|---|---|
| Underwriting (U1-U9) | Approval and denial gaps by group | Action taken, applicant characteristics, underwriting factors | Whether a marginal denial was justified |
| Pricing (P1-P7) | Rate spread and fee dispersion | Pricing fields, discretion and concession records | Whether an exception was legitimate |
| Steering (S1-S8) | Product mix where alternatives existed | Product codes, channel, referral source | Whether the applicant chose or was directed |
| Redlining (R1-R12) | Volume against tract minority concentration | Geocoded addresses, assessment area, peer data | Whether the pattern reflects market or exclusion |
| Overt indicators (O1-O5) | Nothing measurable from the register | Policy and training documents | The whole assessment, which stays manual |
Peer Benchmarking and Valid Comparison Sets
On its own a disparity figure carries little meaning. An approval gap of 4 percentage points might sit well inside what comparable lenders in the same market produce, or well outside it, and the number alone does not say which.
A valid peer set holds constant the things that drive lending patterns:
- Asset size
- Assessment area or market geography
- Product mix
- Origination channel
The redlining factor depends on comparison most heavily. According to the FFIEC procedures, examiners look for significant differences in the number of applications received from areas with relatively high concentrations of minority group residents, and significance only has meaning against lenders serving the same market.
Fair lending monitoring runs on a cadence for a practical reason. Peer sets come from published HMDA releases, so a comparison against last year’s data measures the institution against a market that has since moved.
What the Analysis Output Has to Contain
Two things make an analysis usable as fair lending evidence:
- The disparity finding stated with the population it was drawn from and the control variables applied to it.
- Document-evidence coverage: which loans in the tested population have the supporting file an examiner would ask for, and which do not.
Comparative file review is how the Interagency Fair Lending Examination Procedures work. Examiners build an applicant profile spreadsheet, isolate marginal transactions where the applicant was neither clearly qualified nor clearly disqualified, and compare similarly situated applicants using benchmark and overlap techniques.
Compliance monitoring and testing software assembles that population and surfaces the candidate pairs. Deciding that two applicants were similarly situated, and that a difference in outcome was explained, is a person’s call and is recorded as one.
Fair Lending Testing in Ask Kaia
We recently launched a Fair Lending Compliance Testing agent in our AI compliance expert, Ask Kaia. Learn more about it in our complimentary webinar or request a demo.
The agent takes an uploaded LAR data file and supporting documentation, lets the user select peer institutions for comparison, generates a dashboard of segment, geographic and pricing patterns, displays document-evidence coverage, and produces exam-ready workpapers formatted for regulatory review.
Frequently Asked Questions
What data does fair lending software need?
The loan application register supplies the core fields: action taken, applicant characteristics, pricing, product type and geocoded property location. Supporting loan documents show whether a measured disparity has a documented explanation in the file. Peer data from published HMDA releases supplies the comparison set for geographic analysis.
Can fair lending software replace a comparative file review?
No. The Interagency Fair Lending Examination Procedures direct examiners to build an applicant profile spreadsheet, isolate marginal transactions and compare similarly situated applicants using benchmark and overlap techniques. Software assembles the population and surfaces candidate pairs. Deciding whether two applicants were similarly situated, and whether a difference was explained, is a determination a person makes and records.
How often should fair lending analysis be run?
Most institutions run a full analysis annually and monitor between cycles. Annual analysis alone leaves a lag of up to twelve months between a pricing or underwriting change and the first measurement of its effect.
Learn how Ask Kaia can assist your organization’s compliance team in gaining clarity on regulatory changes.
Request Demo- Policy Drafting
- Compliance Automation
- Audit Trails
- Regulatory Intelligence