BILLWICK
Why do my clients keep paying late?
Five reasons invoices sit unpaid, and the fix for each one — written so you can apply it to your next invoice with whatever tool you already use.
Five reasons invoices sit unpaid, and the fix for each one — written so you can apply it to your next invoice with whatever tool you already use.
You finished the work weeks ago. The file is delivered, the client is happy, and your money is somewhere in their accounts payable queue, taking its time. Late payment is one of the least pleasant parts of freelance work — not finding clients, not scope creep. Getting paid on the schedule you actually agreed to.
The uncomfortable part is that late payment is rarely about whether the client likes you. It is about friction: small gaps in the invoice that let it slip to the bottom of a stack. Here are five common reasons, each with a fix you can make before your next one goes out.
An invoice that says Due on receipt or Net 30 hands the timing decision to someone else. Their accounts team batches payments on whatever cycle suits them, and a document without a hard date never becomes overdue in anyone's system — so nobody notices it slipping.
The other failure mode is vagueness by politeness: writing “when you get a chance” because a firm date feels aggressive. It isn't. A date is the least confrontational way to be clear, because it removes the need for a follow-up conversation entirely.
The fix
Put one real calendar date on the invoice — Payment due by 30 October 2026, not a term. Work backwards from when you need the money: send on the 1st with 14-day terms, and the date reads 15 October. Any invoicing tool, spreadsheet template or PDF lets you type this. Say it once more in the email subject line so it survives being forwarded.
A lot of mid-sized clients don't pay invoices. They pay purchase orders. If your document doesn't carry the PO number they gave you, the reference they use internally, the correct legal name of their entity, or a tax/VAT identifier where one is required, it fails a validation step before a human ever decides anything. It goes back to the requester, who forwards it back to you, and the clock restarts.
Ask each client once, at the start of working together, what their accounts team needs to process a payment. Write the answer down. Then never send an invoice without those fields filled.
The fix
Build a short checklist into your template: PO number, client entity name, your address, sequential invoice number, service period, due date. Five minutes once per client, saved forever after. If a client has paid you before, forward them last month's invoice and ask “same details?”
You have a good relationship with the design lead, the founder, the marketing manager. So the invoice goes to them. They forward it to finance on a Tuesday, it lands in a shared inbox nobody owns, and by Friday it has been forgotten twice. Every handoff is a place an invoice can quietly die.
Worse: many companies route invoices through a portal or a dedicated billing address, and anything sent to a personal email is technically not received at all. The client isn't stalling. Their system never got the document.
The fix
Onboarding question #2, right after payment terms: “Who should the invoice go to, and is there a billing address or portal I should use?” CC your contact so they can nudge internally. If they insist on a portal, register once and note the steps somewhere you'll find them next time.
Your client pays many other suppliers too. Their accounts payable queue is a list sorted by whoever complains loudest, not by who was owed first. Silence reads as “not urgent,” and the invoice drifts down the stack without anyone deciding anything.
Following up is usually skipped for a simple reason: nobody wants to be the annoying one. The trick is that a short, boring, factual note isn't annoying — it's administrative. Save the emotional apology for the third one, and even then keep it brief.
“Hi Ana — quick note that invoice BW-2026-0148 ($2,400) fell due yesterday. Attached again in case it got buried. Let me know if you need anything else from me.”
“Following up on BW-2026-0148. Could you confirm which date it's scheduled for? Happy to resend to a different address if accounts needs it elsewhere.”
“Still no payment on BW-2026-0148. Can we get a call on this week — I'd rather pause new work until it's settled than let it run on.”
The fix
Pick two dates now and put them in your calendar when you send: one nudge the day after it's due, one a week later. Copy the wording above and change the numbers. If chasing feels confrontational, remember you're asking for money for work already finished — the awkwardness is not yours to carry.
Open the attachment, read the number, switch apps, find their banking site, paste carefully, come back, type your reference wrong, start over. Every step is a reason to click “I'll do it later” — and later has no deadline attached to it.
It helps to make payment as easy as possible: a link that opens a page where the amount is already filled in and they just choose how to pay. Card for small invoices, bank transfer for large ones, because different clients genuinely mean different things by “easy.”
The fix
Stop sending attachments as the only path. Put a payment link at the top of the email body, not buried in a PDF. If your client's finance team insists on manual transfers, give them a clean block with everything in one place: amount, reference, both account identifiers, and the due date repeated.
Five fixes, none of which require changing tools. But if you're doing all of this by hand every month, there's a version where it's already done for you.
Full disclosure again: we're Billwick, and this piece is ours to write. Here's what it handles from the list above, and what you can do without it.
It is invoicing software for freelancers and small studios. One screen holds the invoice and everything accounts teams ask for, so nothing gets returned for a missing reference. Reminders go out on their own, in a tone you'd actually send. And the client pays from the invoice itself, by card or bank transfer, without leaving the page.
Invoice number, due date, PO field, entity name, line items with service dates — filled once per client, reused on every invoice after.
Nudges go out on day 1, day 7 and day 14 in plain language. You don't write them, and you don't have to be the bad guy twice.
The client opens your invoice, picks how they want to pay, done. No attachment to download, no numbers to retype.
You set the schedule once per invoice. These are the messages that go out on their own — no calendar reminders for you, no awkward re-read of your own sent folder.
“Hi Ana, a friendly note that invoice BW‑2026‑0148 fell due yesterday. You can pay by card or transfer right here.”
“Still waiting on BW‑2026‑0148 ($2,400). Could you let us know which date it's scheduled? Happy to resend if accounts needs it elsewhere.”
“One more nudge on BW‑2026‑0148. If something's holding it up, tell us and we'll sort it out directly.”
Reminders stop. The invoice is marked settled. You get one notification, not three.
Fourteen days, full features, no card needed to start. Send a real invoice to a real client and see whether the reminders do their job.
Screenshot this and keep it next to your invoice template. None of it depends on Billwick.
Made with Octet Prow