The document checklist that decides every SaaS collection dispute

Every SaaS dispute I've worked comes down to whether five documents exist. Not whether the customer is right. Whether the paper supports the claim.

I've watched a $340,000 dispute collapse in forty minutes because the debtor's CFO opened a drawer and pulled out a signed MSA with a venue clause that put the fight in his county. I've also watched a $90,000 file that should have been an easy collect drag for six months because nobody could produce an invoice the debtor would acknowledge receiving.

The difference between those outcomes isn't the size of the debt. It's the file. Here are the five documents we ask for at placement—and why each one matters.

1. The signed order form or MSA

Not an emailed proposal. Not a verbal agreement. Not a "we've been doing business with them for years, it's fine." The signed document with terms, term length, and fees.

A CFO at a mid-market SaaS company once told me, "We have a good relationship with them, we don't need the paper." Six months and $120K later, the debtor's position was "we never agreed to a three-year term." The CFO had nothing to counter it with. A signed document ends that argument before it starts.

The order form is the frame of the dispute. Without it, everything else is arguing from a weaker position.

2. The invoice trail

Every invoice sent, when, to whom. Not the AR aging report—the actual invoices.

A clean invoice trail makes a dispute about the invoice itself hard to sustain. One debtor claimed they never received a bill for six consecutive months. We produced the send receipts, the opened receipts, and the email thread where their AP manager acknowledged it. The dispute changed from "we never got it" to "we need more time" in the same phone call.

The aging report is a summary. The invoice is the evidence. Don't send one without the other.

3. The usage and access logs

For SaaS, "we never used it" is the most common dispute. Login logs, API calls, seat assignments—access records proving the customer was live are the answer.

I worked a file where the debtor claimed they'd never deployed the software. Their own login data showed 47 active users in the week before the invoice went past due. The collector didn't have to argue. He just read the numbers. Nobody argues with their own login data.

If your platform tracks seat assignments or session records, export them before you place the account. They're the single most persuasive document in a SaaS dispute.

4. The implementation and acceptance record

Project sign-off, training attendance, go-live date. This kills the "the software never worked" argument.

A signed acceptance document is hard to explain away. A debtor who certified that the implementation met their requirements and then claims the product was unusable has a credibility problem, not a dispute. If your CSM documented the rollout with dates and signatures, the collector has a weapon most agencies don't know to ask for.

Without it, you're relying on people's memories. With it, you're relying on their signature.

5. The communication history

Emails, calls, promises to pay. A documented trail of broken promises is more persuasive than any demand letter.

"We'll send it next week." "Finance approved it, just waiting on the check." "Can you resend the invoice, we'll process it today." Each one is an acknowledgment of the debt. A debtor who acknowledged the obligation in writing and then stopped paying has run out of room to dispute—they've already admitted the debt exists.

Save the emails. Every one of them. What looks like a polite exchange to you is a legal admission to us.

What PCA does at placement

We ask for these five things at placement. If they exist, the file is strong and we know where to start. If they don't, we know what we're working with—and we adjust the strategy accordingly.

A CFO who has these documents ready doesn't just make our job easier. They cut their own resolution time in half. Because when the paper supports the claim, the dispute doesn't last long enough to need a second strategy.