Should you send, wait, pause, or ask an account owner to review?
Overdue invoice follow-up is not one-size-fits-all. Use this checklist before sending a reminder so paid, disputed, promised-payment, and relationship-sensitive invoices do not get the wrong note.
Send
Prepare a friendly reminder draft when the invoice is overdue and the context is clean.
- Invoice is overdue and still open.
- No recent reminder was sent.
- No known dispute, scope issue, or service concern is attached.
- Recipient appears to be the right billing contact.
- The reminder tone is reasonable for the relationship.
Wait
Hold the reminder when there is a promised payment or recent follow-up context.
- Client already promised a payment date.
- A reminder was sent recently and another one would feel pushy.
- An account owner is waiting for a client response.
- The team needs to reconcile deposits before nudging again.
Pause
Stop reminders when the invoice should not be treated as a normal overdue item.
- Invoice is paid, void, archived, or do-not-contact.
- Invoice is disputed or tied to a scope/service issue.
- The contact is suppressed or no longer valid.
- The account or billing state blocks sending.
Account-owner review
Route the reminder to a human when the relationship or facts need judgment.
- The client relationship is sensitive.
- The invoice is materially old or high-value.
- The project owner knows context that finance does not.
- Reminder wording needs custom tone before approval.
How Ledgerly uses this logic
The goal is fewer wrong reminders, not blind automation.
Ledgerly’s current product evidence supports CSV-first review, reminder draft creation, exact-copy approval, safety-gated sending, and in-app weekly report previews. It does not support claims about live accounting sync, legal collections, guaranteed recovery, or fully unattended sends.
- CSV imports normalize invoice rows for review, but review is still required.
- Paid, disputed, void, archived, do-not-contact, suppression, stale approval, billing, provider, and duplicate-send checks are part of the safety model.
- Reminder drafts should be reviewed and approved as exact copy before sending.
- Weekly report previews help the team see what was reviewed, skipped, drafted, or still needs action.