India GST on Stripe invoices: how to show GSTIN on the invoice PDF

Not specified by the original author.

TL;DR

Stripe Tax calculates India GST when the customer address is in India; to make the PDF compliant, set your business GSTIN in the account tax settings and add GSTIN display plus HSN/SAC codes via custom fields. Verify the PDF shows the GSTIN, the tax split (CGST+SGST intra-state, IGST inter-state), and the place of supply. Test with an intra-state and an inter-state customer.

Steps

1. Enter your GSTIN in the Stripe account tax information settings. Expected: The seller GSTIN is available to every invoice template.

2. Enable Stripe Tax and confirm India GST rates apply for Indian customer addresses. Expected: Tax calculates with the correct slab.

3. Add custom fields or footer text for GSTIN display, HSN/SAC codes, and place of supply. Expected: The PDF carries the fields Indian auditors expect.

4. Generate a test invoice for an intra-state customer and one for inter-state. Expected: You verify CGST+SGST vs IGST rendering on real PDFs.

5. Store the customer's GSTIN as a tax ID on the customer for B2B input-credit support. Expected: Business customers get the GSTIN they need for credits.

When to use

• You invoice Indian customers from Stripe
• The PDF must show GSTIN and GST breakup
• You need CGST/SGST vs IGST handling

When not to use

• Your customers are outside India (different tax regimes)
• You only need US sales tax (simpler setup)
• GST registration does not apply to your turnover (check thresholds)

Compatibility

Stripe Tax with India GST support; invoice customization (logo, custom fields, footer). Test mode renders PDFs identically.

Variant phrasings

### Stripe invoice GSTIN India

### GST invoice format Stripe CGST SGST

### HSN code Stripe invoice India

Root cause

Indian GST law prescribes tax-invoice contents: GSTIN of supplier, HSN classification, rate, and the CGST/SGST vs IGST split by place of supply. Stripe Tax computes the numbers, but the prescribed display fields come from your template configuration.

Edge cases

• Export invoices (LUT) are zero-rated but still need the prescribed format
• Place of supply determines the split; a wrong customer state flips CGST/SGST to IGST
• E-invoicing (IRN/QR) thresholds may require integration beyond the PDF for large turnovers

Provenance

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

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

Thread query: India GST on Stripe invoices: how to show GSTIN on the invoice PDF

TL;DR: Stripe Tax calculates India GST when the customer address is in India; to make the PDF compliant, set your business GSTIN in the account tax settings and add GSTIN display plus HSN/SAC codes via custom fields. Verify the PDF shows the GSTIN, the tax split (CGST+SGST intra-state, IGST inter-state), and the place of supply. Test with an intra-state and an inter-state customer.

Not specified by the original author.

TL;DR

Seller tax IDs live in the Stripe account tax settings, and you can add several (one per country or regime); Stripe prints the relevant ones on invoices. Add each registration number with its country, then verify it appears on a test invoice PDF for a customer in that jurisdiction. Keep the list current as you register in new countries.

Steps

1. Open account tax settings and add each seller tax ID with its country and type. Expected: Registrations are stored per jurisdiction.

2. Generate a test invoice for a customer in each registered country. Expected: You confirm the right ID prints on the right invoice.

3. Check invoice customization so tax IDs render in the header or footer area auditors expect. Expected: Placement matches local invoice conventions.

4. Document which ID applies where for your finance team. Expected: Nobody guesses during audits.

5. Set a reminder to update the list when registrations change or expire. Expected: Stale IDs never ship on invoices.

When to use

• Invoices lack your VAT/GST/tax registration number
• You are registered in multiple countries
• Customers need your tax ID for their input credits

When not to use

• The missing ID is the customer's tax ID (different field)
• You have no registration in that country (get one first)
• Tax calculation itself fails (check addresses and Tax setup)

Compatibility

Stripe dashboard account tax settings; invoice PDF rendering. Available on all plans.

Variant phrasings

### Stripe seller VAT ID on invoice

### add tax registration number Stripe invoice

### invoice missing company tax ID

Root cause

Tax IDs are account-level credentials, not per-invoice data URIs Stripe stores them once and selects which to print by the invoice's tax jurisdiction. A missing ID on the PDF almost always means it was never entered at the account level, not a per-invoice bug.

Edge cases

• Some jurisdictions require the ID even on zero-tax invoices; the display setting is separate from calculation
• Changing a tax ID does not rewrite already-finalized invoices; credit note and reissue if needed
• Marketplace facilitator regimes may shift who the seller of record is; check before adding IDs

Provenance

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

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

Thread query: Stripe invoice missing seller tax IDs: adding tax IDs per country

TL;DR: Seller tax IDs live in the Stripe account tax settings, and you can add several (one per country or regime); Stripe prints the relevant ones on invoices. Add each registration number with its country, then verify it appears on a test invoice PDF for a customer in that jurisdiction. Keep the list current as you register in new countries.

Not specified by the original author.

TL;DR

amounttaxdisplay controls presentation only: whether the Stripe invoice PDF shows line amounts with tax included or excluded. It does not change the tax computed; taxbehavior on the price does that. Set the display to match local convention and your taxbehavior so the PDF is internally consistent: inclusive display with inclusive behavior for VAT regions, exclusive display with exclusive behavior for US sales tax. A mismatch (exclusive computation shown as inclusive) is the classic source of 'your invoice math is wrong' tickets.

The query

Stripe "amount_tax_display" inclusive vs exclusive on invoice PDFs

Use this when

• Invoice PDF totals confusing customers about tax
• Matching PDF display to VAT-inclusive pricing
• amounttaxdisplay setting on Stripe invoices

Not for

• Changing how much tax is charged (use tax_behavior and tax rates)
• Email receipt formatting (separate template)

Steps

1. Confirm the tax_behavior on your prices first: inclusive or exclusive. Expected output: The computation convention is established.

2. Set amounttaxdisplay to match that convention on the invoice settings. Expected output: Display and computation agree.

3. Generate a sample PDF and walk the line items: base, tax, total. Expected output: The PDF reads correctly to a customer in that market.

4. Check both a VAT-region and a US-style customer if you serve both. Expected output: Each market's PDF follows its convention.

5. Document the pairing in your billing setup notes. Expected output: Nobody flips one without the other later.

Variant phrasings

Stripe amounttaxdisplay inclusive exclusive

invoice PDF shows tax included Stripe

Stripe tax display on invoice PDF

Root cause

Stripe separates computation (taxbehavior) from presentation (amounttax_display) because the same computed tax can be legally displayed either way depending on jurisdiction. The bug class is display disagreeing with computation, which reads as wrong math even though the money is right.

Edge cases

• The display setting can be overridden per invoice; prefer account or customer defaults
• Credit notes mirror the invoice's display; check them too

Provenance

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

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

Thread query: Stripe "amounttaxdisplay" inclusive vs exclusive on invoice PDFs

TL;DR: amounttaxdisplay controls presentation only: whether the Stripe invoice PDF shows line amounts with tax included or excluded. It does not change the tax computed; taxbehavior on the price does that. Set the display to match local convention and your taxbehavior so the PDF is internally consistent: inclusive display with inclusive behavior for VAT regions, exclusive display with exclusive behavior for US sales tax. A mismatch (exclusive computation shown as inclusive) is the classic source of 'your invoice math is wrong' tickets.