Invoice follow-up email templates for B2B SaaS finance teams

An invoice follow-up email should do three things: remind the customer what is owed, make the next step easy, and keep the relationship calm. The best messages are short, specific, and tied to the actual invoice, not a vague "checking in" note.

For B2B SaaS finance teams, the hard part is not only wording. Invoices can get stuck behind accounts payable (AP) approvals, procurement portals, missing purchase orders (POs), usage questions, contract exceptions, partial payments, and promised-payment dates that slip. A good follow-up sequence needs templates for the normal cadence and rules for when to pause the cadence and route the issue to a human reviewer.

Use the templates below as a starting point. Replace the bracketed fields, attach or link the invoice, and adjust the tone based on invoice age, customer tier, and the account history.

Quick answer: the first invoice follow-up email to send

Send the first overdue invoice follow-up email one to three business days after the due date. Keep it polite, assume the delay was accidental, and include every detail the customer needs to pay without searching for the original invoice.

Subject: Invoice [Invoice number] is now past due

Hi [First name],

I am following up on invoice [Invoice number] for [Amount], which was due on [Due date].

You can view and pay the invoice here: [Payment link]. I have also attached a copy for reference.

If payment has already been sent, thank you and please disregard this note. If anything is holding up payment, reply here and I will help route it to the right person.

Best,
[Sender name]

That email works because it is factual. It names the invoice, amount, and due date, gives a payment path, and leaves room for the customer to tell you if there is a blocker.

What every invoice follow-up email should include

Every invoice follow-up email should be self-contained. The AP contact should not have to search their inbox, open your customer portal, or ask the business owner what you mean.

Include:

• Invoice number.
• Customer name or account name when useful.
• Original due date.
• Amount due and currency.
• Payment link or exact payment instructions.
• A copy of the invoice or a link to the invoice.
• The specific next step you want: pay, confirm payment date, share the blocker, or route to the correct AP contact.
• A real reply path for questions.

Before sending, confirm the invoice is still open. If payment arrived but was not matched to the invoice, another reminder creates avoidable friction. This is where billing reconciliation matters: collections follow-up should use current invoice and payment status, not last week's spreadsheet.

Invoice follow-up email cadence by stage

Use a sequence, not a random set of one-off messages. The exact timing depends on your invoice payment terms, customer tier, and contract language, but this cadence works for most B2B SaaS teams.

Do not keep sending standard reminders after the customer replies with a real issue. A dispute, missing PO, partial payment, or promised payment should change the workflow.

Invoice follow-up email templates by stage

1. Before the due date

Send this when the invoice is not late yet. The goal is to prevent surprises, especially for customers with AP approval queues or scheduled payment runs.

Subject: Upcoming invoice [Invoice number] due [Due date]

Hi [First name],

A quick reminder that invoice [Invoice number] for [Amount] is due on [Due date].

You can view and pay it here: [Payment link]. I have attached the invoice as well.

If this needs to go through a specific AP process, procurement portal, or PO reference, please let me know so we can make sure everything is in place before the due date.

Thanks,
[Sender name]

2. On the due date

Keep this short. The customer may already have the invoice in a payment run.

Subject: Invoice [Invoice number] is due today

Hi [First name],

Invoice [Invoice number] for [Amount] is due today, [Due date].

Payment link: [Payment link]

If payment has already been scheduled, thank you. If anything is needed from our side to process it, reply here and I will help.

Best,
[Sender name]

3. One to three business days overdue

This is the best default overdue invoice email. Assume good intent.

Subject: Invoice [Invoice number] is now past due

Hi [First name],

I am following up on invoice [Invoice number] for [Amount], which was due on [Due date].

You can pay it here: [Payment link]. I have attached a copy for reference.

If it has already been paid, thank you and please disregard this note. If something is holding it up, let me know and I will help route it.

Best,
[Sender name]

4. Seven to ten days overdue

At this point, ask for a payment date or the exact blocker.

Subject: Following up on invoice [Invoice number]

Hi [First name],

I am checking back on invoice [Invoice number] for [Amount]. It was due on [Due date] and is still showing as unpaid.

Could you confirm when payment is expected, or let me know if this is waiting on approval, a PO, a portal update, or another issue?

Payment link: [Payment link]

Thanks,
[Sender name]

5. Fifteen to thirty days overdue

Use this after earlier reminders have not produced payment or a clear blocker. Keep it factual, not angry.

Subject: Action needed: invoice [Invoice number] is [Days overdue] days overdue

Hi [First name],

Invoice [Invoice number] for [Amount] is now [Days overdue] days overdue. We sent previous reminders on [Dates sent], and the balance is still open.

