Over / Under Billing

Definition — what it is

Over/under billing is the difference on a given contract between the amount billed to the owner to date and the revenue earned to date based on percent complete. When billings exceed earned revenue the job is overbilled — billings in excess of costs and estimated earnings, a contract liability — and when earned revenue exceeds billings the job is underbilled — costs and estimated earnings in excess of billings, a contract asset. It exists because billing and earning follow different clocks: billings are governed by the pay-application schedule and the owner's payment terms, while earnings are governed by physical progress and cost. Over/under billing is not profit and it is not cash on hand; it is a timing reconciliation that reveals whether the contractor is currently financing the owner or the owner is financing the contractor, and it is one of the most diagnostic figures on the entire WIP schedule.

Also known as: Billings in Excess of Costs, Costs in Excess of Billings, Over/Underbillings, Contract Assets and Liabilities

Why it matters — what it protects

Over/under billing is where cash health and reported earnings diverge, and it is the number that explains a profitable company running out of money. An underbilled job is earning profit on paper while tying up the contractor's cash in unbilled work, and a portfolio drifting underbilled is a working-capital warning long before the bank balance shows it. Reading over/under is how a controller sees a cash problem coming.

It reveals borrowed billing that must eventually be earned out. A front-loaded, overbilled job enjoys positive cash early, but those billings are effectively an interest-free loan against work not yet performed; as the job finishes and billing flattens while cost continues, the position reverses. An overbilled job near completion is a job that has already spent its future, and misreading that as strength is a classic error.

It is a primary surety and lender diagnostic. Sureties treat heavy overbilling near completion and large underbilled balances as risk signals, because both indicate that reported earnings and available cash are out of step. The over/under position, more than the margin itself, often shapes bonding capacity and covenant assessments, because it speaks to whether the earnings are real and collectible.

It disciplines the honesty of billing. Chronic overbilling can be a symptom of a company billing ahead of progress to prop up cash, which borrows from tomorrow and masks a cash shortfall that is actually structural. Tracking over/under per job and in aggregate forces the question of whether billings are keeping honest pace with earnings, or whether the company is quietly financing itself on its owners' money.

Lifecycle — how it moves

1. Billing and cost capture

   Billed-to-date from pay applications and cost-incurred-to-date from the job cost report are captured as of cutoff. Timing differences between when cost posts and when it can be billed are the root of most over/under movement.

2. Earned revenue calculation

   Percent complete, usually cost-to-cost, is applied to current contract value to derive earned revenue. The integrity of the estimate at completion behind percent complete directly determines the over/under figure.

3. Position derivation

   Billed-to-date minus earned revenue classifies the job as overbilled or underbilled and sizes the balance. This is computed per job because portfolio netting hides jobs at both extremes.

4. Balance-sheet posting

   Overbilled amounts post as contract liabilities (billings in excess), underbilled amounts as contract assets (costs in excess), reconciling the WIP schedule to the balance sheet. Misposting distorts working-capital ratios.

5. Analysis and cause attribution

   Each material position is examined: is the job underbilled because of unbilled changes, retainage, or slow application processing; is it overbilled from deliberate front-loading or from a stale percent complete. The cause dictates the action.

6. Corrective billing action

   Underbilled jobs are worked to bill the earned but unbilled amount — pushing pending change orders, accelerating pay applications, releasing retainage where due. Overbilled positions are monitored so the earn-out is planned, not sprung.

7. Trend monitoring

   The aggregate and per-job over/under trend is tracked across periods, because a steadily worsening underbilled trend is a cash trajectory and a growing overbilled near-complete balance is a reversal waiting to happen.

Anatomy — the data it carries

Contract and current contract value

The job and its revenue ceiling including approved changes, the base earned revenue is computed against.

Billed to date

Cumulative owner billings from pay applications, one half of the comparison. Sensitive to application timing and approval delays.

Earned revenue to date

Percent complete applied to contract value, the other half. Only as reliable as the estimate at completion behind it.

Cost incurred to date

Actual plus accruals, the numerator of cost-to-cost percent complete and thus an indirect driver of the position.

Percent complete

The progress measure translating cost into earnings. A stale or soft percent complete directly mis-sizes the over/under.

Overbilling (billings in excess)

Billed minus earned when positive, a contract liability. Flags front-loading and future earn-out obligation.

Underbilling (costs in excess)

Earned minus billed when positive, a contract asset. Flags cash tied up in unbilled earnings.

Retainage receivable

Earned amounts withheld by the owner under retainage, a component of underbilling that will release on milestones and should not be mistaken for a billing failure.

Unbilled change orders

Approved or pending changes earned but not yet in a pay application, a frequent and recoverable cause of underbilling.

Prior-period position

Last period's over/under, carried so the direction and speed of movement are visible, not just the level.

Percent complete threshold flag

Marker for jobs past a high completion percentage, where overbilling becomes an earn-out risk rather than a benign timing item.

Failure modes — how it breaks

Overbilling read as profitability

