Property management companies have been automating just about every process they can think of. Leasing inquiries, maintenance requests, billing and accounts receivable. Just about everything that a real estate operator does is being automated every day. Plenty of work still happens by hand, but the share of it shrinks with every software cycle, and the trajectory is not in question.

The tradeoff to all of this automation is that errors now propagate faster and further than they used to. A misconfigured setting applies to every unit it touches, often without anyone noticing until a resident or a regulator does. And when that happens, the question of who is responsible has a consistent answer that many owners find surprising. The regulated party is the owner. The software vendor is a contractor.A landlord fined for a rent increase that violated a local ordinance cannot hand that fine to the platform that calculated it. A landlord who missed a compliance deadline because a tracking system failed still missed the deadline.

At a mobile home park in California, a rent increase of $923 per month appeared on the online payment portal the day before Thanksgiving in 2023, set to auto-debit from residents’ bank accounts that Friday. When residents confronted the owner, Three Pillar Communities, the company said the change was premature and blamed a system error. The city advised residents not to pay anything until arbitration concluded.

Whether the error was genuine is beside the point. The ordinance governs what an owner can charge, and a payment portal configured to debit an unapproved amount is an owner problem regardless of which system generated it. The arbitration process did not pause because the increase appeared by accident.

Federal enforcement has put a sharper version of this question in front of the industry. In December 2025, Greystar Real Estate Partners agreed to pay $24 million to settle a lawsuit brought by the Federal Trade Commission and the Colorado attorney general, with $23 million going to the FTC and $1 million to the state. Regulators alleged that the country’s largest apartment manager advertised base rents that excluded mandatory recurring fees for pest control, valet trash, package concierge service, and utility administration, and that renters typically did not learn the full monthly cost until after paying a nonrefundable application fee. It was the second FTC rental fee case in two years, following a $48 million settlement with Invitation Homes in September 2024.

A week after the Greystar settlement, the FTC sent warning letters to 13 property management software providers. The letters said available information suggested these platforms were limiting the ability of rental property managers and owners to accurately advertise total monthly prices by failing to include all mandatory fees, and advised the companies to review their website hosting platforms and the software controlling the flow of information to listing sites.

That is the agency identifying the tooling as part of the problem. If a platform does not support displaying an all-in monthly price, an operator trying to advertise compliant pricing may not have had a straightforward way to do it. The FTC evidently reached something close to that conclusion, which is why it wrote to the vendors at all. The vendors received a warning about future conduct and a reminder that continued violations could carry civil penalties of up to $53,088 each. The operator had already paid $24 million.

Algorithmic pricing litigation has produced the clearest version of this pattern. Roughly 50 of the largest apartment owners and operators were named alongside RealPage in class actions consolidated in federal court in Tennessee, alleging that the software enabled landlords to coordinate rents. Twenty-seven landlords settled for a collective $141 million in October 2025. MAA settled for $53 million in January 2026 and raised its loss contingency reserve to $62.5 million. Camden Property Trust settled for $53 million in April. A second batch of settlements filed in May covered 11 more defendants for $218 million. RealPage, which built the software, reached its own settlement with the Justice Department in November 2025.

Municipal enforcement is producing the same outcome on a smaller scale. Providence filed its first action under a 2025 ordinance barring software-driven rent coordination, naming Audubon Capital Partners LLC and accruing fines at $500 per day. In Philadelphia, a tenant sued property manager Willow Bridge under a similar law that entitles private plaintiffs to treble damages or $2,000 per violation. The statutes are written to reach the companies that used the software, not the company that sold it.

Owners who pay property taxes through an escrow account often assume the servicer bears the consequences of a missed disbursement, and federal regulation does provide recourse. Under RESPA, a servicer that fails to make a timely payment must correct the error and cover any penalties that resulted. HUD rules are explicit that late payment penalties cannot be charged back to the borrower absent borrower error.

Courts have consistently held that the taxpayer remains ultimately responsible for the tax, and county treasurers proceed accordingly. A lien attaches to the property, not to the servicer. Many counties will waive a penalty as a courtesy when an owner produces a letter from the servicer documenting the failure, which is helpful and entirely discretionary. The owner is the one filing the waiver request, chasing the documentation, and carrying the exposure until it is resolved.

Software errors can also generate litigation an owner never intended to file. In Alexandria, Virginia, a property management firm brought an unlawful detainer action against a sitting city councilwoman for nonpayment of rent she had in fact paid. The company acknowledged in court papers that a glitch in its computer system had generated the filing. Court records showed it had dropped similar mistaken cases against the same resident before. The suit was dropped, but an eviction action had been filed, docketed, and scheduled for a hearing, all of it in the owner’s name.

Most operators think about software risk as a service quality issue, addressed through contracts, service level agreements, and indemnification clauses. Those instruments are worth having. They also operate entirely within the relationship between the operator and the vendor, which is not the relationship that generates the penalty.

A regulator assessing a violation is not evaluating whether an owner’s software performed as promised. A tenant bringing a claim under a local ordinance is not suing the platform. The system that failed is context, sometimes mitigating context, but the party holding the license, the deed, and the obligation is the one answering for it.

As more of the operating stack becomes automated and more jurisdictions write rules aimed specifically at how that automation gets used, we are likely to see this gap between operational responsibility and legal responsibility come up more often. Owners who understand it now will ask different questions during procurement than those who discover it after the notice arrives.

The post When Property Management Software Fails, the Landlord Still Pays appeared first on Propmodo.

​