Your field-service customer is still using the software. So why is the invoice 120 days late?

The software is being used. Logins are happening. Jobs are being scheduled, technicians are closing work orders, dispatchers are routing trucks. And the invoice sits at 120 days past due while AP says they're "still reviewing it."

Here's what a generalist agency sees: a subscription dispute. Here's what we see: a customer with a structure problem. That's where the money is.

The three reasons live field-service accounts stop paying

First: the implementation that never "quite went live." The franchisee in Tulsa says the go-live was botched, while corporate signed off on it in Charlotte. Both are right, and neither has approved the invoice. The implementation dispute is the most common stall in this vertical—and it's almost always about a branch, not the platform.

Second: the approval gap. HQ signs the master agreement. The region that actually uses the software has the budget. The branch that benefits from it has neither. So the invoice bounces between three entities while the technicians keep clocking in. The software is being used by people who were never asked to approve anything.

Third: the renewal bump. Year two arrives with a per-technician price increase or an expansion to a new region—and nobody in the customer's organization actually approved the new number. They keep using the platform at the old price. That's not malice. It's a missing signature.

Active users is not a payment plan

Before the first call on a field-service account, we want the file that proves the customer decided to pay—not the file that proves they logged in:

• The signed order form and addenda—not the quote, the signature
• The implementation sign-off and go-live acceptance, ideally by branch
• The usage export showing active technicians and dispatched jobs after the dispute date
• The renewal notice and the email thread where they agreed to the new price
• Every "we'll send it Friday" promise in writing

We don't walk in asking "what's the dispute?" We walk in asking "who signed, who approved, and who's been paying for the last 18 months?" That's the difference between a collector and a moderator.

What the generalist misses

A generalist sees a SaaS invoice and sends a dunning letter. But a field-service vendor's real leverage is continuity—the customer can't run dispatch on a spreadsheet forever, and they know it. The collector who understands the industry goes to the branch that's using the platform, usage report in hand, and lets the customer's own dispatch team make the argument. The receivable that looked like a dispute turns out to be an approval problem with a paper trail.

We recently reviewed a mid-market field-service portfolio with about $400,000 stuck at 120+ days across a dozen accounts. The amounts were complicated. The excuses weren't. Every single one was a branch approval, a go-live gripe, or an unsigned renewal—and every single one had a document that ended the argument.

The short version

If your field-service customer is still dispatching jobs but not paying, the account isn't hopeless—it's unworked. Pull the signatures, the go-live record, and the usage export, and call someone who knows what to do with them. At 120 days, this stops being an AP delay. It becomes a decision.