The invoice you're afraid to send

Sending it puts you in the position of asking for money. That position is uncomfortable in a way the actual work never was.

Why it waits

An invoice is shaped like a request: your name, a number, a date, an implicit please. The work was agreed weeks ago and delivered. The document records what already happened.

Read it as a request and you start waiting for a good moment to ask. There isn't one.

The price was settled before you started. It's in an email, or in a call where someone said “sounds good”. The invoice doesn't reopen that conversation.

If you catch yourself adding a discount nobody asked for, the discount is what you're paying to skip a conversation you'd rather not have.

The third one is harder to say out loud. You know how long the work took, including the parts you did from memory, so the number looks large next to the effort.

Nobody buys a process. The client is paying for a site that works, or a document they can send to their board without editing it first. Your hours are how it got made.

What changes it

Three changes, and all of them are paperwork.

Put the due date in the contract. “Net 14” agreed at signing is a term. The same words appearing for the first time on an invoice are a surprise, and surprises get argued with.

Send it the day you deliver. The delivery email and the invoice leave together. The next morning is when the second-guessing starts, and it doesn't stop on its own.

Make it boring. A boring invoice gets paid on schedule. An apologetic one, the “so sorry to bother you, totally understand if it takes a while” kind, tells the client the timing is flexible. They'll take you at your word.

Six fields

Miss one and you'll spend a week chasing it.

1. A number that increments. 2026-011 rather than invoice-final-v2. It signals you have a system, which signals you'll notice if it isn't paid.
2. Issue date and a due date. A real date: Due 19 November. “Within 30 days” is not a date.
3. A description the client recognises. The thing they asked for, described the way they'd describe it.
4. Amount and currency. Explicit. $4,200 USD. If you work across borders, this is where you prevent a two-week email thread.
5. How to pay. Account details or a payment link, on the invoice. Leave out “let me know and I'll send details” and you save a round trip.
6. What happens if it's late. One line is enough: Late payments incur 2% per month. You probably won't enforce it. Having it changes the timeline.

The three emails

Length reads as anxiety, so keep them short. Each of the three below runs under forty words.

Day 1, the due date. Assume they forgot. They probably did.

Subject: Invoice 2026-011, due today

Hi [name], invoice 2026-011 is due today. Attached again in case it got buried. No action needed if it's already scheduled.

Day 8. State the fact.

Subject: Invoice 2026-011, 8 days overdue

Hi [name], invoice 2026-011 was due on 19 November and hasn't landed yet. Can you confirm it's in your payment run, or let me know if something's blocking it?

Day 22. Name the consequence.

Subject: Invoice 2026-011, pausing work

Hi [name], invoice 2026-011 is now 22 days overdue. I'm pausing new work on [project] until it's settled. Happy to jump on a call if there's a problem I don't know about.

None of the three apologises or justifies. None of them says “just checking in”, because that phrase tells the client the due date is negotiable.

Today

Open your drafts and send the invoice before you reread it.

You did the work already. The invoice is the other half of the same trade. It's the part that gets you paid.

Next week: the proposal that wins by saying what you won't do.