TL;DR (60 seconds):
Most residential developers we meet track "percentage invoiced" instead of retention held and released. They know exactly how much they've billed clients, but the money still sitting with those clients? That stays buried in job costings until someone...
Most residential developers we meet track "percentage invoiced" instead of retention held and released. They know exactly how much they've billed clients, but the money still sitting with those clients? That stays buried in job costings until someone specifically digs it out.
Retention held and released matters because it separates work you've done from money you can actually spend. According to NetSuite's construction guide, retainage typically withholds 5% to 10% of payments until project completion. For a developer completing $5 million in homes annually, that could mean $250,000 to $500,000 sitting with clients at any point.
The percentage invoiced figure treats that withheld money as if it's in your account. It isn't. When cash flow planning relies on invoiced amounts rather than actual collections, developers consistently overestimate available funds. Projects get delayed waiting for payments that were "due" weeks ago but are actually held until final completion.
We'll examine what retention tracking actually costs developers, why percentage invoiced creates planning gaps, and the specific retention metrics that show real cash position. The goal is identifying whether better retention visibility would return enough to justify changing how your team tracks project progress.
Most developers this affects us have between 8 and 40 active projects running simultaneously.
The number you already trust
Percentage of completion is the metric most residential developers rely on instead of tracking retention held and released separately.
This makes sense. When you sell a $450,000 home and collect $400,000 upfront with $50,000 held back until final inspection, percentage of completion tells you how much of that withheld amount you have actually earned through work performed.
According to EY's guidance for homebuilders, developers using Accounting Standards Codification 606 recognise revenue as performance obligations are satisfied over time. Your percentage of completion drives revenue recognition, which directly affects the portion of retention you can claim as earned.
The appeal is obvious. One number captures both progress and money. At 75% completion on that $450,000 home, you know you have earned 75% of the total contract value, including 75% of the $50,000 retention held back. The arithmetic is clean: $37,500 of that withheld sum now belongs to you as earned revenue, even though you cannot collect it yet.
This works because most retention arrangements are straightforward. According to NetSuite's retainage guide, retention typically represents 5% to 10% of contract value, withheld uniformly across all work phases. When retention is a flat percentage held against the entire project, percentage of completion multiplied by total retention gives you the earned amount.
Why it works most of the time
The substitute succeeds when retention terms mirror project progress. On single-family homes with standard retention clauses, this alignment holds reliably.
Consider a $500,000 home with 5% retention held back. At 60% completion, percentage of completion suggests $15,000 of the $25,000 retention is earned. If retention terms are uniform across all work phases, this calculation reflects reality. You have completed 60% of the scope, so 60% of all withheld amounts should be available for release upon request.
The method also works when retention percentages stay constant throughout the project. [Beancount's analysis of custom home builder accounting](https://beancount.io/blog/2026/06/02/residential-general-contractor-custom-home-builder-book
Where the two disagree
The divergence appears when retention release schedules slip whilst project completion milestones hit on time. The substitute metric - typically completion percentage or units handed over - shows steady progress. The actual retention position deteriorates as clients delay final inspections, dispute punch list items, or invoke warranty holdbacks beyond the standard release schedule.
The mechanism behind the gap
Retention held and released operates on two distinct timelines that completion-based metrics cannot capture. The first timeline tracks project milestones: practical completion, certificate of occupancy, and handover. The second timeline governs retention release: initial release at completion, partial release after defects liability periods, and final release after warranty expiry.
According to FASB guidance on retainage presentation, retainage represents amounts earned but not yet collectible, creating a timing difference between revenue recognition and cash collection. The substitute metric conflates these timelines by assuming retention release follows completion automatically.
The aggregation error compounds across multiple projects. A developer completing 10 units monthly might show 100% project delivery whilst retention release stalls on older completions. The completion metric averages current performance with legacy collection issues, masking the deterioration. Each delayed release carries forward into subsequent months, creating a growing gap between reported progress and actual cash position.
Double-counting occurs when developers track both gross revenue at completion and net revenue after retention adjustments. The completion percentage reflects gross billing, whilst cash flow depends on net collections. NetSuite's construction retainage guide confirms that typical retention withholding ranges from 5% to 10% of contract value, meaning this timing difference affects substantial sums.
The mechanism breaks further when clients dispute completion quality. A unit marked 100% complete for internal reporting might trigger retention holdbacks pending remedial work. The substitute metric shows delivery; the retention balance shows collection risk. Both readings derive honestly from the same underlying position - the unit is complete enough to hand over but not complete enough to release retention.
Warranty obligations extend the divergence. Construction retainage often includes warranty holdbacks lasting 12 to 24 months beyond practical completion. The completion metric reaches 100% at handover; retention release waits for warranty expiry. The developer has delivered the product but cannot access the cash.
How long the gap can hide
The lag between divergence starting and detection depends on the developer's reporting frequency and retention release schedules. Monthly completion reporting masks retention delays for up to 90 days - the typical period between practical completion and first retention release.
Quarterly financial reviews extend this invisibility. A retention release scheduled for month-end but delayed into the following quarter appears as a timing difference, not a collection problem. The 50-state survey of retainage statutes shows significant variation in statutory release requirements, making delays harder to distinguish from normal process variation.
The detection lag worsens with project overlap. Developers running concurrent builds cannot isolate retention delays on individual projects from aggregate cash flow reporting. New project deposits mask retention collection shortfalls from completed work, creating artificial liquidity that postpones recognition of the underlying problem.
Warranty-related retention extends the hiding period to 12 to 24 months. [Beancount's analysis of construction accounting](https://beancount.io/blog/2026/06/02/residential-general-contractor-custom-home-builder-bookkeeping-section-460-percentage-of-completion-completed-contract
Which one to act on
Use retention held and released for operational decisions. Use net receipts for cash flow planning.
The decision rule is straightforward: if you are deciding whether to start a project, hire staff, or commit to materials, retention held and released tells you what each unit will generate. If you are managing working capital, servicing debt, or timing distributions, net receipts shows what hits the bank.
According to FASB guidance on Topic 606, retainage represents earned revenue that contractors must present as a receivable, not deferred income. This accounting treatment reflects the economic reality: retention held is money you have earned but cannot yet collect.
Most residential developers we encounter manage their businesses around net receipts because it feels safer. They see $450,000 hitting the bank on a $500,000 project and plan accordingly. But this creates two operational problems.
First, they systematically underprice. When you think in net receipts, a $500,000 project that costs $425,000 to build looks like it generates $25,000 on $450,000 of work. That is a 5.6% margin. The actual margin is 15% on the full contract value. Price the next project at a 5.6% margin and you lose money.
Second, they under-invest in capacity. If your business generates what looks like $25,000 per unit but actually generates $75,000 per unit, you will hire too few project managers, buy too little equipment, and pass on deals you should take.
The operational change is simple but requires discipline. Track both numbers but make decisions on retention held and released. When evaluating a new project, calculate margins on the full contract value. When planning staff levels, use the full value per unit to determine how many units justify another hire. When setting prices for the next quarter, work backwards from the margin you need on retention held and released, not net receipts.
The exception: if your retention release rate falls below 85% of amounts due, or if release typically takes longer than 120 days after practical completion, net receipts becomes the safer planning number. At that point, retention is more like a contingent asset than a reliable receivable.
According to [EY's guidance on ASC 606 for homebuilders](https://www.ey.com/content/dam/ey-unified-site/ey-com/en-us/technical/accountinglink/documents/ey-tl02740-161us-12-04-2020.
Next Steps
Using percentage of completion without tracking actual retention creates a growing blind spot that compounds with each project.
Start by separating these two numbers in your next project review. Calculate what you've earned under percentage of completion, then subtract what clients are actually holding back under retention terms. The difference shows money you've recognised as revenue but cannot collect until project completion.
Track this gap monthly. If it represents more than 15% of your working capital, you need better cash flow forecasting. According to FASB guidance on retainage presentation, construction contractors must properly classify retention receivables to avoid misleading stakeholders about liquidity.
Test your current system: can your bookkeeper produce both figures within an hour? If not, your project accounting is missing a critical control. Most developers discover they have been systematically overestimating available cash, particularly when multiple projects reach substantial completion simultaneously.
The 50-state survey of retention statutes shows retention terms vary significantly by location and project type, making manual tracking increasingly unreliable as you scale.
We help residential developers build systems that automatically track both completion percentages and retention terms, showing exactly when cash will actually arrive. If this cash flow blind spot is costing you more than $2,000 monthly in financing or missed opportunities, book a free 20-minute diagnosis at autospark.ai.
About AutoSpark
AutoSpark helps established small and mid-sized businesses find the one place AI or automation is genuinely worth applying, then builds and deploys it. The method is plain: interview the people doing the work, find where work repeatedly gets stuck, rank the problems by what they cost, and only build when the maths shows a clear payback.
AutoSpark is led by Patrick Nesbitt, a CA(SA), CFA and former private-equity investor, so AI is treated as an investment rather than a trend. Not an AI audit. Not a transformation programme. A short, evidence led diagnosis of where the money is leaking and what fixing it returns.
Start here: autospark.ai