08 Jun 2026 Cash, AR, and Retainage: Why Profitable Contractors Still Feel Cash Pressure
Many contractors know what their margin looks like.
Far fewer have equal clarity on what is happening to cash.
That gap matters.
A company can show profit on paper and still feel constant working capital pressure if receivables age, retainage stacks up, disputes linger, or billing follow-up slows down.
That is why a strong Monthly Job Review should not stop at forecast, WIP, and job cost. It should also include a clear look at AR, retainage, and cash conversion.
Why this matters
Cash pressure usually does not appear out of nowhere.
It often builds gradually through issues like:
-
- delayed pay applications
- incomplete billing support
- unresolved change orders
- disputed invoices
- slow collections follow-up
- or large retainage balances concentrated across a few jobs
Those are not purely accounting problems.
They are operating issues with financial consequences.
That is why AR and retainage should be part of the job story.
What AR is really telling you
Open AR is not just a number on an aging report.
It can help leadership understand:
-
- whether customers are paying in line with expectations
- whether disputes are emerging
- whether billing is clean and timely
- whether approved work is converting into cash
- and where follow-up needs to happen now
The key is not just knowing the total AR balance.
The key is understanding:
-
- what is current,
- what is aging,
- what is disputed,
- and who owns the next step.
Why retainage deserves more visibility
Retainage is often treated as “normal” in construction.
And in many cases, it is.
But normal does not mean risk-free.
Retainage can quietly become a cash strain when:
-
- it is concentrated across too many jobs
- release requirements are not tracked carefully
- project closeout drags on
- punch list or documentation issues delay release
- or leadership underestimates how much cash is tied up
That is why retainage should be reviewed intentionally, not just accepted as a static balance.
What leadership should want to know
A useful AR/retainage discussion should answer:
-
- What open AR exists by job?
- How much is current vs aging?
- How much retainage is outstanding?
- What amounts are disputed or blocked?
- What action is required this month?
- Who owns that action?
That turns the conversation from “cash is tight” into something more manageable:
“Where exactly is cash getting stuck?”
Common causes of cash friction
Several patterns show up repeatedly:
Billing is behind production
The work has been done, but the application has not gone out or is incomplete.
Change orders are unresolved
Revenue may be forecasted, but the billing support is not yet there.
Documentation is weak
Backup, approvals, lien waivers, closeout items, or other paperwork may be slowing payment.
Collection follow-up is unclear
The balance is known, but ownership of the next step is vague.
Retainage release is not actively managed
Cash is sitting in the job, but no one is driving release timing.
Red flags to watch
A few warning signs usually show up before cash pressure becomes more serious:
AR aging rises month after month
That often signals a billing, dispute, or follow-up problem.
Large balances sit in one customer or one job
Concentration creates risk quickly.
Retainage grows, but closeout plans are vague
That may mean cash will stay tied up longer than expected.
The same disputed items appear every month
That usually means the issue is not being resolved, only tracked.
Teams know the balances, but not the next action
Visibility without ownership does not move cash.
What a useful AR/retainage view should include
A practical monthly view should show:
-
- job
- customer
- billings to date
- open AR by aging bucket
- retainage outstanding
- disputed amounts
- next action
- owner
This gives leadership a working tool, not just a report.
Final thought
Profit matters.
But profit only becomes useful operating capacity when it turns into cash.
That is why AR and retainage deserve a standing place in the Monthly Job Review process.