The point where work gets scattered
An inaccurate reminder makes the client repeat information and can encourage another payment attempt when one is already in progress. The best first step is to inspect what happened, not to sharpen the wording.
Check the request and the latest result
Open the invoice or payment request and confirm its identifier, amount, currency, scope and agreed due date. Review the relevant conversation for a changed date, a query or promised correction. Check actual confirmed payments allocated to this work. A separate funding step or a client’s screenshot may require inspection; it should not be casually equated with the recipient’s completed payment.
If the payment is unfinished, inspect the same attempt through the available payment experience before asking for another one. If the client says the payment belongs to a different project, resolve that allocation. If the invoice contains an error, correct it through your existing document process and explain the correction before asking the client to act.
- Right invoice, amount, currency and due date.
- No confirmed payment or credit missed.
- No unanswered client question or unfinished attempt ignored.
Write a neutral reminder with a useful next step
Sample wording: ‘Hi Ren, I’m checking invoice M-08 for the August content package. The remaining amount is $640 USD, due 12 September under our agreed schedule. I have not found a confirmed payment allocated to it. Please check the invoice and payment link, or let me know if your team needs a correction or has a processing date. If you have already paid, please share the payment reference so I can inspect the result.’
Use this wording only after the checks are true. Avoid a broad ‘you have not paid’ if you cannot see every possible payment route. Include a recognizable reference and the existing payment route rather than changing bank or recipient details in a reminder. Keep unnecessary private project information out of the message.
Adapt the reminder to the actual obstacle
For a partial payment, acknowledge the confirmed amount and show the remaining balance: ‘The $400 payment is confirmed; $240 remains on M-08.’ For a missing reference, ask for that detail. For a price question, point to the exact line and relevant accepted scope, then resolve the question. For an internal processing delay, ask the client for a specific expected date.
If the client cannot pay as expected, discuss a real next arrangement instead of implying one already exists. Record any agreed change to timing or amounts and check its effect on the project. Do not add unagreed fees, legal threats or invented consequences to make the message stronger. If specialist help is needed, seek it based on the actual circumstances.
Confirm the outcome before closing the reminder
When a payment is confirmed, check that it belongs to this request and send a concise acknowledgment. If a balance remains, state it accurately. If the client promises a processing date, record that as a promised date, not as a completed payment. Set your next review around the real arrangement so reminders do not continue after the matter is resolved.
Keep the invoice, relevant conversation and payment result connected by the project reference. A useful closing note might be: ‘The remaining $240 for M-08 is confirmed, thank you. That invoice is now fully paid. Our next action is your review of the September outline.’ This finishes the payment question and returns the relationship to the work.
Keep the context with the conversation
Choose the relevant payment records and conversation context in Messages, then prepare reminder wording for review. Inspect the original payment result before sending or retrying. Use the existing payment experience for an approved payment. Business helps with the context you provide; it does not automatically know unshared outside payments or send every drafted reminder.
Understand your Twin · See Business access and metered AI usage