The common leak points
- Work completed but never invoiced, because the job closed without a billing step.
- Extras performed on site and never approved, so they cannot be billed at all.
- Change orders approved verbally and never written down.
- Deposits collected and then not applied, or applied twice.
- Materials used beyond the estimate and never reflected in the price.
- Trip charges, after-hours rates and disposal fees waived by default.
- Invoices that age past the point of realistic collection.
- Refunds and credits issued informally with no record.
Why leakage is invisible in reporting
Reports summarise what was recorded. An invoice that was never created contributes nothing to any dashboard, so the business looks like it earned exactly what it billed.
That is why leakage is usually found by comparing two things that should agree: completed jobs against issued invoices, approved amounts against invoiced amounts, scheduled milestones against applied payments. The gaps are the leaks.
Four checks that surface most of it
- Completed jobs with no invoice, older than a few days.
- Invoices lower than the approved total plus approved change orders.
- Milestones that came due with no matching payment applied.
- Open balances that crossed an aging threshold without a follow-up recorded.
Closing leaks without adding paperwork
Most leaks close by moving one decision earlier: approving extras before the work instead of arguing after, invoicing at completion instead of weekly, recording payments in the field instead of at the office.
The office cannot bill what it was never told about. Every leak is really a handoff that relies on someone remembering — which is exactly the class of problem a system is supposed to absorb.