Invoice Hours Don't Match Client's? The Paddling Pool

2026-10-25

The email arrives at 14:20 on a Thursday. You read it standing barefoot on the lawn, one hand on a garden hose.

"Hi Mara, thanks for the invoice. Our records show about 31 hours on the project, but yours says 42. Could you send a breakdown?"

Behind you, your niece is shrieking happily in a paddling pool. You're minding her for the afternoon so your sister can get to an appointment. The water is too cold, and the sun is out. Your stomach has dropped anyway.

Eleven hours. That's a lot of hours to explain from a lawn.

The sentence you can't say

Your first thought isn't they're wrong. It's am I wrong?

You know you worked on the project. You remember the long Tuesday of rewrites and the three calls that ran over. You remember the weekend you promised yourself you wouldn't touch it, and then did, for an hour, at the kitchen table.

But remembering isn't the same as showing. Your records are a notes app with half-finished lines, a calendar with a few blocks that didn't quite happen as planned, and a timer you started on some days and forgot on others. The 42 on the invoice came from adding it all up one evening and rounding to what felt fair.

Now the client has asked a perfectly reasonable question, and you realise you don't have a perfectly reasonable answer ready.

You type a reply. "Of course, I'll send a breakdown shortly." You delete "shortly." You put it back. You put the phone face-down on the patio table, next to a plate of orange slices nobody is eating.

What it quietly costs

Nothing happens for the next hour, and that's the problem. You wave at the pool, refill the hose, and laugh at the right moments. Underneath, a small voice runs its loop.

What if they think I padded it? What if I did, a little, without meaning to? What if I cut the invoice to 31 just to make this go away?

That last thought is the one that bothers you most. Not because 31 is unreasonable, but because you'd be agreeing to it out of discomfort, not out of facts. Maybe the real number is 34. Maybe it's 40. You honestly can't tell.

So you'd either defend a number you can't prove or give away hours you did work. Either way you'd feel a bit less like a professional and a bit more like someone guessing out loud.

That's the quiet cost. It isn't only the eleven hours. It's the small crack in how you see your own business.

The evening that went differently in your head

Later, with the pool drained and your niece asleep in the car seat, you sit on the back step and imagine the version of this where the email doesn't scare you.

In that version, you open one file. The project is there, with its hours listed by date, each with a short note. Tue, 3.5 h, rewrite of onboarding screens. Thu, 1 h, call with their product lead. The invoice sits right beside it, and the two agree because they came from the same place.

You don't need a clever defence. You copy the list into a calm reply: "Here's the breakdown. If any date looks off to you, tell me and we'll look at it together."

That last line is the part you'd actually like to be able to write. It's open, it's friendly, and it works because you're not afraid of the answer.

And if one entry turns out to be wrong, say a call that was shorter than you logged, you'd simply fix it. A small correction between two people who trust each other, not a verdict on whether you can be trusted.

An ordinary Monday, afterwards

The picture you keep returning to is surprisingly small. It's Monday morning, coffee in hand, and you're logging Friday's two hours before you've even opened your inbox. It takes less than a minute. Nothing feels dramatic.

When a client writes "quick question about the hours," you read it the way you'd read "quick question about the colour." You open the project, find the line, and answer.

The invoice is no longer a number you assembled from memory on a tired evening. It's a record that was already there, and you're only reporting it. You'd still make the occasional mistake, because everyone does. But a mistake you can see and fix is a very different thing from a hole you can't find.

And on a Thursday afternoon with a hose in your hand, the email would just be an email.

What you actually do that evening

In the real version, you spend two hours digging through the notes app, the calendar and a chat thread, rebuilding the project hour by hour. It's tedious but doable. You find 38 hours you can stand behind, with dates. Four hours fall into the gap between what you remember and what you can show.

You send the breakdown with the 38, and you add a kind, honest line about the rest. The client replies the next morning, politely, and the matter settles.

It turns out fine. But you close the laptop knowing it only turned out fine because you had a free evening and a good memory, and that next time you might have neither.

A quieter way to keep the record

We built the Get Paid On Time – Freelance Invoice, Hours & Client Tracker for exactly that gap. It's an Excel tracker where your clients, projects, hours and invoices live side by side, with auto invoice numbers, due dates, overdue flags and a simple dashboard. It comes with sample data so you can see how it looks filled in, plus a short PDF guide. It's made to be set up in a few minutes: enter one client, and the overview starts to fill.

It won't settle a disagreement for you, and it doesn't replace talking to your client. It simply means that when someone asks about the hours, you already know the answer.

There's a 30-day money-back promise: if it doesn't help, you get a full refund, no questions asked.

See the Freelance Invoice, Hours & Client Tracker →

An illustrative story, written with AI assistance.