<html><head><style></style><style></style><style></style><style></style><style></style><meta content="MSHTML 11.00.10570.1001" name="GENERATOR"><title>Preparing for the ELDA transfer web service</title></head><body><h3>Preparing for the ELDA transfer web service</h3><div><br></div><div>The ELDA software is no longer maintained by ELDA 01.01.2027. From a future web update on the version 29.25, the data exchange with ELDA no longer takes place via ELDA software but via the ELDA transfer web service. This change does not affect the maintenance expenses of the ELDA software. We inform you as soon as the ELDA transfer web service is operational, via the newsletter.<br><br>In order to use the ELDA transfer web service, both the ELDA serial number and the ELDA customer password must be stored in parameters in BMD NTCS. The ELDA serial number has also been required for the data exchange so far. This means that only the ELDA customer password belonging to the ELDA serial number must be recorded everywhere where the ELDA serial number is also stored.<br><br>From the <strong>WebUpdates 2026.29.01.85, 2026.29.02.75 or 2026.29.25.19</strong> the ELDA customer password can be stored in the parameters preparing. The login details for the ELDA can be found</div><ul><li>under master data - settings - PAYROLL parameters - ELDA data hub - general: parameters ELDA serial number and ELDA customer password or</li><li>under master data - settings - CRM parameters - CRM - ELDA: parameters ELDA serial number and ELDA customer password</li></ul><div>Please note that the parameters in the PAYROLL package are always defined depending on the dataset and the year. Please carry out parameterisation for each dataset and each payroll year, provided that ELDA notifications need to be sent from several datasets or from previous payroll years. This is the case for imported datasets and possibly for subsequent or comparison payments.<br><br>If necessary, the ELDA customer password on the ELDA website can be used on the page  <a href="https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.elda.at%2Fcdscontent%2F%3Fcontentid%3D10007.838877%26portal%3Deldaportal&amp;data=05%7C02%7Cbuchwiser%40bmd.at%7Cbe4d3ec8484e4462caf708df1a1efeac%7Ce5a8b706cb0f410a820b50cb519a438a%7C0%7C0%7C639258392563678446%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&amp;sdata=vK6Ii3pBPU9%2FNxEKT1J2XxfYV%2BwqMmYFV1WuwcvU9IY%3D&amp;reserved=0" target="_blank">"Info for the customer password"</a>, reset via the link "CUNDENPASSWORTVERwaltUNG". <strong>Important note:</strong> If the ELDA customer password is reset, the new ELDA customer password must not only be stored in BMD NTCS in the above-mentioned parameters but also in the respective ELDA installation so that the data exchange with ELDA via the ELDA software works for the moment!<br><br>Of course, we inform you about the next steps in time in the form of customer information and current information as soon as data exchange with ELDA is possible via the ELDA transfer web service.<br><br>If ELDA notification confirmations are to be archived automatically in the employee's personnel file, a suggestion for a category for the document origin "PYRL: ELDA notifications" must be stored in the program CRM - master data - CRM and firm - DMS - DMS default values.<br></div>
</body></html>