A front-loaded job shows strong early cash and is treated as healthy, when the billings are borrowed against future work. As the job completes and billing flattens, cash reverses, and management is surprised by a downturn it created.

Underbilling from unworked change orders

Approved changes are earned in cost but never added to a pay application, so the job is underbilled and cash is stranded in recoverable receivables. The money is billable; it simply was not billed, and the leverage to collect it fades with time.

Stale percent complete distorting the position

A soft or un-refreshed estimate at completion inflates percent complete, overstating earned revenue and making an overbilled job look underbilled or a real position look benign. The over/under is only as honest as the cost-to-complete behind it.

Retainage confused with underbilling

Retainage receivable is counted as a billing failure and someone chases it as if it were unbilled work, when it is withheld earnings that release on contractual milestones. The two require completely different actions and conflating them wastes effort.

Portfolio netting hides both extremes

The aggregate over/under nets to a comfortable number while individual jobs sit heavily overbilled and heavily underbilled. The net conceals both a cash-stranded job and an earn-out risk, each of which needs attention the total hides.

Chronic overbilling masking a cash shortfall

The company routinely bills ahead of progress across jobs to keep cash positive, which borrows structurally from future work. The habit hides a working-capital deficiency that surfaces the moment new billing slows.

Misposting to the balance sheet

Overbilled and underbilled amounts are posted incorrectly or netted, distorting the contract asset and liability accounts and the working-capital ratios lenders and sureties rely on. The financial statements misstate the company's true position.

Metrics — how it is measured

Net over/under position

Portfolio billings in excess minus costs in excess. The headline, but only meaningful alongside the per-job spread it may be hiding.

Underbilled balance and trend

Total costs in excess and its direction. Rising underbilling is cash draining into unbilled work, a working-capital signal.

Overbilled near completion

Billings in excess on jobs past a high completion threshold. The earn-out obligation that will reverse cash as jobs finish.

Unbilled earned revenue

Earned but not yet billed, excluding retainage. Directly recoverable underbilling that better billing discipline could convert to cash.

Retainage receivable

Withheld earnings separated from other underbilling, so genuine billing gaps are not confused with contractual holds.

Days billing lags earning

Average lag between when revenue is earned and when it is billed. A process metric on billing responsiveness and a cash-cycle input.

Over/under volatility by job

Swing in position period over period, which flags jobs with erratic billing or unstable percent complete.

The AI shift — what actually changes

Conversational

The over/under position becomes explainable on demand. You ask which underbilled jobs are stranded on unbilled change orders versus retainage, which overbilled jobs are past 80 percent complete and must earn out, and whether the comfortable net position is hiding extremes at the job level — and get the specific jobs, pay applications, and change records cited.

Generative

The analysis is drafted, not just the number. Given billings, cost, and percent complete, a model derives each job's position, attributes underbilling to unbilled changes, retainage, or slow applications, and produces a corrective billing plan with the specific pay-application lines and change orders to pursue for management to approve.

Orchestrated

Over/under stops being a static month-end figure. It pulls billings from pay applications, earned revenue from percent complete, and unbilled changes from the change log, posts the contract asset and liability entries, and flags recoverable underbilling and earn-out risk with the underlying records attached so the corrective action is one step away.

Autonomous

The routine derivation and monitoring run unattended: positions computed and posted consistently, retainage separated from recoverable underbilling, jobs crossing the near-complete overbilling threshold flagged, and worsening underbilled trends escalated — while humans own the billing strategy, any decision to front-load, and every corrective billing action that touches the owner relationship.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — The net over/under looks fine but you suspect it is masking problems.

Look past the net over/under position on this portfolio. Compute each job's position and show me the full spread, not the net. For every underbilled job, break the underbilling into recoverable unbilled change orders, retainage receivable, and slow pay-application processing, so I know what is actually collectible. For every overbilled job, flag the ones past 80 percent complete and quantify the billings that still have to be earned out as the job finishes. Tell me how much total earned revenue is unbilled and directly recoverable this month. Check that percent complete on the extreme jobs is refreshed and not stale, since a soft estimate distorts the position. Cite the pay applications, change orders, and estimates behind each finding.

What good output looks like: A per-job over/under breakdown that separates recoverable underbilling from retainage, quantifies near-complete earn-out risk, and tests percent complete for staleness, each finding tied to a specific record.

Follow-ups:

• Rank the underbilled jobs by directly recoverable cash and draft the billing actions.
• Which overbilled jobs will reverse cash next quarter, and by how much?
• How much of the underbilling is just retainage we should stop chasing as if it were unbilled work?

Generative — You need the over/under schedule and a corrective billing plan for the month.

