5 Invoice Mistakes That Delay Your Payments (and How to Fix Them)

The invoice is the final metre of a long race

You did the work. You delivered on time. The client is happy. And then — silence. The payment doesn't come. You send a reminder. You wait. You send another. Three weeks later the money lands, with no explanation for the delay.

Sound familiar? Here's the uncomfortable truth: most late payments aren't caused by bad clients. They're caused by invoices that make it easy to stall, forget, or misplace.

Small friction points compound fast. An invoice without a due date becomes "I'll pay when I get to it." An invoice sent to the wrong email lives in someone's spam folder for a fortnight. An invoice with a typo in the bank details starts a week-long back-and-forth.

These are fixable. All of them.

Mistake 1: No due date, or "Net 30" buried in the footer

An invoice that says "due upon receipt" gets paid roughly 3× faster than one with vague terms or no terms at all. When there's no deadline, payment simply isn't urgent — and urgent things always win.

What to do instead:

Set a specific calendar date: Due: 11 April 2026. Not "30 days from invoice date" — that requires mental arithmetic the client won't bother with. A hard date creates a psychological anchor. Put it at the top of the invoice, not the bottom.

For ongoing work, consider shorter cycles. Net 14 is standard in many European markets. Net 7 is increasingly common for digital services. The less time between delivery and due date, the less time there is for things to fall through the cracks.

Mistake 2: Sending to the wrong person

You worked with Maya, the marketing lead. You sent the invoice to Maya. But Maya doesn't control accounts payable — that's Stefan in finance, who has never heard of you.

Invoices routed through the wrong person routinely sit in inboxes for weeks while the chain of "can you forward this to the right place?" plays out in slow motion.

What to do instead:

Ask before you invoice: "Who should I send the invoice to, and is there a PO number or reference code I need to include?" Do this when wrapping up the project, not after you've already sent it. One question saves two weeks.

Also: always CC yourself and keep a sent copy. If a client claims they never received your invoice, you want receipts.

Mistake 3: Vague line items

"Design work — €3,200" tells a client almost nothing. The more opaque the invoice, the more likely it triggers an approval loop: What exactly was this? I need to break it down for accounting. Can you send a breakdown?

Now your invoice is on hold while you go back and forth.

What to do instead:

Be specific enough that a third party (someone who wasn't in the project) can understand what was delivered. You don't need a novel — a short description plus hours plus rate is almost always sufficient:

| Description | Qty | Rate | Amount | |---|---|---|---| | Brand identity — logo, colour system, typography guide | 8 h | €120 / hr | €960 | | Website redesign — 6 pages, responsive | 18 h | €120 / hr | €2,160 | | Revision round 2 | 2 h | €120 / hr | €240 |

Clear line items also build trust. A client who can see exactly where the hours went is far less likely to push back on the total.

Mistake 4: Making it hard to pay

You send a PDF. The PDF has your IBAN at the bottom in 8pt font. The client has to open their banking app, manually type in the IBAN, the BIC, the reference, and your name. One typo anywhere and the payment bounces. They try again the next day. Or the day after.

Every step you add to the payment process is a chance for it not to happen.

What to do instead:

Add a direct payment link wherever possible — Stripe, PayPal, Mollie, whatever your setup supports. If you're bank-transfer-only, put the payment details in a visually prominent block, not buried in the document footer. Make the reference code crystal clear: Reference: INV-2026-042 — use exactly as shown.

If you're working with clients in multiple countries, check whether you need to provide local bank details or accept local payment methods. A German client paying a Dutch freelancer via SEPA instant is fast; an international wire is not.

Mistake 5: Waiting until after the project to start the clock

This is the subtlest one. Many freelancers send the invoice when the project is "done" — but done is often fuzzy. Final feedback still outstanding? One more revision? Just waiting on the client to sign off on the last file?

The longer you wait to invoice, the more time passes, the more the work fades from the client's memory, and the less urgency they feel to pay promptly.

What to do instead:

Invoice as close to delivery as possible. If your contract allows it, invoice upon delivery of the draft, not after the final approval. For longer projects, use milestone billing: 30–50% upfront, 50–70% on delivery. This isn't just good for cash flow — it's good for the client relationship, because it keeps the financial conversation active and normal throughout the project.

The compounding effect

None of these mistakes is catastrophic on its own. A vague line item here, a missing due date there — no single thing feels like a big deal. But they stack.

An invoice sent to the wrong person, with no due date, via PDF that requires manual bank transfer, for "design work" with no breakdown, will reliably sit unpaid for four to eight weeks. Fix all five issues and most invoices get paid within the first week.

The goal isn't to be aggressive about money. It's to make paying you as frictionless as possible, so that good clients — the ones who genuinely intend to pay — can do it quickly, without obstacles in the way.

auftakt turns your tracked time directly into itemised invoices. Set your rates once, track as you work, and generate a complete invoice in one click — with the right line items, the right amounts, and a clear due date already filled in.