Getting Paid Faster: Invoicing for Traffic Control Contractors

Ask a traffic control owner why receivables run long and you will usually hear something about customers. Look at the actual aged invoices and a different picture emerges: the slow ones are disproportionately the ones that went out late, lacked a signature, or contained a device count that nobody could substantiate when questioned.

That is good news, because those are all things you control.

The three failures that cause most of it

1. Invoice lag

Every day between the work and the invoice is a day of memory decay on both sides. The site superintendent who could have confirmed your crew was there on Tuesday has moved to another project by the following week. The person who receives the invoice has no way to verify it except to ask someone, and asking takes time, so it sits.

An invoice issued within days of the work, against a record the customer's own representative signed, arrives while everyone still remembers. It gets approved because there is nothing to check.

The obstacle is almost never billing capacity. It is that assembling the invoice requires gathering field facts from several places — timesheets, a device list, someone's memory of whether standby was incurred — and that gathering is what takes eleven days.

2. Weak substantiation

A traffic control invoice makes claims that are hard to verify after the fact: how many devices were on site, for how many days, how many crew hours, whether mobilization occurred twice.

If those claims rest on your internal records alone, a payer under pressure to reduce costs has an easy move — question the count. You then either produce evidence or discount. Most companies discount, because producing evidence weeks later is expensive and often impossible.

The fix is contemporaneous and countersigned: a daily ticket, generated at the zone, listing hours and devices, signed by someone on the customer's side, with a timestamp and location attached. It converts a dispute into a document review. We covered the mechanics in preventing daily ticket disputes.

3. Rental that stops being invoiced while devices are still out

This one is specific to device rental and it is pure lost revenue rather than slow revenue.

Rental accrues while nothing visible happens — that is the product. If billing depends on someone noticing that a job is still live, devices will sit on sites past the last invoice, sometimes for weeks. The reciprocal error is equally common: devices picked up on the 3rd but not marked off-rent until the 20th, which is a credit you will issue and a customer relationship you will spend.

Recurring rental billing has to run on the contracted cycle without a human trigger, with off-rent recorded the day pickup happens. The full requirement set is in the barricade rental management software guide.

The public-work complications

Two things make subcontract work on public projects slower than private work, and both need to be visible rather than absorbed.

Retention. A percentage held back until completion is normal and contractual. What is not normal, and is very common, is showing retention inside general accounts receivable so that the cash forecast counts money that is not collectible for months. Track it as its own balance. If nobody can answer "how much of our AR is retention" in one place, you are forecasting fiction.

Pay-when-paid. Where a subcontract conditions your payment on the prime's receipt, your collection timeline is partly the prime's collection timeline. That is a fact to price and plan around, not to argue with mid-project. Ask about payment terms and the prime's own billing cycle before signing, and align your invoicing to their cycle — an invoice that misses the prime's monthly pay application by two days waits a full extra month.

Open compliance findings can gate payment too. Agencies inspect the work they are paying for on a defined cadence — TxDOT directs its district responsible person to perform formal inspections of all traffic control devices twice a month at approximately two-week intervals, with at least one at night after initial setup on overnight projects, and deficiencies corrected per the department's form. A finding that has been fixed in the field but never closed on paper reads, to whoever is approving your pay application, as an open finding. Close findings with dates, in the same place the ticket lives.

Certified payroll can gate payment. On projects subject to Davis-Bacon or a state prevailing wage law, wage determinations set minimum rates and fringe amounts by classification and locality, published and searchable through the federal wage determinations lookup on SAM.gov. Where certified payroll submission is a condition of payment, a late or non-conforming report holds your money regardless of the quality of your work. See certified payroll for traffic control contractors.

Make the payer's job easy

A useful reframe: your invoice is a task on someone else's desk, and it competes with other tasks. Anything that makes it harder to approve pushes it down the pile.

Practical consequences:

One customer, one invoice. Separate labor and rental invoices for the same customer and period create reconciliation work for the payer. Present both clearly on one document where the contract allows.

Reference what they reference. Purchase order number, project number, permit number, the prime's job number — whatever their system keys on. An invoice they cannot match to a project is an invoice they cannot code.

Attach the substantiation. The signed tickets should travel with the invoice, not wait to be requested. A payer who has to ask for backup has already decided to look at it skeptically.

Send it to the right person. This sounds trivial and accounts for a startling share of aging. Confirm the billing contact at contract signing and again if the project team changes.

The measurement that changes behavior

Track two numbers monthly:

Days from work completion to invoice issued. This is entirely yours, and it is usually the largest single component of days-sales-outstanding in this trade. Most companies have never measured it and are surprised by it.

Percentage of invoiced amounts disputed or short-paid. This measures substantiation quality. If it is not near zero, the field record is the problem, not the collections process.

Both improve from the same change: the invoice being a rendering of a signed field record rather than a reconstruction assembled later. That is also what makes accounting integration behave — the seam between operations and the ledger is covered in QuickBooks and traffic control software.

If your receivables aging has a long tail you cannot explain, bring it and one disputed invoice to a walkthrough. The disputed one usually explains the tail.