Imagine denying an apartment to a qualified renter because your screening report showed two eviction filings — when in reality there was only one, counted twice by the software that compiled it. That's not a hypothetical. It's what federal regulators say happened, repeatedly, at one of the country's larger tenant screening companies, and in July 2026 it cost the company $2.25 million.
The Federal Trade Commission announced that RentGrow, Inc. — a Massachusetts-based provider of tenant screening reports used by landlords and property managers across the country — agreed to pay $2.25 million to settle allegations that it violated the Fair Credit Reporting Act (FCRA) and the FTC Act. The case is a useful case study for any small business, not just property managers, because it shows exactly how "we just report what the data says" stops being a legal defense once your own systems start distorting that data.
What the FTC Says RentGrow Got Wrong
According to the FTC's complaint, RentGrow's violations weren't a single bad actor or a one-time glitch — they were structural problems in how the company built and delivered its reports.
Duplicate criminal and eviction records. The FTC alleges RentGrow's reports frequently listed the same criminal case or eviction proceeding more than once, making an applicant appear to have more legal history than they actually did. Investigators found that in many instances, the underlying data vendors had supplied accurate, non-duplicated records — the duplication was introduced by how RentGrow itself processed and displayed that data before handing it to a landlord.
Undisclosed data sources. The FCRA requires consumer reporting agencies to be transparent about where their information comes from. The FTC says RentGrow used a third-party data service to pull historical addresses and name variations for matching applicants to public records, without disclosing that source — making it harder for consumers to understand, and challenge, how a report about them was assembled.
Broken dispute handling. When consumers noticed something wrong and filed a dispute, the FTC alleges RentGrow sometimes mislabeled valid disputes as invalid and stopped investigating them. In other cases, the company reportedly told the consumer their correction had been sent to the property manager — while the actual report the landlord saw remained unchanged. That combination — an FCRA accuracy failure plus a misrepresentation about the fix — is what turned this into an FTC Act deception case as well as an FCRA case.
None of this required proving RentGrow intended to harm anyone. The FCRA's core obligation on a consumer reporting agency is to follow "reasonable procedures to assure maximum possible accuracy" of the information it reports. The FTC's position is that RentGrow's process, as built, wasn't reasonable — regardless of intent.
The Settlement Terms
The $2.25 million payment goes to the U.S. Treasury as a civil penalty — it is not a fund for affected consumers to claim from. Renters who believe they were harmed by an inaccurate report still have to pursue their own claims separately, including through the FCRA's private right of action.
Alongside the penalty, the consent order requires RentGrow to:
- Implement accuracy procedures specifically designed to prevent duplicate case records from appearing in a single report
- Fully comply with FCRA disclosure, dispute-investigation, and reinvestigation requirements going forward
- Stop misrepresenting to consumers whether a corrected report has actually reached the landlord or property manager who requested it
The order also comes with standard compliance monitoring and recordkeeping obligations, giving the FTC visibility into whether the fixes actually stick.
Why This Matters Even If You Don't Screen Tenants
It's tempting to file this under "landlord problem" and move on. But the underlying issue — a vendor's data pipeline silently degrading the accuracy of information used to make a decision about a real person — shows up anywhere a small business relies on a third-party report to approve, deny, or price something:
- A property manager screening rental applicants
- An employer running pre-hire background checks
- A lender or landlord pulling a credit report to set terms
- A marketplace or gig platform vetting sellers or drivers against a background-check API
If you're on the receiving end of these reports, the FCRA still puts obligations on you, separate from your vendor's. The FTC's landlord guidance is explicit: before ordering a report you need a permissible purpose and the applicant's written consent; if you deny an applicant (or charge them a higher deposit or rent) based even partly on the report, you owe them an adverse action notice naming the reporting agency, disclosing the reason, and explaining their right to dispute the report and get a free copy of it. Those obligations don't disappear just because your screening vendor made a mistake — they're yours to meet regardless of what the vendor got wrong.
Practically, that means:
- Don't treat a screening report as gospel. If a report shows something that seems inconsistent with the applicant's story — two evictions listed for what should be one address change, for instance — it's worth a second look before you act on it.
- Keep a paper trail. Retain the signed consent, the report you received, and copies of any adverse action notice for at least several years. If a dispute or lawsuit surfaces later, this file is what shows you followed the process even if your vendor didn't.
- Apply criteria consistently. Whatever screening standard you use — credit threshold, eviction lookback window, criminal history policy — apply it the same way to every applicant. Inconsistent application is its own liability separate from the vendor's data quality.
- Know your vendor's dispute process. Ask how quickly they investigate consumer disputes and how they confirm a correction actually reaches you, the report's recipient. RentGrow's alleged failure here — saying a correction went out when it didn't — is exactly the kind of gap that leaves you relying on stale, disputed data without knowing it.
The Bookkeeping Angle: Documenting Compliance Costs, Not Just Compliance Risk
Background-check and tenant-screening fees, adverse-action mailing costs, and any legal or compliance consulting tied to FCRA obligations are real, recurring line items — and they're easy to bury in a generic "software" or "office expenses" category where you lose the ability to see them. If your business runs applicant screening regularly (rental units, contractor onboarding, employee hires), it's worth tracking those costs in their own account so you can see the true cost of your screening process and confirm it's being applied consistently across every applicant, not just the ones where something went wrong.
That kind of granular, auditable tracking is exactly where plain-text accounting earns its keep. With Beancount, you're not limited to whatever categories a SaaS bookkeeping tool predefines — you can create an account like Expenses:Compliance:TenantScreening and reconcile it against your applicant log in a version-controlled ledger. If a regulator or an applicant's attorney ever asks how consistently you applied your screening process, having that history in plain text, timestamped and diffable, is a far stronger position than reconstructing it from memory.
Keep Your Compliance Records as Clean as Your Books
Regulatory scrutiny of consumer reporting isn't slowing down, and the RentGrow case is a reminder that accuracy failures anywhere in a screening pipeline — yours or a vendor's — can become your legal exposure. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data, including the compliance-related costs that are easy to lose track of elsewhere. Get started for free and see why developers and finance professionals are switching to plain-text accounting.