Billing receipt

Deliver accurate charge confirmation with line-item clarity for finance and support teams.

Open linked layout View Pro

Workflow assembly

Trigger to production output

Trigger

Real send event

Workflow

Message journey

Layout

Complete structure

Components

Reusable blocks

Email

Production output

Workflow structure

Sent when a payment is captured or subscription invoice is finalised.

Goal

Confirm billing details clearly and reduce support tickets about charges.

Layout

Receipt System

Pro archive

This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.

Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.

What the production package needs.

A workflow is useful when the implementation contract is visible before anyone starts editing markup.

invoice.number

Example: INV-1042

Reference for finance reconciliation.

invoice.total_gbp

Example: £179.00

Total amount charged.

billing.download_url

Example: https://app.example.com/billing/invoices/INV-1042

Optional invoice PDF or portal destination.

Variant routes

Payment failed: Swaps confirmation copy for remediation steps and retry CTA.
VAT invoice required: Adds tax fields and legal footer language for VAT compliance.

Package access

Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
Full MJML source for this workflow
Compiled HTML output ready for ESP upload
Variant-ready workflow pack files
Versioned workflow updates inside Template Hedgehog Pro

Linked production layout

Receipt System

Receipt email layout with line items, invoice summary, and a concise compliance-safe footer.

Component stack

Header Centred, Receipt Line Items, Invoice Summary Card, Footer Privacy Light

Source file

receipt-email.mjml

Open layout

QA and handoff.

The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.

QA risks to review

Currency symbol and amount alignment can drift if number formatting is not fixed before send.
Line-item tables can clip in mobile clients when product names are excessively long.

Handoff steps

Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.

Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.

Use this workflow inside Pro.

Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.

View Pro