Stripe Product Tax Code

Product tax code vs tax rate vs QuickBooks tax code

Three similar-sounding things sit in a Stripe-to-QuickBooks setup, and they do different jobs.

A product tax code (txcd_) describes the product. It says nothing about a percentage. Stripe Tax combines it with the customer's location and your registrations to work out the tax.

A Stripe tax rate (txr_) is a fixed percentage you create yourself and attach to invoices or subscriptions. It is the manual alternative to Stripe Tax: Stripe applies the rate you chose and makes no taxability decision of its own.

A QuickBooks tax code lives in QuickBooks and controls how QuickBooks itself calculates or reports tax on a transaction line. Changing a Stripe product tax code changes none of these other two.

Where the code comes from: product, preset and shipping

Stripe gives you two places to set a product tax code. You can set it on each Product, in the Dashboard or with the tax_code parameter in the API. Or you can rely on the preset product tax code in your tax settings, which Stripe uses for any product without a code of its own. Transactions that pass product_data instead of a saved Product can carry a tax_code there too.

The preset does a second job. Stripe uses it to estimate the thresholds you are approaching under threshold monitoring. A preset that doesn't match what you actually sell skews both the tax and the warnings.

Shipping has its own preset. It defaults to the Shipping code (txcd_92010001), and Stripe lets you switch it to Nontaxable. Stripe recommends leaving it on Shipping, because states tax shipping in different ways, some in proportion to the goods shipped and some at the highest rate in the order.

When one product could fit two codes, Stripe's advice is to split it. Software sold to both consumers and businesses becomes two Products with two codes. Business-use software as a service (txcd_10103001) and personal-use software as a service (txcd_10103000) are separate codes, and Stripe notes the distinction matters only if you have US sales.

How a wrong code shows up

A wrong code is a classification error, so the symptom is tax that is wrong in kind, not off by a cent. A taxable product coded as Nontaxable collects nothing. An exempt product coded as general tangible goods collects tax the customer shouldn't have paid. Either way, the error repeats on every sale of that product until someone changes the code.

The itemized export is where to look. Every row carries the tax_code Stripe used, the taxability (taxable or nontaxable) and a taxability_reason. A row with product_exempt or reduced_rated tells you the code drove the result. A row with not_collecting needs a second look. Stripe notes that not_collecting means either that you have no registration in that jurisdiction or that the product carries the Nontaxable code. Check the code before you conclude it is a registration gap.

Fixing the code changes future calculations. It does not rewrite what already happened. Stripe doesn't let you change the amounts on a finalized invoice. Past sales taxed under the wrong code get corrected with credit notes or with the tax authority, not by editing the code.

Tax codes on imported transactions

If you import sales from other platforms into Stripe Tax, each imported line needs a product tax code too. line_item.product_tax_code is a required column in the import CSV. Shipping lines take either Nontaxable (txcd_00000000) or Shipping (txcd_92010001). The platform's own code can ride along in the optional external_tax_code column, where Stripe stores it as metadata.

The code still matters when you supply the tax yourself. Stripe runs each imported line through its own tax engine to set the jurisdictions, rates, taxability and taxability reasons in its reports, and it keeps those classifications even when they conflict with the tax amount you supplied. Rows whose reporting amounts Stripe had to adjust to fit your tax show back_calculated in the itemized export's determination_method column.

Choosing a code without guessing

Stripe's list of product tax codes, and the Tax Codes API that returns the same list, are the complete set of active codes. Stripe is explicit that a code which looks plausible but isn't on that list is unsupported, and that neighboring codes are not interchangeable. Pick from the list by category name and description, and use a General code only when nothing more specific fits.

The classification itself is a tax decision. If a product sits between two categories and the difference changes whether it is taxed, that is a question for whoever advises you on sales tax, not something to settle by picking the cheaper code.