Every Monday morning you open the books, see the same three "due last week" invoices still open, and spend forty-five minutes composing a polite-but-firm email you wish you didn't have to send. The chase isn't a people problem — it's a process problem. Five fixes a non-tech can put in place this week, plus the honest escalation for when the DIY path has hit its ceiling.
"Chasing late invoices" means the same polite, on-schedule nudge sent by the same person on the same template — never a custom email from whoever noticed first. Two-minute checklist before the longer guide:
1. Pick one reminder cadence (most teams settle on day 1, day 7, day 14 after the due date).
2. Move your default terms from net-30 to net-14 (most customers pay net-30 because you let them, not because they need 30 days).
3. Send one person the reminders from one inbox so two employees can't both be chasing the same customer on the same day.
If not, walk through the five fixes below in order.
The single biggest reason invoices go cold is that no one is responsible for the follow-up. The bookkeeper notices Tuesday, the owner notices Thursday, the salesperson notices the following Tuesday — each one with a slightly different tone, and each customer has now been nudged twice in one week from two different people at your company. Customers stop replying because they're confused, not because they don't want to pay.
What to do: write one reminder email (three paragraphs is enough) — friendly opener ("just making sure this didn't get buried"), a one-line fact statement ("Invoice 1042 for $4,500 was due Friday, May 9"), and a clear call-to-action ("if there's anything blocking payment, reply here and I'll sort it on my end"). Save it as a template. Send the same template on day 1, day 7, and day 14 after the due date. No edits between sends.
Where this usually goes wrong: businesses write a fresh reminder every time, so each outgoing email reads like a different writer's voice. Customers pick up on that and deprioritize. A template is also how you stop dreading the chase — you've already written the email once, and now you're just pressing send.
Most small businesses send invoices with "net-30" printed in the corner because that's what the template said, not because they checked what their customers actually pay in. The data is the other way around: businesses that bill net-7 or net-14 collect about the same share of invoices within fourteen days — they just collected them at day nine instead of day twenty-eight. Cashflow is the same; peace of mind is much better.
What to do: change your invoice footer (and any contract template that still says "net-30") to "net-14." Add a one-line note: "Early-payment discount: 2% if paid within 7 days." Keep the discount — even if no one takes it, it gives the customer a reason not to sit on the invoice for thirty days while they prioritize other vendors.
Where this usually goes wrong: businesses assume their enterprise customers will reject net-14. In practice, the same enterprises already pay their AWS and Twilio invoices net-15. If your invoice is under $10K, a "net-14" footer on a small-business invoice is the default most customers pay without comment.
A late fee isn't a punishment — it's a schedule. The minute you put "1.5% per month after the due date" on the invoice footer, two things change: the customer sees it once when they receive the invoice, and now they have a reason to pay on time independent of how busy they are. Late fees also do the chasing for you — the customer's AP system will flag your invoice as overdue on its own.
What to do: add a single line to your invoice template — "A late fee of 1.5% per month applies to balances unpaid after the due date." Most customers won't pay it. Most of the rest will pay the invoice early to avoid it. The few who don't pay it after thirty days now owe you the late fee on top — and a polite reminder email that references the late fee collecting itself is much harder for them to ignore than a generic nudge.
Where this usually goes wrong: businesses add a late fee "retroactively" — i.e., they charge a late fee on an invoice that didn't say one was possible. That isn't a late fee, it's a surprise, and it usually leads to an awkward conversation and a refunded fee. The fee has to be visible on the original invoice or it doesn't exist.
If invoices@yourcompany.com is forwarded to a shared inbox that anyone on the team can see and reply from, you'll get crossfire. The salesperson replies Tuesday to ask about the project scope. The bookkeeper replies Wednesday to ask about the payment. The owner replies Friday to ask, ironically, why the customer hasn't paid yet. The customer is now managing three separate conversations and has gone quiet.
What to do: pick one person (or one shared inbox routed to a single queue with rules like "only @bookkeeper replies to AR threads") and make that person the canonical sender for all invoice follow-up. Set up an email rule: any thread whose latest message contains an invoice number routes to that one person. Two weeks of this and the chase becomes predictable.
Where this usually goes wrong: businesses try to assign a different owner per customer. The owner-of-the-day churns because the customer-facing team rotates every quarter; the new owner doesn't know the invoice history; polite, gentle follow-up turns into aggressive, unfamiliar follow-up; the customer stops engaging. One owner per invoice beats rotating owners every time.
The best late-invoice is the one you never had to send. Half the invoices small businesses chase are net-30 invoices for projects that, thirty days earlier, the customer had zero skin in the game. A 30% deposit at booking — or two milestone payments (50% at the halfway point, 50% on delivery) — cuts the total amount you ever need to chase by more than half, because the customer's AP team has already approved payment once.
What to do: redraft your standard contract or engagement letter to require a non-refundable deposit at signing (most services settle on 25–50% of the total). For longer projects, add explicit milestones with explicit invoices — "milestone 2 invoice, due on delivery of design v2" — so the customer pays as work lands, not in one lump thirty days after delivery. Send the deposit invoice the same day you send the contract. If they won't pay a 30% deposit, that's a signal.
Where this usually goes wrong: businesses fear the deposit will scare the customer off. In practice, the customers who won't pay a deposit are usually the same customers who'll chase you for six months over the final invoice. Asking for the deposit filters them out before you do any work.
If you've put the five fixes in place and you're still chasing the same invoices every month, the rest of the rabbit hole — collections agencies, small-claims court, factoring companies, automatic-suspend-on-overdue service agreements — costs more time and goodwill than the money it's chasing.
Here's the honest answer: if your team has spent more than an afternoon a month on invoice follow-up for two quarters in a row, that's not an accounts-receivable problem. It's a process problem. The same way businesses automate invoicing or onboarding or reporting, the right move is a small done-for-you setup that handles the cadence, the late fees, the deposit terms, and the one-inbox rule for you — so the chase happens automatically and only the edge cases ever reach you. (And if invoices are chasing you because the printer won't print the emailed PDF the customer needs to authorize wire transfer, fix the printer first — the same shape of fix lives in our printer-offline guide. If your invoice emails are landing in the customer's spam folder instead of their inbox, fix the SPF/DKIM/DMARC first — same shape, in our business-email-setup guide. And if your accounting laptop is the only device on the office network and it keeps dropping, the SOS reminder is leaving days late — same shape, in our Wi-Fi guide.)
We automate one business process for $89 — same-day fix or your money back. No retainer, no monthly fee. You describe what's broken, Nikita builds the fix.
Not sure what counts? See a real example: the Shopify-to-Sheets guide.
Start — $89OneFix is a small automation service for small businesses — we don't sell invoicing software, payment plans, or collections tools. If you'd rather keep chasing, our refund policy doesn't apply (you haven't paid us anything yet). Back to onefix.tech.