Wine Trade Duty Calculation Software, Effective-Dated to HMRC's Own Bands

Built on HMRC's Own Duty Bands, Not a Rate Someone Remembered

Excise duty on wine is calculated per litre of pure alcohol, using the wine's own ABV and the volume of the movement, against a set of bands rather than one flat rate — not looked up by hand and not typed from memory. HMRC publishes the current bands at gov.uk/guidance/alcohol-duty-rates, and they are revised periodically. Bacchus ERP holds them as effective-dated rows rather than a single current figure, so a movement calculated today uses whichever rate was actually in force on that day. Most still and fortified wine sits in the band covering roughly 8.5% to 22% ABV, and that band's rate is meaningfully different from the ones either side of it — a spreadsheet with a stale figure in the wrong band does not fail loudly, it just quietly overcharges or undercharges every case that passes through it. That effective-dating matters most for a case that's sat in bond for years and is only withdrawn now, and what it means at audit time is covered in full in our guide to duty and VAT on wine out of bond.

A Live, Read-Only Preview Before Anything Posts

Because a duty and VAT figure has real cashflow consequences, on both sides of a sale, it helps to see the number before committing to the movement. Bacchus ERP exposes a preview calculator, explicitly read-only, that computes the duty and VAT figure for a wine without posting anything to the ledger — useful on a large case, an unusual ABV, or a movement straddling a rate change. You don't have to take that on trust: our own leak calculator runs on the same duty table and shows, from numbers you type in yourself, what a gap in your own rate table could be costing you annually.

Never Charged Twice on the Same Stock

Once duty has already been settled at an earlier withdrawal — stock that moved to duty-paid status and is later resold, for example — it must not be recalculated and charged again. The engine takes an explicit fee-only path for stock that is already duty paid, so a later movement of the same units doesn't silently re-trigger the duty calculation a second time.

Calculated Where the Stock Already Lives, Not in a Second System

The duty and VAT figure isn't produced by a separate calculator that someone then re-keys into an invoice. Because the same platform already knows the wine's ABV, the movement's volume, and the unit's bond status, duty and whichever VAT scheme applies are raised automatically on the withdrawal invoice the moment a dispatch out of bond is recorded — not before, since nothing is due while stock stays in bond. For the full standard-scheme-vs-margin-scheme picture, including how each is actually worked out, see our guide to duty and VAT on wine out of bond.

Not a Generic ERP's Bolted-On Duty Field

A generic ERP or accounting package has no concept of a duty band, a bond status, or a duty point at all — duty calculation gets handled outside it, in a spreadsheet, and re-keyed back in. Bacchus ERP's engine sits on top of the same bonded warehouse stock management record that already tracks bond status and ABV, and posts straight into the same wine trade ledger everything else on the sale posts to. There is no second system for duty and VAT to drift out of sync with the first.