Why Slow Construction Receivables Start Before Collections

Construction companies often describe cash flow problems as a collections issue. An invoice gets old, someone starts calling, and the goal becomes getting the customer to pay faster.

That is sometimes necessary. But after more than 20 years working in accounts receivable, I have found that many slow receivables start much earlier, before an invoice is technically late.

The delay can begin when billing is created with missing backup, a purchase order is wrong, a pay application does not match the schedule of values, a lien waiver is missing, a portal submission is incomplete, or a change order has not been resolved. The customer may be willing to pay. The invoice simply has not cleared the process required for payment.

That distinction matters because the financial cost of slow payment in construction is enormous. Rabbet's 2024 Construction Payments Report estimated that slow payments cost the U.S. construction industry about $280 billion in 2024. Its 2025 report estimated the cost at $299 billion and found that general contractors lose about 65 hours per month to payment administration. The problem is not just aging receivables. It is the operating friction wrapped around billing, approval, documentation and follow-up.

The best place to improve DSO is often the front end

Days sales outstanding is useful, but the number by itself does not tell you why cash is slow. Two companies can have the same DSO and completely different problems.

One may have customers that routinely pay beyond terms. The other may have invoices sitting in portals, rejected pay applications, unbilled work, unresolved deductions, missing technician documentation, retainage that is not being actively tracked, or follow-up that starts only after the due date.

Those problems require different responses. Treating every delay as a collections problem can create a lot of activity without fixing the underlying cause.

A better question is: where does earned revenue stop moving?

That question forces the business to look at the full path from completed work to cash. In construction, that path can include field documentation, billing preparation, customer-specific formatting, pay applications, schedules of values, lien waivers, portal submission, approval, dispute resolution, retainage and payment follow-up.

A focused operating review can expose where that path is breaking without assuming in advance that collections is the only problem.

Establish the real baseline

Start with the numbers you can defend. Calculate DSO consistently and separate billed receivables from earned but unbilled work. Track retainage separately rather than letting it disappear inside the general aging. Segment open receivables into useful aging buckets and identify invoices that are technically open but operationally blocked.

The goal is not to create a prettier report. It is to distinguish money that is collectible now from money that cannot move until someone resolves a billing, documentation or approval dependency.

Review the billing path

Review recent delayed, rejected or resubmitted invoices and look for repeat failure points. Common examples include missing PO numbers, incorrect customer formats, incomplete pay application backup, unapproved change orders, missing lien waivers, missing time or material documentation, portal errors and invoices that do not match contract requirements.

Then build customer-specific billing requirements into the process before the invoice goes out.

This is one of the highest-leverage improvements an AR team can make because it reduces avoidable delay before collections work ever begins.

Move follow-up earlier

Do not wait for an invoice to become seriously delinquent before confirming that it is moving through the customer's process.

Confirm receipt. Verify that the invoice or pay application was accepted. Know who owns approval. Capture exceptions while they are still small. If a customer portal shows a rejected item or missing requirement, treat that as an operational exception that needs an owner and a due date, not as something to discover weeks later.

Early follow-up should be professional and useful. The purpose is not to pressure the customer. It is to make sure nothing is quietly preventing payment.

Separate aged debt from process failures

Work older receivables deliberately. Separate true delinquency from disputes, deductions, short pays, retainage, documentation gaps and internal dependencies.

That separation matters. A past-due invoice that is waiting on a customer's payment cycle is different from an invoice that was never accepted because the backup was incomplete. A technician who has not submitted required material detail is an internal billing dependency, not customer delinquency. A disputed change order requires resolution, not another generic collection email.

When those categories are visible, management can assign the right owner and escalation path instead of asking AR to chase everything the same way.

What improves when the process is visible

A stronger receivables operation does more than call customers more often. It creates visibility around what is billable, what was submitted, what was accepted, what is blocked, who owns the blocker, what is due next and when a normal follow-up issue should become a recovery issue.

That visibility also gives leadership a more accurate view of cash flow risk. It helps distinguish a customer-payment problem from a billing-process problem, a documentation problem, a contract issue or an internal execution problem.

And that is the larger point: slow receivables are often an operating-system problem before they become a collections problem.

If your aging report keeps growing even though your team is following up, look upstream. The fastest route to better cash flow may be fixing the reasons invoices stall before asking anyone to collect harder.