Glossary

QuickBooks Tax Code

A QuickBooks tax code is the label attached to a line item that tells QuickBooks which sales tax rate applies to it, which agency the tax accrues to, and how it should appear on your tax reports.

Also called: QBO tax code, sales tax code, QuickBooks tax rate, group tax rate, combo tax rate

Start a free trial View Pricing

Definition

Tax has to land on something. In QuickBooks Online, that something is a tax code attached to a line item, and it is the object every Stripe-to-QuickBooks tax setup either succeeds or fails at.

The vocabulary is worth pinning down, because QuickBooks uses three related words for three different things. A **rate** is a percentage owed to a particular agency. A **tax code** is the classification you attach to a line, which resolves to one or more rates. A **combined rate**, called a group rate in some regions, bundles rates you charge at the same time so a single selection on the transaction produces several tracked amounts.

Intuit describes that last one directly: a combined rate groups "individual tax rates that you charge at the same time," and while you select one rate on the sale, "each rate is still tracked separately" for reporting. That matters for anywhere that stacks taxes, like GST plus PST in Canada.

The part that surprises people is that what you can do with tax codes depends heavily on which country your QuickBooks company is registered in. US and non-US QuickBooks behave differently enough that the same integration has to take two different routes.

Key points

+A tax code is what attaches tax to a line item; a rate is the percentage behind it.
+Combined or group rates bundle several rates into one selection while still tracking each separately.
+US QuickBooks defaults to automated sales tax, which calculates from the transaction location.
+QuickBooks Online’s US Sales Tax Center does not allow third-party creation of official tax rates.
+Non-US QuickBooks companies can map to real tax codes such as VAT 20 percent or GST 5 percent.
+QuickBooks requires non-US companies to carry tax on every line item.
+Default product and fee tax rates are usually set to Exempt so only mapped rates apply.

Tax code, tax rate, combined rate

These three are used loosely in conversation and mean specific things in the product.

A **tax rate** is a single percentage tied to a single agency. It is the thing that eventually produces a number on a return.

A **tax code** is what you attach to a line item. It is the classification, and it is what determines whether a given line is taxed at all, taxed at a standard rate, or exempt. Exempt is a tax code too, which is easy to forget and important when you are configuring defaults.

A **combined rate**, or group rate, exists because real jurisdictions stack taxes. Intuit’s guidance is to use one when you charge several rates at the same time: you pick a single combined rate on the transaction, and QuickBooks keeps the components separate underneath for reporting. In non-US regions the same idea appears as combining existing tax codes into a single combo rate.

Intuit also names when a custom rate is the right tool rather than the automated calculation: when "QuickBooks doesn’t have the special rate you need, such as meals, lodging, or excise tax rates," when you sell internationally and want those sales tracked separately, or when you are in a state that allows a single flat rate instead of exact location-based rates.

The US restriction that shapes every Stripe setup

This is the single most consequential fact on this page, and it is a QuickBooks restriction rather than anything to do with your integration.

QuickBooks Online’s US Sales Tax Center does not allow third-party creation of official QBO tax rates. No external application can reach in and create the rate objects that the US automated sales tax module uses. That is true for every integration on the market, not just one of them.

So the obvious design, where each tax rate in your payment processor maps to a matching tax rate in QuickBooks, is largely unavailable to US filers. What works instead is aggregation: the tax amount gets carried into QuickBooks as a line on a product mapped to a liability account, your liability accrues in one visible place, and you file from your processor’s own tax reports rather than from the QuickBooks tax module.

That is a legitimate way to keep books. It just means US companies should not expect the QuickBooks sales tax reports to be the system of record for tax collected through Stripe. The liability account is what they should be reconciling.

Why non-US QuickBooks is a different problem

Outside the US, QuickBooks exposes real tax codes that can be created and mapped, so VAT 20 percent or GST 5 percent can be attached to a line and flow through QuickBooks’ own tax module. That is the clean version of the workflow, and it is why non-US setups can use QuickBooks tax reporting directly.

There is a constraint that comes with it. QuickBooks requires non-US companies to have tax on every line item, with no line left blank. In practice this means every line needs a code, including the ones that are not really taxable, which is what Exempt is for.

