Restaurant VAT Categories: Get Menu Item Tax Codes Right at Upload

A VAT category is the tax treatment attached to a menu item, telling your system whether the item is standard-rated, zero-rated, or exempt. That single setting decides the VAT applied when you receive stock against a supplier invoice and when you sell the item. It also controls what tax posts to your accounts. Because the category travels with the item, you set it once and the system reuses it on every transaction. Getting it right at the item level is what keeps your recorded costs, your prices, and your tax return consistent across every branch you run.

Why they go wrong comes down to how the item master is built. Most groups inherit a long list of items, and much of it was entered by staff focused on getting products live rather than on tax rules. Codes get guessed, copied from a similar item, or left blank. A blank code then falls back to a default that may not fit the item. None of this is loud, so the errors sit quietly until a cost looks off or a VAT return does not reconcile. That is why an audit before upload catches far more than a spot check later.

How the rate is resolved follows a fixed order, so a line is never left guessing. The rate stated on the supplier invoice line is used first, which matters because suppliers are often inconsistent between deliveries. If the invoice gives no rate, the item's own tax code is applied. If that is missing too, your default receiving tax takes over, and the exempt rate is the last resort. This order means each received line carries the correct VAT automatically, even across messy supplier data. In Supy, that resolution runs on every delivery, so the recorded cost reaching your accounts is already right.

Should they carry VAT depends on who the stock is going to. Moving stock from your central kitchen to one of your own branches is an internal transfer, which usually goes out on a proforma document with no VAT, because no sale has happened. Selling the same item to an outside business is a tax invoice that does carry VAT. Treating every movement the same way is a common mistake that either adds VAT that should not be there or drops VAT that should. Setting up customer groups lets the same item follow different tax rules depending on the destination.

What happens is your recorded cost inflates on every affected invoice. VAT should be worked out from the subtotal and shown as a separate line, not added on top of a gross total that already includes it. When it is added to the total, you pay tax on tax in your own records. On a $2,400 invoice at an illustrative 10% rate, that is $240 of cost that was never real. Multiply that across a month of deliveries and your food cost percentage drifts upward for no operational reason. The fix is to base VAT on the subtotal at receiving.

How you check it is quicker than a full audit. Export or open your item master and sort it by tax code, which pushes every blank to the top where you can see it at a glance. Review each blank and each item where the code looks copied rather than chosen. Pay special attention to items that should be zero-rated or exempt, since those are the ones most often left on the standard default. Do this before you import, not after, because a wrong code fixed at upload never gets the chance to mis-cost a single transaction. It is a one-time setup task.

Which category applies depends on the item and your market's rules, so the safe path is to code deliberately rather than accept a default. Zero-rated items carry a zero percent rate but are still reportable, which is different from exempt items that sit outside VAT entirely. Standard-rated items take your market's normal rate. The important move is to never leave the field blank, because a blank falls back to whatever default is set and that is rarely correct for the item. When you are unsure of a specific item, confirm its treatment with your accountant, then set the code once so it holds.