Why Entering a Tax Number Does Not Verify Its Registration

Entering a seller tax number records the text you supplied. It does not establish that the number exists, belongs to the named supplier or is appropriate for the transaction. The current EInvoiceCreator does not contact tax registries or VIES, and its field checks should not be described as identifier verification.

Keep three questions separate: what value was entered, what an external service checked, and what the transaction requires. The seller-details workflow uses confirmed information as input. It does not turn the act of typing a plausible number into evidence of registration or a decision about tax treatment.

Understand what the form knows

An application can check that a required field contains text or that a value matches a particular pattern. Even a detailed pattern check cannot establish every registration fact. A number can have the right length and prefix while belonging to another entity, being outdated or being unsuitable for a particular purpose.

In the current creator, the seller tax-ID field is part of the application record. It is not a live lookup, and the form does not confirm an association with the entered seller name or address. A passed field-check result must therefore be read in the limited context of the checks the application performs.

Do not type a fabricated identifier merely to make a document look finished. If the value is unknown, consult the appropriate source and retain a draft while the question is resolved. A visibly unresolved fact is safer than an invented value presented as confirmed business information.

Choose an appropriate external check

Use the official service relevant to the identifier and question. Your Europe describes VIES as a tool for checking relevant EU cross-border VAT registration information, retrieving data from national systems. That scope is narrower than a universal check of every business identity or tax obligation.

Its guidance explains that an invalid response can reflect different registration circumstances and that database updates may not appear immediately. Follow the official guidance or contact the relevant authority when a result needs clarification. Do not convert a single unexpected response into a confident conclusion about every aspect of the business.

The identifier-role explanation helps identify whether the number you hold is actually the kind of value the service checks. A company registration number or customer supplier code should not be substituted into a VAT verification process simply because it is the only available number.

Confirm the relationship with the seller

A useful preparation record links the identifier to the supplier name and other relevant facts through trusted evidence. A valid value associated with a different entity does not make an invoice’s seller block coherent. Check the relationship rather than stopping at a positive status label.

For a fictional group of businesses, two companies might share a brand and office address. Copying the tax number from one company’s older invoice into the other company’s draft can produce a plausible-looking record. The relevant review must identify which entity actually supplied the transaction and which number belongs with it.

Where official services limit the information disclosed, follow their process for confirmation. Do not infer ownership from an unrelated public search result or contact the wrong business based on a similar trading name. Keep the source and any remaining uncertainty explicit.

Keep verification separate from tax treatment

A registration-related result does not decide the correct rate, exemption, reverse-charge treatment or place-of-supply conclusion for every transaction. Those decisions can require additional facts and applicable rules. The browser form does not establish them from a tax number or country selection.

If an adviser confirms the treatment, record the advice in a form that can guide the invoice entry. Distinguish the confirmed tax category and rate from the evidence about registration. A short note saying “number checked” should not be used as a substitute for a transaction-specific tax decision.

The current creator records rates, categories and reasons you enter. It cannot report that the invoice is legally valid or accepted by a tax authority because the seller tax number is present.

Record what was actually checked

Keep a record appropriate to your business of the service used, date, queried identifier, relevant result and any unresolved qualification. Follow official guidance on retaining verification evidence where applicable. Do not record sensitive information unnecessarily or expose the query result in a public invoice note.

Also distinguish verification evidence from the exported invoice itself. A JSON file containing the tax-ID text does not contain proof that a registry check happened. A readable PDF showing the number does not establish the check’s date, source or scope either.

Resolve uncertainty before presenting a final claim

If the value conflicts with business records, ask the authorised supplier contact or relevant authority to clarify it. Preserve the disputed source rather than editing digits until a service returns a favourable result. If the question affects an already issued document, use the appropriate correction process rather than silently rewriting a historic record.

Once the fact is confirmed, enter it accurately and review the whole seller block. State the result narrowly: a value was recorded, a particular external check was performed, or a transaction decision was confirmed. Those are useful, defensible facts. Reporting generic “tax compliance verified” would imply work that the current product and a simple identifier lookup do not perform.