A new product, copied from the last one
The bakery adds a new line: chocolate-coated biscuits for a coffee shop chain. Someone sets it up in the invoicing system by copying the nearest existing product, a plain biscuit, and changing the name and price. The VAT code comes along with the copy. Months later, the accountant's quarterly review turns up the question of whether the code is right.
Nobody made a decision. The code was inherited, the way many codes in the product list were.
Why VAT codes drift in bakery product lists
Bakeries sell a mix of products, and your accountant may treat some of them differently for VAT. Product lists in invoicing systems grow by copying, and the VAT code is just one field among many. Nobody reviews it product by product.
- Products are set up by copying a similar product.
- VAT codes are not reviewed when products change.
- Your accountant's decisions are in emails, not in the product list.
- The same product may be set up twice with different codes.
- Nobody checks codes until the quarterly return.
What it costs
The effort usually lands at the worst moment, when the return is due and the accountant needs answers quickly, and the person who set up the products two years ago cannot remember why a particular code was chosen.
Time with your accountant correcting codes and working out what to do about invoices already sent. Possible corrections to returns. Credit notes and reissued invoices for customers. And the worry that other products might be wrong too.
We do not advise on VAT. Which treatment applies to each product is for your accountant or tax adviser. We make sure the code they confirm is the one that is used.
Product records we build
- Your product list is brought in from Xero, QuickBooks, Sage or your ordering system, with the current VAT code on each product.
- A review list goes to your accountant, grouped by type of product, so they can confirm or change each code, with a note of their decision.
- Confirmed codes are held against each product with the date and who confirmed them, and pushed back to your invoicing system.
- New products cannot be invoiced until a VAT code has been confirmed. The setup form asks for one and flags it for your accountant if unsure.
- Any product whose description, recipe or category changes is flagged for a code check.
- A monthly check lists anything unusual: products with codes that differ from similar products, duplicates and products never confirmed.
| Check | What it catches |
|---|---|
| New product without a confirmed code | Blocked from invoicing until set |
| Product changed | Flagged for review |
| Similar products with different codes | Listed for your accountant |
| Duplicate products | Listed for merging |
What the bakery and the accountant get
A product list where every VAT code was confirmed by the person responsible, with a date. New products set up properly from the start. Fewer surprises at the quarterly return. And a much shorter conversation with your accountant, because the list is already sorted into what needs their eye.
The same product records can drive your price lists, labels and ordering page, so the product is described consistently everywhere.
When a customer queries an invoice line, the office can see which code the product carries, who confirmed it and when, and pass the question to the accountant with the full picture rather than a guess.
Could this be your product list?
- New products are set up by copying old ones.
- Your accountant has queried VAT codes on invoices.
- Nobody can say who decided each product's code.
- Some products appear twice in the invoicing system.
- Product changes do not prompt a code review.