A customer pays a $1,200 deposit on a $6,000 kitchen remodel. Three weeks later they pay $2,000 cash when drywall goes up. Then they Venmo you $500 for a change order you forgot to invoice separately. Now it's time to send the final bill, and you're trying to remember: is the balance $2,300 or $3,300? If the answer lives in your head, a text thread, and a stack of paper receipts, you're one busy week away from either under-billing a customer out of $1,000 or chasing money that was already paid — which is its own kind of embarrassing phone call.
Partial payments aren't the problem. Losing track of them is. The fix isn't complicated, but it does mean treating every job as one invoice with a running balance, not three or four separate transactions you're mentally stitching together at the end.
{"h2":"Start With One Invoice, Not Three Receipts"}
The most common mistake is generating a new document every time money changes hands — a deposit receipt, a progress payment receipt, a final invoice — with no link between them. Each one looks fine on its own. Together, they're a reconciliation project. The customer has three pieces of paper and no single number that tells them what they still owe. You have the same problem, multiplied across every active job.
The better model is one invoice per job that stays open from the first deposit to the final payment. Every payment — deposit, progress draw, change order, final balance — gets logged against that same invoice as a line item. The invoice total doesn't change unless the scope changes; what changes is the running balance due, which drops every time a payment posts. At any point, you or the customer can look at one document and see exactly what's been paid, what hasn't, and what the job originally cost.
If you're not sure how to structure the deposit-to-final-payment sequence in the first place, deposits, progress payments, and final payments explained covers how to split a job price into stages that make sense for both sides before you ever get to the tracking part.
{"h2":"What the Customer Should See on the Invoice"}
A customer who's made two partial payments should never have to ask "wait, how much have I paid so far?" The invoice should answer that without a phone call. At minimum, show:
{"ul":["The original contract or estimate total","Any approved change orders added to that total, itemized separately so the customer can see what changed the price","Each payment received, dated, with the method (check, card, Zelle, cash) and the amount","A running balance due that updates automatically after each payment","The next amount expected and when it's due, if you're on a milestone schedule"]}
This matters more than it sounds like it should. Disputes over "I already paid you for that" almost always trace back to a customer who never had a document showing cumulative payments in one place — they paid a deposit by check, a progress payment by card, and have no way to add those up against what they were quoted. Giving them that view up front heads off the argument before it starts.
{"h2":"How to Record a Payment Against a Specific Invoice"}
Every payment you receive should be applied to the invoice it belongs to, the moment you receive it — not batched up at the end of the week from memory. When a $2,000 progress payment comes in, it should be recorded against that job's open invoice, with the date, method, and amount, immediately reducing the balance due. If you wait and try to reconstruct payment history later from bank deposits and memory, you will eventually misattribute a payment to the wrong job, especially if you're running two kitchen remodels at once for customers with similar names.
A few habits that prevent this:
{"ul":["Record the payment the same day it's received, not at invoicing time","Always note the method — a $500 Zelle and a $500 check look identical on a balance sheet but very different on a bank statement when you're trying to match things up later","If a payment covers a change order and not the base contract, label it that way so the itemization stays clean","Never delete or overwrite a prior payment record to \"fix\" a balance — add a correcting entry instead, so there's a paper trail if a customer ever questions it"]}
If you're billing across multiple approved change orders on the same job, the payment tracking gets more layered — you may have a deposit against the base contract plus partial payment against a later change order. That scenario is worth handling deliberately; see how to invoice a customer when a job has multiple approved change orders for how to keep the math straight when the scope has shifted more than once.
{"h2":"Progress Payments Tied to Milestones"}
On larger jobs, payments are often tied to specific points in the work — deposit at signing, draw at rough-in, draw at drywall, final payment at completion. The tracking question here isn't just "how much have they paid" but "are they paid up to the stage we're actually at." If a customer is two milestones behind on payment and the crew is already three days into the next stage, that's a cash flow problem you want to see coming, not discover when payroll is due.
The simplest way to catch this is to tie each milestone payment to a specific trigger before the crew moves to the next phase — don't start drywall until the rough-in payment has cleared, for example — and to flag any invoice where the expected payment date has passed without a payment logged. That flag is more useful than a spreadsheet column, because it surfaces the problem automatically instead of requiring you to remember to check.
{"h2":"Chasing the Remainder Without Losing Track of What's Already Paid"}
When it's time to follow up on a balance, the message should always reference the real number — not a rounded guess. "You're all paid up except the final $1,800" lands very differently than a vague "just checking on the remaining balance," because the customer can verify it against their own records instantly instead of wondering if you've double-counted something. A follow-up that references the wrong balance — even by $50 — gives a slow-paying customer an easy reason to stall while they "look into it."
This is also where a clean payment history protects you if a customer disputes the balance. If every payment was dated, method-tagged, and applied to a specific invoice, you can show exactly what was paid and when in under a minute. If you've been working from memory and loose receipts, that conversation takes a lot longer and you're negotiating from a weaker position. For the broader playbook on collecting what's owed without burning the relationship, how to follow up on an unpaid contractor invoice walks through timing and tone for each stage of the chase.
{"h2":"Where Trusso Fits"}
Trusso keeps one invoice per job with every deposit, progress payment, and final payment logged against it automatically, so the balance due is always current and the payment history is always visible to both you and the customer — no separate receipts to reconcile. It's part of the same flat-rate plan as estimating, scheduling, and crew management: $29/mo for an owner plus two crew, $59/mo up to ten, or $99/mo unlimited, with no per-user fees and a 14-day free trial to see if it fits how you actually bill jobs.
Run your business the simple way
Try Trusso free for 14 days and send your first estimate in minutes.
Start 14-Day Free TrialKeep reading
What Is Construction Takeoff Software and Do Small Contractors Need It?
Takeoff software measures quantities—areas, lengths, counts—straight from plans so you can price a job without a tape measure and a calculator. Here's when a small contractor actually needs it.
Read articleComparisons7 Best Contractor Foreman Alternatives for General Contractors
Contractor Foreman covers a lot of ground but little of it goes deep. Here are 7 alternatives GCs switch to once they need real takeoff, sub bid-outs, or sharper scheduling.
Read article