VAT on mixed-rate bundles
Set controls for mixed-rate VAT bundles so invoices, product data and VAT return evidence agree.
VAT errors rarely start with the VAT return. They start when source data, tax codes and evidence do not agree. Bundles create VAT risk because one customer price can hide items with different VAT treatments. This guide focuses on mixed-rate bundle coding 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
VAT Notice 700/22 says VAT-registered businesses must keep VAT records digitally and file VAT returns using software that can communicate with HMRC through the API platform. Check the current wording in VAT Notice 700/22 on Making Tax Digital for VAT before making a binding filing, software or tax decision.
What to control
| Area | Control | Why it matters |
|---|---|---|
| Product data | Identify the VAT treatment of each component | The bundle rate may not be one simple code |
| Invoice layout | Show enough detail to support the VAT split | Evidence should match the calculation |
| System rules | Test product and bundle tax codes | Automation can apply the wrong single rate |
| Review | Check margin and VAT reports after changes | Product updates can change the VAT outcome |
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
- Using the highest or lowest VAT rate without review
- Changing product bundles without tax code testing
- Leaving the VAT split in an offline calculation
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 mixed-rate bundles 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.