Skip to content
The Algorithm
Case StudiesFinancial Services
Financial Services
22 / 25

Automated Underwriting + Regulatory Reporting — How We Built Lending Compliance Infrastructure That Actually Works

Key Outcome
Zero
compliance deficiencies on next regulatory examination
Team
14 engineers
Timeline
14 weeks
Industry
Financial Services
01The Situation

A growing lending operation — consumer and small business loans — operating across 8 states with plans to expand to 20. Their compliance team was manually reviewing every loan file, manually generating HMDA and CRA reports, and manually checking state-specific regulations. With 200 loans per month, they needed 4 compliance analysts. At their target of 2,000 loans per month, they'd need 40. The model didn't scale.

02What Changed

A state regulatory examination found 12 compliance deficiencies — none critical, but enough to trigger enhanced monitoring. The compliance team was overwhelmed and errors were increasing with volume. The CEO faced a choice: slow down growth to match compliance capacity, or build compliance infrastructure that scaled with the business.

03Why The Algorithm

They needed compliance automation that was actually automated — not a workflow tool that still required human review on every file. We built compliance engines that enforce rules, not document violations after the fact.

04What We Built

Automated underwriting compliance engine. Every loan application processed against federal and state-specific regulatory rules before decision. Fair lending analysis running in real time — ECOA compliance enforced in the decision logic, not checked after the fact. Automated adverse action notice generation with regulation-specific language by state. HMDA data collection automated at the point of origination. CRA reporting automated from transaction data. State-specific rate and fee compliance checking against usury laws. Regulatory examination preparation — the system generates a complete examination package on demand.

05 — The Result

Compliance review went from 4 analysts reviewing every file to 1 analyst reviewing exceptions — the 3% of files the automated engine flagged. The next regulatory examination found zero deficiencies. Scaled from 200 to 1,200 loans per month without adding compliance staff. State expansion became a configuration change, not a hiring exercise.

Facing a Similar Situation?

The first call is with a senior engineer.

Tell us the industry, the regulatory environment, and what needs to be built. We'll tell you if we've done it before, what it should cost, and how long it takes.

Talk to an EngineerAll Case Studies
Related Services, Platforms & Engagements
Service
Compliance Infrastructure
Service
Regulatory Intelligence
Platform
ALICE — Compliance Engine
Platform
Regure — Regulatory Intelligence
Platform
ProofGrid — API Compliance
Related Case Study
A Personal Finance App That 200,000 Users Trust With Their Money
Related Case Study
Building a Mortgage Platform That Takes a Borrower From Application to Close
Engage Us