Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
Payment Follow-up Draft
A respectful overdue invoice reminder grounded in due date, invoice context, and any prior payment promise.
Use it when
Start from a clear structure, then check the facts.
These templates are deliberately plain. The value comes from pairing the message with the source records that support it.
payment follow up
Payment Follow-up Draft
Subject: Follow-up on invoice [number]
Hi [Client name],
I am checking in on invoice [number] for [project], which was due on [date].
The invoice was sent on [date], and the related deliverables were sent on [date].
Could you let me know whether anything is missing on your side, or when payment is expected?
Thanks,
[Your name]Before sending
Review the evidence first.
Status
Is the project confirmed, unclear, overdue, or blocked by a missing record?
Tone
Does the message fit the client relationship and the current state of the work?
Related
Continue with the matching workflow.
FAQ
Who should use Payment Follow-up Draft?
Independent professionals and small teams who need a calm, source-aware starting point before sending a client message.
Should I copy it exactly?
Use it as a structure, then adjust the facts, tone, and relationship context before sending.
What should I check first?
Check the relevant approval, scope, delivery, invoice, or payment record before using the template.
Early access
Bring this template into real client work.
Early access helps us test these workflows against actual project records.