Please arrange payment by [Requested date] using this link: [Payment link]. If the invoice is waiting on approval or there is a billing issue, please reply today with the owner and expected resolution date.

Per our agreement, late payment may affect [late fee / service access / account review language, if applicable].

Best,
[Sender name]

If you mention fees, make sure the wording matches your contract and policy. For a deeper policy walkthrough, see LedgerUp's guide to late payment fees.

6. Final notice

Use a final notice only after earlier reminders are documented and there is no active dispute, promised payment, or internal review path.

Subject: Final notice: invoice [Invoice number] overdue

Hi [First name],

This is a final notice for invoice [Invoice number] for [Amount], originally due on [Due date]. We have not received payment or a confirmed resolution path after reminders on [Dates sent].

Please pay the full balance by [Final date]: [Payment link]

If payment is not received by that date, we will move the account to the next step in our collections process. We would prefer to resolve this directly, so please reply today if there is a dispute, AP approval issue, or payment timing problem we should review.

Regards,
[Sender name]

B2B SaaS follow-up templates for common blockers

A lot of SaaS invoices are not unpaid because the customer refuses to pay. They are unpaid because the invoice is stuck somewhere. Use these templates when the blocker is known or likely.

AP approval is stuck

Use this when the customer says payment is waiting on an internal approver.

Subject: Approval status for invoice [Invoice number]

Hi [First name],

Thanks for the update. Could you confirm who currently owns approval for invoice [Invoice number] and when it is expected to clear?

For reference:

Invoice: [Invoice number]
Amount: [Amount]
Due date: [Due date]
Payment link: [Payment link]

If the approver needs the invoice, contract, PO, or usage detail again, I can send that over today.

Best,
[Sender name]

Missing PO or procurement portal issue

Use this when the invoice needs a PO, vendor portal submission, or customer-side vendor record update.

Subject: PO or portal details needed for invoice [Invoice number]

Hi [First name],

I am following up on invoice [Invoice number] for [Amount]. It looks like payment may be waiting on PO or portal requirements.

Can you confirm the correct PO number, procurement portal, and any vendor submission steps we should use? Once we have that, we can update or resubmit the invoice right away.

Attached: invoice [Invoice number]

Thanks,
[Sender name]

Billing dispute or usage question

Use this when the customer questions usage, seats, contract terms, tax, credit, or invoice accuracy.

Subject: Reviewing your question on invoice [Invoice number]

Hi [First name],

Thank you for flagging the question on invoice [Invoice number]. I am pausing standard payment follow-up while we review it.

To resolve this quickly, can you share the specific line item or amount you want us to check? We will review [usage / contract terms / credit / tax / seat count] and get back to you by [Date].

If part of the invoice is undisputed and ready for payment, let me know and I can help separate the next step.

Best,
[Sender name]

For SaaS teams with frequent invoice questions, connect this handoff to your billing support ticket workflow so disputes do not disappear in inboxes.

Partial payment or short-paid invoice

Use this when the customer paid less than the invoice amount.

Subject: Remaining balance on invoice [Invoice number]

Hi [First name],

Thank you, we received a payment of [Amount paid] toward invoice [Invoice number]. The remaining balance is [Remaining amount].

Can you confirm whether the remaining balance will be paid by [Requested date], or whether the short payment was tied to a credit, dispute, or adjustment?

Payment link for the remaining balance: [Payment link]

Best,
[Sender name]

A short-paid invoice should get a reason code and owner. Otherwise, the remaining balance is easy to lose during collections follow-up and month-end close.

Missed promised payment date

Use this when the customer committed to a payment date and missed it.

Subject: Payment date missed for invoice [Invoice number]

Hi [First name],

I am following up on invoice [Invoice number]. We had payment scheduled for [Promised date], but it is still showing as unpaid.

Can you confirm whether payment was sent, or provide a new firm payment date? If something changed, please let me know what is blocking it so we can route the right next step.

Payment link: [Payment link]

Best,
[Sender name]

Wrong AP contact or customer handoff

Use this when the original contact is not the person who can process payment.

Subject: Correct AP contact for invoice [Invoice number]

Hi [First name],

I am following up on invoice [Invoice number] for [Amount]. If you are not the right person for payment processing, could you point me to the AP contact or shared inbox that should receive this?

Invoice: [Invoice number]
Due date: [Due date]
Payment link: [Payment link]

Once I have the right contact, I will update our records so future invoices go to the correct place.

Thanks,
[Sender name]

Subject lines for invoice follow-up emails

Good subject lines are clear before they are clever. Include the invoice number whenever possible.

