Payment Reminder Email Templates for Subcontractors

I was at a construction finance conference in Phoenix recently, talking with a subcontractor controller about collections. When I asked what gave her team the biggest headache, she hesitated before admitting they still tracked collections in a spreadsheet and sent follow-up emails manually. 

She laughed because she knew Siteline automates a lot of that (and I was wearing my crispest Siteline logoed polo), but the issue isn’t funny. A clean pay app would go out, everyone would assume it was moving, and 30 days later nobody on the GC’s side had even confirmed they received it. Now it’s past due.

This is a prevalent problem in construction collections, and the fix isn’t a louder email—it’s a structured sequence that keeps the unpaid pay app top of mind for all parties involved. Below are practical payment reminder email templates for the three moments that matter most: confirming the pay app was received, reminding the GC before payment is due, and following up once payment is past due.

Why a Payment Reminder Email Sequence Beats One-Off Follow-Up

A good payment reminder email sequence doesn’t feel aggressive, it feels organized.

This matters because most GCs are not sitting around plotting how to ignore your invoice. Your pay app is one of many sitting in someone’s inbox, waiting on approval, backup, a lien waiver, owner funding, or someone named Larry who is somehow always out of office.

One vague “just checking in” email on day 45 won’t do much. But a few specific, well-timed messages will, as long as they:

1. Confirm the GC received the pay app
2. Remind the GC of the upcoming payment date
3. Escalate once the payment is actually late

That progression protects the relationship while building a paper trail. Then, if payment stalls, you can get firmer without sounding emotional. 

The Three Payment Reminder Emails Subcontractors Should Use

These templates are written for subcontractors billing commercial construction projects, but the structure works for any team that needs to collect from GCs without damaging the relationship.

Use them as a starting point, adjusting the tone based on your GC, payment terms, and how long the invoice has been outstanding.

Email 1: Submission Acknowledgement

• When to send: One day after the pay app is submitted
• Who to send it to: The GC’s accounting contact, project accountant, or PM
• What it does: Confirms receipt, documents what was sent, and anchors the expected payment date
• Tone: Friendly, helpful, and specific—no pressure, just confirming

This preliminary email isn’t necessarily a collections one. It’s a small step that ensures the pay app is on the client’s radar. 

A lot of teams skip it, and I think that's a mistake. If the GC later claims they never received the pay app or didn't know when payment was due, you have a record. It also gives them an early chance to flag anything missing or incorrect—a piece of backup, a wrong amount—before it becomes a problem later down the road.

Example

Subject: Confirming receipt of Pay App #[NUMBER] for [PROJECT NAME]

Hi [NAME],

Confirming we submitted Pay Application #[NUMBER] for [PROJECT NAME] on [SUBMISSION DATE], in the amount of [AMOUNT DUE]. I’ve attached a copy for your records.

Could you confirm you received it? Per our contract, payment is due [DUE DATE]. If anything looks off or you need additional backup, let me know and I’ll turn it around quickly.

Thanks,
[YOUR NAME]
[COMPANY]
[PHONE]

Email 2: Payment Due Soon

• When to send: Three to five days before the payment due date
• Who to send it to: The same accounting contact, with the PM cc’d if that is normal for the account
• What it does: Gives the GC a polite nudge before the pay app becomes overdue
• Tone: Friendly but proactive

This is the “let’s not let this become a problem” email, and the best version of it does two things: it repeats the exact amount and due date, then makes one last check for anything missing or off while there’s still time to fix it.

That last part is important. By now, you’ve given the client two chances at this point to flag issues before the window closes. I’ve seen payments get pushed a full cycle because of one missing waiver, one approval, or one piece of backup nobody asked for until it was already late. Don’t give the process a chance to surprise you.

Example

Subject: Payment for Pay App #[NUMBER] on [PROJECT NAME] due [DUE DATE]

Hi [NAME],

A quick reminder that payment for Pay Application #[NUMBER] on [PROJECT NAME] is due [DUE DATE]. The amount due is [AMOUNT DUE], and I’ve attached the pay app for reference.

Everything should be in order on our end. If any documentation, approval, lien waiver, or backup is still needed, please let me know and I’ll get it handled.

Appreciate your help keeping this on track.

Thanks,
[YOUR NAME]
[COMPANY]
[PHONE]

Email 3: Payment Is Past Due

• When to send: Starting the day after payment is due, then at a set cadence‍
• Who to send it to: Accounting contact first, then cc or escalate to the PM or senior contact as needed‍
• What it does: Marks the payment as late and asks for a status update or firm payment date

This is where the real collections work begins. Past-due is one reminder type, but it's meant to be sent several times at set intervals, each message a little firmer than the last as the invoice ages.

Here's the cadence I'd start with.

Past Due Reminder #1: Day One Past Due

Tone: Warm, but explicit

Subject: Payment past due for Pay App #[NUMBER] on [PROJECT NAME]

Hi [NAME],

Following up on Pay Application #[NUMBER] for [PROJECT NAME], submitted on [SUBMISSION DATE]. The amount due is [AMOUNT DUE], and payment is now [DAYS PAST DUE] past due.

Can you confirm the status and let me know the expected payment date? If there is a holdup on the GC or owner side, a quick heads-up would help us plan accordingly.

Thanks for your help getting this sorted.

[YOUR NAME]
[COMPANY]
[PHONE]

