If a completed pressure-washing job is unpaid, do not treat it like a sales follow-up. Treat it as an accounts-receivable record with a verified balance, a clear status, a documented customer response and one next action.
The simplest workflow is:
Verify the invoice → assign a status → follow up clearly → record the response → set the next action → stop when paid or move the issue to manual review.
The goal is not to chase customers more aggressively. It is to stop letting unpaid invoices live in your memory, text messages and scattered notes.
Unpaid invoice follow-up is different from estimate follow-up
An estimate is part of the sales process before the work is approved. An invoice is the bill for completed work. Mixing those two workflows makes it harder to know what you are actually waiting on.
If the customer has not approved the job yet, use a pre-sale follow-up process such as Pressure Washing Estimate Follow-Up. Once the agreed work is complete and the invoice has been sent, move the customer into an A/R workflow instead.
Track seven fields for every open invoice
You do not need a complicated collections system to stay organized. For each unpaid invoice, keep these seven fields together:
- Invoice number. Give each invoice a unique reference so every message can point to the same record.
- Customer and job. Identify the customer and completed service clearly.
- Balance due. Record the current unpaid amount, not just the original invoice total.
- Due date. Use the date already stated on the invoice or agreed with the customer.
- Status. Examples include Sent, Not Yet Due, Overdue - Reminder Due, Customer Responded, Payment Pending, Dispute / Manual Review and Paid.
- Last contact and result. Record what was sent or discussed and what the customer said.
- Next action date. Every unpaid record should either have a next action or a reason no automated action should occur.
If those seven fields are current, you can review A/R without rebuilding the story from your phone.
Verify the record before sending another reminder
Before contacting the customer, check that the invoice itself is ready to defend as a business record. Confirm:
- the correct customer and contact information;
- the completed job and scope;
- approved additions, removals or changes;
- the amount currently due;
- the stated due date and payment instructions;
- whether a payment has already arrived but has not been recorded;
- whether the customer has already raised a question or dispute.
If any of those items are unclear, fix the record before sending another automatic reminder.
A good invoice starts earlier in the workflow. The Pressure Washing Estimate Template guide explains why clear scope and payment expectations belong in the job paperwork before a balance becomes overdue.
Use statuses instead of one giant “unpaid” bucket
“Unpaid” does not tell you what to do next. A simple status system does.
| Status | What it means | Next action |
|---|---|---|
| Sent | Invoice delivered and recorded | Wait for the stated due date unless a normal pre-due reminder is part of your process |
| Not Yet Due | Invoice is open but not overdue | Do not describe it as overdue |
| Overdue - Reminder Due | Due date has passed and no payment or unresolved response is recorded | Send a clear reminder |
| Customer Responded | Customer replied with information or a question | Record the response and choose the next action from what they actually said |
| Payment Pending | Customer says payment has been initiated or agreed | Set a verification date and reconcile the payment |
| Dispute / Manual Review | Customer questions scope, amount, completion or another material issue | Pause routine reminders and review the underlying job record |
| Paid | Balance is reconciled | Stop follow-up |
The point is not the exact names. The point is that each status tells you whether to wait, contact, verify, review or stop.
A reminder should answer five questions
A useful invoice reminder should make it easy for the customer to understand what you are referring to without searching through old messages:
- Which invoice is this?
- What balance is currently due?
- What due date is on the invoice?
- How can the customer review or pay it?
- Who should they contact if something is wrong?
Keep the tone factual. You usually do not need a long explanation, pressure language or a threat.
Current QuickBooks Online documentation confirms that businesses can send invoice reminders manually or automatically based on invoice due dates and can customize the reminder message. That supports the workflow concept, but it does not prove that one reminder schedule is best for every pressure-washing business. See Intuit's current invoice-reminder guidance.
Use a decision tree after every contact
After a reminder or customer response, do not automatically schedule another identical message. Ask what changed.
- Payment received? Reconcile the payment and mark the invoice Paid.
- Customer says payment was already sent? Pause reminders while you verify it.
- Customer asks for the invoice again? Resend the invoice or payment instructions and record that action.
- Customer questions the amount or scope? Move the record to Dispute / Manual Review and compare the invoice with the estimate, approved changes and job notes.
- Customer gives a specific payment commitment? Record the stated commitment and a reasonable verification date rather than continuing generic reminders.
- Partial payment received? Update the balance and keep the record accurate before any further communication.
- No response? Keep the next step inside your documented business process, then move persistent exceptions to manual review rather than endlessly automating messages.
Know when automation should stop
Automation is useful only while the record is simple. Pause routine reminders when:
- the customer disputes the amount, scope or completion;
- you are unsure whether a payment has posted;
- the invoice record is wrong or incomplete;
- the customer has entered a separate payment arrangement that needs to be documented;
- you are considering fees, formal collection activity or legal escalation.
Those situations need judgment, not another template.
This guide is an operating workflow, not legal advice. Rules involving late fees, collection practices, contracts and formal remedies can vary by jurisdiction and situation. If an unpaid balance reaches that stage, use qualified legal or accounting guidance appropriate to your business.
Hypothetical example: turn one unpaid invoice into a clear record
This is a hypothetical recordkeeping example. The dates and timing are examples only, not a recommended or universal reminder cadence.
Suppose a pressure-washing owner completes a job and sends Invoice #1048 for $650 on September 2. The invoice shows September 5 as its due date.
| Example date | Status | Record | Next action |
|---|---|---|---|
| Sept. 2 | Sent | $650 invoice sent with stated due date | Wait for due date under this example process |
| Sept. 6 | Overdue - Reminder Due | No payment recorded; invoice details rechecked | Send clear reminder |
| Sept. 7 | Customer Responded | Customer says they are checking payment status | Record response; set an example follow-up date rather than sending another immediate generic reminder |
| Sept. 9 | Payment Pending or Manual Review | Verify whether payment arrived and update the record from the actual result | If paid, close. If not, choose the next documented manual action. |
The useful part is not the number of days. It is that every contact changes the record and produces a deliberate next action.
Review open A/R once a week
A weekly A/R review can be simple:
- List every invoice with a remaining balance.
- Sort by due date or status.
- Verify that each open invoice has a last-contact note.
- Identify records with no next action.
- Separate straightforward reminders from disputes and exceptions.
- Reconcile payments that arrived.
- Close paid records so they stop generating work.
This review is also where patterns become visible. If many invoices reach the same problem state, the fix may belong earlier in your estimate, job-completion or invoicing process.
Spreadsheet or CRM?
A spreadsheet can handle this workflow when one person can keep the seven fields current. A CRM or business operating system becomes more useful when customer communication, multiple jobs, invoices and follow-up history need to stay connected.
If you are deciding where that crossover happens, read Pressure Washing Spreadsheet vs CRM: When Do You Actually Need Software?.
For a connected operating workbook that includes jobs, invoices, accounts receivable and money owed, see the Pressure Washing Business OS. If your immediate need is professional invoice paperwork and customer follow-up assets, the Starter Office Kit is the lighter option.
Frequently asked questions
How often should I remind a customer about an unpaid pressure-washing invoice?
Use the due date and the process you have established for your business rather than copying a universal schedule. The important part is to record each contact and customer response so automation does not continue blindly.
Should I add a late fee when an invoice becomes overdue?
Do not add a fee simply because a generic article recommends one. Fees and payment terms can have contractual and jurisdiction-specific requirements. Use the terms that properly apply to your business and get professional guidance when needed.
What if the customer disputes the invoice?
Pause routine reminders. Review the agreed estimate, approved changes, job-completion record and invoice. A dispute is a manual-review issue, not a reason to increase automated message frequency.
What if the customer says they already paid?
Pause reminders and reconcile the payment record first. If payment is confirmed, update the invoice to Paid and stop follow-up.
Do I need software for unpaid-invoice tracking?
No. A disciplined spreadsheet can work for a simple operation. The system matters more than the tool: every open balance needs a status, contact history and next action.
Make every unpaid invoice have one next action
The biggest improvement is not a more aggressive reminder. It is removing ambiguity.
Verify the invoice, give it a status, record what the customer actually said and decide the next action. When the invoice is paid, close it. When the issue becomes a dispute or exception, stop routine automation and review it manually.