The Month I Invoiced Late and Lost the Context

I had a client I genuinely liked working with. Good communicator, interesting projects, paid without a fight.

I got comfortable. Too comfortable.

Instead of invoicing monthly like I should have, I let it slide. The project was ongoing. Things were good. I told myself I would sort it out when there was a natural stopping point.

The stopping point came six weeks later than it should have.

The Invoicing Session From Hell

I sat down to build the invoice. I had time entries, mostly. Some gaps where I had forgotten to log for a few days and backfilled from memory. A few entries that just said "work" with a duration and no notes.

I had one entry that said "revisions" for four hours. I could not remember what I revised. I had another that said "call" for ninety minutes. I had no memory of what that call covered.

The invoice I was trying to write needed to make sense to a client who had not spoken to me in three weeks. I needed to be able to explain every line if asked.

I could not explain half of them.

What I Ended Up Doing

I sent a reduced invoice. Not because the client asked me to. Because I could not in good conscience bill for time I could not describe.

I wrote off probably four hours of real work because my notes were useless and I did not want to send something I would have to defend without any evidence.

Four hours is a real number. Multiplied across a year of similar situations, it is a serious leak.

The Two Habits That Broke Simultaneously

The problem was not just the late invoicing. It was that the late invoicing exposed a second problem: my time entries were not detailed enough to hold up over time.

When you invoice weekly or biweekly, vague entries are annoying but manageable. You remember what "revisions" meant because it was three days ago. You can fill in the context in the invoice description.

When you invoice six weeks later, a vague entry is useless. You have no idea what it refers to. You cannot reconstruct it without the notes, and if you did not write notes, the information is gone.

The habit of logging entries with real descriptions matters much more than it seems in the moment. It takes thirty extra seconds to write "revised homepage headline and button copy based on client feedback from March 3 call" instead of just "revisions." That thirty seconds is the difference between an invoice you can send confidently and one you quietly discount to avoid a conversation.

How Time-Trak Helped Me Fix Both Problems

I started using Time-Trak to add descriptions to every entry as I closed it out. Right when I stopped the timer, while the work was still in my head.

I also set a reminder to run a billing review every Friday. Five minutes. Look at the week's entries, make sure everything is labeled clearly, flag anything that needs to go on an invoice.

The floating timer made it easier to stay in the habit because I could see when a timer was running. If I finished a task and forgot to stop it, I caught it before too much time passed. That kept my entries cleaner.

Invoicing more frequently meant each invoice was smaller and faster to produce. I knew exactly what was on it. The client received invoices more often but for amounts that were easy to review and approve.

No more six-week gaps. No more writing off hours because I had no idea what I did.

The Uncomfortable Truth

Late invoicing feels like a cash flow strategy sometimes. Let it build up, send a bigger number, collect a bigger check.

In reality it is a data decay problem. The longer you wait, the less you can prove, the less you can confidently charge, and the more you quietly write off to avoid awkwardness.

Invoice when the work is fresh. Your notes are only as useful as your memory, and your memory has a shelf life.

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