Credit Union Coalition Pushes House Vote on FCRA Liability Caps

Credit-union compliance teams should map the FCRA Liability Harmonization Act now, but they should not relax dispute, accuracy or adverse-action controls while the proposal remains pending. The bill would change remedies available in private litigation; it would not erase the operational duties that create member and examination risk.

America's Credit Unions reported October 9 that it and other trade groups are asking House leaders to bring H.R. 5775 to the floor when lawmakers return in November. The coalition says the proposal would bring FCRA private-litigation exposure closer to other consumer-finance statutes while retaining individual and class-action rights.

The bill is not law. The House Financial Services Committee ordered an amended version reported favorably on June 30 by a 27–23 vote. It would still need House and Senate passage and the president's signature. Managers should therefore treat the October request as an advocacy event, not a compliance effective date.

What the proposal would change

The coalition says H.R. 5775 would cap damages, eliminate punitive damages in private FCRA litigation and set limits on attorney fees. The introduced bill text covers civil liability under the FCRA, including class actions. Because the committee adopted an amendment before advancing the bill, legal teams should compare any floor text with the introduced and committee versions rather than rely on a summary.

Consumer advocates sharply disagree with the policy. The National Consumer Law Center said the proposal would remove punitive damages, cap actual and statutory damages for class actions and constrain fee shifting, reducing accountability when reporting errors affect many people. That dispute matters for boards: projected litigation savings and possible member-remedy consequences belong in the same analysis.

What would not change on day one

Even if Congress enacted the proposal, credit unions would still need accurate furnishing, reasonable investigations of disputes, controlled access to reports, compliant notices and evidence that decisions match approved policy. Lower potential private damages would not make bad data harmless, eliminate supervisory scrutiny or repair a member's denied loan, higher price or delayed housing purchase.

That distinction is especially important when consumer-report data moves through several systems. A credit union may receive information from a reporting agency, enrich it through a decision engine, apply an underwriting rule, generate an adverse-action reason and later investigate a dispute. Each handoff needs an owner, timestamp, source record and reproducible decision path.

Build a two-track change record

Legal and compliance teams can prepare without assuming passage. One track should monitor the legislative text, status and effective-date language. The other should preserve the current control baseline: dispute volumes and aging, correction rates, repeat errors by source, adverse-action reason quality, vendor response times and member remediation.

Before changing litigation reserves, contract terms or escalation thresholds, management should document the triggering legal event and obtain counsel review. If a final law changes exposure, the record should show which assumptions changed—and which accuracy and member-protection controls remained intact.

Credit unions already changing score providers or underwriting data should connect the legislative watch to existing model and vendor governance. Our coverage of FICO's restructuring and score competition identifies the vendor-change questions, while the VantageScore 4.0 implementation analysis shows how to keep the selected report, underwriting, pricing and delivery path consistent.

The near-term decision is straightforward: monitor the House agenda, preserve versioned legal analysis and keep current FCRA controls operating. The coalition's request may change the likelihood of floor action, but it does not yet change the credit union's duties to members.