One Wrong Digit.

The Digit

A new customer registers. Somewhere in the form, the VAT identification number is entered as DE 123 465 789. The correct number is DE 123 456 789. Two digits have changed places.

Side by side, the difference is easy to miss. Reading only one of them — which is what actually happens — there is nothing to notice at all. Nobody is being careless here. The form simply has no opinion about what a valid VAT ID looks like.

Where It Travels

Nothing stops it, so it moves:

By the fourth step, someone has to work out which documents carry the wrong number, which of them have been sent, which have been posted and what has to be reissued. The cost is not the typo. The cost is the distance between the point where it entered and the point where it surfaced.

Not Only Rework

For intra-Community supplies there is a second consequence, and it is the expensive one. Since the EU-wide VAT quick fixes took effect on 1 January 2020, a valid VAT identification number issued to the customer by another member state is a substantive condition for the exemption — not a formal reporting duty that can be tidied up afterwards. The basis is § 6a (1) sentence 1 together with § 4 no. 1 (b) of the German VAT Act, implemented in the Federal Ministry of Finance circular of 9 October 2020.

In plain terms: if the number does not hold, the exemption can fall away, and the VAT can be assessed after the fact — against the supplier, who by then has issued an invoice without it. Somewhere around that point the transposed digit stops being a question of tidiness.

How it plays out in a given case belongs with your tax adviser, and nothing here is tax advice. The process point stands on its own: a field carrying this much weight should not be able to pass through unchecked.

Where It Stops

The check itself is not difficult. VIES, the European Commission's VAT information exchange system, answers whether a number is valid. The question was never whether such a check exists. The question is where it sits.

In a process model it sits at a defined step, and the steps around it are defined too:

Every one of those steps is recorded — not because an audit trail is a feature worth advertising, but because the alternative is reconstructing six months later who entered what, and when.

What This Is Not

It would be easy to describe this as AI reading the form more carefully. That is not the claim.

An agent without context would be doing exactly what the person did: looking at a string of digits with no idea what the field means, what makes it valid or what happens downstream if it is wrong. Context is what turns it into a check. The model states that this field is a VAT ID, that it is verified against VIES at this step, that a mismatch halts the case and that this role handles the query.

And because the rule lives in the model, it changes without code. If the check needs to move earlier, or if non-EU customers need a different one, that is a change to the model — not a release.

Which source of error would you remove first in customer registration?