Subscription Invoice Email Template for Recurring Billing

A recurring billing email protects trust by making the next charge predictable. It should never surprise the customer with a total that differs from the billing system.

Decide which lifecycle state you are sending

State	Email job	Primary action
Upcoming renewal	Explain the planned charge	Review plan or billing method
Invoice issued	Deliver the invoice	View or pay invoice
Payment received	Confirm settlement	View receipt
Payment failed	Explain recovery	Update payment method
Plan changed	Confirm new recurring terms	Review subscription

Use separate templates or explicit state blocks. “Your subscription invoice” should not say “payment received” before settlement.

Required data

• Customer and account name
• Plan or product name
• Billing interval
• Service period
• Amount, currency, taxes, and credits
• Next charge or due date
• Invoice, receipt, and secure portal URLs
• Current payment method summary
• Cancellation or plan-change deadline when one exists

Render from the canonical invoice or subscription object. If the total is not final, label it as an estimate rather than calling it an invoice.

Upcoming renewal template

Subject: Your {{product_name}} subscription renews on {{renewal_date}}

Preheader: Next charge: {{amount}} {{currency}}.

Hello {{customer_name}},

Your {{plan_name}} subscription renews on {{renewal_date}}. The next charge is {{amount}} {{currency}} for {{billing_period}}.

Subscription	Details
Plan	{{plan_name}}
Service period	{{service_period}}
Payment method	{{payment_method_summary}}
Next charge	{{amount}} {{currency}}

[Manage subscription]

Review your plan or payment method before {{change_deadline}}. No action is needed if these details are correct.

{{company_name}}

Avoid billing surprises

If the amount changed because of a plan upgrade, usage, taxes, credits, or a contract term, name the reason. If a promotional price ends, show the old and new recurring amount with the date of change.

Do not include a “cancel now” button as a dark pattern. Provide the real account-management path and honor the product’s cancellation policy.

Sequence rules

• Suppress the upcoming-renewal email if the subscription is canceled before the send.
• Re-render near send time if usage or tax can change the amount.
• Use the invoice-issued message after the invoice is finalized.
• Use a receipt only after the payment settles.
• Transition to dunning after a failed charge.

QA checklist

• Renewal date and timezone are correct.
• Amount matches the billing preview or finalized invoice.
• Plan, period, taxes, and credits are legible.
• A canceled or paused subscription is suppressed.
• Links open the correct account and respect permissions.
• Duplicate billing events do not send duplicate notices.

For the finalized record, use the invoice email template; for recovery, use the dunning template.

Changes that deserve a notice

The customer should not discover a billing change from the card statement. Consider a dedicated notice when:

• the plan price changes;
• a trial or promotional price ends;
• seats or usage change the recurring amount;
• the billing interval changes;
• tax or billing entity changes the total;
• a payment method or renewal date changes.

Show the effective date and the old-versus-new amount when the product policy requires it. Keep the renewal invoice itself focused on the record.

Reconciliation checklist

Before the send, compare the subscription, invoice preview, payment method, and customer timezone. If the invoice total is still subject to usage or tax calculation, label it as an estimate and send the finalized invoice later. Suppress renewal notices after cancellation, but retain required records and receipts.