VAT on dropshipping and marketplaces
Review VAT on dropshipping, marketplace liability, supplier location and customer evidence before the VAT return.
VAT errors rarely start with the VAT return. They start when source data, tax codes and evidence do not agree. Dropshipping changes the evidence chain because the seller, supplier, marketplace and customer may all be in different places. This guide focuses on dropshipping and marketplace VAT evidence so the VAT file stays reviewable before the return is submitted.
For wider context, use VAT schemes and returns . If the topic affects a filing deadline, software choice or tax treatment, confirm the live position before acting. The workflow below is designed to keep the evidence in one place so the owner, bookkeeper and accountant can all review the same record.
Official point to verify
GOV.UK guidance explains that online marketplaces can be liable for VAT on certain goods sold to UK customers, so sellers need to separate marketplace VAT evidence from their own VAT decisions. Check the current wording in GOV.UK online marketplace VAT guidance before making a binding filing, software or tax decision.
What to control
| Area | Control | Why it matters |
|---|---|---|
| Sale route | Identify direct website sales versus marketplace sales | Marketplace liability can change who accounts for VAT |
| Goods location | Keep evidence of where goods are at sale | Location affects VAT treatment |
| Supplier invoice | Review supplier country and import evidence | Purchase VAT may not be straightforward |
| Settlement | Reconcile marketplace fees and refunds | Net payouts hide VAT detail |
Review routine
Review the VAT treatment before the return is locked. Match the source document, payout report or customs evidence to the VAT code, then keep a short explanation where judgement was used. If a transaction is unusual, flag it before the VAT submission rather than leaving it for the year-end file.
A useful review note should answer three questions: what source evidence was used, what judgement was applied, and who approved the treatment. Keep that note beside the transaction or period report rather than in a separate inbox.
Common mistakes
- Assuming the marketplace handles every VAT question
- Ignoring where goods are located
- Posting supplier charges from bank lines only
The best prevention is a short, repeated checklist. If a control is too complicated to run every month or quarter, it will probably fail when the deadline is close.
How ReAI helps
ReAI keeps VAT coding close to the transaction and makes exception review visible to the accountant. That helps stop repeated coding errors from flowing through every return. For hands-on help with setup, see Accounting Assistance for Small Businesses .
Summary
Treat VAT on dropshipping and marketplaces as a recurring accounting control, not a one-off admin task. Put the source data, review owner, exception list and submission evidence in the same system before the deadline arrives. That makes compliance work easier to check and much less dependent on memory.