THE TWO-PART RULE
Days determine when to check. State determines what to ask.
A calendar prevents avoidance and inconsistency. It should not make every invoice sound the same. Start with a fixed cadence, then leave it as soon as the client gives you a more useful fact.
Do not send a generic day-14 reminder when the real event is a broken promise, partial payment, routing problem, or invoice dispute.
Create the record before anything is late.
Save the invoice number, total, due date, payment instructions, client contact, accounts-payable contact, and the date you will check again. Confirm delivery when routing is uncertain.
Remove administrative friction.
A brief reminder can confirm that the invoice is in the payment run and that the payer has the correct document and payment link. Keep this note neutral; the invoice is not overdue yet.
Check receipt and routing.
Name the invoice, outstanding amount, and original due date. Ask whether anything is blocking processing and offer to resend the invoice or copy the appropriate payer.
Ask for the scheduled payment date.
Move beyond “any update?” Request a specific processing or payment date. If payment has already been sent, ask for the remittance reference so you can reconcile it.
Make the record firm and complete.
Restate the invoice, balance, due date, previous follow-up, and requested response date. Mention only consequences or fees that are accurate, documented, and available in your circumstances.
Choose a real next step.
Review the agreement, preserve the correspondence, and decide whether to pause new work, escalate internally, seek qualified advice, or use an appropriate recovery option. Do not bluff.
WHEN THE STATE CHANGES
Leave the generic schedule.
- Acknowledged, no date
- Ask for the scheduled payment date and payer confirmation.
- Promised date missed
- Reference the missed date and request a replacement date.
- Partial payment received
- Acknowledge it, state the remaining balance, and ask when it clears.
- Question or dispute
- Define the exact disputed item and ask whether the undisputed balance can proceed.
THE MINIMUM RECORD
Keep enough detail to know what happens next.
- Invoice reference, original amount, and remaining balance
- Original due date and current days overdue
- Last contact date, channel, and client response
- Promised payment date or issue requiring resolution
- Next follow-up date and the person responsible
COMMON QUESTIONS
Freelance invoice follow-up FAQ
How soon should a freelancer follow up after an invoice is due?
If payment has not arrived, a short receipt and routing check within one to three business days is reasonable. Name the invoice, amount, and due date, and ask whether anything is blocking payment.
How often should an overdue invoice be followed up?
Use a fixed cadence rather than emailing whenever anxiety spikes. A practical starting point is one to three days, seven to ten days, fourteen to twenty-one days, and thirty days overdue. Stop or reschedule the cadence when the client gives new information.
What should I send after a promised payment date is missed?
Follow up on the next business day. Refer to the promised date as a fact, say that payment has not arrived, and ask for the new scheduled payment date or remittance reference.
How should I respond to a partial invoice payment?
Acknowledge the amount received, state the remaining balance, and ask when that balance will be paid. Do not restart the email as if no payment occurred.
Should a freelancer add a late fee during follow-up?
Only apply a fee that is supported by the written agreement and applicable rules. Keep an internal delay-cost estimate separate from any amount you are entitled to charge.
SOURCE NOTE
Use the cadence as a starting point, not a legal rule.
Reminder schedules vary with the written payment terms, client process, relationship, jurisdiction, and amount at stake. The operational principle is consistency plus an accurate record.
FURTHER READING
Why promise dates deserve their own state.
Enterprise receivables systems separately track promises to pay, tolerated days, accepted amounts, and broken-promise actions. See the Oracle PeopleSoft documentation and this Upwork overview of reminder cadence.