When an EU supplier’s VAT number produces an invalid VIES response, a research record should describe the response and the unresolved question. It should not label the company fraudulent on that result alone. The European Commission’s explanation allows several reasons for a negative response and separately discusses unavailable data.

This article reads the official Your Europe page on 3 October 2026; the page lists a last-check date of 18 June 2026. It does not query an actual VAT number or advise how to tax a transaction.

Identify what the system is checking

VIES is described as a search engine drawing information from national VAT databases, rather than a standalone database containing every company attribute. An invalid response may involve a nonexistent number, missing activation for intra-EU transactions or an unfinished registration. The official guidance also notes that changes may not be reflected immediately.

This limits the inference a supplier researcher can make. A tax-registration query is not a factory inspection, a trade-credit assessment or confirmation that a person emailing a quotation controls the named business. Those questions require their own evidence.

Preserve the input before requesting an explanation

Record the country selection, number as entered, observation time and exact response category. Keep the supplier’s submitted number alongside the entered version. A transcription difference is a document issue worth resolving before starting a broader dispute. Do not alter a digit merely to produce a valid result.

Then preserve the supplier’s legal name and address from the quotation separately. If additional national confirmation is pursued, the official page describes confirming whether a particular name and address is associated with the number. That is a more specific request than asking someone to certify that a vendor is generally trustworthy.

Do not turn an outage into a negative check

An unavailable-data message belongs in a different field from an invalid response. Otherwise a temporary inability to retrieve information becomes a negative company attribute in an internal database. Keep an unresolved observation rather than a guessed result, and follow the appropriate official route when data remains unavailable.

A second observation should be logged as a new event rather than replacing the first without explanation. The history tells reviewers whether the issue was input correction, a change in recorded status or a retrieval problem. It also prevents an old screenshot being reused as if it were today’s result.

Route the real transaction question

Ask the supplier for the relevant national confirmation where necessary, and send the documents to the responsible tax or legal reviewer. A researcher can organise the evidence and explain the discrepancy; deciding tax treatment or accepting an invoice is outside this article.

A useful closing note says that a particular query returned a particular response on a particular date and that national confirmation remains outstanding. Our editorial judgement is that this narrow language makes the file easier to review and avoids both unjustified clearance and unjustified accusation. The official VIES guidance recommends retaining validation records. No actual supplier, certificate, payment destination or transaction has been verified here.