Adjustments | Swissdec 5.0

Task #11855 | 5060.002

With version 5060.000, we released Swissdec V5 ELM Management. Based on initial customer feedback, additional adjustments listed below were made:

•FAK declaration can now also be triggered if there is only one FAK contract for all cantons that are reported. 

•FAK declaration exported different data depending on whether ‘Per child’ or ‘Default’ was defined in the “Family allowance details” field in the Payroll Setup. The data for the same canton is now filtered and transmitted identically, regardless of whether ‘Per child’ or ‘Default’ is selected.

•If two main/settlement pay runs (without supplement) were settled for a person while one resignation date was entered in the pay process list, then the “WithdrawalDate” field was included twice in the XML. We made sure now that the resignation date is only exported once in this constellation.

•If the “Report to all” field was recorded on the “Salary declaration” page, a schema validation error occurred. This has been corrected and reports could be submitted to cantons. 

•An error message “​Single-parent family cannot be empty” occurred during income tax submission if the Concubinage field was processed with ‘yes’ and no single-parent family rate (H, P or U) assigned. Now we check during ELM reporting whether one of these IT rates has been processed and only then export single-parent family information. It is therefore possible to store a common-law spouse independently of the IT rate. 

•If no country code or canton was stored in the partner’s alternative address, an XML validation error occurred. Now we check whether these fields have been filled in and show in the error message the Employee N° that still requires this information to be filled.

•The Function field cannot be edited in the pay process list. Corrections have been made and this field can be edited directly in the pay process list.

•When income tax is reported, the recapitulation part is always displayed as “Salary declaration comments” in the response, although this information is no longer sent as a response from Swissdec V5. Therefore, this section is no longer displayed. 

•If Swissdec encountered an error with XML validation, an attempt is made to read the response anyway. Since there is no readable response, the error message appeared: “The following exception occurred while processing XML data: ‘Root element is missing’ in line 0 at position 0”. Corrections have been made and a new verification is carried out to determine whether there is at all a response to the display. The error display has been improved and the message “An error has occurred. Would you like to see the error log?”

•When a negative AHV salary was transmitted, the split values in some constellations did not match the reported AHV salray. This caused an error message. Automatic AHV splitting has been adjusted. At the same time, the “AHV Minus Salary Notification Date” field is decisive in the Employee card in terms of whether the splitting is to be carried out or not. If a date is entered in this field, only this date is exported in the ELM XML, the splitting has to be done manually and the distribution of minus wages has to be coordinated with the AHV compensation office.
The ‘AHV Summary ’ report has also been adjusted so that the logic that applies to ELM reporting is also taken into account in it.

•If a regulation was assigned in the “Company car regulations” field in the Employee card, the Salary Certificate could no longer be generated with Swissdec V5. Starting from Swissdec V5, this field no longer exists in the scheme. Therefore, we have completely removed the code that is responsible for the ELM export. The corresponding comment is no longer printed on the Salary certificate starting from version Swissdec V5.

•Another occupation and the corresponding level of employment must be transmitted during wage reporting. If the level of employment for other income sources is unknown, the conversion to a 100% level of employment is carried out with 0. The field in the export has been adjusted for compliance with the Swissdec guidelines and the export only takes place if a value greater than 0 has been processed.

•A retroactive canton correction error occurred during wage reporting because the validity date could not be read correctly. The calculation was correct, the validity date could not be exported for wage reporting. With this change, the validity from the Time Machine is now also transferred to the XML file, as is the case for the remaining mutations.