The decision in one line: Give each message a job.
01 / COMMUNICATION
Give each message a job
A useful message identifies the invoice, the recorded amount, the payment context and the question the recipient can answer. It should be easy to forward internally without losing its reference. What information belongs in a polite payment reminder?
02 / COMMUNICATION
Make room for a reply
A promise, a correction or a dispute changes the record. Save the response with its date and do not treat silence as agreement. The reader goal here is to draft an accurate, concise reminder from verified invoice facts and give the recipient a clear response route..
03 / COMMUNICATION
Know when to pause
Routine follow-up should stop when a substantive dispute, missing evidence or a vulnerability requires a different route. The pause is part of the process. Return to the action map when the file changes.
NEXT CHECK
Keep the next action visible
Use the Receivables Action Map to name the state of the file, the evidence still missing and the point at which the routine should pause. It is a working prompt, not a legal conclusion.