Get paid faster: nine fixes that actually move an invoice
Simonas Petkevicius
· 9 min read

Almost nobody sits down, reads your invoice, and decides not to pay it. What actually happens is duller: your invoice enters a queue, loses to whatever is on top of it, and stays lost until someone is reminded. Every fix below does the same small thing — it removes one reason to put your invoice back down.
Late payment is a queue
Between the moment you press send and the moment money lands in your account, your invoice passes through five hand-offs. It has to arrive somewhere a human will see it, be opened, be matched to a budget, be entered into a payment run, and then actually clear. Each hand-off is a place it can quietly stop.
That reframing matters, because it changes what you do about it. If late payment were a refusal, the answer would be a harder conversation. It usually isn’t. The answer is almost always a small piece of missing information, sent to a slightly better address, a few days earlier.

1. Invoice the day the work lands
Most businesses run payments in batches — weekly, or on the 15th and the last working day. An invoice that arrives the day after a run closes doesn’t wait a day. It waits until the next one.
Which means the cheapest speed-up available to you costs nothing and takes two minutes: send the invoice when you finish the work, not when you get around to doing your admin. Batching your own invoicing to the end of the month feels efficient and quietly costs you weeks.
For anything recurring, take yourself out of the loop entirely. A schedule that generates and sends on the 1st will beat you every time, because it is never busy and never forgets.
2. Write it for the person who approves it
You know your client. The person who approves your invoice often doesn’t. They have a screen full of documents and a rule for each one: does this match a purchase order, is the supplier on file, is the tax treatment right, is the total what we expected?
Write for that person and your invoice stops being a judgement call. Six blocks do it.

Two of those are worth dwelling on, because they cause most of the bounce-backs I see.
- Their legal name, not their brand. Finance systems match on the registered entity. “Acme” and “Acme Trading Ltd” are two different payees, and only one of them is in their supplier list.
- Your tax number, if you have one. A VAT or tax registration number missing from an invoice is the single most common reason it comes back — and it comes back after a week of sitting in someone’s queue, not immediately.
3. Put their reference where they look first
If your client gave you a purchase order number, a project code, a cost centre, or even just the name of the person who signed off the work, that string is the key their system uses to match your invoice to a budget. Without it, approval doesn’t get refused — it never starts.
Print it in the header, near the invoice number, exactly as they wrote it. Not in the body of a line item, not in the email. And if they never gave you one, ask before you invoice rather than after: “Is there a PO or reference you’d like on this?” costs one message and saves a fortnight.
Almost everything that delays an invoice is information the client already has and you didn’t print.
4. Make the due date an actual date
“Net 30” is a term of art that requires the reader to know when the clock started and to do arithmetic. “Due 14 March 2026” does not. Print the date. If you want to keep the terms, print both: Payment terms: 30 days · Due 14 March 2026.
While you’re there, be honest about your terms. Thirty days is conventional; fourteen is perfectly normal for freelancers and small studios, and clients rarely push back if it’s on the engagement from the start. What causes friction is changing terms halfway through a relationship, not having short ones.
5. Send a link, not just an attachment
A PDF attachment has to be downloaded, saved somewhere, and forwarded to whoever actually pays it. Every one of those is a step where it can go missing — and attachments are exactly what mail filters strip or quarantine in larger companies.
A link opens in the browser on any device, forwards cleanly, and can’t be the wrong version. Send both: the link in the body, the PDF attached for whoever wants to file it. And send it to the accounts-payable address if they have one, with your day-to-day contact copied. The contact is who you talk to; AP is who pays you.
6. Stage the big ones
A single large invoice at the end of a long project is the worst of both worlds: it’s the one most likely to need extra approval, and it arrives when your leverage is lowest, because the work is already delivered.
Split it. A deposit up front, one or two milestones, a balance on completion. Three smaller invoices clear faster than one large one, they surface disputes while you can still do something about them, and they keep your cash flow from depending on a single event.
7. Make paying it a single action
Look at your last invoice and count the actions between reading it and the money leaving. Every one you can remove is days off the average.
- Bank details on the invoice itself, not in a separate email or a previous thread.
- The exact reference you want on the transfer, spelled out — usually the invoice number.
- The currency named, not just a symbol. “$” is at least five currencies; “USD 4,200.00” is one.
- If you take cards or a payment provider, a button that goes straight to the payment page.
8. Chase on a schedule, not a mood
Most people chase when they start to feel anxious about the money, which is both later than useful and worse for the tone of the message. Decide the schedule once, then follow it without any emotional input.
A cadence that works: a short, friendly note three days after the due date; a firmer one at fourteen days that restates the amount and the original terms; a call at thirty. Keep the first two boring and administrative — “just making sure this one didn’t get stuck” — because the overwhelming majority of late invoices are stuck, not disputed, and an accusatory first message makes the person who could unstick it defensive.
9. Keep your numbering boring
One unbroken sequence, no gaps, no restarts, no clever encoding of the client name and the month. Gaps in an invoice sequence are a red flag in an audit in most of Europe and the UK, and duplicate numbers cause your client’s system to reject the second one silently as a suspected duplicate.
INV-2026-0184 is a good invoice number. It sorts correctly, it survives a change of year, and nobody has to decode it. Whatever you pick, let software own the counter — the one thing you should never be doing by hand is remembering what number you’re on.
Doing all this without a spreadsheet
None of the above is hard. It’s just nine things to remember every time, forever, which is exactly the kind of task humans are worst at and software is best at.
That is the entire reason Invcly exists. Numbering is sequential because the app owns the counter. Due dates print as dates because the app computes them from your terms. Every invoice gets a public link and a clean PDF, because both are generated the moment you finalize it. Client details, tax numbers, and references are stored once, on the client, and come along with every invoice you write for them. Recurring work runs on a schedule so nobody has to remember the 1st of the month.
And it’s free. Not free-for-three-invoices, not free-until-you-need-a-PDF — free, with no tiers to compare and no card to put on file. If you want the longer argument for that, it’s in the best free invoicing software is the one that stays free.
Simonas Petkevicius
Founder, Invcly. Building a small, free invoicing tool for people who would rather be doing the work than billing for it. Say hello.
Keep reading
Invoice vs. receipt: what’s the difference, and when do you need each?
One is a request, the other is proof. They sit on opposite sides of the moment money moves — and mixing them up is what makes an expense claim bounce.
Read itThe best free invoicing software is the one that stays free
Free plans in this category are usually a countdown. Here is how to read one before you build a year of billing history inside it.
Read it