Produce this month's over/under billing analysis from the billing, cost, and percent-complete data attached. For each job, present current contract value, billed to date, earned revenue, cost incurred, percent complete, and the over/under position classified as billings in excess or costs in excess, with retainage receivable shown separately. Carry the prior-period position so movement is visible. Then build a corrective billing plan: for each underbilled job, list the specific unbilled change orders and earned-but-unbilled amounts to bill next cycle, and estimate the cash it would release. Flag overbilled jobs past 80 percent complete as earn-out risks. Return the schedule, the movement analysis, and the billing plan, and flag any job whose percent complete looks stale enough to distort its position.

What good output looks like: An over/under schedule with retainage separated and prior-period movement shown, plus a concrete corrective billing plan naming the change orders and amounts to bill and estimating the cash it releases.

Follow-ups:

• Draft the pay-application line items for the top three recoverable underbilled jobs.
• Show the cash impact if we execute the whole billing plan this cycle.
• Which overbilled positions should we deliberately hold and which should we let normalize?

Orchestrated — You want over/under derived across systems and the balance-sheet entries prepared.

Derive this period's over/under billing across the connected systems and prepare the accounting. Pull billed-to-date from the pay applications, cost incurred and accruals from the job cost reports, and percent complete from each job's estimate at completion. Compute earned revenue and classify each job's position, separating retainage receivable and identifying unbilled but earned change orders. Prepare the contract asset and liability journal entries for costs in excess and billings in excess, and reconcile them to the balance-sheet accounts. Flag every job where billing lags earning by more than the normal cycle, and every job whose position moved sharply because of a percent-complete change rather than a billing or cost change. Return the positions, the draft entries, and the reconciliation with exceptions named.

What good output looks like: Cross-system over/under positions with retainage separated, draft contract asset and liability entries reconciled to the balance sheet, and exceptions for lagging billing and percent-complete-driven swings named.

Follow-ups:

• For jobs where the position moved on percent complete, show me the estimate change that caused it.
• Which underbilling is recoverable this cycle versus locked as retainage until milestones?
• Confirm the draft entries tie to the balance-sheet contract accounts.

Autonomous — Standing policy for monitoring and acting on over/under billing.

Monitor over/under billing continuously under these rules. Each period, derive every job's position from pay applications, cost, and percent complete, separate retainage receivable from recoverable underbilling, and prepare the draft contract asset and liability entries reconciled to the balance sheet. Flag jobs crossing the near-complete overbilling threshold, worsening underbilled trends, and positions that swung on a stale percent complete rather than real activity. Surface recoverable unbilled earned revenue and unbilled change orders as billing opportunities. Never issue or alter a pay application, never change a job's percent complete, never front-load a billing, and never post the balance-sheet entries without human approval — route those with the supporting records, and give me a weekly exception queue of earn-out risks, recoverable underbilling, and stale-estimate distortions rather than the full schedule.

What good output looks like: A monitored over/under position where routine derivation, retainage separation, and draft entries are automatic, and every billing action, front-loading decision, and posting stays a human choice, with exceptions escalated.

Follow-ups:

• Show me the recoverable underbilling you surfaced and which we chose to bill.
• Report how our net position and per-job spread moved this quarter and why.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Not tracked

   Over/under is not computed between year-ends. Cash and earnings are managed separately, and the company cannot see itself financing its owners until the cash is gone.

1. Level 1 — Computed on the WIP

   Positions are derived monthly on the WIP schedule and posted to the balance sheet. Analysis is thin and the net often hides per-job extremes.

2. Level 2 — Analyzed and acted on

   Underbilling is broken into recoverable versus retainage, near-complete overbilling is flagged, and corrective billing is a deliberate monthly action. Positions are managed, not just reported.

3. Level 3 — Assisted and integrated

   Positions are derived across systems, entries are drafted and reconciled, and recoverable underbilling and earn-out risks are surfaced with source records for review.

4. Level 4 — Operated

   Routine derivation, retainage separation, and draft posting run unattended, while humans own billing strategy, front-loading, and every corrective billing action.

Common questions

Is overbilling a good thing or a bad thing?

Neither by itself; it depends on stage and intent. Modest overbilling early in a job is normal front-loading that funds mobilization and improves cash flow, and most healthy contractors carry a small net overbilled position. It becomes a problem when a job is heavily overbilled near completion, because the billings were borrowed against work not yet done and cash will reverse as the job finishes. The stage of the job, not the sign of the number, tells you whether to worry.

Why can a profitable company be short of cash because of underbilling?

Because underbilling means the company has earned revenue and incurred cost it has not yet billed, so profit shows up on the income statement while the cash is still tied up in unbilled work. A portfolio drifting underbilled is financing its owners, and the reported profit provides no relief until it is billed and collected. This is exactly why controllers watch the underbilled trend as a working-capital signal rather than relying on the profit line.

How is retainage different from ordinary underbilling?

Retainage is earned revenue the owner is contractually withholding until milestones like substantial completion, so it is underbilling that cannot be collected early by billing harder. Ordinary underbilling from unbilled change orders or slow pay applications is recoverable now with better billing discipline. Conflating the two leads teams to chase retainage as if it were a billing failure, which wastes effort, and to overlook genuinely recoverable amounts, which strands cash.