Payment and Invoice Reminders That Actually Get Paid
The short answer
A payment reminder ladder is six messages from three days before due through 60 days past due, tone shifting at each step. iMessage reaches the approver, not a shared alias: blue bubble, read inside three minutes. This page covers timing, tone, and copy.
4 use cases in this category
Trigger
Event in your CRM
Under 60s
Send iMessage
Result
Reply in the thread
Key takeaways
- Late invoices: 43% of B2B credit sales overdue (Atradius 2025).
- Reminder emails fail: shared AP alias, no-reply sender, spam-flagged.
- The reminder ladder runs in four phases, and the tone changes at each one on purpose.
- The cadence is six sends across sixty days, the working shape for most B2B invoices on net-30 terms.
- Reminder copy should sound like the person who did the work, because that is who the customer has a relationship with.
- Yes, and collections compliance splits into two questions.
Where iMessage runs in the funnel
What Does a Late Invoice Actually Cost You?
Late invoices: 43% of B2B credit sales overdue (Atradius 2025). Bad debts hit 5% of long-overdue invoices. The work shipped; the money is just a follow-up away.
- Collection odds decay: 68.9% at 3 months, 51.3% at 6 months, 21.4% at 12 months (CCAA data). At each point, the invoice ages, stakeholders move on, and odds fall quietly through the floor.
- Run it on a quarter. A hundred thousand dollars of receivables that slips from a 30-day cycle to a 90-day one does not disappear; it stops being available for payroll, ad spend and inventory.
Why Do Invoice Reminders Get Ignored?
Reminder emails fail: shared AP alias, no-reply sender, spam-flagged. Email open rate: 27.7%. Text open rate: 98%. Email flagged as spam: 85%. Texts: under 3%.
- Silence in that channel is ambiguous. You cannot tell whether the invoice was seen and deprioritized, routed to a portal, or never delivered, so the next email is a guess.
- A blue-bubble reminder removes the ambiguity: it reaches a named human on a device they check constantly, and read receipts tell you which situation you are actually in.
- Guessing produces the two failure modes that make collections awkward: chasing someone who already paid, and going quiet on someone who never received the invoice at all.
How Does the Reminder Ladder Work, Step by Step?
The reminder ladder runs in four phases, and the tone changes at each one on purpose. Phase one is the pre-due nudge, three business days before the due date.
- Phase two is the due-day reminder, sent on the morning of the due date in the recipient's local time. Amount, invoice number, link, done. No urgency language, no exclamation points.
- Phase three is the overdue ladder on days 3 and 10. Phase four is escalation on days 21 and 35. Past day 60 the sequence stops and the account moves to a human, a payment plan, or an agency.
- Phase one exists to surface a problem while there is still time to fix it: a missing PO number, an invoice sent to the wrong entity, an approver on vacation.
- A neutral message on the due date reads as competent bookkeeping. An emotional one reads as distrust, and the invoice is not even late yet.
- In phase three the invoice is almost certainly stuck rather than refused. Day 3 asks what is blocking it. Day 10 asks for a specific payment date, which turns an open-ended problem into a scheduled one.
- Firmness in phase four comes from specificity. Name the contract term, name the date the next thing happens, and carry it out. A late fee you mention and never charge teaches the customer that your deadlines are decorative.
- Automation is good at the first sixty days and bad at everything after. Where we stop on collections work is at /use-cases/debt-and-credit-services.
Reading how it works is not the same as watching it answer one of your own leads. The Blue Funnel Map does the second one.
See it on your own listWhat Does the Cadence Look Like?
The cadence is six sends across sixty days, the working shape for most B2B invoices on net-30 terms. Stretch the pre-due window for net-60 or net-90, and compress the overdue rungs for smaller balances.
- Schedule every send inside the recipient's local business hours and keep the ladder on weekdays. A payment reminder at 8pm on a Saturday says more about you than it does about the invoice.
Pre-due nudge
- Timing
- 3 business days before due date
- Tone
- Helpful, zero pressure
- What the message does
- Confirms the invoice landed, offers the link, invites blockers
Due day
- Timing
- Morning of the due date, local time
- Tone
- Neutral and factual
- What the message does
- States amount, invoice number, payment link
First follow-up
- Timing
- Day 3 past due
- Tone
- Curious, assumes friction
- What the message does
- Asks what is holding it up, offers to resend to AP
Second follow-up
- Timing
- Day 10 past due
- Tone
- Direct, still warm
- What the message does
- Asks for a specific payment date
Escalation
- Timing
- Day 21 past due
- Tone
- Firm and specific
- What the message does
- Names the contract term now in effect
Final notice
- Timing
- Day 35 past due
- Tone
- Formal, unemotional
- What the message does
- States the next step and the exact date it happens
Handoff
- Timing
- Day 60 past due
- Tone
- Person to person
- What the message does
- Sequence ends and the account moves to a human, a plan, or an agency
What Should the Messages Actually Say?
What Should the Messages Actually Say?
Reminder copy should sound like the person who did the work, because that is who the customer has a relationship with. Lowercase, contractions, first names, one idea per message.
- The invoice number and the exact amount appear every time, so the recipient can act without opening anything. Each message gives the customer an easy way to be helpful rather than defensive.
- The day-21 message is where people flinch or overcorrect. The version that works stays boring, and you only write the late-fee sentence if the fee is in the contract and you intend to apply it.
- Pre-due, three days out: "hey marcus, quick heads up that invoice 4471 for $8,400 is due thursday. link's here if you want to clear it early. anything you need from me first, PO number or anything?"
- Due day: "morning marcus, 4471 ($8,400) is due today, link's below. if it's already in this week's AP run just tell me and i'll leave you alone."
- Day 10 past due: "hey marcus, 4471 is ten days out now. usually that means it's parked on someone's desk rather than anything on our end. want me to send it straight to your AP team, or is something missing on it?"
- Day 21: "marcus, 4471 is three weeks out. per the agreement the 1.5% monthly late fee starts today and i'd rather not run it. can you get me a payment date by friday?"
Is Texting Invoice Reminders Compliant?
Is Texting Invoice Reminders Compliant?
Yes, and collections compliance splits into two questions. The first is about the message: TCPA governs business texting on every channel, so the number needs a legitimate basis and opt-outs must be honored.
- The second is about the obligation itself. The FDCPA defines debt as an obligation incurred primarily for personal, family or household purposes, which puts commercial invoices outside its scope.
- A2P 10DLC governs US carrier SMS routes, and iMessage is not carrier SMS. That is a registration distinction rather than a consent exemption, and no A2P registration is required for these reminders.
- Most FCC consent-revocation rules took effect on 11 April 2025, with the revoke-all provision extended to 31 January 2027 by order DA 26-12.
- Blue Reacher enforces STOP and plain-language opt-out handling automatically and account-wide, so a customer who asks you to stop texting moves to email or a phone call.
- A company chasing its own invoices in its own name is a first-party creditor rather than a debt collector.
- Regulation F, the CFPB rule effective 30 November 2021, sits on top of the FDCPA and carries the same consumer-debt boundaries. Place a file with a third-party agency and that agency's own obligations attach.
How Do You Set This Up in Your CRM?
How Do You Set This Up in Your CRM?
Setup starts with the trigger, and the trigger is a date rather than a manual action. Most CRMs are native already: GoHighLevel, HubSpot, Close, Salesforce, Pipedrive and Follow Up Boss.
- Zapier, Make, n8n and the REST API and webhooks cover the rest. When an invoice is created, the record carries four custom fields onto the contact: invoice number, amount, due date, payment link.
- Your CRM does the date math and enrolls the contact three business days before the due date. Step delays run forward from enrollment, which keeps one six-step sequence maintainable across hundreds of invoices.
- Fire the enrollment off the due date field rather than the invoice creation date, so a net-30 invoice and a net-60 invoice both enter the ladder at the same relative point and every downstream delay lines up.
- Wire a payment-received webhook from your billing system that pulls the contact out of the sequence immediately. Chasing someone who already paid costs more trust than the invoice was worth.
- Run an iMessage availability check on the billing contact before the first send, and let delivery fall back to RCS then SMS where the number is not on iMessage.
- Set scheduled sends to fire inside the recipient's local window so a Pacific customer never gets a 6am reminder.
- Route every inbound reply to a person with a same-day response standard. A reminder ladder that generates replies nobody answers is worse than no ladder.
- Treat the day-3 reply as data collection: log the reason the invoice stalled as a field on the account, and after a quarter you will know which customers need a different process rather than a different message.
How Do You Know It Worked?
How Do You Know It Worked?
Days sales outstanding is the number that matters, so baseline it first. Pull the last two quarters before you turn anything on, then compare the same metric ninety days later.
- Three supporting metrics tell you which rung works: percentage paid on or before the due date, percentage of dollars sitting in the 60-plus aging bucket, and write-off rate as a share of billings.
- Read receipts turn a silent account into a diagnosable one. A day-10 message that never shows as read points at the contact record, so call. A read day-10 message with no reply points at priority.
- A working ladder shows up in average collection time first, because the pre-due and due-day messages move the middle of the distribution before they rescue the worst accounts.
- Write-off rate as a share of billings measures the whole system, and it moves last.
- Hold back ten to twenty percent of invoices on email-only for the first quarter if you want a clean read on the difference.
Frequently asked questions
Is it acceptable to text a business customer about an unpaid invoice?
Yes. Texting a business customer about an invoice they agreed to pay is ordinary commercial communication, and the mobile number on the account is usually the one they gave you for account matters. TCPA governs business texting on every channel, so keep the basis documented and honor opt-outs.
Does the FDCPA apply to reminders I send to my own customers?
The FDCPA generally does not reach commercial invoices. Its definition of debt covers obligations incurred primarily for personal, family or household purposes, and a business collecting its own invoices in its own name is a first-party creditor. Once you place a file with an agency, that agency's obligations govern.
When should the first reminder go out?
Three business days before the due date is the highest-value send in the whole ladder. A pre-due nudge catches the problems that actually cause lateness, a missing PO number or an approver out of office, while there is still time to fix them.
How many reminders is too many?
Six sends across sixty days is the practical ceiling for a single invoice, and the spacing is what keeps it from feeling like harassment. Two messages in one week with no reply is where a text ladder stops helping and a phone call starts. Escalate by getting more precise, not by sending more.
Should the amount and invoice number go inside the message?
Yes, in every message. The recipient should be able to identify the invoice, confirm the amount and act without opening an attachment, a portal or their email. Include the payment link too, since the gap between deciding to pay and being able to pay is where the friction lives.
What should I do when a customer replies asking for more time?
A request for more time is the second-best outcome available. Ask for a specific date rather than a vague assurance, confirm it back in writing, and set the follow-up for the morning after that date. A dated commitment turns an aging invoice into a scheduled one.
Do payment reminders require A2P 10DLC registration?
No A2P registration is required. A2P 10DLC governs US carrier SMS routes, and iMessage is not carrier SMS: a registration distinction, not a consent exemption. Your TCPA consent and opt-out obligations are unchanged. What disappears is the registration queue and the per-message carrier fees.
What happens if the billing contact is not on iPhone?
Delivery falls back automatically, RCS first and then SMS, so the reminder still lands. An availability check runs before the send, which also lets you segment: blue-bubble contacts get the conversational ladder, fallback contacts get slightly more formal copy.
Turn your aging report into cash
Run the full ladder from one dedicated iMessage line: pre-due nudge, due-day reminder, and a four-rung overdue sequence that sends inside your customer's local business hours and drops the contact the moment your billing system fires a payment-received webhook. $249 per line per month, unlimited iMessages (unlimited covers the conversations you're in; new outreach is paced at the safe-send rate of up to 50 opted-in / 30 cold new conversations per line per day, because this is a conversation channel, not a blast tool), no per-message fees, no A2P registration required. Six native CRM integrations, plus Zapier, Make, n8n and the REST API and webhooks. White-glove activation is handled for you and waived on annual billing.