Marketplace Facilitator Tax: How to Account for Sales Tax the Marketplace Collected
In July 2026, near the end of a call, a customer’s team asked whether SKU.io calculates tax or takes it from Shopify. I gave the true answer: the tax on each order is pulled in from the channel and shown on the order.
That answer was right and it missed the point. Where the tax number comes from is rarely the problem. Where it lands in the ledger is. On a marketplace order the tax is real money that passes through the settlement, and it belongs to the state, not to you. If it lands in your Sales Tax account, your books say you owe tax you will never pay. If it lands in revenue, your sales are too high.
This guide covers the accounting for tax a marketplace collects and pays for you: what the law does, the two correct ways to book it, the mistakes I see most, and how to check your own ledger in under an hour. It also covers two questions that ride in the same settlement: which date your revenue belongs to, and what currency your supplier bills are in. It is part of the ecommerce accounting standards, checks 32 to 34.
What marketplace facilitator tax is
A marketplace facilitator law makes the marketplace, not the seller, responsible for collecting sales tax on the sales it hosts and paying it to the state. The laws followed the Supreme Court’s 2018 decision in South Dakota v. Wayfair, which let states tax sellers with no physical presence. Missouri was the last state with a sales tax to adopt one, and its law took effect on January 1, 2023. Since then, every US state with a sales tax has one.
In practice that means Amazon, Walmart, eBay, Etsy, Temu, TikTok Shop and Faire collect sales tax from the buyer and pay it to the state for you, in every US state with a sales tax. The tax still shows up on your order and in your settlement report. It just never becomes yours.
Your own store is different. On Shopify, BigCommerce, WooCommerce or a wholesale portal, you are the seller of record. The tax you charge there is tax you collect, and you owe it to the state. There is one Shopify wrinkle: since January 1, 2025, Shopify’s help center says orders placed directly in the Shop app and on shop.com have their US sales tax collected, remitted and filed by the Shop channel, and that tax is deducted from your Shopify Payments payout. Orders on your own online store checkout are not covered. The Shopify post goes through each platform.
Whose liability is it
Two kinds of sales tax can pass through an ecommerce seller’s books, and they must never share an account:
| Tax you collect | Tax the marketplace collects | |
|---|---|---|
| Who charges it | You, at your checkout | The marketplace, at its checkout |
| Who pays the state | You | The marketplace |
| Where it belongs | A Sales Tax liability account, until you file | Nowhere that lasts. It should net to zero |
| What it does to revenue | Nothing | Nothing |
Neither one is revenue. The first is a debt you hold in trust until the return is filed. The second is not your debt at all.
Two caveats that are tax questions, not bookkeeping ones. Depending on the state and whether you are registered there, you may still have to file a return that reports your marketplace sales, even though no tax is due on them. And states differ on whether marketplace sales count toward your own economic nexus threshold. Both are state-by-state questions for your tax adviser. What follows is how to keep the ledger right whatever the answer.
Two correct ways to book it
Take one Amazon order for $40.00, with $3.20 of sales tax that Amazon collects and pays.
Method 1: leave the tax out of the sale. Post the invoice at $40.00, with no tax line at all. The settlement’s tax lines (the tax charged to the buyer and the same tax withheld by Amazon) are mapped to one account where they cancel. Your ledger never sees the $3.20 as a balance.
Method 2: book it gross, through a clearing account that nets to zero. Post the tax twice to a separate Marketplace Facilitator Tax account: once as collected by the marketplace, once as remitted by it.
| Account | Wrong (posted to Sales Tax) | Method 2 (clearing account) |
|---|---|---|
| Accounts Receivable | debit $43.20 | debit $40.00, what Amazon pays you |
| Sales | credit $40.00 | credit $40.00 |
| Sales Tax | credit $3.20 | nothing |
| Marketplace Facilitator Tax | nothing | credit $3.20 “Tax collected by Amazon” and debit $3.20 “Tax remitted by Amazon” |
Revenue is $40.00 under both methods. What changes is that Sales Tax no longer holds tax you don’t owe, and the receivable matches what the marketplace actually pays you. A refund posts the same pair with the signs reversed.
Both methods are correct. I prefer the second, and some accountants will disagree with me. The net method is fewer lines. The gross method leaves a trail: you can see in the ledger, per channel and per month, how much tax the marketplace collected, and you can test that it netted to zero. When a state asks what your marketplace sales and the tax on them were, that trail is the answer. When the account does not net to zero, it tells you a tax code is mapped wrong before the error grows for a year.
Whichever you pick, the test is the same. At month end the account that holds marketplace tax should be at zero, or within a dollar of it, for every channel.
The mistakes I see most
1. Marketplace tax posted to Sales Tax, like your own. This is the most common one. The order invoice credits Sales Tax $3.20, the same as a Shopify order would. Nobody ever pays it out, because the marketplace already did. The liability grows every month. It is also SKU.io’s default until you change it, so I can’t pretend it’s only other people’s problem.
2. The withheld line mapped to fees. The settlement shows the tax twice: charged to the buyer, then withheld. If the withheld line is mapped to Marketplace Fees, your fees are overstated by the whole tax amount and your profit is understated by the same figure. Combined with mistake 1, the two errors hide each other: the bank reconciles, and the P&L and balance sheet are both wrong.
3. The tax line mapped to revenue. If the tax charged to the buyer is mapped to Sales, revenue is overstated. Margins look better than they are, and every ratio built on revenue is off.
4. Two systems sending the same marketplace orders to your tax filing service. If your filing service is connected to Amazon directly and also receives the same orders from your inventory system, the orders arrive twice. A copy that arrives without the marketplace flag can read as tax you owe. Pick one source and flag marketplace orders as such. I wrote about the wholesale side of that problem when we connected a filing service.
5. Treating every Amazon marketplace the same. Amazon collects and pays US sales tax for you. On some of its other marketplaces, such as amazon.ca and amazon.com.mx, you collect and remit the tax yourself. That tax is yours, and it belongs in Sales Tax.
6. Forgetting refunds. A refund on a marketplace order reverses the tax as well. If refunds post the sale reversal and not the tax reversal, the clearing account drifts by the tax on every return.
How to check your own books
This takes under an hour with a ledger export and two settlement reports.
- Compare your Sales Tax balance with your returns. Find the Sales Tax liability balance at the last month end. Put it beside what your most recent returns said you owed and had not yet paid. If you only file for your own store, those two numbers should be close. If the balance is many times larger, marketplace tax is in it.
- Follow one settlement. Pick one Amazon or Walmart settlement. Find each tax line on the settlement report and follow it into the ledger. Note which account each one hit. On Walmart, look for the pair Sale: Product tax and Sale: Product tax withheld. They should land in the same account and cancel.
- Check the marketplace tax account for each month. If you have a clearing account, run it by month and by channel. Each month should end at zero, give or take rounding.
- Check fees as a share of sales. If marketplace fees on a channel jumped by roughly your average tax rate in the months you began selling there, a withheld tax line is probably mapped to fees.
- Check refunds. Pick a refunded marketplace order and see whether the tax reversed in the same account it was posted to.
- Check your non-US marketplaces. If you sell on amazon.ca or amazon.com.mx, confirm that tax lands in Sales Tax, not the clearing account.
A worked example: one year to repair
These numbers are invented. A seller sells on its own Shopify store and on Amazon.
- Shopify: $9,000 of tax collected during the year, $8,600 paid to the states, $400 owed for December. The Sales Tax balance should be $400.
- Amazon: $48,000 of tax collected and paid by Amazon. The order invoices credited Sales Tax. The settlement’s tax-withheld line was mapped to Marketplace Fees.
At year end the Sales Tax account shows $48,400. Marketplace fees are overstated by $48,000, so profit is understated by $48,000. The bank reconciles perfectly, which is why nobody noticed.
The repair is one journal per channel and month, so each month’s P&L is corrected in its own period:
| Account | Debit | Credit |
|---|---|---|
| Sales Tax | $48,000 (spread across 12 monthly journals) | |
| Marketplace Fees | $48,000 |
If the withheld line had gone to Sales instead, the credit would go to Sales. If the marketplace paid the tax to you inside each order payment, with no withheld line at all, the credit goes to the account those payments were deposited to. The rule is the same in each case: take the tax out of Sales Tax and put it back where the other half of it went.
Two things to watch. First, change the mapping and the treatment before you post the repair, or new orders keep refilling the account while you empty it. Second, if some of those months are already locked in your books, date the journals on the first open day after the lock and say in the memo which month each one belongs to. Don’t reopen a filed year to make the ledger tidy.
After the repair the Sales Tax balance is $400, which matches the December return.
Revenue timing: the other date in the settlement
A marketplace settlement also forces a second question: which month does a sale belong to? Most ecommerce sellers recognize revenue on the order date. When orders ship within a day or two, the difference between order date and ship date at month end is small.
It stops being small with pre-orders and long lead times. Say a pre-order brand has $500,000 of paid, unshipped orders at month end (invented numbers). For a brand that ships within two days, the same gap is a rounding error. For this one it is a month’s revenue.
Booked at the order date, that $500,000 is revenue with no cost of goods sold behind it yet. Margins look strong and the month is wrong. The fix is to recognize revenue when each order ships, and hold the cash received in the meantime as a liability. When shipping terms and title come into it, the FOB shipping point vs destination post covers which date to use.
Currency: the other number in the supplier bill
The third timing question is on the cost side. If a supplier bills you in yuan or euros and your books are in dollars, the bill can be posted two ways: converted to dollars on the day, or in the supplier’s own currency. Post it converted, and the payable in Xero or QuickBooks is a dollar figure that never moves. When you pay it at a different rate, the difference has nowhere to go, and it usually ends up in a rounding account or in COGS.
Post the bill in the supplier’s currency, and your accounting system holds what you really owe and books the realized exchange gain or loss when you pay. I said on a customer call in September 2025 that we would never post bills that way. I was wrong, and the multi-currency post explains why. If you match bills against purchase orders and receipts before you pay, the three-way match explainer covers how deposits and terms fit around it.
How SKU.io handles it
SKU.io sends its accounting to Xero or QuickBooks Online. Your accountant still owns the ledger and the returns. Here is what it does for each of the three questions, and where it stops.
Marketplace facilitator tax
By default SKU.io posts the tax on a marketplace order the same way as tax you collect yourself, to your Sales Tax account. That is mistake 1 above, and you switch it off by adopting the clearing treatment. Each marketplace order then posts its tax to a separate Marketplace Facilitator Tax account twice, once as collected and once as remitted, so it nets to zero and stays out of Sales Tax. Tax you collect yourself, on Shopify for example, still posts to Sales Tax. The treatment applies by order date from the day you adopt it. Months that already posted are fixed with a separate repair, which posts one balanced reclass journal per channel and month and never edits what was already posted. The month-end close has a check that the account nets to zero for each channel, within $1.00 by default. The steps are in the marketplace facilitator tax guide.
In my own business, Amazon’s US tax now goes to its own clearing account, and tax from amazon.ca, where we remit it ourselves, goes to Sales Tax. The guide covers that case: Amazon’s buyer tax codes are mapped to the clearing account, and tax from a marketplace where you remit it posts to Sales Tax automatically.
On Shopify and eBay payouts, the sale line can also be split into product, shipping, discount and tax, which sends the tax a buyer paid to your Sales Tax account, never to revenue (payout mappings guide). SKU.io does not file or pay sales tax. If you use Numeral, SKU.io sends it every sale and credit from every channel, marketplace orders flagged, and Numeral does the registering, filing and paying (Numeral guide).
Revenue timing
Revenue is recognized at the order date by default. For sellers who need revenue to wait for shipment, such as pre-orders, long lead times or ASC 606 reporting, an optional fulfillment basis moves revenue to Sales as each shipment goes out, in the same entry as its cost of goods sold. On payout channels it covers Amazon, eBay, Shopify and Walmart, not TikTok Shop or Temu. You preview it month by month on your own recent orders before you switch, and orders created before the switch date keep order-date recognition (fulfillment revenue guide). I’ve set my own business to switch on January 1, 2027.
Supplier bills in a foreign currency
An optional setting posts bills on foreign-currency purchase orders in the supplier’s currency at the bill-date rate, so Xero or QuickBooks books the realized exchange difference when you pay. While it is off, SKU.io says so on the purchase order, the invoice and the bill, and the close checklist carries a warning. QuickBooks Online needs Multicurrency switched on. Xero needs a plan that holds foreign-currency documents (foreign-currency bills guide).
What SKU.io does not do
It does not decide where you have nexus, register you, or file returns. That work belongs to your tax adviser or a filing service.
Who this is for
If you sell only on your own Shopify store, most of this page does not apply to you. Your tax is yours, it goes in Sales Tax, and your filing service can connect straight to Shopify. Under about $1M a year on one channel, a simpler inventory app such as Zoho Inventory or inFlow beside Xero or QuickBooks is likely a better fit than SKU.io.
This page is for the seller on two or more marketplaces plus their own store, where both kinds of tax move through the same ledger every day. That is where the Sales Tax balance quietly grows.
Related reading
- How to record marketplace facilitator tax in QuickBooks and Xero, the journal entries for both methods
- Is Shopify a marketplace facilitator? Amazon, Etsy, eBay, TikTok Shop and Walmart compared
- FOB shipping point vs destination, on when ecommerce revenue counts
- Multi-currency accounting for supplier bills, on realized exchange gains and losses
- How to track supplier deposits, payment terms and the three-way match
- Ecommerce accounting standards: 36 checks for a seller’s books
The accounting overview covers the rest of SKU.io’s accounting in one place. If you want to see the facilitator tax report on your own settlements, book a walkthrough.