WIPBillingSurety

WIP Schedule Overbilling: How to Catch It Before Your Surety Does

By Kwabena Kesse, CPA · Founder, BuilderIQ Analytics · March 25, 2026 · 5 min read

Your Work in Progress schedule is the single most scrutinized document in a surety audit. And the #1 thing they look for? Overbilling.

Overbilling means you've billed your client more than the work you've actually completed. It's common, it's often unintentional, and if your surety finds it before you do, your bonding capacity gets reduced — or worse, your program gets cancelled.

What Is Overbilling (and Why Does It Happen)?

On any construction project, there are two numbers that should track closely:

Earned Revenue = Contract Value × Percent Complete
Billed to Date = Total invoices submitted to owner

When Billed to Date > Earned Revenue, you're overbilled. The gap is your overbilling exposure.

In Nevada, it happens in patterns that are specific to how work moves here:

Why Your Surety Cares So Much

From a surety's perspective, overbilling means:

Risk Signal: The contractor has already consumed future cash flow. If the project goes sideways, there's no billing cushion left to fund completion. The surety is on the hook.

A single project with significant overbilling triggers a deeper review. Multiple projects overbilled simultaneously can lead to substantial bonding program reductions — the financial hit isn't the correction itself, it's the capacity you lose at renewal.

How to Detect Overbilling on Your WIP

Step 1: Calculate Earned Revenue per Project

Earned Revenue = Contract Value × (% Complete / 100)

Use the cost-to-cost method (GAAP preferred): % Complete = Costs Incurred to Date ÷ Total Estimated Costs. Don't use the PM's subjective estimate — use actual cost data.

Step 2: Compare to Billed-to-Date

Over/Under Billing = Billed to Date − Earned Revenue

Step 3: Flag the Danger Zone

Rule of Thumb:
• Overbilling > 5% of contract value on a single project = Monitor
• Overbilling > 10% of contract value = Correct immediately
• Net overbilling across portfolio > $500K = Surety will flag on next audit

Hypothetical Example

Consider a fictional Nevada GC (composite based on typical industry scenarios) with 7 active projects on their WIP:

Desert Valley Terminal Expansion (public infrastructure, Clark County)
Contract: $22M | Billed: $7.2M | Earned: $6.16M (28% complete)
Overbilled by $1.04M — The PM front-loaded billing before summer heat slowdown. Surety audit risk if not corrected within 2 billing cycles.

Boulder Highway Hotel Renovation (private, Henderson corridor)
Contract: $18.5M | Billed: $8.2M | Earned: $7.03M (38% complete)
Overbilled by $1.17M — Change order for lobby redesign was billed in March, CO wasn't signed until May. Largest single-project exposure in the portfolio.

Combined overbilling: $2.21M across two projects. Both have Nevada-specific root causes — heat-driven billing acceleration and slow public agency CO approvals. This is exactly the pattern that triggers a surety program review.

How to Correct It

  1. Don't shock the cash flow. Reduce billing gradually over 2–3 pay applications. A sudden $1M reduction in a single billing cycle creates a different problem.
  2. Update percent complete monthly. Stale completion estimates are the root cause. If costs have progressed, update the WIP.
  3. Document the correction. Show your surety a plan: “We identified $1.04M overbilling on the terminal project. Adjusting next 2 pay apps by $520K each to normalize by Q3.” Sureties want to see you found it first and have a timeline.
  4. Automate the detection. Manual WIP reviews miss things. Automated tools flag overbilling the day it happens, not the month your surety audits.

That $2.21M Pattern Gets Caught on Day One

The GC in our example didn't discover the $2.21M overbilling until they manually rebuilt their WIP for the quarterly surety package. By then, two billing cycles had passed and the correction required a $500K+ reduction in a single pay app — exactly the cash flow shock they were trying to avoid.

BuilderIQ Analytics flags overbilling the day it appears. Upload your financials, and the platform computes earned revenue vs billed-to-date for every project in your portfolio. When the terminal project crossed the 5% threshold, you'd have known that week — not that quarter.

$2.21M is a surety program review. $200K caught early is a one-line adjustment on your next pay app. Start your free 30-day trial →

About the Author
Kwabena Kesse is a licensed CPA (Nevada & North Dakota) with a Master's in Data Analytics and 13 years of experience in retail and commercial banking. He is the founder of BuilderIQ Analytics.
Disclaimer: For educational purposes only — not financial or professional advice. Thresholds vary by surety and underwriting profile. Examples use fictional composites. Software outputs are for informational purposes and should be verified by a qualified professional.