By using a simple CSV file, the “VAT Validation” is a way to check your entire database. We started with this import interface and build in the upcoming version 1.4 the number to formats (JSON, XML, and XLSX).
We ensure that compatibility is maintained when the CSV VAT inspection interface is extended. This allows you to use the latest version without additional effort when integrating into your ERP system.
In order to ensure that the individual VAT ID number records are included in your master data, you have the option to up to two unique keys in the import file. These are returned in the export file and can be used for reimport into your ERP system. You can also leave these two fields (key_1 and key_2) blank.
The default separator for each element for the VAT Validation is the ‘|’ character (pipe). This can be changed via the settings. Bold Field Names are mandatory fields (the delimiter can be changed via settings).
The qualified validation of your VAT data within the CSV file is only available using the interface of BZSt, which is currently only available for german customs.
Please note that all fields must be specified in the import file, even if you only have a simple query you want to perform.
Example in the form of a CSV file:
4711|2|EN123456789|AT12345678|||… (other VAT validations)
When creating the VAT import file, please ensure the correct number of Columns (8 columns). This note is important for possible errors during import when using CSV. Future , we will support other import formats that no longer have this limitation.
The CSV export file of the VAT Validation contains the returned values of each query.
|own VAT ID||String||DE123456789|
|Foreign VAT ID||String||AT12345678|
|ResultText||String||The requested VAT ID number is valid.|
|Timestamp||Date + Time||2019-11-05 14:35:43|
Example in the form of a CSV file (with standard delimiter):
4711|2|EN123456789|AT12345678|200|The requested VAT number is valid.|2019-11-05 14:35:43
The fields of the VAT Validation within the CSV import or export file are named in German. In the course of the extension of the import formats, these will be internationalized, i.e. we will in the future in English. However, we have thought of configuring the field names in order to increase flexibility.