1. Check what was actually agreed.
Before sending an aggressive reminder, gather the facts: quote, contract, agreement, approval messages, invoice, due date, expected deliverables, delivered work, requested revisions and files handed over.
This prevents two mistakes: chasing payment without clear documentation, or discovering too late that the client disputes the scope rather than the payment.
2. Send a factual reminder.
Keep the reminder short, calm and specific. Refer to the invoice, due date, project and expected payment method. Avoid accusations in the first message: you are seeking a reply and a payment date.
Example: “Hello, I am following up on the invoice for [project], which was due on [date]. Could you confirm the planned payment date? I have included the delivery and approval records below.”
3. Separate a simple delay from a dispute.
An administrative delay needs a different response from a dispute. If the client says “I will pay tomorrow”, ask for a clear date. If they say “the work does not match”, revisit terms, deliveries, revisions and approval. The record should show what was agreed and what was done.
4. Plan final-file access for future projects.
An unpaid invoice can reveal an overly open workflow: final files sent too early, implied approval, production access given before payment or scattered messages. For the next project, plan preview delivery and final release after approval.
5. What Dealokr changes before an invoice becomes overdue.
Dealokr helps build a record before a problem arises: terms, provider payment status, preview delivery, client approval, release and event history. It does not collect debts for you, but reduces the ambiguity that makes reminders difficult.