CONSTRUCTION BILLING VELOCITY
Billing velocity is the cycle time from work completion to cash receipt — pay app cutoff to ACH deposit. Most subcontractors run a 75–105 day billing cycle without knowing it, and most assume the cycle is determined by the GC’s pay terms. It isn’t. About 30–50% of typical billing cycle time is inside the sub’s control: pay app preparation time, documentation completeness, submission timing, and AR follow-up cadence. Tightening these four bottlenecks compresses cycle time by 15–30 days — freeing 15–30% of working capital without raising prices, winning new work, or changing customer relationships.
The GC’s pay terms set the floor. Your billing velocity sets the actual cycle. Most subs operate 15–30 days above the floor without realizing it.
BILLING VELOCITY DEFINED
Billing velocity measures the elapsed time from when billable work is performed to when cash is received against that work. For pay-application work, the cycle starts at pay app cut-off date and ends at ACH receipt date. For T&M and emergency work, the cycle starts at work completion and ends at customer payment receipt. For stored materials, the cycle starts at material delivery to staging and ends at billing recognition plus payment.
Most subcontractors don’t measure billing velocity at all. They measure days sales outstanding (DSO) as a single annualized number, which tells them roughly how long their receivables run but doesn’t surface where the cycle time actually accumulates. The fix is breaking the cycle into segments and measuring each one separately.
WHERE THE TIME ACCUMULATES
WORK PERFORMED TO PAY APP CUT-OFF
The pay app cut-off date is contractual (usually the 25th of the month for work performed through that date). Work performed after the cut-off rolls into next month’s pay app. Most subs don’t actively manage which work bills in which month, so end-of-month push work gets billed in the wrong cycle and produces a 30+ day delay before recovery. Aggressive cycle management means pushing eligible work into the current cut-off and letting tomorrow’s work bill on tomorrow’s cycle.
CUT-OFF TO PAY APP SUBMISSION
From cut-off date to pay app delivered to GC. This segment ranges from 3 days (disciplined billing team) to 20+ days (busy PM with no billing cadence). Cut-off to submission delay compounds across every pay app, every project. A 14-day delay on a $400K monthly pay app is roughly equivalent to a $200K interest-free loan to the GC every cycle. Most subs don’t see it as a loan; they see it as administrative slowness.
SUBMISSION TO GC APPROVAL AND PAYMENT
This is the segment most subs assume is fixed by GC pay terms. It’s actually variable based on documentation completeness. Pay apps submitted with complete waivers, properly executed change orders, accurate SOV billing, and signed compliance documents process at the contractual cycle. Pay apps with incomplete documentation kick back for revision, adding 15–30 days per kickback. Most subs experience kickbacks regularly and treat them as normal friction; they’re actually cycle time compounding.
RETENTION HOLD AND RETENTION RELEASE
Retention at 5–10% sits unpaid until project substantial completion. Retention release requires additional documentation (lien waivers, warranty package, as-builts, closeout paperwork) and active pursuit. Most subs treat retention as "money that will eventually arrive" without an active workflow for documentation and pursuit. Retention release that should take 30–60 days post-completion routinely takes 6–14 months when nobody owns the workflow.
WHAT VELOCITY IS WORTH
The financial value of billing velocity compression is direct and large. A $5M subcontractor with average receivables turning at 75 days has $1.03M of working capital tied up in AR. Compressing the cycle to 60 days drops working capital tied up in AR to $822K — a $208K reduction in capital requirement. The cash that was tied up returns to operating availability and stays there.
Compressing the cycle by 15 days requires:
- Pay app preparation cadence: Cut-off to submission compressed from 14 days average to 4 days average. Net savings: 10 days.
- Documentation completeness: Kickback rate reduced from 1 in 4 pay apps to 1 in 20. Net savings: 5–7 days per cycle averaged across all pay apps.
- Retention pursuit: Active retention release workflow instead of passive waiting. Net savings: 3–6 months on retention release timing (compounds across the AR aging).
None of this requires raising prices, winning new work, or changing customer relationships. It’s pure operational discipline applied to billing and collections.
HOW VELOCITY GETS BUILT
Building a billing velocity system requires three operational components: cadence, documentation discipline, and active AR management.
- Cadence: Pay app preparation begins on the cut-off date with a written checklist per project. Submission target is 5 business days post cut-off. Weekly billing review on Mondays covers what got submitted, what’s outstanding, and what’s upcoming.
- Documentation discipline: SOV billing rounded to whole percents, signed change order log maintained per project, lien waivers prepared with each pay app, compliance documents tracked against contract requirements. Documentation kickbacks become rare events instead of routine friction.
- Active AR management: AR aging worked weekly with direct phone follow-up on items over 45 days. Retention tracked separately on its own aging schedule with active pursuit at substantial completion. Operations and finance share responsibility for collections; PMs aren’t left to handle it alone.
The system isn’t complicated. It’s just rarely implemented. Most subs have functional billing (pay apps get submitted, payments get received) but no billing velocity discipline (the cycle takes whatever time it takes). Adding the system structure compresses cycle time within the first 60–90 days of operation.
FREQUENTLY ASKED
