What to Do About a Client Who Pays Late Every Single Time
There's a particular kind of client you've probably met by now. The work is good. The meetings are friendly. They renew the project, refer you to a colleague, o...
A practical case for sending invoice reminders BEFORE the due date — the timing that lifts on-time payment rates, the language that protects the relationship, and the templates you can paste in tonight.
It is the third week of the month and you are looking at an invoice that went out 21 days ago. The due date is Friday. You are running the familiar debate — send a reminder now, or wait until it is officially late so you do not look pushy? You wait. Friday comes. Nothing arrives. By the time you send the polite nudge, the invoice is two weeks past due and the whole exchange feels heavier than it should.
If you run a one-person business or a small team, that loop is the default. Most people only think about reminders after a payment is late, which means the entire conversation lives in the awkward zone — asking for something the client already promised and forgot to deliver. There is a calmer version of the same workflow, and it starts a few days earlier than you think.
This post is the case for moving your reminders to BEFORE the due date — and the practical playbook for doing it without sounding nervous or premature. You will find the timing windows that consistently lift on-time payment rates, the wording that keeps the message warm, the three scenarios where a pre-due nudge is the wrong call, and a short FAQ for the questions that come up the first time you try it.
When the first reminder a client sees arrives after the due date, two things happen at once. The client realizes they missed something — which is mildly embarrassing — and you are asking for money they already agreed to send. Even when the message is friendly, the dynamic has changed. The conversation is no longer a routine business event; it is a small failure you are pointing out, however gently.
The data backs up the discomfort. According to U.S. Chamber of Commerce small business research, roughly half of small-business invoices are paid late, and most of that delay is not clients refusing to pay — it is clients forgetting, misfiling, or losing track of an invoice that arrived a few weeks earlier and quietly slid down the inbox. After-the-fact reminders try to recover from a memory problem after the memory has already failed.
A reminder sent BEFORE the due date sits in a completely different psychological frame than a reminder sent after. The before-due note is helpful information. The after-due note is a request for action that is already overdue. Same words, totally different temperature.
When you send a friendly heads-up a few days early, the client reads it as a service. No implied accusation, no pressure to apologize, no scrambling. They open the email, see they have a few days, and either pay it or flag it to whoever handles their bills. You have not asked them to fix a problem — you have helped them avoid one. That subtle shift is most of the reason these reminders work.
There is also a salience effect. Most invoices land in inboxes that hold dozens of unread messages a day. The original gets buried within 48 hours. A second message a week before the due date is often the first time the invoice is actually visible again. You are not nagging — you are surfacing something that disappeared.
There is no single right time to send a pre-due reminder, but a few windows show up over and over in the operations of service businesses that get paid quickly. Pick the one that fits your invoice cadence and stick with it long enough to see the effect.
For Net 30 invoices, one reminder seven days before the due date covers most payment behavior. It gives the client a week to act, which clears most internal accounts-payable cycles, and lands in a window where the client still associates the invoice with the work it covers. Earlier than seven days feels premature; later than three days does not give bigger clients time to push it through their own approvals.
For Net 15 invoices, a reminder three to five days before the due date is the sweet spot. The total runway is shorter, so the message has to land while there is still time to act. For invoices billed at project milestones with no fixed due date, a single reminder one week after the work was delivered often performs the same function. If your work involves recurring monthly retainers, a fixed day of the month — say the 25th — turns into a predictable rhythm the client comes to expect.
The biggest worry about pre-due reminders is sounding distrustful, as if you assume the client is going to stiff you. The fix is not to over-soften the message — apologetic emails feel worse, not better — but to write it as a service note.
Subject line: "Quick reminder — invoice [#1042] is due [Friday, May 16]"
Body: "Hi [Name], just a quick heads-up that invoice [#1042] for [project] is due on [Friday, May 16]. The original invoice is attached again for convenience, and you can pay through [your usual link]. If anything looks off or you need it re-sent to a different email for processing, just let me know — happy to sort it out. Thanks again for the work this month."
Notice what is doing the work. The subject line states the date so the email is useful even unopened. "Heads-up" rather than "reminder" positions the note as helpful information. Re-attaching the invoice removes a step. The line about resending to a different email pre-empts the most common reason invoices get lost — they went to the wrong inbox. And the close thanks the client for the work, not for paying, which keeps the relationship in the foreground.
If you are looking for wording for the messages that come AFTER the due date, the first reminder email guide covers the next step, and the broader 2026 payment reminder playbook maps the full cadence.
A pre-due reminder is the right default for most invoices, but there are three situations where it can backfire. Knowing them up front saves you from learning each one the hard way.
The first is a client who pays consistently without any prompting. If a client has paid every invoice within five days of receipt for the last six months, a pre-due nudge introduces noise into a system already working. Skip it for that account, and reserve your pre-due cadence for clients whose payment patterns are less reliable.
The second is an invoice that is part of an active back-and-forth — disputed scope, a pending change order, a question about totals. Sending a pre-due reminder on top of an unresolved conversation reads as if you are trying to push past the open question. Resolve the substance first; the timing reminder belongs only on invoices both sides agree on.
The third is a short window — the first few business days of January, or the week of a major holiday — when the client's accounts-payable team is closed or skeleton-staffed. A reminder three days before a due date in that window does not produce a faster payment; it produces an out-of-office reply. Send it a week earlier or a week later instead.
When you add a pre-due reminder to your standard sequence, the rest of the cadence gets quieter, not louder. The friendly note three days after the due date — usually the first uncomfortable message — becomes the SECOND touch instead of the first. You can write "following up on my note from last week" instead of "this is to remind you that this invoice is now overdue," which is a much warmer opening even when the facts are identical.
The downstream effect is that fewer invoices ever reach the harder messages — the second reminder, the final notice, the conversation about a payment plan. For freelancers and small teams who already feel the friction of those messages, the volume drop is the real return. For the underlying behavioral logic in more depth, the psychology behind friendly reminders is the companion piece.
If you do most of your reminders by hand, you can layer this in tomorrow with a calendar block — ten minutes on a Monday morning to scan upcoming due dates and send the heads-up notes. If you run higher invoice volume, a tool like DueDrop can run the pre-due touch automatically alongside your existing invoicing setup, so the cadence happens whether or not you remember to look.
Not when it is written as a heads-up rather than a request. Most clients read a friendly pre-due note the same way they read a flight check-in reminder — useful information, not an accusation. The frame depends almost entirely on the wording, which is why the template above leans on "heads-up" and "happy to sort it out."
Anything earlier than ten days feels premature on a Net 30 invoice — the client just received the original and a second touch can read as nervous. The reliable window is three to seven days for Net 30, and three to five days for Net 15. If you are testing this for the first time, start at seven days and adjust from there.
Yes. Re-attaching removes the most common excuse — "I cannot find your invoice" — and shortens the path by one step. Many invoicing systems also let you re-send the original from inside the platform, which preserves the link to the same record so you do not end up with two open invoices in the client's books.
Yes, arguably better than for one-off projects. A pre-due note on a recurring invoice becomes a reliable monthly ritual. After two or three cycles, clients learn to expect it and route the invoice on the same day each month, which makes your cash flow much more predictable.
Move one reminder earlier and the whole conversation gets easier. You stop chasing late payments and start preventing them — and it costs nothing more than the ten minutes a week it takes to send the heads-up.
Connect your tools in five minutes. Let the first reminder go out tomorrow morning — sounding exactly like you'd write it yourself.
Start my free 14-day trial