A CFO’s Guide to Days Sales Outstanding in Construction

Approved work does not automatically translate into predictable cash. In construction, cash becomes difficult to forecast when the signals that determine payment readiness are spread across pay applications, waivers, compliance records, retainage, change orders, and approval workflows. Finance may see progress on paper while lacking a clear view of what is truly ready to become cash.

Days Sales Outstanding, or DSO, measures how long it takes to collect payment. In construction, it also reveals how clearly finance can see what is approved, what is blocked, and what still needs action before payment can move. The closer that visibility is to the live payment workflow, the more accurately finance can forecast cash timing, working capital needs, and liquidity.

Why DSO becomes unstable in construction

Construction creates more distance between approved work and collectible cash. In a standard Accounts Receivable model, finance issues an invoice and tracks payment against a due date. In construction, payment often depends on several steps between billing and release:

• a pay application is still under review
• a waiver is missing
• a compliance document has expired
• a change order has not yet been reflected in the billing record
• retainage is still holding back part of the amount due

That makes DSO harder to read at face value. Receivables can move into older aging buckets even when the customer is following the expected process, because billing and payment release are separated by more checkpoints. When those checkpoints are handled manually or across different systems, finance loses sight of what’s actually delaying cash.

That’s when forecast quality starts to weaken. Approved values, submitted pay apps, retained balances, blocked payments, and unresolved exceptions begin to blur together. Finance can still see activity, but it becomes harder to tell what’s collectible now, what’s being held back, and what action needs to happen before payment can move.

The DSO gap is a visibility gap

DSO becomes harder to control when finance cannot separate approved work from payment-ready cash. In construction, those are not the same thing.

Workflow stage	What finance needs to know	What becomes unclear when systems are disconnected
Pay application submitted	Whether the billing package is complete and under review	Submission quality, missing documents, and current review status
Pay application approved	Whether approved work is ready to move toward payment	Waiver, compliance, or exception holds that still block release
Change order activity	Whether billed values reflect the current contract position	Gaps between work performed, approved changes, and collectible amounts
Retainage tracking	How much cash is still contractually held back	The difference between earned value and near-term cash availability
ERP and reporting	What should appear in the financial record today	Lag between workflow activity and finance visibility

Finance decisions depend on timing as much as approvals. A project may show strong billed progress while collectible cash remains delayed by missing waivers, retained balances, or other unresolved conditions. When those constraints are difficult to see, DSO compresses multiple sources of delay into a single number.

A clearer payment record also helps finance diagnose where the drag is coming from, and ensures disconnected cost systems aren’t the cause of budget problems. 

Why DSO affects cash flow predictability

Forecasting becomes less reliable when payment records lose transparency. Finance may still see invoice volume, but volume alone doesn’t show what’s ready to collect, what’s being held back, or what still needs to happen before cash can move.

That uncertainty weakens the forecast. Working capital becomes harder to assess, short-term cash planning carries more risk, and borrowing decisions become harder to time with confidence. Margin can also come under pressure as teams spend more time resolving exceptions and tracing payment delays across projects.

For a CFO, this is where construction cash flow predictability starts to erode. Small delays at project level become portfolio-level noise when finance cannot identify obstacles to cashflow, determining whether the accumulation of older outstanding amounts (aging) are being driven by customer behavior, internal review lag, missing documentation, retainage, or unresolved change-order activity.

The controls that narrow the DSO gap

CFOs narrow the DSO gap by tightening the controls that determine when approved work is actually ready to convert into cash.

Standardized pay application submission

A consistent submission process reduces preventable delays at the front end. When pay apps arrive with the right values, supporting records, and required documentation, review can move faster and finance has a clearer view of what is truly in process. This is especially the case where AIA pay applications shape the billing workflow.

Visible approval status

Finance works better with current status visibility than with periodic updates. A live view of what is submitted, approved, blocked, or pending makes it easier to distinguish routine review timing from an issue that will delay cash conversion. That shared record also helps project and finance teams work from the same payment status instead of separate interpretations of the same activity.

Waivers and compliance tied to payment readiness

Aged receivables in construction often include amounts that are operationally approved but not yet ready to move because a waiver, compliance condition, or billing discrepancy is still unresolved. When those issues are visible in the workflow, finance can see what is held, why it is held, and what still needs action before cash can move.

Clear handling of change orders and retainage

Change-order lag and retainage can distort the relationship between billed work and near-term cash. Finance needs those categories treated clearly in the workflow so approved values, held balances, and collectible amounts do not blur together. That is especially important when forecasting by project or comparing billed progress against expected cash timing.

ERP-connected records and current reporting

