Stripe invoice footer and custom_fields: what shows where on the PDF
Places content correctly on Stripe invoice PDFs. Use footer for legal text and custom_fields for labeled key-value info. Not for line-item data.
TL;DR
On the Stripe invoice PDF, the footer is freeform text at the bottom for legal notices, payment instructions, or terms; customfields render as labeled key-value pairs (up to a small limit) in the invoice body area. Use customfields for things like PO number, VAT ID, or contract reference that need a label, and the footer for paragraphs like remittance details or late-fee policy. Keep both concise: PDFs have finite space and long footers push onto extra pages. Preview the PDF after changes; the dashboard preview is the truth.
The query
Stripe invoice footer and custom_fields: what shows where on the PDFUse this when
- Adding PO numbers or VAT IDs to Stripe invoice PDFs
- Where to put legal text on a Stripe invoice
- Custom fields not showing on the invoice PDF
Not for
- Line-item level data (belongs on the line items)
- Email body content (separate from the PDF)
Steps
- Decide what is labeled data (PO number, VAT ID) vs paragraph text (terms, remittance info).
Expected output: Each piece has a home before you configure anything.
- Set custom_fields with name/value pairs on the invoice or customer.
Expected output: Labeled fields appear in the body area of the PDF.
- Set the footer text for legal and payment-instruction paragraphs.
Expected output: The footer renders at the bottom of the PDF.
- Preview the PDF in the dashboard and check placement and wrapping.
Expected output: What you see is what the customer gets.
- Keep a template of standard footer text per entity or region for consistency.
Expected output: Every invoice from an entity looks the same.
Variant phrasings
Stripe invoice custom_fields PDF
Stripe invoice footer text
where do custom fields show on Stripe invoice
Root cause
The split exists because invoices need both structured reference data (auditors and AP systems look for labeled fields) and unstructured legal prose. custom_fields serve the machines and the footer serves the humans.
Edge cases
- custom_fields have a count limit; prioritize what auditors actually need
- Footer text is per invoice or customer default; set defaults rather than hand-editing each invoice
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_Hv7BPfyEdmtGGTlA8AaDOw
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.