VAT for marketplace seller reports
Turn marketplace seller reports into VAT-ready records for gross sales, fees, refunds, reserves and marketplace VAT.
VAT errors rarely start with the VAT return. They start when source data, tax codes and evidence do not agree. Marketplace reports are useful only when the accounting file keeps gross sales, fees and VAT roles separate. This guide focuses on marketplace seller report review 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 |
|---|---|---|
| Gross sales | Import order totals before deductions | VAT review starts with gross activity |
| Fees | Post marketplace fees separately | Fees are not reductions in sales |
| Tax collected | Identify marketplace-collected VAT where shown | The seller may need different postings |
| Returns | Reconcile refunds and chargebacks | Refund timing affects VAT and revenue |
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
- Posting bank payouts as sales
- Ignoring marketplace-collected tax columns
- Not reconciling returns to the original order
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 for marketplace seller reports 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.