The DSO gap widens when payment workflow data and finance records fall out of sync. ERP-connected reporting helps finance work from a current record of approved amounts, held amounts, and exceptions that still require action. That improves forecast quality because the financial view stays closer to the live payment process. 

Early visibility into payment blockers

A blocked pay app is easier to manage when the reason is visible early. Missing documents, mismatched values, or unresolved conditions should surface before they sit inside aging and distort the collections picture. Exception visibility is one of the most direct ways to reduce payment delays construction teams would otherwise carry into the forecast. 

What finance should monitor beyond headline DSO

While useful, Headline DSO is too broad to explain where predictability is breaking down. Finance needs supporting measures that show whether delay is coming from collections behavior or from the construction payment workflow itself.

The most useful metrics include:

• time from pay application submission to approval
• percentage of submissions blocked by waiver or compliance issues
• approved but unpaid amounts
• retainage outstanding by project
• approval exceptions by cause
• aging viewed in context with review status as well as invoice date
• discrepancies between approved values and billed values

These measures help finance isolate the source of delay. They also make forecast conversations more concrete. A rising DSO number on its own tells you there is drag somewhere. A view into blocked approvals, retained balances, and unresolved exceptions tells you where to act.

That level of visibility strengthens efforts to improve cash flow forecasting in construction because finance can separate timing issues from collections issues before both end up buried in the same aging report.

What to ask when evaluating a payment workflow platform

A CFO’s software questions should interrogate control and visibility.

Ask:

• Can finance see which amounts are approved, blocked, retained, or still pending?
• Are waiver and compliance conditions tied directly to payment status?
• Can project and finance teams work from the same live record?
• Can forecasting reflect payment readiness instead of invoice volume alone?
• Does the workflow reduce re-entry between payment operations and the ERP?

A platform that cannot answer those questions clearly will make days sales outstanding performance in construction harder to interpret, even when invoicing appears to move faster. Finance needs a record that supports decision-making at the point where approved work becomes payment-ready cash.

What DSO should tell finance leadership

DSO should help finance distinguish between delayed collections and delayed payment readiness. When approved work is still waiting on waivers, compliance clearance, retainage release, or exception resolution, the issue sits inside the payment process rather than in customer payment behavior.

That distinction improves decision-making. Finance can forecast cash with more confidence when it can see which amounts are collectible now, which are held back, and which still require action before payment can move.

See how GCPay helps finance teams improve cash flow visibility and payment control.

Book a GCPay demo

 

 

 

Frequently Asked Questions

What is Days Sales Outstanding in construction?

Days Sales Outstanding measures the average number of days it takes to collect payment after billing. In construction, the metric carries more complexity than it does in a standard invoice-and-payment model because cash timing can be affected by pay app review, waivers, compliance requirements, retainage, change orders, and approval status. That means DSO often reflects payment workflow conditions as well as customer payment behavior. For a CFO, the number is most useful when it is paired with visibility into what is approved, what is blocked, and what is still pending inside the workflow.

Why is DSO harder to control in construction than in standard accounts receivable?

Construction adds more checkpoints between billed work and collectible cash. A pay application may be approved while a waiver is still missing or a compliance document is still holding release of funds. Retainage can delay part of the amount even when work has progressed, and change-order timing can create gaps between approved work and billable status. These conditions make DSO harder to manage unless finance has clear visibility into payment readiness. Without that visibility, older outstanding amounts can reflect both customer payment timing and delay inside the workflow.

What causes DSO to rise even when work is approved?

Approved work does not always mean payment-ready cash. DSO can rise when approved amounts are still waiting on waivers, compliance clearance, unresolved exceptions, retainage release, or change-order alignment. It can also rise when finance cannot see which aged amounts are operationally blocked and which are truly outstanding for collections reasons. That distinction matters to a CFO because the response is different in each case. One calls for collections follow-up, while the other calls for tighter payment controls and better workflow visibility.

Which metrics should CFOs review alongside DSO?

DSO is more useful when it sits beside operational measures that explain where timing is slipping. The most important supporting metrics usually include time from pay application submission to approval, approved but unpaid amounts, retainage outstanding, exception volume by cause, missing-document holds, and aging tied to review status. Those measures help finance understand whether delays are driven by collections behavior or by payment-process conditions. They also improve forecasting conversations because the source of the delay becomes easier to identify and address.

What payment workflow controls improve DSO predictability?

The strongest workflow supports visibility at the point where approved work becomes payment-ready cash. That includes standardized pay app submission, clear approval status, waiver and compliance conditions tied directly to payment readiness, distinct handling of retainage and change orders, ERP-connected records, and early visibility into exceptions. Together, these controls improve construction accounts receivable visibility and make it easier for finance to see what is collectible now, what is held back, and what still needs action.