The Job Is Finished. The Money Isn't.
Your crew pulled three leaking underground storage tanks, hauled off 400 tons of contaminated soil, and closed out a six-month remediation job for a gas station owner. You invoice the property owner for $180,000. Payroll is due Friday. The check doesn't come Friday — because the property owner isn't paying you out of pocket. They're waiting on a reimbursement check from the state's underground storage tank cleanup fund, and that check is 6 to 8 weeks out, assuming the state doesn't kick the claim back for a missing invoice or a cost that exceeds the fund's per-gallon cap.
This is the defining bookkeeping problem of environmental remediation contracting, and it's almost never mentioned in general construction-accounting advice. You're not just tracking percentage-of-completion on a job. You're tracking percentage-of-completion on a job where the entity cutting the check has no contract with you, runs on its own review cycle, and can partially deny your claim months after the work is done.
Who Actually Pays a Remediation Contractor
Most small remediation contractors work one of three payer structures, and each one changes how you should book the job.
State cleanup funds (the most common structure for smaller sites). States like California, Massachusetts, Colorado, and Texas run trust funds — usually financed by a tax on petroleum products — that reimburse underground storage tank (UST) owners for cleanup costs after a leak. California's UST Cleanup Fund and Massachusetts's Petroleum Product Cleanup Fund are two of the largest. The property owner (or "responsible party") is technically your customer and signs your contract, but the fund is the actual source of cash. Some states allow "state-lead" work where the fund reimburses you, the contractor, directly.
Superfund cost recovery (larger, more complex sites). On federal Superfund sites, the EPA can perform or oversee cleanup and later sue responsible parties to recover costs, or a group of potentially responsible parties can hire contractors directly and split the bill through a cost-allocation agreement. Payment timing here is even less predictable — recovery litigation can run for years.
Private-pay and insurance-backed jobs. Environmental liability insurance, real estate transaction escrow holdbacks, or a property owner's own capital. These behave more like normal construction jobs from a cash-flow standpoint, but the accounting phases below still apply.
If you don't know which bucket a given job falls into before you break ground, you can't set client payment terms, staff the job correctly, or forecast cash flow. That classification belongs in your job-cost system on day one, not buried in a project folder.
The Five Phases That Should Drive Your Job Costing
Remediation liabilities and remediation contracts are typically built up from a sequence of distinct phases, and your chart of accounts and job-cost codes should mirror them rather than treating "the cleanup" as one lump job:
- Remedial investigation — sampling, drilling, lab analysis to define the extent of contamination
- Feasibility study — evaluating remediation methods and costs
- Remedial design — engineering the actual cleanup plan
- Remediation — the excavation, treatment, disposal, or in-situ work itself
- Post-remediation monitoring — years of groundwater sampling and reporting after the "dirty work" is done
Each phase has a different cost profile, a different billing cadence, and — critically — a different reimbursement approval pattern with the paying fund. Monitoring work, for example, often gets billed in small recurring increments over years, which behaves more like a subscription than a construction contract and deserves its own recurring job code rather than getting lumped into the original project.
Tag every cost — labor hours, disposal manifests, lab invoices, equipment rental — to both the site and the phase. When a state auditor or fund reviewer asks for backup on a claim (and they will), the ability to produce a clean phase-by-phase cost breakdown for one site, instantly, is the difference between a reimbursement approved in weeks and one stuck in review for months.
Percentage-of-Completion, With a Third-Party Twist
Standard construction accounting under ASC 606 recognizes revenue over time as you satisfy performance obligations, typically measured by costs incurred against total estimated costs (percentage-of-completion). A work-in-progress (WIP) schedule tracks contract value, costs to date, billings to date, and the resulting over- or under-billing position on every open job.
Remediation contracting layers one more variable on top: collectibility. ASC 606 requires that collection of the consideration you're entitled to be probable before you can recognize revenue on a contract. When your actual payer is a state fund rather than your contracting counterparty, ask three questions before you book revenue at the same confidence level as a normal job:
- Is there a cost cap or per-occurrence deductible? Most UST funds only reimburse costs above a deductible and below a cap. Work performed above the cap is effectively unbillable to the fund — someone (usually the property owner) is on the hook for it directly, and if that party can't pay, it's not revenue you should count on.
- Has the fund pre-approved the scope and estimated cost? Funds that require pre-approval of a corrective action plan give you a much stronger basis for revenue recognition than funds that only review costs after the fact.
- What's this fund's actual denial rate on ineligible or "unreasonable" costs? Every state fund publishes eligibility rules — equipment markup limits, hourly rate caps, disallowed cost categories. Firms that have worked a fund for years usually know its real-world approval rate; new contractors should ask their state program directly rather than assume 100% of billed costs come back.
None of this means you should hold off recognizing revenue until the reimbursement check clears — that would understate a healthy job. It means your WIP schedule should flag the portion of each job's costs that fall outside the fund's typical reimbursement pattern, so your gross margin isn't a surprise six months later when a claim comes back partially denied.
The Cash-Flow Gap Is the Real Risk, Not the Accounting
The accounting technique here is manageable. The cash-flow mechanics are what put small remediation contractors out of business. A typical pattern: you front labor, disposal fees, and subcontractor costs for 30, 60, sometimes 90 days before you can even submit a complete reimbursement claim, then wait another 6 to 8 weeks — often longer — for the state to process and pay it. Meanwhile, payroll, fuel, and equipment lease payments don't wait for anyone.
Three practical responses, all things your books should be built to support:
- Track reimbursement aging separately from ordinary accounts receivable. A UST fund claim pending at week 4 is a fundamentally different asset than a private-pay invoice at day 4. Blending them into one AR aging report hides your real liquidity position.
- Price and staff around the lag, not around the invoice date. If a fund reliably takes ten weeks to pay, that's a financing cost of doing business with that fund, whether or not you ever formally account for it as interest. Some contractors negotiate "we invoice you when we're reimbursed" terms with property owners specifically to avoid carrying that float themselves — know before the job starts whether that's the deal, because it changes when you should expect cash, not just when you recognize revenue.
- Consider AR factoring or a line of credit sized to your reimbursement cycle, not your revenue. A contractor with $2 million in annual revenue but a 10-week average collection cycle on fund-paid jobs needs meaningfully more working capital than one with the same revenue and 30-day private-pay terms.
Common Mistakes That Cost Remediation Contractors Real Money
Commingling costs across sites. Sharing a disposal manifest or equipment rental across two jobs without splitting the invoice is a fast way to make both reimbursement claims harder to substantiate — and to lose track of true job profitability.
Booking the reimbursement, not the contract, as revenue. Your revenue is what you're owed under the contract for work performed. The reimbursement is simply your customer's funding source. Conflating the two makes it easy to miss the deductible/cap gap discussed above.
Losing the paper trail. Funds require documentation that work was authorized, performed, and actually paid for — invoices, lab reports, disposal manifests, time sheets, all tied to the specific claim period. A remediation contractor's books are only as good as the backup that sits behind every line, and that backup needs to be retrievable by site and phase, not buried in a shared inbox.
Treating monitoring-phase billing like a one-time job. Years of quarterly groundwater sampling invoices for a site you closed out long ago deserve recurring job coding, not a stale project file that nobody's tracking margin on anymore.
Building the Records That Survive an Audit
Because remediation work sits at the intersection of environmental regulation, tax rules on capitalizing versus expensing cleanup costs, and a third-party payer with its own review process, the underlying financial records need to hold up to more scrutiny than a typical trade contractor's books — a state fund auditor, an IRS examiner evaluating whether costs should have been capitalized, and your own CPA at tax time may all eventually look at the same job file.
Plain-text, version-controlled accounting fits this kind of work well: every job-cost entry, every reimbursement claim, and every adjustment lives in a durable, auditable record you control — not locked inside a vendor's database where pulling five years of site-by-site cost history for a monitoring claim becomes its own project. Beancount.io gives contractors and their bookkeepers plain-text accounting that's transparent, git-tracked, and easy to slice by site, phase, or fund without fighting the software. Get started for free and keep your remediation job costs as clean as the sites you're cleaning up.