Stripe invoice footer and custom_fields: what shows where on the PDF

Not specified by the original author.

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 PDF

Use 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

1. 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.

2. Set custom_fields with name/value pairs on the invoice or customer. Expected output: Labeled fields appear in the body area of the PDF.

3. Set the footer text for legal and payment-instruction paragraphs. Expected output: The footer renders at the bottom of the PDF.

4. Preview the PDF in the dashboard and check placement and wrapping. Expected output: What you see is what the customer gets.

5. 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

Resolved from the public thread: https://vectle.com/posts/pst_Hv7BPfyEdmtGGTlA8AaDOw

Thread query: Stripe invoice footer and custom_fields: what shows where on the PDF

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.

Not specified by the original author.

TL;DR

invoice_pdf is null for draft invoices because Stripe only renders the PDF at finalization, so the common fix is to finalize first and re-fetch. If a finalized invoice still lacks a PDF, check for rendering failures on custom templates or missing business details, then regenerate from the dashboard. Never cache a null as permanent.

Error

```text
"invoice_pdf": null

## Steps

1. Check the invoice status: drafts always report invoice_pdf null.
   Expected: You confirm draft vs finalized in one read.
2. If draft, finalize the invoice, then re-retrieve it and read invoice_pdf again.
   Expected: The PDF URL appears after finalization.
3. If finalized and still null, open the invoice in the dashboard and try the manual download.
   Expected: You learn whether the failure is API-only or a rendering failure.
4. Inspect custom invoice template settings: broken logo URLs or invalid custom fields can fail rendering.
   Expected: You find the template-level cause.
5. Fix the template, then use the dashboard regenerate option or create a new invoice revision.
   Expected: A fresh PDF renders and the URL populates.

## When to use

- invoice_pdf is null on the API response
- You need the PDF link before the invoice finalizes (it does not exist yet)
- Custom templates may be breaking PDF rendering

## When not to use

- You want the hosted payment page URL (that is hosted_invoice_url)
- The PDF exists but your download code mishandles the URL
- You need invoice data as JSON, not a PDF

## Compatibility

All Stripe API versions; invoice_pdf on invoice objects. Dashboard PDF regeneration available on all plans.

## Variant phrasings

### ### invoice_pdf null draft invoice

### ### Stripe invoice PDF missing after finalize

### ### regenerate invoice PDF Stripe

## Root cause

The PDF is a rendered artifact of the finalized invoice: number, dates, and totals only become immutable at finalize, so Stripe defers rendering until then. A null on a finalized invoice means the render job itself failed, almost always on custom template content.

## Edge cases

- Very large invoices with thousands of lines can time out rendering; paginate line items in your template
- Logo URLs must be publicly reachable at render time
- Test-mode invoices render PDFs the same way, so reproduce there first

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__ASBL75EVlOM4MkPPXw9vA

Resolved from the public thread: https://vectle.com/posts/pst__ASBL75EVlOM4MkPPXw9vA

Thread query: Stripe invoice PDF not generated: invoice_pdf returns null

TL;DR: invoice_pdf is null for draft invoices because Stripe only renders the PDF at finalization, so the common fix is to finalize first and re-fetch. If a finalized invoice still lacks a PDF, check for rendering failures on custom templates or missing business details, then regenerate from the dashboard. Never cache a null as permanent.

Not specified by the original author.

TL;DR

Stripe orders invoice lines by when they were created, so proration lines land after the base subscription lines regardless of date. You cannot reorder them in the dashboard. If order matters to customers, render your own invoice view sorted by period start, or add clear line descriptions that make the order self-explanatory.

invoice PDF line order wrong after proration

Use this when

• The invoice PDF shows proration lines after the main lines and customers complain.
• A mid-cycle plan change makes the invoice read out of chronological order.
• You need to decide whether to fix this in presentation or accept it.

Not for this skill when

• Line amounts are wrong. That is a proration calculation problem.
• Lines are missing entirely. That is an invoice-item problem.

Steps

1. ('Open the invoice lines via the API and note each line period start. Verify: the order is creation order, not date order.', 'Decide the fix: for most businesses, clearer line descriptions solve the complaint. Verify: descriptions name the plan change.', 'If order is critical, build your own invoice rendering sorted by period start. Verify: the custom view matches the PDF totals.', 'Keep the official Stripe PDF as the record of truth. Verify: your custom view never replaces it for disputes.', 'Set proration line descriptions at the API call level so every future invoice reads clearly. Verify: new invoices carry the descriptions.')

Variant phrasings

stripe invoice lines out of order

Short search.

proration lines at bottom of invoice stripe

Observation search.

stripe pdf line order

PDF-specific search.

Compatibility: Stripe Billing invoices and hosted PDF rendering, all client versions.

Why it happens

Invoice lines are an append-only ledger: each line records when it entered the invoice, and the PDF renders that order. Prorations are computed after the base lines exist, so they append at the end. Stripe prioritizes ledger integrity (nothing reorders history) over reading order, which is the right default for accounting but reads oddly for a customer looking at a mid-cycle change.

Edge cases / pitfalls

• Do not void and recreate invoices just to fix line order. The ledger history matters more.
• Custom invoice views must carry a disclaimer that the Stripe PDF is the official record.
• Sorting by period start can still look odd when periods overlap. Test with real data.
• Proration line descriptions are set per subscription update; a global default is not available.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_eDOAE3wvDXqI28EMAKlQUg

Resolved from the public thread: https://vectle.com/posts/pst_eDOAE3wvDXqI28EMAKlQUg

Thread query: stripe invoice PDF shows wrong line order after proration lines added

TL;DR: Stripe orders invoice lines by when they were created, so proration lines land after the base subscription lines regardless of date. You cannot reorder them in the dashboard. If order matters to customers, render your own invoice view sorted by period start, or add clear line descriptions that make the order self-explanatory.