Client Promised Payment but Didn't Pay: How to Follow Up Professionally
There is a unique kind of irritation reserved for this exact moment:
Your client emailed you on Tuesday saying, “So sorry for the delay! I’m sending this to our accountant right now, it will be paid by Friday.”
Friday afternoon comes and goes. Saturday passes. Monday morning arrives. You log into your bank, refresh the screen twice, and see… nothing.
Now you're in an awkward bind. They didn't just ignore you; they made an explicit promise and broke it. Your instinct might be to feel disrespected or lied to. You want to ask, “Hey, you said Friday, what happened?” But you worry that calling them out will make things tense or awkward.
Here is the truth: most broken payment promises aren’t deliberate lies. More often, your contact approved the invoice and assumed their accounting department paid it, or an unexpected fire drill consumed their Friday afternoon.
Your job isn’t to accuse them. It’s to use their own commitment as a polite anchor to close the loop.
1. The Direct Follow-Up Template
Send this on Monday morning or Tuesday if a promised Friday payment didn't arrive. Keep it short, neutral, and collaborative:
Replace the highlighted details before sending, or customize a reminder for your situation.
2. The Psychology: Why This Phrasing Works
In behavioral psychology, Robert Cialdini’s well-known research on Commitment and Consistency shows that people have an innate drive to be—and appear—consistent with what they have already said.
When a client tells you “I’ll pay on Friday,” they have publicly committed to that reality.
If you attack them (“You promised to pay Friday and you didn't”), their instinct will be defensive justification. But when you phrase the follow-up as a shared troubleshooting effort (“Checking if it went through on your end, because it hasn't reflected here”), two things happen:
- You give them a graceful exit: If they genuinely thought accounting handled it, they can forward your email to finance immediately: “Hey team, did this go out? Freelancer says it hasn’t arrived.”
- You trigger their desire to keep their word: If they simply forgot, your polite message serves as an instant prompt to fix the discrepancy without feeling humiliated.
3. Anatomy of a Good vs. Bad Follow-Up
Let's dissect what makes the difference between maintaining trust and burning goodwill:
❌ The Accusatory Approach
“Hey Mark, you said you’d pay this by Friday. It’s Monday and I still haven’t received anything. Please let me know what’s going on.”
- Why it fails: It sounds like a scolding parent. Even if you're factually right, the tone puts the client on the defensive. They will remember feeling attacked long after the invoice is settled.
The Collaborative Anchor
“Following up on our note from last week—just wanted to confirm if the transfer went through on your side, as it hasn’t hit our account yet.”
- Key Elements Highlighted:
- “Following up on our note from last week” — Politely references their previous commitment without saying "you broke your promise."
- “Confirm if the transfer went through on your side” — Frames the issue as a potential banking or system delay, not personal dishonesty.
- “Hasn’t hit our account yet” — States an indisputable, objective fact.
4. Reusable AI Prompt for Custom Situations
If your client gave a specific excuse (e.g., waiting on their own client, software switch, vacation) and you need a tailored response, copy this prompt into ChatGPT, Claude, or your writing assistant:
5. Don't Wait for Apologies—Just Close the Loop
When a client breaks a payment date, it’s easy to get trapped in your head, waiting days before speaking up because you don't want to make them uncomfortable.
Remember: you did the work, and they already agreed to the timeline. Checking in when money doesn't arrive isn't pushy—it's standard business reconciliation.
If sending manual follow-ups every time a date slips feels like a drain on your focus, tools like PoliteChase handle automatic, gentle check-ins on your behalf, so you can stop playing detective and get back to creating.
Related reading: