Do I name the tenant ID and PO in the first reminder?

Yes. Tenant or workspace name, PO, invoice number, amount, due date. That's the file. Without those five, you're asking them to hunt. They will not hunt for you between a standup and a ticket pile. Put them in the subject and again in line one. Duplicate is fine. Missing is how you wait another cycle.

What if corporate AP owns the invoice and the department only uses the product?

Ask in line two who owns AP. Offer to move the thread. Don't keep leaning on the department head for a corporate term. They can confirm the tenant is live. They often can't release a check. A clean handoff is faster than 4 reminders to the wrong desk. Thank them for the pointer. Then follow it.

Should I pause reminders during a go-live they named?

Yes if they named it or the changelog is public. Go-live week is tickets, not AP. Your reminder will sit under 60 vendor emails and a Sev list. Wait until the Tuesday after. Then send the same file facts. Don't add urgency you invented because your month is closing.

How do I ask about a short-pay on implementation hours?

Name the invoice, the amount paid, the amount open, and ask for the reason code. That's operations. Don't threaten. Don't write disappointed. A short-pay with no code is a process miss until they tell you it isn't. Offer to send the milestone sheet. Leave legal language for a later step you actually mean.

When do I call instead of sending a second invoice follow-up?

After the second email, or sooner if the amount is large enough that a missed cycle hurts both of you. Call with the same five facts. Don't perform. Ask which gap is open. If you get voicemail, 20 seconds that names tenant, invoice, and your number is enough. Don't recap your company story on a recording.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · Department Head · After Invoice

Follow-Up Email on an Invoice for a SaaS Department Head

An invoice follow-up to a SaaS department head is a file chase: invoice number, amount, due date, and PO in the first screen. Assume a coding miss or a milestone dispute before you assume a fight. Departments pay when the packet matches the tenant. Write like a CS note, not collections theater.

Copy-ready template

Subject

Invoice [Invoice Number] for [Tenant / Company Name]

Body

Hi [First Name],

Invoice [Invoice Number] for [Tenant] at [Company Name] is [Amount], due [Due Date], PO [PO Number]. Treating this as a missing page, not a fight.

Is the hole a PO, an implementation milestone, or corporate AP? Reply with the gap and I'll send that sheet today. If it's already in the [Pay Cycle] run, a received is enough and I'll wait.

[Your Name]
[Your Title]
[Your Company]

Why this follow-up works

The subject is a file label they can search between standups.
You assume a process miss, which is usually true across SaaS AP.
Three gaps (PO, milestone, AP) let them answer in one word.
Offering the missing sheet cuts a round trip they don't have time for.
You don't threaten on the first reminder, so the renewal still exists.

When should I send this to a SaaS Department Head?

Send the first reminder 2 or 3 business days after the due date, on a weekday morning. Avoid GA weeks and posted incidents. If they have a known corporate pay run, write the morning after that day. Don't drip daily. After the second reminder, pick up the phone and name the same file. A third email that only restacks the amount without a new gap question is noise. If they told you about a planning freeze, wait. Your reminder during that week is how you become the vendor they delay on purpose. 09:30 local on Tuesday beats Monday at 07:00 when they're covering tickets. Night-before-close emails sit. Send after the sprint, not during it.

What this Department Head actually cares about

A department head is protecting budget, a renewal narrative, and a team that still needs the tool. They read email between a ticket review and a VP update. The first two lines have to be a file they can forward to AP without rewriting. Asking how the quarter is going as a warmup is how you get ignored. They'll spend 8 seconds deciding if you're creating work. Show the numbers, name three possible gaps, then stop. Don't CC the CFO to apply pressure on reminder one. Don't joke about the check is in the mail. Be exact. Wrong tenant names are a professional insult during a go-live. If your note would look sloppy in a finance forward, rewrite it. They live in 15-minute blocks between standups and leadership.

How SaaS changes the note

SaaS AP lives inside POs, tenants, and implementation milestones that slip when one PDF is missing. A department head isn't the clerk, but they can unstick a file if you give them a number and a gap. Your reminder has to sound like you've billed a software team before. Talk invoice, PO, and the blocker. Don't talk brand love. Quiet after an invoice often means the packet sat under a security questionnaire or a go-live checklist. Completeness is how you get paid. Charm without paperwork is a delay. If you can't name the tenant and the due date, you're nagging a person whose day is already a series of tickets. A 2-day miss on a 14-day term is overtime in AP. A short-pay on implementation hours with no reason code is a week of email. Put the numbers first. Seat invoices and professional-services lines stall for different reasons. Name which one you mean.

Customization tips

Use the tenant name they see in the product, plus the legal entity on the MSA.
If implementation hours are on the invoice, say so. Mystery lines stall.
Match their pay cycle, not your hope.
If corporate AP owns the check, ask for that inbox in sentence two.
Don't send this during a posted incident. They'll remember the timing.

Common mistakes

Opening with per my last email and no invoice number.
Going legal on reminder one.
Reattaching a 40-page pack they already filed.
Using a cute subject like friendly nudge on a seat invoice.

How this scenario compares

Dimension	For this template
Best send window	Weekday morning, 2-3 days after due, skip GA week
Ideal length	Under 100 words, numbers first
Primary ask	Which file gap is blocking the pay run
Unlike a proposal follow-up	Terms were accepted. You're in collections-lite, not sales.
Unlike the original invoice send	You're hunting a gap, not introducing the company

Questions people ask before they hit send

Two or three business days, weekday morning. Same-day-after-due notes feel like you didn't wait for the run. Waiting 14 days trains them that you're optional. If they published a pay calendar, write the morning after that cycle. Don't send during a posted incident. They'll remember you as noise.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1175.