How can AI handle overdue invoices and payment follow-ups?
AI can draft and send payment reminders in the right tone, time them to a sensible cadence, pull the exact amount and invoice number from your records, and retry failed card charges. The hard part is not the writing; it is matching each message to the right account, the right contractual hook, and the right moment, then doing it consistently across every late payer without nagging the ones who already paid.
Chasing money is the job nobody wants. A guest hasn’t paid the balance before check-in, a tenant is past the grace period on rent, a client is sitting on a 15-day-old invoice, or a subscription card just declined. Each one is a small, awkward conversation, and you have to have it again and again without sounding like a debt collector or accidentally pestering someone who paid yesterday. It is tedious because it is repetitive, and it is hard because tone and timing have real consequences for the relationship and the cash.
What actually decides the outcome
A few things separate a follow-up that gets paid from one that gets ignored or resented.
Timing and cadence. People respond to rhythm, not random nudges. A note on the due date, a firmer one a week or two later, a final notice near 30 days. Too soon feels paranoid; too late lets the balance drift into bad debt.
Tone matched to the relationship. A repeat client gets warmth and benefit of the doubt. An anonymous failed card gets a quick, transactional “update your details.” A tenant gets a measured, on-the-record message. The same words do not fit all three.
The contractual hook. Your ask has teeth when it points to something real: a lease late-fee clause, net-30 terms on a signed agreement, a booking policy. Early reminders can stay friendly; escalations land better when they cite the term the other side already agreed to.
Friction on the payment itself. “Please remit payment” is a dead end. A working link or portal in the message removes the step where people give up. The easier you make paying, the faster it happens.
Failed-card retries vs. human follow-up. This is the distinction most advice skips. A declined card is a mechanics problem (expired card, temporary hold) and is solved by a retry timed sensibly plus a card-update prompt. An unpaid invoice is a person problem and needs a worded message. Treating them the same wastes effort on both.
How to do it by hand
This part is free knowledge, so here is the honest manual version.
- Pull a list of what is actually overdue from your accounting tool, PMS, or rent platform. Confirm each one really hasn’t been paid, including payments that arrived but weren’t recorded.
- For each account, find the invoice number, amount, and original due date.
- Pick the stage: first reminder, firm follow-up, or final notice, based on how late it is.
- Write the message in a tone that fits that person, with the exact figures and a way to pay.
- Send it, then note the date so you know when the next step is due.
- When money lands, mark it paid and stop the sequence.
For failed cards, you instead watch your payment processor for declines, trigger a retry, and send a short note asking the customer to update their card.
Where it goes wrong
The classic failures are all about consistency. You forget to send the second reminder, so the invoice ages quietly. You send a reminder to someone who already paid, which is embarrassing and erodes trust. You misquote the amount because the spreadsheet was stale. You let dread delay the awkward email until the balance is weeks old and the conversation is harder. Or you retry a failed card too aggressively and trip the bank’s fraud flags. Each mistake is small. Across dozens of accounts every month, they add up to real lost cash and frayed relationships.
Doing it yourself vs. handing it to Physea
By hand, this is a recurring chore that competes with the actual work. You can buy a tool for one slice (a Stripe retry plugin, an email template, a rent-reminder feature), but then you are stitching the slices together yourself and still deciding who gets what, when.
Physea’s Liminality runs the whole thing end to end over MCP, across the tools you already use, whether that is QuickBooks and Gmail, a rental platform like AppFolio, a booking system, or Stripe. It reads what is genuinely overdue, matches each message to the right account and tone, drafts it with the correct figures, sends it, schedules the follow-ups, and stops the moment payment clears. Because it is grounded in your live data and reuses the route it has already worked out, you get the result, paid invoices and fewer awkward chases, instead of the chore. You stay in control of approvals; it handles the legwork.
Common questions
- What should an overdue invoice email actually say?
- Lead with the facts: invoice number, amount, original due date, and how many days late it is. Keep the tone neutral and assume good faith on the first reminder. State a clear next step (a payment link beats 'please remit') and a date you expect payment by. Reference the contract or terms only when you escalate. Physea can draft this from your live accounting data so the numbers are always right and send it without you copy-pasting.
- How many times should I follow up on a late payment?
- A common rhythm is a friendly note on the due date, a firmer reminder around 7 to 15 days late, and a final notice near 30 days that mentions late fees or next steps. Stop the moment payment clears, and never send a reminder to someone who already paid. Physea tracks which invoices are still open and runs the sequence per account so the cadence stays right on its own.
- How is retrying a failed card different from chasing an overdue invoice?
- A failed card is usually an expired or maxed-out card, not a refusal to pay. The fix is a smart retry (often timed for payday or after a card-updater refresh) plus a short 'update your card' message. An overdue invoice is a person who has not paid a bill you sent, which needs a worded follow-up against your terms. They are two separate jobs. Physea handles both and routes each one to the right treatment.