Construction software AR: the project ended, the invoice didn't

Construction software is landing in our queue more than it did three years ago—project management platforms, estimating tools, field collaboration apps, connected jobsite hardware. It comes with the most complicated receivables we collect.

The reason is simple: construction companies don't pay from a corporate account. They pay from a project. And when the project ends—or the job goes sideways—the invoice dies with it.

The paperwork maze

A single construction software account can involve: the general contractor who signed the contract, the project-specific entity that was formed for the job, the subsidiary that actually used the software, the owner who holds the purse strings, and a change-order dispute that's been running for nine months. By the time the invoice is 90 days old, nobody at the debtor is sure which company owes it—and "which company" is the whole ballgame.

General contractors are also masters of the domino excuse: "we're waiting on the owner, and the owner is waiting on the lender, and the lender is waiting on the appraisal." The project financing chain becomes an excuse chain, and the software vendor's invoice is at the bottom of it.

Disputed change orders: the classic stall

The construction industry runs on change orders, and the change-order dispute is the industry's default delay script. "The change order was never approved" gets attached to invoices that have nothing to do with changes. The rebuttal is the paper trail: the signed change order, the email approval, the revised scope that the site team actually executed. Construction disputes are documentation disputes—and construction documentation is terrible.

How we find the entity that actually owes

• Trace the contract chain—the entity that signed is liable, even when the entity that used the software is different
• Map the project finances—which entity holds the project budget, and what's the payment chain from owner down
• Use the usage record—the jobsite that logged in every day is the one that got the value, and their operations team will say so
• Separate the change-order noise—the disputed change order covers the disputed scope, not the licenses you've been billing for three quarters

The short version

Construction software receivables aren't uncollectible—they're buried. Under project entities, GC chains, and change-order paperwork. Keep the contract chain and the usage records. Place it before the project closes. That's the whole play—the vendor who waits until the job ends is arguing with a dissolved entity. Don't be that vendor.