Stripe per-line tax rates vs invoice-level tax on Stripe invoices
Chooses between per-line and invoice-level tax on Stripe invoices. Use when different line items need different tax treatment. Not for customer exemption status.
TL;DR
Stripe lets you set tax rates per invoice line or default them at the invoice/customer level. Use per-line rates when line items genuinely differ (taxable software plus exempt services, or multi-jurisdiction lines); use invoice-level defaults when everything on the invoice shares treatment. Per-line precision costs complexity, so default to the invoice level and override per line only where the tax rules require it. Audit the choice on a sample invoice per product mix; wrong-level tax is a quiet compliance leak.
The query
Stripe per-line tax rates vs invoice-level tax on Stripe invoicesUse this when
- Mixed taxability on one invoice
- Different tax rates per product line
- Choosing where to set tax rates in Stripe
Not for
- Customer-level exemption (use customertaxexempt)
- Computing tax automatically (use Stripe Tax)
Steps
- Map your product lines to their tax treatments per jurisdiction.
Expected output: You know which lines actually differ.
- Set the common treatment as the invoice or customer default.
Expected output: The normal case needs no per-line work.
- Override tax rates on the specific lines that differ.
Expected output: Exceptions are explicit and visible.
- Generate a sample invoice per product mix and verify each line's tax.
Expected output: The invoice is correct line by line.
- Review the mapping when tax rules or product lines change.
Expected output: The config tracks reality.
Variant phrasings
Stripe per line tax rates vs invoice level
different tax rates line items Stripe invoice
invoice level tax default Stripe
Root cause
Tax is legally a per-line-item question (each thing sold has its own treatment), but operationally most invoices are uniform; Stripe offers both levels so the common case stays simple and the mixed case stays possible. The leak is assuming uniformity when the catalog is actually mixed.
Edge cases
- Exclusive vs inclusive tax_behavior interacts per line; keep the convention consistent
- Credit notes copy the invoice's line-level tax treatment; verify on refunds
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_nLWHtlbCE0-5Q5rr58pYkQ
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.