# US sales tax: connect state nexus, inventory and marketplace settlements A marketplace can remit tax on an order while that same order remains relevant to the seller's registration analysis. An ERP implementation must preserve both facts. Importing the platform's net settlement as sales loses the information needed to evaluate exposure, explain revenue and avoid collecting the same tax twice. This guide designs a bounded control for a seller with direct web sales and marketplace sales into California and Texas. It does not determine obligations in every state, local jurisdiction or product category. Before using it, assign a state tax owner to approve the seller's locations, related entities, product taxability, exemptions and marketplace arrangements. A tax engine can calculate an amount only after those facts are correct. ## Build a location and channel record first For California, the CDTFA describes physical presence, including inventory, and an economic threshold exceeding $500,000 of combined tangible personal property sales for delivery into California in the preceding or current calendar year. Marketplace sales and specified related-person sales matter; its marketplace-only seller exception needs separate attention. [CDTFA marketplace guidance](https://cdtfa.ca.gov/industry/MPFAct.htm) Create a location register outside the order feed. Record owned premises, employees, third-party warehouses, marketplace fulfilment locations and dates stock first entered or left each location. Reconcile this register to fulfilment reports monthly. A shipping address on a sales invoice cannot reveal every warehouse in which the seller owned inventory before the sale. Give each order a channel identity, contractual seller identity, destination, gross selling amount, discounts, refunds, tax collected by the seller and tax collected by the facilitator. Retain the marketplace's statement of its collection responsibilities. "Marketplace" is a commercial label; the operating team still needs evidence about the particular platform and transaction. Texas describes its remote-seller safe harbour using total Texas revenue in the preceding twelve calendar months. Its marketplace guidance distinguishes facilitator collections from a seller's own sales, physical presence and permit responsibilities. Evaluate the Texas facts separately from California's calendar-year test. [Texas remote-seller guidance](https://comptroller.texas.gov/taxes/sales/remote-sellers-marketplace-faq.php) The practical output is two approved state decisions, each with its own measurement window and evidence. Do not share a single threshold counter merely because both selected states use a $500,000 figure in their guidance. ## Keep three balances in the ERP The sales ledger should explain the customer's gross purchase. The marketplace clearing account should explain what the provider owes the seller. The sales-tax liability should explain amounts the seller must remit. These balances are connected, but they have different counterparties and completion evidence. For each facilitated order, preserve the tax amount even where it never enters the seller's payable tax account. Put it in a reporting field or appropriately controlled clearing design approved by accounting. Otherwise a marketplace settlement can appear to have an unexplained deduction equal to the tax. For direct orders, route the seller's tax collections to the appropriate liability. Do not let an import reuse a facilitated-order tax flag for direct sales. Where a marketplace feed changes, a small sample of records should prove who collected tax, whose return includes it and how refunds are handled before the new feed posts automatically. Texas explains that a marketplace provider's collection responsibility does not eliminate every seller obligation, including situations involving direct sales. Use its seller/provider distinction when approving the channel mapping. [Texas marketplace providers and sellers](https://comptroller.texas.gov/taxes/sales/marketplace-providers-sellers.php) ## Worked example: revenue is larger than settlement cash The following numbers are synthetic. The seller has no related entities, exemptions, returns or other California presence for this example. Its current-calendar-year California tangible-goods sales are $180,000 direct and $400,000 through a qualifying facilitator. The $580,000 combined amount exceeds the selected California economic threshold. A seller that counted only its direct $180,000 would miss that result. For a separate Texas review, assume $100,000 direct and $300,000 facilitated Texas revenue in the preceding twelve calendar months, with no Texas inventory, employees or other physical presence. The $400,000 total is below the selected remote-seller threshold. This arithmetic does not decide a differently situated Texas business's permit requirement or create an exemption in another state. Now reconcile the California sales. Assume every transaction in this synthetic batch has an approved illustrative tax rate of 8%. This is not a California statewide rate; actual rates depend on the transaction. Assume the seller already holds the required registration and collection starts at the approved time. Ignore cost of goods sold, opening balances and remittances during the batch. Direct net sales are $180,000. The seller collects $14,400 tax and receives $194,400 from customers. Its posting records cash $194,400, revenue $180,000 and sales-tax liability $14,400. Facilitated net sales are $400,000. Customers pay the provider $432,000, including $32,000 tax. The provider remits the $32,000 under the assumed arrangement, charges a $8,000 fee and pays the seller $392,000. The seller records $400,000 revenue, $8,000 fee expense and $392,000 cash, with the customer tax separately traceable to the facilitator's collection evidence. Combined revenue is $580,000. Fee expense is $8,000, leaving a $572,000 contribution before the excluded costs. Cash is $586,400, which equals the $572,000 contribution plus the seller's $14,400 unpaid tax liability. Marketplace tax of $32,000 explains the provider's customer receipts; it is not a second seller liability in this example. The reconciliation therefore proves four different values: threshold sales $580,000, revenue $580,000, seller cash $586,400 and seller tax liability $14,400. A single "sales total" cannot substitute for all four. ## Recover from an incorrect channel mapping Suppose an import posts the facilitator's $32,000 tax into the seller's remittance liability. The ledger now overstates that liability by $32,000. Paying the resulting balance would duplicate the assumed facilitator remittance, while reducing revenue to make the bank reconciliation work would introduce another error. The controller should quarantine the affected batch, identify its original order and settlement IDs, and approve a correction that preserves gross revenue. The tax owner confirms responsibility using the facilitator contract and statement. The integration owner changes the mapping and replays the same records in a test copy. The reconciliation must show that the correction removes the duplicate liability without changing $400,000 facilitated net revenue or $392,000 settlement cash. If fulfilment reports reveal California stock before the economic threshold was crossed, reopen the exposure review from the actual physical-presence facts. Do not simply change the threshold date and assume historical obligations disappear. Keep tax exposure assessment and accounting correction as separate tracked actions. ## Assign close responsibilities Ecommerce operations owns complete order, refund, settlement and warehouse feeds. The tax owner owns the state decision and effective collection dates. Accounting owns clearing balances and liability reconciliation. The ERP owner owns state/channel tax logic and duplicate-import prevention. One controller signs off that these four evidence sets describe the same population. At each close, compare sales by destination and channel with nexus counters, confirm inventory-location changes, and age unexplained settlement differences. Escalate a new warehouse immediately instead of waiting for a year-end threshold report. Keep the evidence used for each state decision so that an auditor can reproduce the measurement window. ## Completion checklist - Approve a separate nexus and registration assessment for each selected state. - Include relevant marketplace sales in the correct threshold population and time window. - Reconcile fulfilment locations to the physical-presence register. - Identify the collector and remitter for each channel and transaction class. - Reconcile revenue, fees, customer tax, settlement cash and seller tax liabilities separately. - Test refunds, duplicate imports, direct sales and a newly discovered warehouse. - Assign owners and retain the signed state decision with the close evidence. Use the [state and marketplace reconciliation worksheet](#template). For the wider design, read [one company with multiple tax registrations](https://erplocalization.com/guides/one-company-multiple-vat-registrations/) and the site's [ERP localization acceptance tests](https://erplocalization.com/guides/erp-localization-acceptance-tests/). Sources checked 17 October 2026. This workflow is intentionally limited to selected California and Texas fact patterns; it does not establish a uniform US rule. ## Worksheet: US state and marketplace reconciliation worksheet Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment. Show the worksheet Use with the [US sales-tax guide](https://erplocalization.com/guides/us-sales-tax-inventory-marketplaces/). Complete a separate state decision, including the correct time window; no universal threshold is implied. ### State exposure decision - Seller, related persons, state and review date: - Offices, employees, warehouses, marketplace inventory and dates: - Relevant economic measure, period and source: - Direct and marketplace amounts included/excluded, with reasons: - Registration/collection decision, start date and tax owner: ### Order-to-settlement proof For each channel record customer net purchase, tax collected, collector/remitter, fees, refunds, clearing movements and cash. Preserve destination and order/settlement IDs. Rehearsal: direct sales180,000 plus illustrative8% tax 14,400 yield cash 194,400. Marketplace sales400,000 plus tax 32,000 yield customer receipts 432,000; provider remits32,000 and deducts fee8,000, paying392,000. Combined cash 586,400 equals contribution572,000 plus seller tax 14,400. ### Exceptions and approval - Unexplained inventory locations or missing transactions: - Duplicate tax liability or wrong channel classification: - Refund mapping and revised state exposure: - Accounting, ecommerce, tax and integration owner approval: Test a marketplace tax duplicate and a newly discovered warehouse. Confirm that correcting the remitter mapping preserves revenue. ## Related on this site - [Country pages](https://erplocalization.com/countries/): key facts with sources - [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support - [All guides](https://erplocalization.com/guides/) Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17. Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more). --- Canonical: https://erplocalization.com/guides/us-sales-tax-inventory-marketplaces/ · Last updated: 2026-10-17 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".