Answer Hub · Financial Management
How do restoration companies improve cash flow between job completion and payment?
The short answer
Shorten the gap by invoicing within a day or two of completion, sending a complete documentation package with the invoice, getting signatures and change approvals during the job rather than after, tracking every open receivable by age and owner, and following up on a fixed schedule. Most delays come from missing paperwork and unclear ownership, not from the payer refusing to pay.
Where the cash actually gets stuck
Restoration companies often finish the work and then wait. Crews and materials were paid for weeks ago, but the money for the job arrives much later. Some of that wait is outside your control, especially on insurance work. A surprising amount of it is not.
Look at a few slow-paying jobs from the last quarter and trace why. The common answers are familiar: the invoice went out late because the PM had not finished the paperwork; the adjuster asked for photos that were on a tech's phone; a change order was never signed; the customer's deductible was never discussed; or nobody was assigned to follow up. Each one adds days or weeks.
The days that matter
Think of the gap in stages and measure each one in days.
| Stage | What happens | Who owns it |
|---|---|---|
| Completion to invoice | Paperwork assembled, invoice created | PM and office |
| Invoice to acknowledgment | Payer confirms receipt and completeness | Office |
| Acknowledgment to approval | Questions answered, revisions made | PM |
| Approval to payment | Payment issued and received | Office |
Most shops can cut the first stage dramatically. A job that took four weeks to invoice because the file was incomplete can often be invoiced in two days if documentation is captured during the job.
Build the invoice package during the job
The single biggest lever is having the file ready when the job ends. That means:
- Signed work authorization before work starts.
- Signed change approvals for every scope change, captured at the time.
- Photos from every stage, on the job, labeled by room and date.
- Daily journal entries showing what was done each visit.
- Labor records tied to the job.
- A completion sign-off from the customer if your process uses one.
When these exist as the job runs, the PM's closeout is a review, not a scavenger hunt.
Talk about money at the start
Many payment delays trace back to the first day. Explain clearly and in writing what the customer is responsible for, such as a deductible or any work outside the claim, and when it is due. For insurance work, confirm the claim number, adjuster contact and how the carrier wants to receive documentation. For commercial and property management clients, confirm who approves invoices and what format they need.
Never adjust scope or documentation to fit what you hope will be paid. Accurate, complete records are what move a claim forward. If there is a coverage question, the customer and their carrier decide it.
Follow up on a schedule
Receivables without an owner do not get collected. Assign every open invoice to one person and use a simple cadence:
- Day 3 after sending: confirm receipt and ask whether anything is missing.
- Day 14: check status and answer open questions.
- Day 30: escalate to the PM or owner, with a call rather than an email.
- Beyond that: follow your written collections policy, and involve your attorney when needed.
Log every contact on the job: date, who you spoke with, and what they said. When a payer asks for something, the request and your response should be easy to find.
A hypothetical comparison
Picture two similar water jobs completed the same week.
On the first, the PM spends the following week collecting photos from two techs' phones, discovers the change approval for extra drywall removal was verbal only, and has to go back to the homeowner. The invoice goes out after three weeks and the adjuster asks for moisture readings that are on a paper log in the truck. Another two weeks pass.
On the second, photos, readings and the signed change approval are already on the job. The PM reviews the file the day after completion and the office sends the invoice with documentation that afternoon. A follow-up call on day three confirms the adjuster has everything.
Same work, same payer type, very different wait.
Common mistakes
- Invoicing in batches at month end. Send each invoice when the job closes.
- Verbal change orders. They are the most common reason a file stalls.
- No receivable owner. Everyone assumes someone else is following up.
- Incomplete packages. Every missing item creates another round trip.
- Not tracking aging. Review open receivables by age weekly.
Talk with your accountant about how to forecast cash during slow-paying stretches, and with your banker about options if you regularly carry large receivables after storm seasons.
Using software to tighten the gap
Capturing signatures, photos, journals and time on the job is what makes fast invoicing possible. RestoreUnited supports this with Electronic Signatures, Photos & Journals and Time Tracking on each job, Custom Reporting for open job and receivable views, and the QuickBooks Integration to connect job records with your accounting.
See it in RestoreUnited: QuickBooks Integration
RestoreUnited product videoFrequently asked questions
How soon after completion should a restoration job be invoiced?
Aim for within one or two business days. That is realistic only if documentation is captured during the job, so the PM's closeout is a quick review rather than days of collecting photos and signatures.
Should we invoice the deductible separately?
Many companies collect or invoice the customer's portion separately from the carrier's, but the right approach depends on your agreements and state rules. Explain it in writing at the start of the job and talk to your accountant or attorney about how to set it up.
What is the most common reason restoration invoices are delayed?
Incomplete documentation is a frequent cause: missing photos, unsigned change approvals or readings that are not in the file. Each gap triggers a request, and each request adds days to the wait.