Construction AR aging report: prioritize collections by payment blocker

Why construction collections needs more than an aging bucket

In its June 2026 report announcement, Billd says its survey covered more than 600 subcontractors, suppliers and GCs. Subcontractors reported an average 51-day wait after submitting a pay application, while GCs estimated 35 days. The company also reported that 83% of subcontractor owners worried about cash flow. These are vendor-sponsored survey findings about respondents, not a census, a universal payment term or a benchmark for every contractor.

That difference in perspective matters to a collections team. Your customer may believe a payment is moving while your office still has no receipt. A useful report shows the last verified event, the open question and who can answer it. An invoice date and a red overdue label cannot explain whether the package was returned, approved for less, scheduled or actually paid.

Sources: Billd: June 23, 2026 National Subcontractor Market Report announcement

Which dates should a construction AR aging report use?

Keep invoice date, submission date, accepted-package date, contractual due date and days past due in separate fields. Your accounting report may age by invoice date; your collections worklist may also need contractual days past due. Name both measures so a 45-day-old invoice with net-60 terms is not described as 45 days late.

When a due date depends on acceptance or another contractual event, retain the event evidence and the reviewed rule used to determine the date. If the event is unknown, mark the due date unverified and assign someone to investigate. Do not change the invoice date to make an old balance look current. Preserve the original record when a corrected package is submitted.

The fields that turn AR aging into a collections worklist

Use one row per open billing item, with a separate allocation when part of the balance needs different treatment. Keep the accounting identifier stable across emails, portal records and spreadsheet exports. An unrelated change request should not share an invoice row simply because it belongs to the same job.

The blank CSV accompanying this guide is a working register, not an accounting subledger. Refresh balances from the authorized ledger, record the extraction date and reconcile the total. Assign a named collection owner even when another person must approve the commercial decision.

Worked example: $120,000 of AR is not one collection problem

Assume a fictional ledger has $120,000 open across four items. Job A has $45,000 of approved progress billing, 18 days past its verified due date, and a missed payment promise. Job B has $30,000 in a package returned for one missing attachment; its due-date trigger remains under review. Job C has $25,000 of retainage whose release condition is not yet met. Job D has $20,000 open, including a documented $5,000 disputed deduction.

The four balances reconcile to $120,000. The immediate follow-up questions concern $45,000 on A and the $15,000 not identified as disputed on D, subject to confirming payment entitlement. That $60,000 is an action category, not a cash forecast or a write-down of the remaining balance. B needs a corrected package; C needs a release plan; the $5,000 dispute needs a commercial decision.

At the next meeting, ask whether A produced a new dated commitment, B received the attachment, C reached its release milestone and D identified a payer for the requested $15,000. Each row now has a different success condition. Sending the same reminder for all $120,000 would hide the work required to move it.

How should the team prioritize collections?

Check time-sensitive contractual notices and legal-rights reviews before sorting by invoice amount. A small balance approaching a verified notice deadline can need attention sooner than a larger balance with a reliable payment commitment. Have the qualified reviewer establish the applicable deadline; the aging bucket does not create one.

Next review broken promises, large overdue approved balances and customer concentration. A customer with six moderately late jobs can expose more cash than a single visibly old invoice. Include remaining committed work in the credit conversation, while keeping it separate from booked AR. The owner should understand how much more cash the next phase requires.

Run a weekly meeting around decisions

Before the meeting, reconcile the list, attach the latest responses and flag changed balances. Use the meeting to decide who will obtain approval, resolve a deduction, confirm payment release or review further exposure. Reading every row aloud adds little when the owner can already see the data.

Finish each selected item with an action, owner and checkpoint. Record why a balance was deferred. Review yesterday’s promised receipts against applied cash before forecasting tomorrow’s. A caller saying that a check was sent is evidence of a statement; accounting still needs to locate and apply the funds.

Measure collections progress without confusing activity with cash

Track overdue progress balance, disputed balance, retainage awaiting release, promises due and promises kept. For the promise-kept rate, define the population in advance: for example, commitments due in the week with the agreed funds received by the checkpoint. Separate commitments with no specific amount or date rather than marking them successful.

DSO can be useful when accounting defines AR, credit revenue and the period consistently. It can also move with seasonality, growth and retainage. Review the construction-specific categories beside it. Twenty reminders sent and ten replies received may demonstrate effort, but neither number establishes collection performance.

Use follow-up support to collect the missing status

Buildalytic offers construction payment-status follow-up. A useful demonstration starts with a reconciled open item and shows how the designated recipient’s response becomes a source-linked next step. Check the supported handoff before assuming the tool can update your accounting system.

Keep write-offs, disputes, settlements and legal notices with the authorized people. The practical outcome is a clearer worklist and fewer unanswered status questions. Test the workflow on both a clean payment promise and a returned package so the team can inspect how unresolved exceptions remain visible.

Sources: Buildalytic: Construction payment follow-up