Table of Content
1. What is product master data?
Before looking at why product master data matters so much for VAT, it’s worth being clear on what the term actually covers.
Master data is the core information about a business object, a product, a customer, or a supplier, that stays valid over a long period and gets reused across many processes rather than recorded fresh each time. A GTIN or a material description doesn’t change from one order to the next; it stays the same for as long as the product exists.
Master data typically falls into a few areas:
| Area | Examples |
|---|---|
| Product master data | Product name, SKU, GTIN, category, material, weight, dimensions, tariff code, tax classification |
| Customer master data | Name, address, customer group, payment details |
| Supplier master data | Supplier details, terms, contract information |
| Financial master data | Chart of accounts, account numbers, currency |
Two other things matter for VAT that aren’t master data at all. Tax logic is the rule set built into the system, deciding which rate applies to which country and which type of goods, a single rule applied across many products at once. The delivery country of a specific order, meanwhile, changes with every transaction and counts as transactional data rather than master data.
So an ERP system relies on three things when calculating VAT: the tax logic as the rulebook, the delivery country as a transactional detail, and product master data as the input that tells the system which tax category a given product belongs to. The system can only work with what it’s given, if the product master data is wrong or out of date, even flawless tax logic will still produce the wrong result.
2. Why product master data affects VAT
Tax logic and country-specific rates are usually set up correctly and maintained centrally. The real risk sits in the input value the system gets for a specific product, that is, in the product master data. This becomes especially clear with products that look similar on the surface: small differences in composition, use, or category can be enough to trigger a different tax rate.
Take an online retailer selling food supplements both as capsules and as a drinkable product, say, a shake. Both contain the same nutrients and look, to the customer, like the same product line. For German VAT purposes, though, they’re treated quite differently: capsules qualify for the reduced 7% rate, while drinkable supplements are taxed at the full 19%, ever since a ruling by the Lower Saxony Fiscal Court classified them as a beverage rather than a food product.¹
If the drinkable version gets filed under the same category as the capsules in the ERP system, it will pick up the wrong, lower rate. The tax logic hasn’t failed here, it’s simply working with bad input.
Which is exactly why solid product master data is the foundation any reliable VAT calculation depends on.
3. Errors at initial setup
Errors in tax logic and errors in product master data differ mainly in how visible they are.
Bad tax logic tends to hit entire product groups at once. A misconfigured rule creates a repeating pattern, and repeating patterns are the kind of thing audits catch quickly.
Master data errors don’t work that way. As the supplement example shows, they show up one product at a time, with no pattern to spot. A single item can be misclassified while thousands of others are handled correctly, which is exactly why these errors tend to go unnoticed for so long.
There’s also a structural reason behind this. Product master data usually isn’t owned by the tax department, it sits with product management, procurement, or the e-commerce team. Those teams know the products inside out, but they don’t always have the tax knowledge to spot when a classification is wrong.
4. Errors from later legal changes
Getting the setup right isn’t the whole story, either. Even correctly maintained product master data can go stale over time, with nothing about the product itself changing at all. VAT rules shift regularly, and not just through headline-grabbing national rate changes. Just as often, it’s the classification of a specific product category that shifts underneath a rate that hasn’t changed, through a new court ruling or a revised administrative interpretation.
Austria is a recent case in point: on 1 July 2026, a new, sharply reduced VAT rate of 4.9% took effect there for a defined list of staple foods, including milk, butter, and eggs, which had previously carried the reduced rate of 10%.² Companies managing their own product master data had to add the new rate by hand, and where that update didn’t happen in time, products were taxed incorrectly overnight without anyone touching the product itself. Only the law had moved, and that’s precisely the kind of change internal master data systems are prone to miss.
5. Why some companies give up on individual classification
Faced with complex tax rules, large catalogs, and a steady stream of new requirements, some companies take a shortcut: they stop classifying products individually and simply apply the standard rate across the board.
That cuts the maintenance burden, but it comes at a cost. Products that would actually qualify for a reduced rate end up overtaxed, hurting margins. Go the other way, misclassifying products under a reduced rate they don’t actually qualify for, and the result is underpayment, with real exposure if it surfaces in an audit.
Across a large catalogue, either mistake compounds fast.
6. How companies can avoid these errors
Reliable VAT calculation starts with reliable data.
Rather than maintaining tax-relevant product information by hand across ERP systems and online stores, many companies now rely on a central solution for VAT classification instead.
Our VAT classification system lets companies classify product data automatically and pull the correct VAT rate for any given market. It connects product information directly to tax requirements and keeps every connected system supplied with current tax data, a single, central source of tax truth for the whole business.
The result: less manual upkeep, no more conflicting data across systems, and products that are always taxed at the correct rate.
Curious how much revenue might be tied up in misclassified tax rates? Contact us or try our product for free.
¹ Lower Saxony Fiscal Court, ruling dated 1 September 2022, Case No. 5 K 70/20.
² See Austrian Federal Ministry of Finance, VAT reduction on selected foodstuffs; new Section 10(1a) of the Austrian VAT Act (BGBl. I No. 37/2026).
