The SaaS purge is leaving unpaid invoices behind

The enterprise SaaS rationalization cycle that started in 2023 is still running. Companies that over-purchased software during the low-interest, high-burn era are systematically auditing their tech stacks and cutting subscriptions. Gartner estimated that the average enterprise runs software from over 100 vendors; many IT organizations are now targeting that number by 30–50%. The cuts are real, they're ongoing, and they're creating a wave of disputed and unpaid invoices that software vendors are only beginning to work through.

The problem isn't just churn. Churn is expected. The problem is that the manner in which enterprise customers are cutting software subscriptions has become increasingly aggressive—and increasingly costly for vendors who don't have disciplined AR processes to respond to it.

The four ways the SaaS purge creates bad debt

1. Mid-contract termination with disputed final invoices. A customer decides to cut a subscription 8 months into a 12-month contract. They stop using the product, inform the customer success team, and then stop paying invoices. When the vendor sends the remaining 4 months of invoices under the contract terms, the customer disputes them, claiming the software "didn't meet requirements" or referencing a clause that doesn't exist. The contract is clear; the customer is wrong. But extracting that payment requires escalation the vendor's team wasn't set up to do.

2. "True-up" refusals at renewal. Usage-based or seat-based contracts with annual true-ups are a common flashpoint. The customer added 50 seats mid-year, used them, and the annual true-up invoice reflects that usage. At renewal, procurement—now under cost-cutting pressure—disputes the true-up amount, claiming internal records show fewer seats, or that seats were added without authorization. The usage logs say otherwise. This dispute category has grown significantly as enterprise procurement teams have been handed explicit cost-reduction targets.

3. Retroactive pricing renegotiation. This is the most aggressive version: a customer who signed a multi-year deal at a specific price demands a mid-term rate reduction, threatens to cancel immediately if refused, and then stops paying the original invoice rate while the "negotiation" is ongoing. They're using non-payment as leverage in a pricing dispute. This is a contract enforcement problem dressed as a negotiation.

4. Acqui-hire and reorg eliminating vendor champions. A company that was a committed customer gets acquired or goes through a significant reorg. The champion who owned the vendor relationship is gone. The incoming team or acquirer treats all existing vendor contracts as subject to renegotiation. Invoices that were being paid regularly stop getting processed. The vendor's contact no longer exists, or no longer has authority over purchasing. These accounts go silent quickly—and silence is the hardest thing to collect against.

What makes this wave different from normal churn

Normal churn produces non-renewals. A customer who decides not to renew stops using the product at contract end, and the vendor loses the forward ARR but collects what was owed. That's a revenue problem, not a receivables problem.

The SaaS rationalization wave is producing non-payment on existing contracts—invoices for services already provided, under contracts already signed, that customers are simply refusing or slow-walking. That's a receivables problem, and it compounds because the accounts tend to be large (enterprise cuts focus on larger spend), the customers are sophisticated (they know how to delay), and the vendor teams are focused on replacement churn rather than AR enforcement.

What vendors with disciplined AR do differently

• Separate churn discussions from payment discussions. A customer who wants to cancel is a customer success and sales conversation. A customer who has an outstanding invoice is an AR conversation. These should never be conflated. "We're considering canceling" is not a reason to stop chasing an overdue invoice—in fact, it's a reason to accelerate.
• Document usage at the contract level, not just the billing level. When a customer disputes a true-up or a usage-based invoice, the resolution depends on usage data. Vendors who maintain granular, timestamped usage logs can resolve these disputes quickly. Vendors who don't can expect the dispute to drag for months.
• Treat retroactive renegotiation as a contract enforcement issue. A customer who stops paying the contracted rate while demanding a lower price is in breach, not in negotiation. Escalating to an external agency at that point isn't aggressive—it's appropriate, and it often produces a settlement at or near the contracted amount faster than continued internal negotiation.
• Set placement triggers for silent accounts. Accounts that go silent—where the contact has changed and no one is responding to invoices—need a defined response. Two attempts to re-establish contact, then a formal notice, then external escalation. A 90-day silence on a signed contract is not ambiguous; it's non-payment.

The timing window that matters

The SaaS rationalization cycle has produced an unusual pattern in our placement book: accounts where the customer clearly owes money, the contract is solid, and the vendor waited 12–18 months before escalating because they were hoping to salvage the relationship or renew at a lower rate.

By the time those accounts reach us, the champion is gone, the AP contact has changed, and the company's financial condition may have deteriorated. We still collect many of them—but at meaningfully lower recovery rates than accounts placed at 90 days. The contract strength is irrelevant if the debtor's situation has changed by the time you decide to enforce it.

The SaaS purge isn't over. If your AR book has accounts from customers who've reduced usage, raised disputes, or gone quiet in the past 12 months, the time to evaluate them is now—not at the end of Q3 when they've crossed 18 months.