- How to Use Progress Billing Analytics to Spot Cash Flow Gaps
- 1. Track Billing and Collections for Each Job
- Identify Overdue Invoices and Track Retainage Separately
- Compare Expected Cash Receipts Against Upcoming Payments
- Connect Billing, Approvals, and Payment Records in One System
- FAQs
- Related Blog Posts
Oh wow! A $80,000 profit on a $500,000 project.
You have every reason to throw a party and email everyone a short heartfelt thanks for being the best team ever… but come Friday, accounting informs you that there’s not enough cash to cover payroll.
What the what?
How is that even possible?
Here what probably happened: you’ve earned $500,000 in revenue, but your client has paid only $300,000.
Meanwhile, you’ve already paid $350,000 to workers, suppliers, and subcontractors. The rest is tied up in outstanding invoices and retainage, neither of which is particularly useful when your crew expects actual paychecks rather than an enthusiastic presentation about projected profits.
It’s an impressive financial achievement: running a profitable project while struggling to pay the people who made it profitable. Your accounting reports insist you’re doing wonderfully, which must be reassuring to everyone except the person responsible for payroll.
This is where progress billing analytics come in.
By separating work earned, amount billed, payment approved, and cash collected, you can see exactly where your money is getting held up instead of treating every dollar of recorded revenue as though it’s already in your bank account.
When integrated with your construction ERP, these figures give you a clearer view of upcoming cash shortages, helping you address billing delays and plan payroll.
In this article, we’ll show you how to use progress billing analytics to stay ahead of cash shortages instead of discovering them on payday.
How to Use Progress Billing Analytics to Spot Cash Flow Gaps
1. Track Billing and Collections for Each Job
Company-wide revenue totals often hide cash pressure at the project level. Two jobs can have the same contract value and the same cumulative billings, yet carry very different cash risk based on how much cash has cleared from each job. For that reason, job-level billing data is the first direct test of actual cash position.
Billing and Collection Fields Worth Tracking by Project
Each project should track the full billing cycle: contract value, change orders, budget and committed costs, schedule-of-values progress, invoice dates, approval status, amounts billed, amounts collected, retainage, and disputes.
In cash-flow analysis, those fields serve three different functions:
- Billing capacity – original contract value, approved change orders, revised contract value, cost budget, committed costs, actual costs, and estimated cost to complete
- Cash collected – schedule-of-values percent complete, invoice submission date, approval date, contractual due date, payment terms, current billing, cumulative billed amount, approved amount, and payments collected
- Cash still at risk – open balance, disputed amount, retainage held, payment date, days outstanding, aging bucket, promised date, collection owner, dispute reason, and next follow-up date
For reporting purposes, billed should mean submitted, and collected should mean cleared payment.
Billed vs. Collected by Job
The clearest view comes from comparing billed amounts with cleared cash. Open balance shows what remains unpaid:
Open Balance = Cumulative Billed Amount − Payments Collected
That balance should be separated into approved but unpaid amounts, disputed amounts, and retainage held. Each category reflects a different source of delay and calls for a different collection action.
Consider two jobs with the same $500,000 contract value and $300,000 in cumulative billings. The Maple Office Renovation has collected $285,000, leaving a $15,000 open balance, including $12,000 in retainage. The Riverfront Warehouse has collected only $180,000, leaving a $120,000 open balance, including $18,000 in retainage. The $105,000 difference should be traced to approval delays, missing backup, billing errors, disputes, or late payment.
Job-Level Metric Table
The metrics below identify the numbers that matter most and the reason each affects cash.
| Metric | What It Measures | Cash-Flow Purpose |
|---|---|---|
| Contract value | Total authorized project value | Establishes billing capacity |
| Revised contract value | Original contract plus approved changes | Prevents billing against outdated contract figures |
| Budget and committed cost | Planned and obligated job spending | Shows near-term cash needs |
| Percent complete | Physical progress by schedule-of-values item | Checks billing against actual field progress, not just project estimates |
| Cumulative billed amount | Total invoiced to date | Measures work converted into receivables |
| Approved amount | Portion accepted by the owner or payer | Separates collectible billing from pending review |
| Collected amount | Payments received to date | Shows actual cash inflow |
| Open balance | Billed amount minus payments collected | Identifies unpaid receivables |
| Disputed amount | Billing under challenge | Highlights delayed or uncertain cash |
| Retainage held | Contractual amount withheld | Identifies cash delayed until a milestone or completion |
| Invoice age | Time elapsed since the contractual due date | Prioritizes collection follow-up |
| Payment date | Date cash was received | Helps forecast receipts |
sbb-itb-5eea312
Identify Overdue Invoices and Track Retainage Separately
Once open balances are visible, aging shows which receivables are actually slowing cash collection.
An open balance on a progress billing does not, by itself, indicate a collection issue. The difference is whether the balance has passed its contractual due date. Aging reports based only on invoice dates can distort cash risk. They may treat a normal approval cycle as late, or hide invoices that have moved beyond stated payment terms.
How Aging Buckets Expose Collection Delays
Aging separates routine processing time from late payment, but only when each invoice is measured against its contractual due date rather than its issue date. A pay application submitted on July 25 with Net 30 terms is due on August 24. On August 20, that invoice remains current. On September 10, it is 17 days past due and belongs in the 1–30-day bucket. That distinction affects cash planning because construction payment cycles are already extended. A 2025 report covered by Construction Dive found that subcontractors waited an average of 56 days after submitting a pay application to receive payment, while general contractors estimated payment arrived in roughly 30 days. Aging should be measured from the contractual due date, not the submission date, so normal processing time is not confused with late payment.
Each aging bucket should trigger a defined internal action tied to expected cash receipt and the effect on payroll, vendor payments, and subcontractor draws. The table below links each bucket to its cash-flow concern and the review action it should trigger.
Why Retainage Needs Its Own Tracking Line
Retainage is cash withheld under the contract. Overdue invoices are payment delays. When both appear in the same aging report, the result is a distorted view of collection risk and an unreliable cash forecast.
Retainage often ranges from 5% to 10% of contract value, depending on the contract and jurisdiction. Its release is controlled by contract terms, not standard payment terms. For that reason, retainage should be tracked separately from ordinary receivables aging.
A retainage tracker should include separate fields for retainage billed, retainage held, retainage released, retainage remaining, the contractual release condition, expected release date, actual release date, and any missing closeout documents. In the cash forecast, retainage should appear as its own category: earned, but still contractually withheld. It should not be folded into standard aging. If a project reaches substantial completion and the expected retainage release date passes without payment, that balance should be flagged for active follow-up and moved into a delayed-release category.
Aging Review Table for Collection Follow-Up
The table below maps each aging bucket to its cash-flow concern and the internal review action it should trigger. Retainage is listed separately because contractual holdbacks require a different response than overdue progress billings.
| Aging Bucket | Cash-Flow Concern | Review Action |
|---|---|---|
| Current | Not yet due | Confirm invoice receipt, approval status, and required backup documents |
| 1–30 days past due | Minor administrative or approval delay | Verify the invoice was received; check for missing lien waivers or corrections requested |
| 31–60 days past due | Approval hold, funding delay, or dispute may be restricting cash | Identify the specific blocker; assign an owner and resolution deadline |
| 61–90 days past due | Delay may affect payroll, vendor payments, or subcontractor obligations | Escalate to project and finance leadership; revise the cash forecast |
| Over 90 days past due | Elevated collection uncertainty; possible cash shortfall | Perform a formal risk review; keep uncertain cash out of near-term commitments |
| Retainage held, not yet due | Retainage held; not yet releasable | Track the release condition, expected release date, and outstanding closeout documents |
| Retainage past contractual release date | Potential delay in retainage release | Verify completion status, closeout submissions, lien waivers, and payment disbursement |
When aging shows a delay, the next step is to centralize the invoice, backup documents, and ownership in one system.
Compare Expected Cash Receipts Against Upcoming Payments
Once aging identifies late receivables, payment-gap analysis shows whether those delays will affect payroll or vendor payments before the next check run. A payment gap is the cash still required to cover a project’s near-term obligations after expected collections are applied. Those obligations include payroll, subcontractor draws, material invoices, equipment costs, and taxes. When the result is a positive number, project cash outflows exceed collections, and the shortfall must be covered by other cash within the business.
Patterns That Signal a Cash Shortfall Is Forming
The earliest sign is often a growing gap between completed work, billings, and collections. For example, $200,000 of completed work, $150,000 billed, and $90,000 collected leaves a $60,000 cash gap before unbilled work is considered.
Other patterns that often appear before a shortfall include:
- Billings increase while collections remain flat
- Open receivables become concentrated in one customer or project
- More balances move into older aging buckets
Retainage can make collections appear weaker than they are, but it does not provide near-term cash.
Key Indicators to Review Each Billing Cycle
These indicators should be reviewed each billing cycle to identify cash pressure before it reaches operations.
| Indicator | What It Measures | Why It Matters |
|---|---|---|
| Billed-to-collected % | Cash collected ÷ amount billed × 100 | A declining percentage across consecutive cycles indicates invoices are not converting to cash |
| Open receivables by project | Unpaid balance per job and customer | Identifies which projects carry the most collection risk |
| Past-due amounts by aging bucket | Overdue balances in 1–30, 31–60, 61–90, and 90+ day ranges | Shows whether delays are isolated or spreading across jobs |
| Retainage as % of unpaid receivables | Retainage ÷ total open receivables | A high percentage may explain slower collections but should not hide ordinary past-due invoices |
| Cash receipts vs. near-term obligations | Expected collections vs. payroll, vendor, and subcontractor payments due in the next 7, 14, and 30 days | The most direct test of whether cash will cover upcoming commitments |
| Days sales outstanding (DSO) | Average collection time | Rising DSO with steady billing volume indicates slower collections |
For example, if a project billed $120,000 and collected $72,000, its billed-to-collected percentage is 60%. Whether that result is acceptable depends on the composition. A 60% rate driven mainly by contractual retainage presents a different risk than a 60% rate driven by invoices that are already past due.
Cause-and-Response Checks for Delayed Cash
Finding a gap is only the first step. Each delayed balance should be assigned a specific cause because the right response depends on what is holding up the cash.
| Warning Sign | Likely Cause | Next Review Step |
|---|---|---|
| Invoice past due, no payment received | Missing backup documents or lien waiver | Confirm required documentation and resubmit the complete package |
| Payment application submitted but not approved | Unapproved application or correction requested | Identify the approver, the missing item, and the expected approval date |
| Billed amount exceeds approved contract value | Unresolved change order | Separate approved base-contract billing from amounts awaiting owner authorization |
| Partial payment received, balance disputed | Disputed line item | Document the specific scope in question, the undisputed amount, and the escalation date |
| Unpaid balance stays open without aging movement | Retainage still held under contract terms | Record the contractual release condition and forecast the release date separately from ordinary collections |
If $83,000 in payroll and vendor payments are due within 14 days and only $50,000 in cash is expected, the project has a $33,000 funding gap. That condition should trigger collection escalation and a payment-timing review before bills become late.
Connect Billing, Approvals, and Payment Records in One System
Disjointed billing, approval, and payment records can hide overdue invoices until payroll is exposed. Centralized construction management software connects contract records, billing activity, payment status, and supporting documents in one workflow, so billed-versus-collected comparisons rely on a single project record. Job-level billing and aging data then become usable in one place.
A Practical Workflow from Contract Setup to Payment Tracking
The workflow begins with the contract record before the first invoice. Contractor Foreman stores and updates the schedule of values, retainage, billing terms, and approved change orders as the project progresses. The office receives current field data rather than relying on scattered emails and spreadsheets.
As work advances, field updates such as completion percentages, installed quantities, and stored materials flow directly into payment application preparation. Office staff do not need to rebuild billing from field notes. Contractor Foreman centralizes schedule of values, retainage, QuickBooks integration, client portals, and mobile updates.
Why Supporting Documents Matter to Billing Analytics
Payment applications, approved change orders, daily or production records, delivery tickets, stored-material evidence, lien waivers, inspection records, and payment correspondence should remain tied to the project file and the specific invoice they support. When an invoice becomes overdue, staff can immediately determine whether the delay is tied to a missing lien waiver, an unapproved application, a disputed scope item, or incomplete backup.
Payment delays remain common in construction – subcontractors waited an average of 57 days to receive payment while funding labor and materials from the start of a project – and attached documentation speeds escalation and dispute resolution.
What Progress Billing Analytics Should Show Every Month
The monthly review should indicate which receivables can cover near-term payroll and vendor payments. That requires a project-by-project breakdown rather than a single company-wide summary.
Each job should show:
- billed amount
- collected cash
- open balance
- retainage held
- overdue balances by aging bucket
When a past-due balance and an upcoming payroll or vendor obligation appear side by side, cash risk becomes visible before obligations turn late. Accurate cash-flow reporting depends on current entries.
FAQs
What is the difference between billed and collected cash?
Billed cash is revenue invoiced for work that has been completed. Collected cash is payment that has been received and deposited.
The difference between the two creates a cash flow gap, often measured through Days Sales Outstanding (DSO). In construction, that delay matters because labor and material costs usually occur before client payments are received.
Why should retainage be tracked separately from past-due invoices?
Retainage should be tracked separately because it is money withheld under contract terms, not a late payment. Past-due invoices may indicate a collection issue, while retainage is a planned holdback, usually 5% to 10%.
Separating retainage from past-due receivables improves cash flow forecasting and helps prevent contractually delayed funds from being treated like unpaid debts requiring immediate follow-up.
How can progress billing data help prevent payroll cash shortfalls?
Progress billing data helps prevent payroll shortfalls by showing cash gaps before they become crises. When completed work is billed through a Schedule of Values with accuracy and consistency, revenue is more likely to keep pace with labor and material costs.
Contractor Foreman centralizes this information so projected cash inflows can be compared with upcoming payroll and vendor obligations. Real-time tracking of these metrics helps project managers and office staff identify potential deficits early and adjust financial planning before cash pressure affects operations.
Related Blog Posts
- How to Forecast Cash Flow for Construction Projects
- Progress vs. Milestone Billing: Key Differences
- Cash Flow Forecasting for Residential Contractors
- 7 Revenue Forecast Reports for Contractors