Use:

• Invoice [Invoice number] is due today
• Reminder: invoice [Invoice number] due [Due date]
• Invoice [Invoice number] is now past due
• Following up on invoice [Invoice number]
• Action needed: invoice [Invoice number] is [Days overdue] days overdue
• Approval status for invoice [Invoice number]
• PO or portal details needed for invoice [Invoice number]
• Remaining balance on invoice [Invoice number]
• Final notice: invoice [Invoice number] overdue

Avoid:

• Quick question
• Checking in
• Urgent
• Friendly reminder with no invoice context
• Your account
• Payment issue with no invoice number

Vague subject lines make life harder for AP teams. They also make your message harder to search later if the account needs escalation.

Mistakes to avoid

The FTC's CAN-SPAM guidance says there is no business-to-business exception for commercial email and that the primary purpose of a mixed message matters. For invoice follow-up, keep the transactional content first and avoid turning the email into a product promotion.

When to pause follow-up or route human review

Manual review is not a failure. It is how you avoid collecting the wrong amount, escalating the wrong customer, or sending a reminder that ignores known context.

Pause standard follow-up and route review when:

• The customer disputes usage, seats, contract terms, taxes, credits, or invoice accuracy.
• The invoice is missing a required PO or procurement portal submission.
• Payment was received but not applied or reconciled.
• The customer made a partial payment and the remaining balance needs a reason code.
• A promised payment date is active and not yet missed.
• A strategic or high-value customer is more than one stage overdue.
• Late fees, service suspension, or collections escalation require approval.
• The customer asks for a payment plan, credit, or contract exception.

A simple rule works: automate routine reminders, but route exceptions. In B2B SaaS, exceptions are where revenue leakage and customer frustration usually start.

When to automate invoice follow-up

Manual follow-up works when you have a small invoice volume and a clean customer list. It breaks down when your team has to track dozens or hundreds of open invoices across Stripe, QuickBooks, NetSuite, Xero, Salesforce, HubSpot, customer portals, and spreadsheets.

Automation is a good fit when you need to:

• Send reminders consistently before and after the due date.
• Personalize messages with invoice number, amount, due date, payment link, and account context.
• Stop reminders when payment is promised, received, disputed, or under review.
• Escalate based on invoice age, amount, customer tier, or risk.
• Keep a record of every email, reply, promise, dispute, and payment status.
• Connect follow-up to collections automation, reconciliation, and contract-to-cash workflows.

LedgerUp's automated payment reminders are built around that model. Ari monitors open invoices, sends contextual follow-ups, reads replies, pauses follow-up when payment is promised, flags disputes in Slack, and escalates the accounts that need a human decision. For teams scaling beyond manual chasing, that is the difference between sending more reminders and running an actual AR collections automation workflow.

FAQ

How soon should I send an invoice follow-up email?

Send the first overdue invoice follow-up email one to three business days after the due date. You can also send a pre-due reminder three to five business days before the due date and a short reminder on the due date. If the customer has a known AP approval or payment-run schedule, align the cadence to that process.

How many invoice follow-up emails should I send before escalating?

Most teams send a pre-due reminder, a due-date reminder, a first overdue nudge, a second follow-up around 7-10 days overdue, and a firmer reminder around 15-30 days overdue before a final notice. Escalate sooner if the customer breaks a promised payment date, disputes the invoice, or the balance is high-risk.

What should I say in a polite payment reminder email?

State the invoice number, amount, due date, and payment link in the first few lines. Assume the delay was accidental, attach or link the invoice, and invite the customer to reply if anything is blocking payment. Avoid guilt, vague urgency, or long explanations.

Should I attach the invoice again?

Yes. Attach the invoice or include a direct link in every follow-up. The easier it is for AP to verify the invoice, route approval, and pay, the fewer back-and-forth messages your team has to send.

How should I follow up if the customer says the invoice is wrong?

Pause the normal reminder sequence, ask which line item or amount they are disputing, assign an owner, and give a date when you will respond. If part of the invoice is undisputed, ask whether that portion can be paid while the disputed balance is reviewed.

Bottom line

A good invoice follow-up email is not clever. It is clear, specific, and timed to the customer's payment process.

Start with a simple sequence: before due, due date, first overdue, second overdue, firmer reminder, and final notice. Then add exception templates for AP approvals, procurement portals, disputes, short-pays, and missed promises. That gives your finance team a repeatable workflow instead of another inbox chore.

When the volume gets too high for manual tracking, automate the routine reminders and keep the exceptions visible. That is how follow-up turns from chasing payments into a controlled contract-to-cash workflow.