What if unused seats caused a true-up they didn't expect?

Name the seat math in one sentence and offer a credit path if that's policy, or a payment, especially around SKO and the bill. Don't lecture them about contracts. Sales VPs will fight a surprise true-up in CS and finance. Help them explain it. That's how you get paid without a war.

Should I copy billing and the sales VP together?

If that's already how this account pays, yes, with a short factual note, especially around SKO and the bill. If the VP was your only contact, ask them who owns AP rather than surprise-adding a finance alias you found on the website. Completeness is good. Ambush CCs are how relationships cool.

Can I pause the sandbox while an invoice is overdue?

Only if the contract says so and you've warned them in writing with a date, especially around SKO and the bill. Cutting access as a surprise punishment delay is how you lose the pod and the reference. Warn, date, and still offer to fix coding the same day, especially around SKO and the bill. Warm and firm can live together.

What belongs in the second reminder?

The same facts, plus what you already offered to fix, plus a date you'll assume it's in the, especially around SKO and the bill. Don't add new commercial terms. Don't add emotion. One extra line asking who owns the PO is plenty. Then wait for that run.

Is a phone call better than a third email?

If you already have a working voice relationship, a short call that names the invoice ID is kinder, especially around SKO and the bill. Voicemail should still carry the facts. Don't recap the product. Don't threaten. Ask whether it's PO, coding, or the next run, then get off the phone.

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

SaaS · Sales VP · After Invoice

Follow-Up Email After Invoicing a SaaS Sales VP

A follow-up after an invoice to a SaaS sales VP should make payment simple and keep dignity on both sides. Money is already on the table. Put the number, due date, invoice ID, and pay path in the first screen. Assume a PO or coding issue before you assume a snub. Warmth without jokes. Facts without a threat.

Copy-ready template

Subject

Invoice [Invoice ID]: seats, PO, or next AP run?

Body

Hi [First Name],

Invoice [Invoice ID] for [Amount] was due [Due Date]. Sharing it in case it sat in a CS or billing queue: [Seat Count] seats on [Plan], pay path [Link or AP email].

If it's waiting on a PO, a coding change, or a true-up question, tell me what's missing and I'll fix the backup the same day. If it's already in the next AP run, a one-word later is enough.

[Your Name]
[Your Title]

Why this follow-up works

The subject is a commercial question, not a scold, so it survives a forward to AP, especially around SKO and the bill.
Facts sit in the first screen, which is how busy VPs actually pay things.
You guess a PO or seat-coding stall instead of implying they skipped you, especially around SKO and the bill.
Same-day fix language makes you a partner to billing, not a collector, especially around SKO and the bill.
One-word later keeps dignity if the invoice is simply in the next run, especially around SKO and the bill.

When should I send this to a SaaS Sales VP?

A polite reminder a few days after the due date, then a firmer operational note if AP still hasn't moved, especially around SKO and the bill. Don't remind them the morning you sent the invoice, especially around SKO and the bill. Don't stack daily notes into close week. If they named a billing cutover, wait until the morning after, especially around SKO and the bill. Escalate to the original buyer only after AP has had a fair chance, and do it with facts, not heat, especially around SKO and the bill. Avoid Monday forecast hour. A midweek morning note is more likely to get dropped into the AP run, especially around SKO and the bill. After two operational notes, a single close-the-loop question is enough, especially around SKO and the bill. Then pick up the phone only if that's already how you work with them, especially around SKO and the bill.

What this Sales VP actually cares about

This VP may not even own AP. They own the relationship and the seat count that created the bill. Write so they can forward the note without embarrassment, especially around SKO and the bill. They read it between a forecast and a CS complaint. The first two lines have to be the invoice, not a check-in, especially around SKO and the bill. Don't CC the CRO. Don't ping every AE who uses the seats. Don't convert an unpaid invoice into a product upsell, especially around SKO and the bill. Their reputation with finance is on the line if you make them look sloppy, especially around SKO and the bill. Protect it. Then stop. A kind, factual note that offers to fix PO language is how grown-ups get paid in SaaS.

How SaaS changes the note

SaaS invoices to a sales VP stall in AP, not in feelings. Unused seats got coded wrong. A PO still says last year's count. CS promised a credit on dark licenses that billing never posted, especially around SKO and the bill. Your follow-up has to sound like you have seen those queues, especially around SKO and the bill. Rage emails get paid last. Jokes about cash get forwarded as a problem. Put the facts up top. Offer to fix coding. Ask if it's in the next run. Warmth is assuming a process issue first. The relationship is real, which is why you don't threaten, especially around SKO and the bill. Quiet after an invoice is often a true-up fight happening without you, especially around SKO and the bill. They are trying to explain why billed seats don't match activated AEs. Help that explanation. Send the seat map. Don't send a collections script you found online. Commercial calm is how you get paid and still get invited to the next QBR. If you invoiced wrong, say so and fix it. Don't apologize for asking to be paid when the invoice was right, especially around SKO and the bill.

Customization tips

Use the real invoice ID, seat count, and due date. Don't paraphrase money.
If AE expansion caused the true-up, say that in one line, not a lecture.
CC AP only if that's how this customer already pays, not as surprise pressure, especially around SKO and the bill.
Attach the PDF they asked for. Don't attach a new quote.
Send a few days after due, not the morning after you issued it, especially around SKO and the bill.

Common mistakes

Threatening, guilting, or burying the amount under a relationship paragraph.
Apologizing for asking to be paid when the invoice was correct.
Upselling seats in the same note as a past-due reminder.
CCing the CRO as surprise pressure on AP.

How this scenario compares

Dimension	For this template
Best send window	A few days after due, then one firmer operational note
Ideal length	Under 90 words, facts in the first screen
Primary ask	Next AP run, or the missing PO or coding doc
Unlike a proposal follow-up	Terms were accepted. You're in collections-lite, not sales.
Unlike an apology email	Only apologize if you invoiced wrong.

Questions people ask before they hit send

Assume a process issue first. Put invoice ID, amount, due date, and pay path up top, especially around SKO and the bill. Offer to fix coding or PO problems. Keep the tone operational. Escalate to the original buyer only after AP has had a fair chance, especially around SKO and the bill. Rage emails get paid last and remembered longest.

Related templates

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