Late payment scripts for freelancers: day 1, day 7, day 14
Leon Silcott
Use day 1, day 7 and day 14 as review points for an unpaid invoice. Adapt to the reply and keep payment promises separate from confirmed receipts.
A reminder sequence gives you a starting point when you are tired of rewriting the same message. It should not become an automatic escalation that ignores what the client has said. A payment report, a purchase-order problem and a disputed deliverable each need a different response.
The scripts below use a hypothetical £720 invoice due on 1 November. Day 1 means one day after that agreed due date. The dates are an editorial example, not a legally required schedule or an AsAgreed reminder preset. Adjust them to your actual terms, working days, client contacts and the conversation.
Before day 1: verify the invoice
Check the accepted price, invoice reference, due date and payment records. Confirm that the client or nominated billing contact received the right invoice. If the terms were never clear, clarify them rather than announcing that a deadline you chose has already been missed.
Look for any question you still need to answer. If the client asked for a corrected address or queried an extra, deal with that point. Do not write “I've heard nothing” when you have an unanswered message in another thread.
Keep the accepted scope, invoice and shared agreement available while drafting. You should be able to explain the amount without relying on the reminder itself as evidence that it is correct.
Day 1: a factual check
“Hi Priya, I'm checking invoice 207 for the October blog series. The remaining £720 was due on 1 November and I haven't located it in my payment records. If you've already sent it, please tell me the date and reference so I can check. Otherwise, could you confirm the payment date or let me know if you need anything from me?”
This gives the client enough information to locate the invoice and one route to reply. It does not assume they forgot, are avoiding you or have a particular financial problem. Use your usual tone, but keep the reference, amount and question intact.
Attach the invoice or the relevant shared-record link. Do not send bank details copied from an unrelated old invoice. Follow your normal process for payment information and independently check unexpected requests to change it.
If they name a payment run
“Thanks. Please confirm the scheduled date and whether anything is still missing from my invoice. I'll note that date for my next check.”
A scheduled run is not a guarantee of arrival. Record the date as the client's stated plan, not a completed payment. If you agree to a different arrangement, confirm what you have actually agreed rather than writing “as agreed” before they reply.
If they say they already paid
“Thanks for letting me know. Please report the amount sent against the agreement and send the reference if needed. I'll check my external payment records and confirm receipt when I locate it.”
AsAgreed does not take the job payment. A report alone does not reduce the confirmed balance; your confirmation after checking receipt does. Do not turn a promise to send money next Friday into a report of money already sent.
Day 7: summarise what happened
If payment has not arrived and the conversation has not resolved the issue, review the records again. In this example, assume the client said payment was scheduled for 5 November, but you have not located it or received an update.
“Hi Priya, following up on invoice 207 for £720, due on 1 November. You mentioned a payment scheduled for 5 November. I haven't located it, so please confirm whether it was sent and provide the reference if so. If the date has changed, please tell me the proposed payment date. I'm available for a short call tomorrow if a specific issue needs discussing.”
Only include the scheduled date if the client actually gave it. A template should not invent a broken promise to make the message sound stronger. Replace dates and references carefully rather than copying the example wholesale.
The call offer is useful if there is a real question to discuss. Agree a time and send a factual summary afterwards. Leaving a voicemail does not mean the client agreed to your proposal.
Branch the sequence when the reply changes the facts
An invoice-processing problem
If a purchase-order reference or billing address is missing, ask for the exact correction and send the revised document through your normal invoicing process. Keep the original reference traceable so the client does not treat the resend as a second bill.
Discuss the payment position explicitly. Do not assume a corrected address automatically creates a new payment term, and do not ignore the practical processing issue merely because your original invoice was sent earlier.
A scope or quality dispute
Ask which deliverable or invoice line is questioned. Check the accepted scope, change history and relevant work. Answer the concern rather than letting the calendar trigger another generic demand.
If a proposed addition was never accepted, say what is missing from the record. Do not call a completed task authorised solely because it exists in the final files. If the issue needs professional advice, preserve the documents and obtain it.
An affordability problem
Ask the client for a realistic proposal with amounts and dates. Decide whether you can accept it, then confirm the actual agreement. A vague “some next week” leaves the next reminder without a reference point.
A partial-payment report does not create an automatic instalment schedule in AsAgreed. Keep the agreed plan in writing and record each external payment when sent, with receipt confirmed after it arrives.
If this job already has an AsAgreed record, check its payment reports and confirmed receipts before the next reminder.
Review your existing agreement
Day 14: state a considered next step
If there is still no payment or useful reply, review your position before writing. Decide what you can responsibly do about future work, what you have already committed to and whether you need advice. Do not threaten an action you have not checked or will not take.
For a genuinely new, uncommitted booking, a script might be:
“Hi Priya, invoice 207 for £720 remains unpaid after my messages on 2 and 8 November. Please reply by 17 November with payment details, a concrete proposal or the specific invoice item you dispute. I am not accepting the new December booking while this is unresolved. If we cannot agree a next step, I will seek advice about the outstanding invoice.”
Use that future-booking boundary only where it matches the actual situation. Do not replace it casually with “I am stopping all current work”. Existing commitments, service continuity and contractual terms can matter. Get suitable advice rather than treating a reminder template as permission to suspend anything you choose.
Leave legal charges out unless properly checked
This sequence does not calculate statutory interest, compensation, collection fees or court deadlines. Their availability depends on circumstances and current rules. A generic freelancer article should not quietly add them to every invoice, including consumer work.
If you want to pursue formal options, use current primary guidance and appropriate advice for the job and jurisdiction. Take the accepted terms, invoices, correspondence and payment records with you. Do not make a legal claim in a message merely because a template sounds authoritative.
The ordinary reminder can remain useful without that claim. A checked amount, a clear request and a realistic next action are enough information for this stage of the discussion.
A hypothetical partial-payment branch
Suppose the client proposes £300 on 17 November and £420 on 24 November, and you accept that plan. Send a written summary of both amounts and dates. Keep any separate question about the work visible rather than implying the plan settles it automatically.
When £300 is actually sent, the client can report it. Once you check and confirm receipt, £420 remains against the £720 invoice. If only £250 arrives, record £250 accurately and discuss the difference. Do not confirm the promised £300 to keep the plan looking neat.
When the final £420 arrives and is confirmed, acknowledge the settlement. If the agreed second amount was missed, refer to that actual date and amount in the follow-up rather than restarting the generic day-1 script as though no conversation happened.
Keep one contact log
Record the date, channel, invoice, reply and next action. Keep original correspondence. A note saying “no reply to 8 November email” is more useful than “client being evasive”, which adds an interpretation the record cannot establish.
If a colleague helps with accounts, decide who sends the next message. Duplicate reminders on the same day can create confusion about whether your records are current. If you discover a payment was missed in your check, correct the record and tell the client plainly.
Review your reminder settings too. AsAgreed reminders depend on the agreement settings, delivery channels and recipient eligibility. Do not assume this editorial schedule is automatically configured or that everyone receives every notification.
If the billing contact changes
A project lead leaving the business can interrupt a payment conversation. Ask the client who now handles the invoice, then send the same checked reference and summary to that person. Keep the previous correspondence available without asking the new contact to accept a story they have not reviewed.
Do not reset the history to “first reminder” simply because the recipient changed. Equally, do not open with accusations about promises made by someone else. Explain the due date, confirmed receipts and outstanding question. Record who owns the next check so you do not send parallel reminders to several staff members.
Make the next invoice easier to follow
Before starting another job, agree scope, price basis, billing contact and payment expectations. Plan how extras will be proposed. In AsAgreed, scope and price revisions stop once a new payment report or receipt exists; later extras need a fresh agreement.
The freelancers page shows scope, changes and the payment record together. For the next project, give both people a clear scope and payment expectation from the start.