Master data: the boring thing that decides everything
One wrong customer record can stop an e invoice, confuse a VAT return and travel into an audit file. Why master data is the quiet hero of digital VAT.

Nobody ever threw a party for master data.
It has no launch date. It never gets a go live. Nobody posts a photo of a beautifully maintained customer record on LinkedIn.
And yet, more and more, it decides whether everything else works.
One record, three problems
Imagine a customer in Belgium. The VAT number in Oracle has a typo. A few years ago that was a small annoyance: the invoice went out as a PDF, the customer paid, and the VAT return needed a manual check.
Today the same typo does a lot more:
- The electronic invoice cannot be delivered, because the customer cannot be found on the Peppol network under that identifier.
- The VAT return or EC Sales List shows a number that does not match, and someone has to explain it.
- The audit file carries the error along for whoever looks at it next, including the tax authority.
One record. Three problems. Probably discovered by three different people.
Addresses are not just for the post anymore
Electronic invoicing added a new kind of address. Next to the street and the VAT number, many customers now need a correct electronic address on a network such as Peppol.
Belgium has required structured B2B e invoices since January 2026. In Norway, from January 2027, suppliers must send e invoices to business customers who can receive them, which turns the national register of electronic addresses into part of everyday invoicing. Germany follows with its own issuing obligation from 2027.
If that address is missing or outdated, the invoice does not arrive. It does not matter how good the rest of the process is.
Small fields, big consequences
The fields that matter for VAT are surprisingly few:
🧩 Legal name and country
🧩 VAT registration number, validated where possible
🧩 Electronic address and scheme for e Invoicing
🧩 The tax profile that drives the VAT treatment
Get these right in Oracle, keep them right, and a lot of downstream problems simply never happen.
Treat it like a product
The organisations that do this well treat master data as a product with an owner, not as a side job. Clear rules for creating a new customer. Validation at the moment of entry, not at the VAT deadline. A regular check of the records that matter most.
And when something is wrong, they fix it in Oracle, so every report built on it improves at once. That is also where itax4apps helps: by showing which differences and transactions trace back to the same root cause.
The quiet hero
Master data will never get a party. But it may well be the most underrated part of your compliance programme.
Next week: Germany is 38 days away. Time to agree who decides what.