ID Validation: About our software
Idea and Origin
The idea for ID Validation came from the continuous development of VAT Validation. We ourselves were dissatisfied with the technology used and the lack of possibility to add more modules to the program itself. Therefore, at the beginning of 2019, we had decided to rewrite the complete “VAT Validation” and completely abandon the dependency on a framework like .Net. The result is Software ID Validation, which is extensible via so-called modules. The first module is of course the “VAT Validation”.
Users of versions 1 or versions 2 of the “old” VAT Validation still know the necessity of installing a .Net framework and in the past years also the necessity of using very specific versions.
Modularization has allowed us to get rid of this completely and we are also able to offer ID Validation for Linux.
The “ID Validation” was implemented completely in Lazarus. Here it was tried to keep all logic out of the program and to pack into the actual service modules.
These modules, first of course the module VAT Validation (ServiceVAT) were also written in Lazarus. In these modules we implemented all relevant logics necessary for processing.
All other modules that we have planned, such as UID Switzerland, will be built according to the same principle. This way we can guarantee that any service can be integrated into third party programs without using the graphical program.
Outlooks and support requests
You have chosen ID Validation from us and are missing a function? You receive error messages, which cannot be explained by faulty directories or by corresponding protocol entries?
For this we have the frequently asked questions (FAQ), which is structured accordingly in case of occurring errors, whose cause could possibly occur to further users. Of course, not all questions related to ID Validation are included here.
For all questions that can be checked specifically only with your data, please use the following e-mail address:
Please include the version used, the data file, and the appropriate data that can be used to track the error, if applicable. This data is for internal processing only. You are also welcome to modify the data, if irrelevant for the support case, in order not to send real data. It is important, however, that the error can still be reproduced. If necessary, test it again yourself before sending it to us in order to generate unnecessary runtimes in the support case.
Of course you can also send us your wishes for function enhancements. Please also use the following e-mail address firstname.lastname@example.org for this purpose. We are always happy to receive suggestions or constructive criticism, which we try to implement as soon as possible. Only through your feedback the software will become what you can use optimally in the end.
If you have a very specific special case for which you have been waiting in vain for a supporting tool, please contact us. We will be happy to review your specifications and implement them.
We are always striving to extend the range of functions to provide you with further information and support on this and other topics.
If you are interested in future changes and innovations, you can view them directly on our roadmap.