Marketplace Facilitator Tax With Stripe in QuickBooks
Marketplace-collected sales tax isn't yours, but the sales still count toward your threshold. How to handle it next to Stripe Tax and keep it out of...
Plenty of businesses that take payments through Stripe on their own website also sell through a marketplace such as Amazon, Etsy or eBay. Those two channels put two very different kinds of sales tax into one business. On your own site, you charge the tax, you hold it, and you owe it to the state. On the marketplace, in most states, the marketplace charges the tax and owes it to the state. It is not yours at any point.
The books have to keep those apart, and so does your sense of where you have to register. Stripe Tax only sees the first channel, and when you import the second, Stripe says plainly that it "can't differentiate between marketplace and non-marketplace sales." Meanwhile the states that matter most count your marketplace sales toward your threshold and still want them on your return, just not as taxable sales.
This guide covers marketplace-collected sales tax from the bookkeeper's side when Stripe Tax handles your own sales: what marketplace facilitator laws change, why your marketplace sales still count, what Stripe's threshold monitor can and can't see, how to keep marketplace tax out of the QuickBooks liability account your Stripe sales feed, and a worked example that carries one business across the Texas threshold. It is bookkeeping guidance, not tax advice. Whether you have to register in a given state is a question for that state and your accountant.
Start a free trial to bring the tax on your Stripe sales into QuickBooks automatically, so the marketplace channel is the only one you handle by hand.
What a marketplace facilitator law changes
A marketplace facilitator law moves the sales tax obligation on a marketplace sale from the seller to the marketplace. California's version is typical. The California Department of Tax and Fee Administration (CDTFA) describes it this way in its Marketplace Facilitator Act guide: "a marketplace facilitator is generally responsible for collecting, reporting, and paying the tax on retail sales made through their marketplace for delivery to California customers."
For the seller, the CDTFA is just as direct. If you sell through a marketplace whose operator is registered with the state, "you are no longer considered the retailer of your sales of tangible merchandise facilitated through a marketplace."
Texas reaches the same place with different words. The Texas Comptroller's remote seller and marketplace FAQ says "The marketplace providers are responsible for collecting and remitting tax on sales made through a marketplace."
Two practical points follow from both states' rules:
- The marketplace's tax is the marketplace's liability. It never becomes a debt you owe the state, so it has no business in a liability account in your books.
- The shift depends on the marketplace actually taking it on. California's relief applies where the facilitator "is registered or required to be registered" with the CDTFA. Texas expects a certification from the marketplace, and says "If the marketplace provider does not issue any type of certification, then you should collect sales and use tax until you receive a certification." Keep the certification or agreement on file.
Your marketplace sales still count toward the threshold
Here is the part that catches multichannel sellers. Handing the tax to the marketplace does not take the sales out of your own threshold math.
The Texas Comptroller answers the question head on. Asked whether a remote seller includes marketplace revenue in its safe harbor calculation, the answer is: "Yes. As of April 1, 2020, you must include all sales in the safe harbor calculation, including marketplace sales, even if the marketplace provider is collecting and remitting the sales tax." The safe harbor is $500,000 of Texas revenue over the previous 12 calendar months.
The Comptroller's own example is the whole story in two sentences. A remote seller makes $300,000 of Texas sales through its website and $300,000 through marketplaces that certify they are collecting the tax. "Because the combined total sales is $600,000, the remote seller is not covered by the safe harbor provision and is required to collect and remit tax for Texas sales made through its website."
California counts the same way. The CDTFA says that to decide whether you have an economic nexus, "you must include all sales of tangible merchandise for delivery in this state, including sales made on your own behalf and those of related persons, as well as your sales facilitated through a marketplace facilitator's marketplace." The California threshold is also $500,000, measured over the preceding or current calendar year.
So a seller whose own website sales sit comfortably under a state's threshold can still be over it once the marketplace is added. And the obligation that results is on the website sales, the ones flowing through Stripe.
What Stripe's threshold monitor can see
Stripe Tax's threshold monitoring is built to warn you about exactly this kind of obligation, but it works from a defined set of inputs. Stripe lists its assumptions, and three of them matter here:
- "We only monitor Stripe-processed sales or imported transactions."
- "We can't differentiate between marketplace and non-marketplace sales."
- Stripe says obligations "aren't monitored for your home US state or country," because the tool is for places where you have no physical presence.
Put those together and there are two ways to run it.
Without an import, the monitor undercounts. Your marketplace sales are invisible to it. In the Texas example above, the monitor would show $300,000 against a $500,000 threshold while the real figure is $600,000. Nothing is broken. Stripe is reporting on what it was given.
With an import, the count can be right, but the label is gone. Stripe's import tool lets you bring transactions from other platforms in by CSV, and imported transactions feed "obligations monitoring." For Texas and California, which count marketplace sales toward the threshold, that is what you want. But the import has no column that says the marketplace collected the tax. The only channel marker is provider (Stripe's own example value is amazon), and line_item.amount_tax is a required column on every row. Once the rows are in, Stripe treats them like any other sale for monitoring.
Stripe's own caveat applies either way: the monitor "highlights potential registration obligations, but it's up to you to confirm whether registration is actually required in each jurisdiction." For a seller with a marketplace channel, confirming means checking each state's rule on marketplace sales, not just reading the number on the screen. Our guide to Stripe Tax threshold monitoring and the QuickBooks work that starts when you register covers the rest of the monitor's assumptions.
Be careful importing marketplace sales into a filing period
Monitoring is one use of an import. Filing is another, and the two don't want the same thing.
If Stripe files your returns, its filing guide tells you to import transactions from another platform when you need them included in the filing period you're reviewing. That is the right move for sales where you collected the tax yourself on another channel, which is what our guide to importing off-Stripe sales into Stripe Tax is about.
Marketplace sales are the opposite case. The state wants them on your return, but not as sales you owe tax on:
- Texas: "Sales made through a marketplace are included in item one (Total Texas Sales) on the sales and use tax return, but excluded from item two (Taxable Sales) if the marketplace provider has certified it will collect and remit tax on your behalf."
- California: registered marketplace sellers "are required to continue to report your total sales on your sales and use tax returns, including those sales facilitated through a marketplace," and "may claim a deduction from sales or use tax as 'other'" for them.
Stripe's import format doesn't carry the fact that would put a marketplace sale on the right line. So before you import marketplace sales into any period Stripe is going to file, ask Stripe how those rows will be reported, and review the filing details before it goes out. If you file yourself, take the marketplace figures for your return from the marketplace's own tax report, not from Stripe's exports. And when you tie Stripe to QuickBooks, filter the itemized export's provider column to stripe so imported marketplace rows don't inflate Stripe's side. Our guide to reviewing Stripe's automated sales tax filing before it runs shows where that review happens each month.
Where each kind of tax belongs in QuickBooks
The QuickBooks side follows from one rule: only tax you owe goes in a liability account.
The Stripe channel. Acodei syncs the tax Stripe Tax calculated. On a United States QuickBooks company it uses the Tax Product method: the tax on each synced invoice or sales receipt is rolled into a single line on a non-inventory product tied to a liability account. Acodei's documentation sends you to Stripe's reports for the state-by-state breakdown and to that liability account to pay from. Every dollar in it is a dollar you collected and owe. Our guide to recording the sales tax Stripe collects in QuickBooks Online walks through the setup.
The marketplace channel. None of this channel's tax is yours, so none of it goes in that account or any other liability account. How it shows up depends on the marketplace. Depending on the platform, the tax either never appears in your payout data at all, or appears on the settlement report as tax collected alongside an equal amount withheld. Either way, the net effect on your books has to be zero:
- Record the sale at the price before tax to a separate income account, for example Marketplace Sales. Keeping it apart from your Stripe income makes both channels easy to tie out.
- Record the marketplace's fees as an expense.
- Record the payout to your bank as the net of the two.
- If the settlement shows tax collected and withheld, either leave both out or run both through a clearing account that ends every settlement at zero. Never post either one to the sales tax liability account.
If you key marketplace sales into QuickBooks as sales receipts rather than summary entries, make sure no tax is calculated on those lines. A sales receipt that adds tax to a marketplace sale creates a liability you don't owe.
A worked example: one business crosses the Texas threshold
A leather goods maker based in Oregon sells two ways: through its own website, using Stripe Checkout with Stripe Tax, and through a large marketplace that has certified it collects and remits Texas tax on the maker's sales. Oregon has no sales tax, so every sales tax obligation the business has is in another state.
The threshold. At the end of June, the maker's Texas sales over the previous 12 calendar months are $310,000 through the website and $240,000 through the marketplace. Stripe's monitor, with no import, shows $310,000, under the $500,000 safe harbor. Under the Comptroller's rule the figure is $550,000. The maker is over the threshold and has to register and collect Texas tax on website sales. The marketplace keeps collecting on marketplace sales.
After registration. With the registration added in Stripe Tax and collection turned on, October looks like this (all figures at an illustrative 8.25% combined rate):
- Website, through Stripe: $26,000 of taxable Texas sales, $2,145.00 of tax collected. Acodei syncs the sales and the tax product puts $2,145.00 into Sales Tax Payable.
- Marketplace: $19,500 of Texas sales. The marketplace collects $1,608.75 of tax and remits it. The bookkeeper records $19,500 in Marketplace Sales, the fees as an expense, and the payout. Sales Tax Payable doesn't move.
The tie-out. Sales Tax Payable holds $2,145.00 for October, and Stripe's report for the Texas registration shows $2,145.00. They match because only one channel feeds the account.
The return. Item one, Total Texas Sales: $26,000 + $19,500 = $45,500. Item two, Taxable Sales: $26,000. Tax due is on the website sales only. The marketplace's $1,608.75 appears nowhere on the maker's return and nowhere in its liability account.
Two ways this goes wrong. The same maker, in a month with a new assistant:
- Marketplace tax posted to the liability account. The assistant books the marketplace's $1,608.75 into Sales Tax Payable. The account now shows $3,753.75 against Stripe's $2,145.00. Worse, it looks like a debt, so someone eventually pays it. That is $1,608.75 the state already received from the marketplace, paid a second time.
- Marketplace sales recorded with tax included. The assistant books the marketplace orders at the buyer's total, $21,108.75, as income. Revenue is overstated by $1,608.75, the liability account looks fine, and the error only surfaces when someone compares income to the marketplace's sales report.
Both show up the same way: a number that no longer ties to its source. Sales Tax Payable has to tie to Stripe. Marketplace Sales has to tie to the marketplace's own report, before tax.
A monthly routine for a Stripe and marketplace business
- Pull the marketplace's tax report for the month and confirm the marketplace collected tax in every state you sold into.
- Check certifications. Keep each marketplace's certification or agreement on file. Texas asks you to keep marketplace sales records for at least four years.
- Record marketplace sales before tax in their own income account, with fees and payouts, and no tax lines.
- Tie Sales Tax Payable to Stripe for each registration, counting only rows where
providerisstripeif you import marketplace sales. The difference should be zero. - Add the marketplace's sales by state to Stripe's figures wherever you are watching a threshold, unless you import them for monitoring. Stripe's monitor without an import is looking at part of your sales.
- Report marketplace sales the way each state asks: in total sales and out of taxable sales in Texas, in total sales with an "other" deduction in California.
- Before any Stripe filing that includes imported marketplace sales, confirm how they will be reported, and review the filing details.
Frequently asked questions
Do I owe sales tax on my Amazon or Etsy sales if I also sell through Stripe?
In states with a marketplace facilitator law, the marketplace generally collects and remits the tax on sales made through it, provided it is registered or has certified that it will. Your Stripe sales are separate: if you are registered in a state, you collect and remit tax on the sales you make outside the marketplace.
Do marketplace sales count toward my economic nexus threshold?
In Texas and California, yes. Texas says all sales count toward the $500,000 safe harbor, "including marketplace sales, even if the marketplace provider is collecting and remitting the sales tax." California includes sales "facilitated through a marketplace facilitator's marketplace" in its $500,000 test. Check each state you sell into.
Does Stripe Tax know about my marketplace sales?
Only if you import them. Stripe's threshold monitoring covers Stripe-processed sales and imported transactions, and Stripe says it "can't differentiate between marketplace and non-marketplace sales." Without an import, marketplace sales are invisible to it.
Should marketplace-collected sales tax go in my sales tax liability account in QuickBooks?
No. The marketplace owes that tax, not you. Record marketplace sales before tax in their own income account, and keep the liability account for tax you collected yourself, so it keeps tying to Stripe.
How do I report marketplace sales on my sales tax return?
It depends on the state. Texas wants them in item one (Total Texas Sales) and out of item two (Taxable Sales). California wants them in total sales, with a deduction claimed as "other." Your accountant can confirm how each of your states handles it.
Where this leaves you
A Stripe seller with a marketplace channel runs two tax systems at once: one where you collect and owe, and one where the marketplace does. Keep the marketplace's tax out of your liability account, keep its sales in your threshold math, and report them the way each state asks. Your Stripe-fed liability account then ties to Stripe every month, and nothing the marketplace already paid gets paid twice.
Start a free trial and connect your Stripe account to QuickBooks Online.
Automate your Stripe to QuickBooks sync
Save hours every month. Acodei automatically syncs your Stripe transactions, invoices, and payouts to QuickBooks Online.
14-day free trial · card required · cancel anytime
How Acodei handles this in your stack
Stripe QuickBooks Integration
See how Acodei syncs Stripe payments, fees, refunds, invoices, and payouts into QuickBooks Online automatically.
Or go straight to a capability
Advanced Product Mapping
Map Stripe products to QuickBooks with rule-based logic on product ID, price ID, metadata, and account. Set rule priority and extend mapping to refunds and fees.
Automated Invoice Sync
Bring Stripe invoices into QuickBooks and auto-apply payments and credit memos, with numbering, invoice matching, and quantity tracking to cut double-entry.
Multi-Currency Mastery
Sync Stripe transactions across currencies with automatic exchange rate handling and currency-specific customer records. Our team enables multicurrency on request, and zero-decimal currencies such as JPY are not supported.
Class Mapping
Map Stripe products to QuickBooks classes for scalable categorization and multi-entity reporting. Class tracking requires QuickBooks Online Plus or Advanced.
Historical Data Import
Backfill historical Stripe data into QuickBooks by month range. Preview volume and cost before syncing so reporting starts from a complete baseline.
How to Connect Stripe to QuickBooks Online
Connect Stripe to QuickBooks Online in minutes. Acodei links both accounts with secure OAuth and syncs payments, fees, refunds, and payouts automatically.
Reconcile Stripe Payments in QuickBooks
Reconcile Stripe in QuickBooks Online automatically. Acodei splits out fees, matches payouts to deposits, and keeps every charge audit-ready.
Related articles
Acodei Journal
Stripe Tax and Use Tax: Recording It in QuickBooks
Acodei Content Team
Stripe Tax and Use Tax: Recording It in QuickBooks
10/2/2026
Acodei Journal
Stripe Tax Imports: Off-Stripe Sales Without Double Counting
Acodei Content Team
Stripe Tax Imports: Off-Stripe Sales Without Double Counting
10/2/2026
Acodei Journal
Stripe Automated Sales Tax Filing: Review It Before the 6th
Acodei Content Team
Stripe Automated Sales Tax Filing: Review It Before the 6th
10/1/2026
Get more operational finance guides like this one
We will only send high-value product and finance content.