Invoice & payments writer at ChaseAI
A strong subcontractor payment reminder email template is less about pressure and more about making payment processing easy for GC finance and AP teams.
The documentation checklist (what GCs/AP need)
- Invoice number and pay period or draw reference.
- Amount due and due date.
- Project name/site reference and PO/CO details.
- Signed ticket, delivery proof, or completion sign-off.
- Required lien waiver form status (if applicable).
- Remittance details and payment instructions.
Missing one item can delay release by another cycle, so include a full packet in every follow-up.
Templates (friendly -> firm)
Friendly reminder (first follow-up)
Subject: "Payment follow-up: invoice #[number] for [project]"
"Hi [Name], quick follow-up on invoice #[number] for [amount], due [date]. I have attached the invoice and support docs again for convenience. Could you confirm expected payment date? Thank you."
Direct reminder (after no response)
Subject: "Second reminder: invoice #[number] outstanding"
"Hi [Name], following up on invoice #[number], now [X] days overdue. Please confirm if anything is missing for release this cycle, or share the scheduled payment date."
Firm reminder (deadline + next step)
Subject: "Action required: invoice #[number] overdue"
"Hi [Name], invoice #[number] remains unpaid after prior reminders. Please process by [date/timezone]. If unresolved by deadline, I will move to next documented step under contract."
Common blockers: missing PO, waiver, approval delay
- Missing PO/CO: request exact reference and reissue invoice if needed.
- Waiver issue: submit correct waiver version and request confirmation same day.
- Approval delay: ask for approver name, status, and payment release date.
This makes your GC payment follow up email practical and process-driven, not repetitive.
Escalation steps (keep it professional)
- Friendly reminder with full document packet.
- Direct reminder asking for specific pay date.
- Firm reminder with deadline and next-step statement.
- Formal past-due notice if still unresolved.
For formal notice wording use past due invoice notice template. For broader overdue strategy use net-30 overdue what to send.
Quick tips
- Always include pay-app context in subject line.
- Attach waiver + completion proof by reminder two.
- Use exact deadlines with timezone for firm notices.
- Keep communication factual and chain all updates in one thread.
Timeline: subcontractor follow-up flow
gantt
title Subcontractor Payment Follow-Up Timeline
dateFormat YYYY-MM-DD
axisFormat %d %b
section Sequence
Friendly reminder :d1, 2026-04-01, 3d
Direct reminder :d4, 2026-04-04, 4d
Firm reminder :d8, 2026-04-08, 6d
Past due notice :d14, 2026-04-14, 16d
Final escalation step :d30, 2026-04-30, 15d Automate follow-ups
Build reminders, blocker-specific responses, and escalations from one invoice using the overdue invoice sequence generator.
- Upload invoice and project details.
- Generate friendly-to-firm sequences.
- Set send cadence and escalation rules.
- Track replies, opens, and payment outcomes.
Generate subcontractor follow-ups in minutes
Create an escalation-ready sequence for GC payment follow-up from one invoice.