The Late Invoice I Blamed on the Client

My Favorite Complaint

For most of last year, I had a running complaint about one particular client. They always paid late. Not by a lot. Usually five to ten days past the due date. But it was consistent. Every single month.

I had mentally tagged them as the late payer. I mentioned it to a freelancer friend once over coffee. I had started building a small cushion into their invoices to compensate for the cash flow lag.

Then I looked at my actual send dates.

What the Records Showed

I was sending their invoice late almost every month. Not by a lot. Usually three to five days after the date I had promised them. But combine my late send with their thirty-day terms and my aggravation about a payment arriving around day thirty-five suddenly looked very different.

They weren't late. I was. And because they paid within a week of receiving the invoice, they were actually being perfectly reasonable. I had just never checked my own end of the timeline.

This is the kind of thing that only shows up when you have records. When you're billing from memory and sending invoices whenever you get around to it, you lose track of your own patterns. You remember the parts where clients behave badly. You forget the parts where you contribute to the problem.

The Gap Between When I Finished and When I Billed

When I dug further into my billing history, I found a consistent gap between when work finished and when I sent the invoice. Sometimes it was a few days. On two projects it had been more than two weeks.

Part of that was workflow. I didn't have a clear end-of-project trigger that included sending the invoice. Work would wrap up, the client would go quiet, and I would move on to the next thing. The invoice would come later, whenever I remembered.

Part of it was avoidance. Sending an invoice means the client has a number in front of them. If they have questions or pushback, it starts then. I had a habit of putting that moment off without consciously deciding to.

Both of those patterns cost me money and made me slower to get paid than I needed to be.

How Tracking Helped Me See My Own Behavior

Once I started logging project time in Time-Trak, I had a clearer picture of when work actually ended. The timer stopped. The report was right there. The invoice should go out the same day or the next morning. There was no good reason to wait.

I built that into my closing routine. Project done, timer stopped, report pulled, invoice sent. The steps connect directly because the tool makes them connect. I'm not going back to a calendar or a notebook or my memory to figure out what I worked on. It's all in the report.

My billing got faster. The client I had been silently blaming for months started paying on time. Turns out they had been on time for a while. I had just been measuring from the wrong starting point.

The Lesson I Didn't Enjoy

It's easy to build a story around a difficult client. Late payers, scope creepers, bad communicators. Some of those stories are accurate. Some of them are accurate only because you're looking at their behavior without looking at your own.

I was handing invoices to that client late and wondering why the money was slow. The records made that impossible to ignore once I actually looked at them.

If you're frustrated with a client's payment timing, check your send dates first. You might find out the story is more complicated than it looked.

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.

macOS + Windows · Floating widget · Auto screenshots