How auditors treat marketplace-facilitated sales in a direct seller audit
The seller is often surprised that marketplace volume is still part of the audit at all. Statutorily, the marketplace may be the collector and remitter on facilitated transactions. Operationally, the auditor is still examining the seller’s returns, books, and supporting records. That means the seller still has to prove how facilitated sales were handled in its own reporting. [1][2][3]
In practice, the auditor usually tests three points:
- Whether marketplace sales were identified correctly in the seller’s records
- Whether the seller’s return reflected those sales correctly
- Whether the claimed marketplace treatment is supported by marketplace-source documentation
The audit is not reassigning the marketplace’s statutory responsibility to the seller by default. It is testing whether the seller’s records actually support the way the seller reported those transactions.
How auditors separate marketplace and direct-channel sales
The cleanest audit file starts with a channel tag at order level. Each transaction should already be identified as direct, marketplace-facilitated, or another distinct flow before the auditor ever asks for records.
If that split already exists, the seller can usually produce a by-state view showing:
- Direct-channel gross sales and tax collected by the seller
- Marketplace-facilitated gross sales and marketplace-collected tax
If the split does not exist, the seller has to reconstruct it during the audit. That is where costs rise. The auditor will typically expect the seller to prove the segregation rather than perform it on the seller’s behalf.
The opening request in a multi-channel audit usually asks for sales by state and period, calculation logs, filed returns, and marketplace settlement reports so the auditor can test that split independently. [4][5][6]
What documentation proves the marketplace collected and remitted
The strongest support is the marketplace settlement report or tax report for the relevant state and period. That report should show the facilitated gross sales and the marketplace-collected tax in a way that can be tied to the seller’s books and return.
The documentation stack usually works in three layers:
- Marketplace settlement reports. These are the primary evidence and should be retained outside the marketplace portal for each filed period.
- Marketplace statutory or help-center guidance. This is secondary support showing that the platform was operating as a marketplace facilitator under the applicable state framework. [1][2][3][7]
- The seller’s own return disclosure. The seller’s return should show the treatment used for marketplace-facilitated sales, deductions, or offsets where the form requires it.
If the settlement report is missing, the seller’s position becomes much harder to defend even if the marketplace actually collected the tax.
Why FBA inventory can still create direct-channel exposure
Marketplace collection and nexus are related, but they are not the same issue.
If inventory is stored in a state through Amazon FBA or another fulfillment arrangement, that inventory can create physical nexus for the seller. When that happens, the state may still examine the seller’s direct-channel sales into that state even if the marketplace handled Amazon-channel tax correctly. [1][2][3][8][9]
That is why a seller can be correct on the marketplace side and still have exposure on the direct side. The marketplace covered facilitated transactions. It did not cover the seller’s direct-channel obligation.
Pennsylvania’s Online Merchants Guild v. Hassell decision is often raised in these discussions, but it is a Pennsylvania state-court decision and does not broadly eliminate FBA-based nexus risk in other states. [10]
The reconciliation the auditor usually runs
In a multi-channel audit, the main test is usually a three-way reconciliation by state and period.
Tie 1: marketplace gross to reported gross
The auditor compares marketplace gross sales from the marketplace report to the seller’s reported gross sales and channel breakout.
Tie 2: marketplace-collected tax to the seller’s marketplace treatment on the return
The auditor checks whether the marketplace tax shown in the marketplace report matches the deduction, offset, or reporting treatment reflected on the seller’s return.
Tie 3: direct-channel gross and tax to the seller’s own calculation and remittance records
The auditor separately tests the direct side using the seller’s calculation logs, return, and payment support.
The strongest workpaper is one page per state per period showing those three ties, with the source reports attached behind it.
What an audit-ready multi-channel operating model looks like
The brands that handle this well usually have three things in place before the audit begins.
- Channel flags at order capture. Direct and marketplace orders are already separated in the system of record.
- Archived marketplace reports. Marketplace tax and settlement reports are saved outside the portal on a recurring schedule.
- Archived inventory and nexus support. FBA and other inventory-location records are retained so the business can support or challenge nexus start dates later.
That is the right place to reference TaxCloud or another provider: as infrastructure that can help preserve channel tags, calculation logs, and filing support across periods. The legal posture still depends on the seller’s records and state-specific rules.