VAT Validation: Validate and check VAT Number

VAT Validation is a module of our ID Validation software that allows you to validate a single VAT number or query a VAT number. However, the main function of our module is batch processing, which allows you to check your entire master data at once.

Overview of the module VAT Validation

ID Validation - module ‘VAT Validation’ check VAT

Single Validation

  • no restriction of workstation installations
  • direct query and response of the interfaces
  • Manual testing can be used without licensing
  • Query and validate via standardised, simple interface
  • Verification (usually) within a few seconds (depending on settings in the program)
  • Storage of raw data for auditing
  • Check and validate with the Bundeszentralamt für Steuern or VIES/MIAS of the European Commission

Batch

cli/Service

  • Identical functions as batch processing
  • 100% integration into existing applications
  • Fully controllable via CLI parameters
  • Possibility of a central directory for background processing
  • Sending e-mails to specialists

Only the Batch Processing and CLI/Service features of the VAT Validation require the purchase of a License. You can purchase a license from the License Order page.

Validate VAT

The verification of the VAT identification number (VAT) is the responsibility of the respective company. If these numbers are not properly checked, claims may be made by the tax office, up to and including criminal proceedings for attempted tax evasion!>

Performing a single query of a VAT registration number

Since you may install ID Validation on any workstation in your company, the single query is also available to every employee.

ID Validation - Module ‘VAT Validation’ VAT number check - single query

This will save you from calling the corresponding web page, since our module uses exactly the identical interface. And this coincides with the legal requirement to log the queries, if you have enabled this feature.

Check VAT registration number with batch processing

With the help of batch processing, you can set up a CSV, JSON, or XLSX export from your ERP system and subsequently check all master data contained in the export directly with the VAT registration number check.

ID Validation - Module ‘VAT Validation’ VAT number check - batch processing

Select the file you want to import or drag and drop it on the ID Validation and you can check the whole file. As with the individual query, the BZSt or VIES interfaces are used (depending on the configuration). After a relatively short time you will have checked each VAT ID number and also logged it according to the legal requirements.

cli/Service setup

You can automate the batch processing. Familiarize yourself with using our VAT Validation as a cli/Service. With this function you even get the possibility to receive the status of the check by e-mail. Thus, a complete automation of the VAT number check!

How to set up the module and how to check your VAT number check is described in detail in our documentation. If you have any further questions, please feel free to have a look at our Frequently Asked Questions (FAQ). If you still have questions, contact us.

Notes

We assume no liability for any loss of data caused by use of the module VAT Validation.

The VAT Validation also has no influence on the results obtained. The program returns the results of the VAT check only in a defined format (CSV, JSON or XLSX). All other fields that are not required for the check are not output in the check results file.

If changes have been made to the interface of the Bundeszentralamt für Steuern (BZSt), an update of the Software created and made available. This usually takes place within 24 hours after being informed.

We update our VAT documentation of the VAT Validation at regular intervals. This allows us to ensure that all important information for the users are available. For changes in the application that are used for the operation does not require any special instructions, we update this Documentation is not forcibly. However, we strive to read the documentation at the latest at the release of a new minor version 1.2.x 1.3.x.