The Deposit You Forgot to Subtract
Invoicing mistakes don't always mean undercharging. Sometimes they mean billing a client for money they already paid.
Most billing accuracy conversations focus on undercharging. Making sure you captured all the hours. Making sure you didn't give away a revision round for free. Making sure your rate held through the whole project.
But there's another kind of billing error that's just as damaging to your professional reputation, and it runs the other direction. Billing for a deposit the client already paid.
It happens more than most freelancers admit.
How the Math Gets Fuzzy
You close a project. You pull up your time logs. You build the invoice based on hours worked times rate. You send it.
Then the client emails back and says they already paid a deposit at the start of the project. You know this. You collected it. But in the rush to get the final invoice out, you built it from your hours total without subtracting what you already received.
Now you've sent a client an invoice that overstates what they owe. The client catches it. You have to correct it. You've introduced friction and made yourself look sloppy at the exact moment you're trying to close out the relationship cleanly.
Or worse, the client doesn't catch it. They pay the full amount. You don't notice for a few weeks. Now you have to explain to someone who already paid you that you accidentally overcharged them, and you'd like to refund the difference or credit it forward.
Neither scenario feels good.
The Deposit Isn't Just a Payment. It's a Data Point.
When you collect a deposit, it needs to live somewhere that connects to your project record, not just your bank account.
The habit of recording it in your project notes or time tracker at the time of payment is what prevents the problem. When you sit down to invoice at the end, the deposit amount is already there, attached to the project, visible before you write the final number.
In Time-Trak, you can build your final invoice directly from logged hours. The structure forces you to work from the project record rather than from memory. That's where you'd catch the deposit before the invoice goes out, because you're looking at the project as a whole, not piecing together a number from scratch.
The Invoice You Send at the End of a Long Project
Long projects are where this gets especially messy. A three-month engagement might have had an upfront deposit, a mid-project payment, and a final invoice. By the time you're writing that last invoice, the earlier payments feel distant.
If you aren't tracking what's been collected alongside what's been worked, the final invoice becomes a guess. You're trying to remember what you received, subtract it from a total you're calculating on the fly, and produce a number that's accurate to the client's ledger.
That's a lot of steps with no safety net. And the error, when it happens, shows up at the worst possible time, right when the client is deciding whether they'd refer you to someone else.
Clean Invoices Come From Clean Records
The discipline here isn't complicated. It's just consistent.
Log your hours in real time. Record deposits when you receive them, attached to the project. When you build the final invoice, start from the project record, not from a fresh sheet. Check the math before you send.
None of that is extraordinary. But it's the difference between an invoice that closes a project professionally and one that opens a conversation you didn't plan to have.
Billing accuracy cuts both ways. Your client deserves to pay what they actually owe, and so do you. Getting the number right means accounting for everything, including what they've already given you.
Track your time, bill every minute.
Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.
Free during beta.
Download Time-Trak →macOS + Windows · Floating widget · Auto screenshots