惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
量子位
腾讯CDC
A
About on SuperTechFans
小众软件
小众软件
Microsoft Azure Blog
Microsoft Azure Blog
T
Tailwind CSS Blog
V
V2EX
B
Blog RSS Feed
H
Hackread – Cybersecurity News, Data Breaches, AI and More
GbyAI
GbyAI
Recent Announcements
Recent Announcements
Microsoft Security Blog
Microsoft Security Blog
博客园 - 叶小钗
罗磊的独立博客
宝玉的分享
宝玉的分享
WordPress大学
WordPress大学
大猫的无限游戏
大猫的无限游戏
IT之家
IT之家
V
Visual Studio Blog
D
DataBreaches.Net
博客园 - 三生石上(FineUI控件)
月光博客
月光博客
有赞技术团队
有赞技术团队

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How to chase an overdue invoice without being awkward (3 ...
Giuseppe Tumino · 2026-06-14 · via DEV Community

Giuseppe Tumino

Every freelancer knows the feeling: the work is delivered, the invoice is sent, and then… silence. The due date passes. A week goes by. And the longer you wait, the more awkward it feels to bring it up.

After tracking a year of my own invoices, I noticed something that changed how I get paid: the invoices I chased on a fixed schedule got paid 2–3 weeks faster than the ones I chased "when I remembered." The difference wasn't the client. It was my timing — and my wording.

Here's the system.

1. Use a fixed follow-up cadence

Stop deciding case-by-case when to nudge. Pick a cadence and apply it to every invoice:

  • +3 days overdue — a gentle, friendly nudge
  • +10 days — a firmer, clearer reminder
  • +20 days — a final notice with next steps

When it's automatic, you never agonize over "is it too soon?" — and clients learn you actually track this.

2. Send the right tone at the right time

The wording matters more than people expect. "Just checking in!" is easy to ignore. A calm, specific ask is not. Here are the three I use:

Friendly nudge (1–7 days late)

Hi [Name], I know inboxes get wild — invoice [INV-014] for $1,200 was due on May 30 and I haven't seen it land yet. Could you check on it when you get a sec? Thanks so much!

Firm reminder (8–19 days late)

Hi [Name], this is my second reminder for invoice INV-014, now 12 days overdue. Please confirm the payment date this week. If there's an issue with the invoice, let me know today and I'll sort it.

Final notice (20+ days late)

Hi [Name], despite previous reminders, invoice INV-014 is now 21 days overdue. Per my terms, a late fee of 1.5%/month applies. If payment isn't received by [date], I'll have to pause ongoing work. I'd much rather resolve this — please get in touch today.

3. Track "unbilled work" too

The most expensive invoice isn't the late one — it's the one you forgot to send. Keep a running list of finished work that hasn't been invoiced yet, and bill it weekly. That habit alone has recovered more money for me than any chase email.

4. Know what you're owed

If your contract includes a late fee, calculate it before you send the final notice — a specific number ("$15 late fee, total now $1,215") lands harder than a vague threat. I built a free late fee calculator that also writes the line for your email.

Make it effortless

If writing these from scratch every time is the part you avoid, I made two free tools, no sign-up:

And if you want the whole thing in one place — a dashboard that tracks every invoice, counts the days overdue, and hands you the right email automatically — that's what I built Get Paid OS for (Notion template or standalone app).

But honestly? Even just adopting the +3 / +10 / +20 cadence with the templates above will change how fast you get paid. Steal it.

What's your follow-up cadence? Drop it in the comments — I'm always refining mine.