This is also where combined rates earn their keep. A Canadian sale carrying both GST and PST needs both to reach QuickBooks and to stay individually reportable, which a group tax code does and two separate line-level guesses do not.

How Stripe tax rates reach a QuickBooks tax code

Acodei does not calculate tax. It reads the tax Stripe already calculated and decides which QuickBooks object it lands on, which is configured under Stripe Tax in the Account Mapping section of the dashboard.

**Tax Product** is the aggregation route, and the one most US companies end up on for the reason above. You create a non-inventory product in QuickBooks mapped to a liability account, and Stripe tax amounts roll into that single line on your QuickBooks invoices and receipts.

**QuickBooks Tax Rate (Advanced)** is the mapping route for non-US companies that want QuickBooks’ tax module doing the work. Acodei pulls the Stripe tax rate IDs available to it and you map each one to the corresponding QuickBooks tax code. Each product line then syncs with the right code attached.

Where a single Stripe line carries more than one rate, GST plus PST being the standard example, Acodei detects that more than one rate applies and lets you map the combination to a QuickBooks group tax code, so the total tax in QuickBooks matches Stripe exactly rather than landing a rounding step away from it.

A third route exists for non-US companies that do not use Stripe Tax at all but still need tax on every line for QuickBooks reporting. Admin QBO Tax Mapping applies a chosen rate after the fact, with separate settings for product tax and fee tax. Because QuickBooks requires tax on every line for non-US companies, this is enabled automatically for non-US accounts connecting to Acodei, and it attempts to select the Exempt rate. Advanced Tax Mapping overrides those settings where both are configured.

Outside those routes, tax tracking from Stripe to QuickBooks is not possible. Either Stripe Tax is enabled so rates and amounts can be retrieved, or tax is applied in QuickBooks after the fact.

Three operational details worth knowing. Default Product Tax Rate and Default Fee Tax Rate are normally set to Exempt so that only your explicitly mapped rates apply. On daily summaries, lines are split by product and tax rate rather than aggregated, so a day with several rates produces several lines. And if a Stripe tax rate has been archived but still appears on older invoices, you may need to add its `txr_` ID manually for it to map onto a code.

Want to see this on your own Stripe data?

Start a free trial

Frequently asked questions

What is a tax code in QuickBooks Online?

It is the classification attached to a line item that tells QuickBooks which sales tax rate applies to that line, which agency the tax accrues to, and how it appears on tax reports. Exempt is a tax code as well, which is what you use for lines that should not be taxed.

What is the difference between a tax code and a tax rate?

A rate is a single percentage owed to a single agency. A code is what you attach to a line item, and it resolves to one or more rates. A combined or group rate sits between them, bundling several rates you charge at the same time into one selection while keeping each component tracked separately for reporting.

Can an integration create sales tax rates in US QuickBooks?

No. QuickBooks Online’s US Sales Tax Center does not allow third-party creation of official QBO tax rates. That restriction applies to any external application, so US companies generally aggregate Stripe tax into a product mapped to a liability account instead of mapping rate to rate.

How do Stripe tax rates map to QuickBooks tax codes?

Through Advanced Tax Mapping, which is the route for non-US QuickBooks companies. Acodei pulls the Stripe tax rate IDs available to it and you map each to the matching QuickBooks tax code, so each product line syncs with the correct code attached.

What happens when one Stripe line has two tax rates on it?

Acodei detects that more than one rate applies to the line and lets you map that combination to a QuickBooks group tax code. The point of doing it that way is that the total tax recorded in QuickBooks matches what Stripe calculated exactly.

Why does QuickBooks want a tax code on every line?

That requirement applies to non-US QuickBooks companies, which must carry tax on every line item. It is the reason Exempt gets used so heavily, and the reason Acodei enables Admin QBO Tax Mapping automatically for non-US accounts and tries to select the Exempt rate when it does.

A Stripe tax rate is archived and will not map. What now?

Archived Stripe tax rates can still appear on older invoices. When that happens you may need to add the `txr_` ID manually in Acodei so it can be mapped onto a QuickBooks tax code.

What customers say about running Stripe through Acodei

★★★★★

“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”

RyanOwner at Indie Music Academy