DEV Community

Cover image for Invoicing Tips for Freelancers
Steven Snell
Steven Snell

Posted on

Invoicing Tips for Freelancers

For a long time, my invoices read like an apology.

I'd tack on a line about "no rush" or "whenever works." I'd bury the total somewhere in the middle of a paragraph instead of putting it where anyone could actually find it. On one invoice, early on, I wrote "sorry to send this over" right at the top, like asking to be paid for finished work was an imposition I needed forgiveness for.

Clients paid late. I figured that was just the job.

It took me an embarrassing while to connect those two things. The invoice wasn't some neutral bit of admin that happened after the real work ended. It was the last thing a client experienced from me, and I was closing out every single project on a note of hesitation.

The invoice is the last thing they feel

Think about how a project actually ends. You do great work, you deliver, maybe there's a warm email thread where the client tells you they're thrilled. Good feelings all around.

Then you send an invoice, and if that invoice is confusing or sheepish or vague, it drags the whole experience down a notch on the way out the door. The client's final impression of working with you isn't the polished deliverable anymore. It's the awkward money moment you created at the end.

I don't think most freelancers see it this way. We treat the invoice as a chore to get through, so it comes out rushed and half-hearted, and then we wonder why getting paid feels like pulling teeth. The client picks up on all of it. An invoice that looks like you weren't sure you were allowed to send it teaches people to treat it as optional.

What my bad invoices were actually communicating

Here's the uncomfortable part. When I went back and looked at the invoices from my first few years, the problem wasn't the numbers. The numbers were fine. It was everything around them.

"No rush, whenever's convenient" told the client the deadline was theirs to set. So they set it wherever they liked, which was usually much later than I'd hoped. The apology at the top told them I felt bad about the whole transaction, which is a strange feeling to hand someone right when you want them to take you seriously and open their wallet. And the missing or buried due date meant there was nothing concrete for anyone to act on.

Every one of those choices came from the same place, which was a quiet discomfort with asking for money. I dressed it up as being easygoing and low-maintenance. Clients read it as uncertainty.

The freelancers I know who get paid fast and without drama aren't harder or colder about it. They're just clear. Their invoices state what the work was, what it costs, when it's due, and how to pay. No hedging, no throat-clearing, no emotional weather report about how they feel sending it.

Rewriting the whole thing

So I rewrote mine, and honestly the changes were small. That's the part that annoyed me most, that it was this easy and I'd spent years not doing it.

First, I put the due date on there and made it specific. Not "net 30 whenever" but an actual date, in plain sight. A real date gives a client something to plan around. A vague window gives them permission to forget.

Second, I cut every apologetic word. All of it. The invoice now says what the work was and what's owed, and then it stops. It turns out you don't need a soft cushion of "so sorry to bother you" language around a number the client already agreed to pay.

Third, I made the line items readable to a normal human. Instead of one lump labeled "content services," I break it into what I actually delivered, in words the client would recognize from our conversations. This does two useful things. It reminds them of the value they got, and it heads off the "wait, what is this for?" email that stalls payment for a week.

And fourth, I stopped treating the payment terms as negotiable body language. Deposit up front for bigger projects, balance on delivery, due dates that mean something. When I present that as simply how I work, clients treat it as normal. Back when I presented it as a nervous request, they treated it as a nervous request.

The part that surprised me

I expected clients to push back on the more direct invoices. Some corner of my brain was braced for someone to reply, "wow, a little pushy with the due date, aren't we?"

Nobody did. Not once.

What actually happened is that people paid faster, and the money conversations that used to feel fraught just got boring, which is exactly what you want them to be. A clear invoice reads as competence. It signals that you've done this a hundred times, that you have a process, that you're a professional who expects to be paid on schedule because that's how professionals operate. Clients respond to that. They pay competent-looking invoices before they pay the sheepish ones, because the sheepish ones feel skippable.

I used to think the way to keep clients happy was to be maximally accommodating right up to the last second, including about money. I had it backwards. Being clear and matter-of-fact about payment is part of being good to work with. It removes a source of confusion and low-grade tension from the relationship, and it lets the project end the way it should, on the strength of the work rather than on an awkward ask.

The invoice is the last handshake. Make it a firm one.

How do your invoices read right now, if you go back and look at them cold? Mine didn't say what I thought they said.

Top comments (0)