Track a Detailing Deposit Against the Correct Remaining Balance

Why Deposit Tracking Goes Wrong

The most common mistake is treating a deposit request as a deposit received. You send a payment link, note the amount on the job, and mentally subtract it from the total. Then the customer pays a different amount, pays late, or you refund part of it after a scope change. Now your notes and your actual bank balance tell two different stories.

A second failure is double-counting. Some operators add the deposit to the job total instead of applying it against the total, which inflates what the customer supposedly owes and creates an awkward conversation at pickup. The deposit is not extra revenue on top of the quoted price. It is an advance on the price already agreed.

The Four Numbers You Need for Every Job

You only need four numbers to track a deposit cleanly: the agreed job total, the deposit amount requested, the deposit amount actually received, and any refunds issued. Everything else is arithmetic. The balance due at pickup is job total minus deposit actually received, adjusted for any approved scope changes and minus any refunds.

Keeping these four numbers separate prevents the most common tracking errors. If a customer pays $75 toward a $100 deposit request, you have $75 received, not $100. If you later refund $25 of that for a weather reschedule, you have $50 received. The job total has not changed unless you formally revised the scope and confirmed it with the customer.

DEPOSIT BALANCE WORKSHEET

Job: ___________________________  Date: ____________
Customer: _______________________  Vehicle: __________

1. Agreed job total (before any changes):       $________
2. Scope change added at drop-off (if any):     $________
3. Scope change removed (credit, if any):      ($________)
4. Revised job total (line 1 + 2 - 3):          $________

5. Deposit amount requested:                    $________
6. Deposit actually received (date: _______):   $________
7. Deposit shortfall (line 5 minus 6, if any):  $________

8. Refund issued (date: _______, reason: ___): ($________)
9. Net deposit applied (line 6 minus 8):        $________

10. Balance due at pickup (line 4 minus 9):     $________

Payment collected at pickup (date: _______):    $________
Job fully paid? YES / NO
If NO, outstanding amount:                      $________

Notes on any discrepancy: ________________________

Hypothetical Worked Scenario: The Partial Deposit and a Scope Add-On

Suppose Marcus runs a solo mobile operation. He quotes a full interior and exterior detail for $320 and requests a $100 deposit to hold the slot. The customer pays $60 online the same day and never pays the remaining $40. At drop-off, the customer asks Marcus to add engine bay cleaning for $65. Marcus confirms the add-on, making the revised job total $385.

At pickup, Marcus needs to collect $325, not $285. His net deposit received was $60. His revised total is $385. So the balance due is $385 minus $60, which is $325. If Marcus had written down $100 as the deposit without checking what actually cleared, he would have charged $285 and eaten $40. The worksheet above keeps those numbers from blurring together.

Handling an Unpaid Deposit Request

An unpaid deposit request is a link that was sent but not paid. It is not a deposit. Do not subtract it from the job total, do not record it as income, and do not assume it will be paid before the appointment. You have three practical options: follow up and wait, require payment before you confirm the appointment, or hold the slot and collect the full balance at pickup.

Which you choose depends on your policy and your relationship with the customer. What matters for tracking is that you update your job record the moment payment actually arrives, not when you send the request. If your appointment day arrives and the deposit link was never paid, the full job total is still owed. A deposit request has no effect on the balance until money changes hands.

When You Issue a Refund

Refunds reduce your net deposit applied, not the agreed job total. If you refund the entire deposit because you had to cancel and the customer is unhappy, your net deposit applied is zero and the full job total is owed if the job is rescheduled. If you issue a partial refund as a goodwill credit, subtract only the refunded amount from what was received.

Record the date, the amount, and a brief reason for every refund. This matters later if a customer disputes a charge or asks why their final invoice looks different from what they expected. A one-line note is enough: Date, amount refunded, reason. Do not count a refund as a scope reduction unless you also formally revised the quoted services.

Keeping the Running Balance in Your Job Record

The safest habit is to update your job record in real time rather than reconstructing the numbers at pickup. When a deposit arrives, note the exact amount and date. When a scope change is approved, revise the total and note who confirmed it. When a refund goes out, subtract it immediately. By the time the customer arrives, your balance due is a subtraction you already did, not a calculation you are doing under pressure.

If you use a CRM to manage appointments and linked tasks, you can attach a note or task to the appointment record each time one of these four numbers changes. This is a process habit, not a feature. The goal is that anyone glancing at the job record can see the agreed total, what was received, and what is still owed without having to do math or open a separate spreadsheet.

Where Weavr Fits Into This Process

Weavr's appointment and CRM workflow lets you attach notes and tasks to individual jobs, which is where you can record deposit status, scope changes, and refunds as they happen. Optional per-appointment invoicing is available if you enable it, and the platform's reporting tools can help you see outstanding balances across your job list. The math itself is still yours to do, but keeping all four deposit-tracking numbers in one place inside the job record means you are not hunting through texts and bank notifications to reconstruct what happened.

Tradeoffs and Failure Cases to Watch For

The worksheet approach works only if you update it every time something changes. Operators who fill it in at booking and never touch it again are just as likely to miscalculate the balance as those who track nothing. Build a habit of opening the job record whenever a payment notification arrives or a customer texts about a scope change.

One failure case worth naming: if you use two separate tools for scheduling and payment, the deposit amount recorded in one may not match what the payment processor actually settled. Processor fees, failed payments, and chargebacks can all make the number in your notes different from the number in your bank account. Always verify received amounts against your actual payment records before finalizing the balance due, not against the amount requested or the amount shown in an email notification.

The practical takeaway

Your balance due is always revised job total minus deposit actually received, adjusted for any refunds. Update all four numbers in real time, treat unpaid deposit requests as zero until money clears, and never count a refund as a scope change.

Explore the relevant WeavrCRM workflow · Review integrations and requirements