Note: I like the line about a holdup on the GC or owner side because it gives them an easy way to tell you what is actually going on. The sooner you know, the better.

Past Due Reminder #2: Seven to 10 Days Past Due

Tone: Firmer, but still professional

Subject: Second notice: past due Pay App #[NUMBER] for [PROJECT NAME]

Hi [NAME],

Circling back on Pay Application #[NUMBER] for [PROJECT NAME], in the amount of [AMOUNT DUE]. Payment is now [DAYS PAST DUE] past due, and I have not yet received an update on the expected payment date.

Can we get this resolved this week? If this needs to move to someone else on your team for approval or release, please point me in the right direction and I’ll follow up with them directly.

I’d like to keep this straightforward for both of us.

Thanks,

[YOUR NAME]
[COMPANY]
[PHONE]

Note: “Point me in the right direction” does a lot of work here. It’s polite, but it also makes clear you are not going to let the invoice sit with the wrong person forever.

Past Due Reminder #3: Around 21 Days Past Due

Tone: Firm, pre-escalation

Subject: Final reminder before escalation: Pay App #[NUMBER] for [PROJECT NAME]

Hi [NAME],

This is my final reminder before we escalate Pay Application #[NUMBER] for [PROJECT NAME], in the amount of [AMOUNT DUE]. Payment is now [DAYS PAST DUE] past due despite prior follow-ups.

We would prefer to resolve this directly. Please send payment, or a firm payment date, by [DATE]. If we do not hear back, we will move to a formal demand to protect our right to payment.

Thank you,

[YOUR NAME]
[COMPANY]
[PHONE]

Note: This email should not sound angry. Anger usually makes you look less in control. Remaining firm and clear does the opposite.

Recommended Payment Reminder Cadence

Here’s a quick recap of the cadence I just covered:

‍

The exact cadence depends on your payment terms and GC relationships. Some teams may want a 14-day past-due reminder before jumping to day 21. Some may want to escalate faster if the project is high-risk or the GC has a history of slow payment. (If you want to go deeper on that, here’s how to build an A/R escalation process that actually holds.)

The bigger point is this: do not let the timing live in someone’s head. Put the sequence in place so every pay app gets the same professional follow-up.

Next Steps for When Automated Reminders Run Out

Sometimes the reminders run out and the money still hasn’t moved. That’s when you reach for these two payment recovery tools: the demand letter and the lien rights standing behind it.

Send a Demand Letter

A demand letter is the step you take when the softer follow-ups have not worked, and it’s where the tone really shifts. You’ve stopped asking for a quick status update and started documenting the debt, referencing the contract, and setting a deadline before further action. 

Unlike routine reminders, demand letters are usually handled on a case-by-case basis because they require judgment about the specific situation, including the payment history, project circumstances, contractual obligations, and whether additional collection or legal action may be appropriate.

• When to send: Usually around 30+ days past due, depending on your contract and internal escalation process
• Who to send it to: The GC’s accounting lead, PM, and a senior contact if needed
• What it does: Creates a formal record and signals that the issue is moving beyond routine follow-up

If you want a stronger starting point, Siteline’s free construction demand letter template gives you a formal structure with space for project details, payment terms, and the deadline for payment.

Act on Your Lien Rights

Better emails are helpful. A good cadence is helpful. A formal demand letter is helpful. But none of that creates real leverage by itself. That’s where your mechanic’s lien rights come in.

The catch is that they only work if you protect them from the start of the project. You can’t manufacture leverage at day 45 that you unknowingly forfeited by missing a preliminary notice deadline back in week one. 

But assuming you’re covered, the move after a demand letter goes unanswered is a Notice of Intent to Lien, which is a formal heads up that you’ll file a mechanic’s lien if payment isn’t made by a specific date. 

• When to send: After the demand letter goes unanswered, and well before your state's lien-filing deadline
• Who to send it to: The GC, and often the property owner and lender, depending on your state's requirements
• What it does: Signals you're prepared to file a lien, which tends to move payment faster than any email can

Twelve states require commercial subs to submit a Notice of Intent before they can file. Regardless, it's widely considered best practice to send one. It cites the statute, names the deadline, and puts everyone with money in the project on notice (the GC, the owner, and in some cases the lender). That's exactly the audience you want paying attention.

How Siteline Helps You Chase Payment and Keep Leverage

Siteline’s Collections workflow helps subcontractors automate the follow-up sequence: submission acknowledgements, payment-due reminders, and as many past-due reminders as you need. Each reminder can be customized by timing, sender, recipients, cc, subject, and message, so teams can match the tone to their process.

Beyond the emails, Siteline also pulls every aging invoice into one view you can sort by project, PM, GC, or how far overdue it is, and lets you assign each one as a task with an owner and a due date.

But reminders are only as strong as the leverage behind them. Siteline’s Lien Rights Management tracks state-specific requirements by project, so your team always knows what's required, when it's due, and whether each project is protected, at risk, or has lost its rights. And when a notice needs to go out, Siteline generates it with your state’s requirements in mind, sends it by certified mail, and logs exactly what went out and when it landed.

That’s the real playbook:

1. Run the reminder sequence so payment doesn’t drift.
2. Protect your lien rights from the start so you keep leverage if it does.

One without the other is weaker than it looks. A polished past-due email won't move a GC who knows your lien rights expired three weeks ago, and lien rights alone won't collect a dime without the day-to-day follow-up that keeps cash moving. Book a demo to see how Siteline runs both in one place.