What a tax advisor should request when onboarding a multichannel online seller

The first request should be a complete list of the seller’s active sales channels, not just the newest one. Shopify’s admin can be used to manage products, orders, and other operations across multiple sales channels, so onboarding should begin with an inventory of every channel that may affect revenue, tax, or reconciliation.

For a seller who has just added another channel, the practical question is simple: which systems are now part of the accounting flow? The answer should include storefronts, marketplace accounts, and any connected payment or reporting source the finance team uses for monthly close.

The next request is about access, not data. Shopify says user roles can be granted access to reports, and users with the Reports permission can view and create reports. That makes reporting access a basic onboarding item: the tax advisor needs to know who can open the reports now, and whether that access will still work once another channel is added.

Shopify also says report access cannot be limited to only certain reports. In practice, that means a seller may need to grant broader reporting access than expected rather than trying to carve out a narrow set of files for the advisor.

If the advisor needs to review sales by channel inside finance reports, Shopify notes that users with Reports permission may also need View products permission to filter by sales channel. When onboarding covers a new channel, that extra permission becomes a useful checkpoint instead of a surprise after the first close.

After access comes report selection. Shopify says its tax reports are available to help file and remit taxes or provide information to a tax accountant, so the handoff should specify which tax-report source of truth the advisor will use each month.

Shopify also says the US sales tax report and the Total sales by order report can be exported as CSV and include tax-relevant fields. For a multichannel seller, those are useful candidates for recurring documentation because they provide structured data that can be reviewed alongside channel-specific reports.

The point is not to rely on every report available in the system. It is to agree in advance on the few reports that will be used regularly, so month-end work does not depend on someone remembering which screen contains the tax detail.

A recurring handoff works better when the export format is fixed. Shopify reports can be downloaded in CSV, XML, JSONL, or Parquet, so an onboarding checklist can state one format for monthly exports instead of letting each team member choose differently.

If PayPal is part of the seller’s channel mix, PayPal balance reports are available in CSV only. That means the standard should be simple: one intake format for the payment-side report and one agreed format for any Shopify report exports used in close. Consistency matters because it reduces the need to re-map files each month.

When Amazon data is part of the onboarding, the Reports API is intended to retrieve and manage reports for a selling business, and Amazon says it regularly adds fields and values. In that case, the report definitions should be documented alongside the export settings so the advisor knows what the file is supposed to contain, not just how it was downloaded.

For a finance lead coordinating with a tax advisor, the useful output is a short control sheet: active channels, who has report access, which permissions are required, which tax reports will be used, and which export format each source will produce. That list should be reviewed again whenever the seller adds a channel, because a new channel can change both the reporting scope and the permissions needed to see it.

Amazon’s Reports API documentation also notes that specific roles are needed for report operations, including finance and accounting. That reinforces a simple onboarding question for any multichannel seller: who owns report access internally, and who is responsible for keeping the advisor’s view complete when systems change? If the answer is unclear, the month-end file set is more likely to drift over time.

A practical checklist does not need to be long. It only needs to make the reporting path visible from source system to tax handoff. This article provides general information and is not tax or legal advice.