# Progress Billing

> The practice of billing periodically for work performed to date rather than at completion, and the revenue-recognition discipline behind it.

- Source: https://briq.ai/acu/object/progress-billing
- Department: Cost, Billing & Accounting (https://briq.ai/acu/department/cost)
- Catalog code: CST 104 · Level: Foundation · Track: Finance · 10 min read
- Also known as: Progress Payments, Periodic Billing, Interim Billing, Percentage-of-Completion Billing

## Definition

Progress billing is the practice of invoicing an owner periodically for the portion of contracted work completed during each period, rather than billing once at project completion. It is the standard billing model for construction because projects span months or years and neither party can carry the full cost to the end. Progress billing is the operating pattern; the pay application is the document that executes it, and the schedule of values is the map it bills against. It is distinct from cost-plus and time-and-material billing, which invoice actual incurred costs, and from milestone billing, which triggers payment on discrete deliverables rather than continuous percent-complete. Progress billing also carries an accounting dimension: how much is billed and when it is billed interacts with percentage-of-completion revenue recognition, producing the over- and under-billing positions that drive the work-in-progress schedule.

## Why it matters

Progress billing is what keeps a long-duration project financeable for both sides. The owner pays as value accrues instead of at the end, and the contractor recovers its outlays across the job instead of financing the entire contract to completion. The cadence and accuracy of progress billing therefore determine whether a project runs cash-positive or bleeds working capital.

It is where billing and accounting diverge and must be reconciled. Cash billed in a period rarely equals revenue earned in that period, and the gap is over- or under-billing. Persistent over-billing borrows tomorrow's cash into today and often masks a job that is actually losing money; persistent under-billing means the contractor is financing the owner and starving itself of cash it has already earned.

It governs the reliability of the financial statements a surety and a bank rely on. Because revenue is recognized on percentage-of-completion, the accuracy of the progress-billing percentages flows directly into reported earnings; optimistic billing inflates current profit and sets up profit fade later. Sureties read the WIP schedule that progress billing produces as closely as they read the balance sheet.

It creates the rhythm the entire project organization runs on. The billing cutoff drives progress assessment, subcontractor billing, lien-waiver exchange, and cash forecasting; a disciplined cycle makes cash predictable, while a chaotic one produces missed cutoffs, disputed applications, and cash surprises that ripple to every subcontractor.

## Lifecycle

1. **Billing cadence agreement** — The contract sets the period, usually monthly, the cutoff date, and the submission and payment windows. This cadence, fixed at the outset, dictates the cash rhythm for the whole project.
2. **Progress assessment** — At each cutoff, percent-complete is measured against the schedule of values. The rigor here is the difference between billing that tracks the work and billing that runs ahead of it.
3. **Billing computation** — Earned value to date is calculated per line, prior billings and retainage are subtracted, and the period amount is derived. On fixed-price work this flows through the pay application; on cost-plus it flows from incurred cost.
4. **Submission and certification** — The billing is submitted, reviewed, and certified. Reductions at certification are corrected in the next period, which is where over-billing gets clawed back.
5. **Revenue recognition entry** — Independently of what was billed, revenue is recognized on percentage-of-completion, and the difference between billed and earned posts as over- or under-billing on the balance sheet.
6. **Cash collection** — Payment arrives within the contractual window, less retainage. The lag between billing and collection is the working-capital cost of the project.
7. **WIP reconciliation** — Each period the WIP schedule reconciles cost-to-date, estimated cost-to-complete, billings, and earned revenue, exposing the over/under position and any developing profit fade.
8. **Final billing and retainage release** — At completion the last progress billing drives every line to 100 percent, retainage is released, and billed cumulatively reconciles to the final adjusted contract sum.

## Anatomy

- **Billing period and cutoff date** — The window the billing covers and the date progress is measured as of. Consistent cutoffs are what make period-over-period comparison meaningful.
- **Percent-complete by line** — The assessed completion of each SOV line, the input that drives earned value and the number most exposed to optimism.
- **Earned value to date** — Cumulative value of work performed, contract sum times percent-complete on fixed-price work, the basis for the period billing.
- **Billed to date** — Cumulative amount invoiced across all prior periods, subtracted to isolate the current period's request.
- **Current period billing** — The amount requested this period, the visible output of the whole calculation.
- **Retainage withheld** — The portion held back per the contract, reducing current cash even where work is complete.
- **Cost incurred to date** — Actual costs booked against the job, the input to percent-complete on a cost-to-cost basis and to the earned-revenue calculation.
- **Estimated cost to complete** — The forecast of remaining cost, which combined with cost-to-date sets the completion percentage used for revenue recognition.
- **Earned revenue** — Revenue recognized on percentage-of-completion, which is compared to billed-to-date to derive the over/under position.
- **Over/under-billing position** — Billed-to-date minus earned revenue. Positive is over-billing, a liability; negative is under-billing, an asset and a cash drag.
- **Change order billings** — Amounts billed against approved changes, tracked separately so base-contract progress and modifications stay distinguishable.
- **Prompt-payment clock** — The contractual and statutory windows for owner payment and downstream subcontractor payment, the timeline the whole cycle is governed by.

## Failure modes

- **Chronic over-billing that masks a losing job** — Billing consistently outruns earned revenue, so cash looks healthy while the job is actually eroding margin. The truth surfaces at cost-to-complete revision as profit fade, and by then the cash has been spent.
- **Under-billing that starves cash** — The contractor performs work faster than it bills, financing the owner out of its own working capital. It is earning revenue it has not requested, and the cash gap can force borrowing on an otherwise profitable project.
- **Percent-complete assessed to a cash target** — Progress is set to produce a desired billing rather than measured against the field or against cost-to-cost. The billing is not defensible at certification and forces reversals that make lines move backward.
- **Inaccurate cost-to-complete** — A stale or optimistic estimate of remaining cost distorts the completion percentage, misstates earned revenue, and hides an over-billing. The WIP schedule looks fine until the estimate is corrected and profit fade appears all at once.
- **Missed cutoff cascades to cash** — A late billing slips a full payment cycle, delaying the contractor's cash and every subcontractor's payment. On a monthly cadence one missed cutoff can mean sixty days without collection on completed work.
- **Change work billed before it is approved** — Progress is billed on changes that are not yet formally executed, so the billing does not reconcile to the contract sum and is rejected. The work is real but the billing basis is not yet in place.

## Metrics

- **Over/under-billing by job** — Billed-to-date minus earned revenue per project. The single most important progress-billing health metric and the core of the WIP review.
- **Billing accuracy versus field progress** — Correlation between billed percent-complete and observed installed progress. Divergence signals billing detached from the work.
- **Cost-to-complete stability** — How much the estimated cost to complete moves period-over-period. Large swings signal poor forecasting and hidden profit fade.
- **Days sales outstanding** — Average days from billing to cash collection. Measures the working-capital cost of the project's payment cycle.
- **On-time billing rate** — Share of periods billed by the cutoff. Missed cutoffs directly delay cash by a full cycle.
- **Retainage as share of receivables** — Portion of what is owed that is tied up in retainage, a lagging drag on cash that release discipline can recover.

## The AI shift

- **Conversational** — Instead of building a WIP schedule to see the over/under position, you ask it directly: which jobs are over-billed and by how much, whether billed percent-complete matches field progress, how much the cost-to-complete has moved this period, and which jobs are financing the owner through under-billing, each answered from the underlying cost and billing records.
- **Generative** — The period billing and its WIP entries are drafted together. Given cost-to-date, an updated cost-to-complete, the SOV, and prior billings, a model computes earned value, the period billing, and the resulting over/under position, and drafts the WIP lines for review rather than leaving the reconciliation to a manual spreadsheet.
- **Orchestrated** — Progress billing is coordinated across systems. The cost ledger feeds cost-to-date, the schedule validates progress, change orders reconcile the basis, and the billing, the revenue-recognition entry, and the cash forecast update together so the over/under position and the cash view stay consistent rather than being reconstructed separately.
- **Autonomous** — The billing cycle runs continuously inside guardrails: assembling cost-to-date and cost-to-complete, computing earned value and the over/under position, flagging jobs billed ahead of field progress or carrying unstable cost-to-complete, and preparing the period billing and WIP entries before cutoff. People own the percent-complete judgments, the cost-to-complete estimates, and every submission.

## Prompts

### Conversational — Understanding the over/under-billing picture across the portfolio before a WIP review.

```text
Across all active jobs, tell me the over- or under-billing position for each: billed-to-date, earned revenue on percentage-of-completion, and the difference. Rank the over-billed jobs by dollar amount and flag any where the over-billing is large relative to the remaining contract balance, since those are the ones most at risk of profit fade. Separately, list the under-billed jobs, since those are financing the owner out of our cash. For each flagged job, tell me whether the cost-to-complete moved this period and whether billed percent-complete is consistent with field progress. Cite the cost and billing records behind each figure.
```

**Expected output:** A ranked over/under table by job with earned revenue and billed-to-date, plus specific flags for over-billing risk and under-billing cash drag, grounded in the records.

**Follow-ups:**

- For the three most over-billed jobs, what would have to be true for the billing to be justified?
- Estimate the working-capital cost of the under-billing across the portfolio.
- Which jobs show a cost-to-complete swing worth investigating?

### Generative — Preparing this period's progress billing together with its revenue-recognition entries.

```text
Prepare this period's progress billing and the accompanying WIP entries for this job. Use cost-to-date from the cost ledger and this period's updated estimate to complete to set the completion percentage on a cost-to-cost basis, compute earned revenue, and derive the current-period billing against the schedule of values without billing any line ahead of its supported field progress. Show billed-to-date, earned revenue, and the resulting over- or under-billing position, and draft the journal entries to recognize revenue and record the over/under. Flag any change work billed here that is not yet formally executed and any line where billed progress and field progress diverge.
```

**Expected output:** A computed period billing, an over/under position, and draft revenue and over/under journal entries, with any unexecuted change work or field-progress divergence flagged.

**Follow-ups:**

- Recompute if the cost-to-complete is 8 percent higher than the current estimate.
- Show the over/under trend for this job over the last four periods.
- Produce a plain-language explanation of the over/under for the project manager.

### Orchestrated — Keeping billing, revenue recognition, and the cash forecast consistent at cutoff.

```text
At this cutoff, reconcile progress billing across systems for all active jobs. Pull cost-to-date from the cost ledger, validate each job's billed progress against the schedule, confirm change-order billings reconcile to executed changes, and compute the over/under position per job. Then update the cash-flow forecast for the resulting billings net of retainage and the expected collection windows, and produce a single reconciliation summary showing where billing, earned revenue, and the cash view agree and where they do not. Tie each discrepancy to the specific record and flag anything you are unsure about instead of forcing a match.
```

**Expected output:** A cross-system reconciliation summary linking billing, earned revenue, and cash forecast per job, with discrepancies traced to their source records.

**Follow-ups:**

- Which discrepancies stem from cost-to-complete versus billing timing?
- Draft the WIP review summary for the operations meeting.
- How does the retainage balance change the collection forecast this quarter?

### Autonomous — Standing policy for running the progress-billing cycle across the portfolio.

```text
Run our progress-billing cycle each period under these rules. Ahead of every cutoff, assemble cost-to-date and the current estimate to complete for each job, compute earned revenue and the over/under position, reconcile change-order billings to executed changes, and prepare the period billing and draft WIP entries. Flag and hold from billing any line billed ahead of field progress, any job whose cost-to-complete moved beyond a materiality threshold I set, and any change work not yet formally executed, escalating each to me with the numbers. Never finalize a percent-complete judgment, never revise an estimate to complete, and never submit a billing without my approval. Route every over-billing risk and every cost-to-complete swing to me with your reasoning.
```

**Expected output:** Ready-to-review period billings and WIP entries, a short exception queue of over-billing and cost-to-complete flags, and a boundary that completion judgments, estimate revisions, and submissions always require a person.

**Follow-ups:**

- Show me this period's drafts plus everything you flagged and held.
- Which jobs have triggered cost-to-complete escalations more than once this year?

## Maturity ladder

- **Level 0 — Level 0 — Ad hoc billing** — Billings are prepared reactively with no consistent link between billed cash and earned revenue, so the over/under position is unknown until a year-end accountant reconstructs it.
- **Level 1 — Level 1 — Periodic and reconciled** — A fixed cadence is followed, billings reconcile to the contract, and a WIP schedule is produced periodically, though percent-complete is office-estimated and cost-to-complete is updated infrequently.
- **Level 2 — Level 2 — Cost- and schedule-linked** — Billings draw cost-to-date from the ledger and validate progress against the schedule, so earned revenue and the over/under position are computed from real inputs rather than assumptions.
- **Level 3 — Level 3 — Assisted preparation** — Period billings and WIP entries are drafted from cost and progress data, over-billing and cost-to-complete swings are flagged automatically, and the cash forecast updates from the billings for human review.
- **Level 4 — Level 4 — Operated** — The billing-to-revenue-to-cash cycle runs unattended inside guardrails, while people own percent-complete judgments, cost-to-complete estimates, and every billing submission.

## FAQ

### How is progress billing different from milestone billing?

Progress billing invoices continuously for the percentage of work completed in each period, so a partially finished portion of work generates a partial bill. Milestone billing triggers a fixed payment only when a defined deliverable is reached, with nothing in between. Progress billing tracks cash to accrued value more smoothly, while milestone billing is simpler to administer but can create large cash gaps between milestones.

### Why can a contractor be over-billed and still be short on cash?

Over-billing measures billed-to-date against earned revenue, an accounting position, not the cash actually collected. A contractor can be over-billed on paper while retainage, a slow-paying owner, or subcontractors already paid have consumed the cash. Over-billing and cash position are related but distinct, which is why disciplined operators watch both the WIP schedule and the cash forecast.

### What drives the over/under-billing position?

It is the difference between what has been billed and what has been earned on percentage-of-completion. Billing ahead of the completion percentage produces over-billing; performing work faster than it is billed produces under-billing. The completion percentage itself depends on cost-to-date against total estimated cost, so an inaccurate estimate to complete is a common hidden driver of a misstated over/under position.

### Is over-billing a bad thing?

Modest, intentional over-billing is normal and healthy because it keeps a project cash-positive and funds the work ahead. It becomes a problem when it is large, unintentional, or masks a job that is actually losing money, because the over-billed cash must eventually be given back as the work is performed and the true margin emerges as profit fade.

## Related objects

- [Pay Application (AIA G702/G703)](https://briq.ai/acu/object/pay-application)
- [Schedule of Values (SOV)](https://briq.ai/acu/object/schedule-of-values)
- [Work in Progress (WIP) Schedule](https://briq.ai/acu/object/wip-schedule)
- [Over / Under Billing](https://briq.ai/acu/object/over-under-billing)
- [Revenue Recognition (ASC 606)](https://briq.ai/acu/object/revenue-recognition)
- [Cash Flow Forecast](https://briq.ai/acu/object/cash-flow-forecast)