Your move
Schedule the reminder sequence
A due date should trigger the next action without relying on you to remember it.
Tie reminder drafts to invoice state and due date. A before-due, due-date, and overdue sequence is a PickBits starter pattern; use the cadence and language your agreement, customer relationship, and local rules permit.
Do this now
Three moves, in order.
- Define the invoice states your system can observe: prepared, sent, due, paid, overdue, disputed, or paused.
- Write a short draft for each allowed state using the approved amount, date, invoice link, and contact.
- Stop future reminders immediately when payment, dispute, or a human exception is recorded.
Build the artifact
Payment reminder schedule
Copy these fields into a note, document, or sheet you already use.
State
Observable invoice status
Trigger
Date or event that permits a draft
Message
Approved factual reminder
Stop condition
Paid, disputed, corrected, or human-owned
Give AI the bounded job
Prompt from your artifact—not from vibes.
Draft payment reminders from the invoice record and approved terms only. Include the invoice identifier, approved amount, due date, payment path, and a way to report a problem. Never invent fees, threats, urgency, or account status.
Before you use it
The work leaves your hands only when:
- The invoice is still unpaid and not disputed before any send.
- Amounts, dates, and links match the record.
- The customer has a clear route to resolve an error.