No receipt link or PDF
Users need to download receipts for expense filing. An email without a receipt link generates support requests.
SaaS email template
Fire invoice.paid with plan, amount, period and receipt URL. else.events sends a clean, branded receipt that users can file and forget.
Users need to download receipts for expense filing. An email without a receipt link generates support requests.
A receipt that shows the amount but not the billing period (e.g. May 2026) is not useful for accounting purposes.
The receipt should clearly show: plan, amount, billing period, next billing date. Generic confirmation emails get no confidence from finance teams.
Receipt email logic tied to the billing service means every copy change requires a deployment.
Stripe and Paddle provide a receipt or hosted invoice URL. Include it in the event payload. The template renders it as a "Download receipt" link.
Include all billing fields in the event payload. The template renders a complete receipt without any database query.
Receipt emails use the same MJML template base and brand variables. Finance teams recognise the sender.
Edit receipt copy, add a tax number field or update the footer without touching the billing service.
{{ user.name }}Recipient name{{ user.email }}Billing email address{{ data.plan }}Plan name (e.g. Pro, Premium){{ data.amount }}Charged amount with currency{{ data.billing_period }}Billing period (e.g. May 2026){{ data.next_billing_date }}Next charge date{{ data.receipt_url }}Link to download or view the receiptFull billing detail from the payload, receipt link included, consistent branding. No hardcoded billing email.