With the SD Worx (Difference) integration, changes to past payment periods are added to the export buffer in real time as they are recorded in Nepton. Changes made to current or future payment periods are not added to the export buffer in real time, they must be exported either manually or automatically using an integration schedule. When a change is made to a past payment period, the difference between the event before the edit and after the edit, is added to the export buffer.
Good to know
- Employees with employee number 0 are not included in the data.
- An event can be recorded in a past payment period even if there are problems with the integration. For example, an incorrect integration rule or a problem with the SFTP server will not prevent the event from being recorded. The user will be warned about the error.
- It is possible to define multiple rule sets for an integration. If multiple rule sets are defined, recording an event may take slightly longer.
Settings
Payment groups
See Payment groups for general instructions on how to add and configure payment groups.
A payment group must be configured with payment periods and each payment period must have an approval deadline. When the approval deadline has passed, the payment period is in the past, and any edits made to events within that period will be sent to the export buffer in real time as the difference between the events before the change and after the change.
Integration settings
1. Defining persons' IDs
Persons' IDs can be defined in Employees > Person's information > Identifiers.
If the person's SD Worx ID has not been set, the employee number will be used.
2. Adding a target server
If there is no target server for the integration yet, add it in the Working Community settings under Integrations > Target servers. See Target servers for work time exports for general instructions on how to add a target server and set the SFTP settings.
SFTP settings for the target server must specify at least the SFTP server address, SFTP username, and SFTP password (or public key authentication).
3. Integration settings
In order to enable the integration, a rule set must be defined to generate the data. In the export options, select SD Worx (Difference) as the export format.
Select the target server for the integration, that you added in step 2.
The exact timestamp [timestamp-ms] must be added to the export file name, like in the example below. If a timestamp is not used, each file will have the same name and they will overwrite each other.
4. Export scheduling to the target server
Finally, you need to set the export schedule for the target server buffer. You can read more about this in the article Target servers for worktime exports.
File format
The transfer file is ISO-8859-1 formatted text data separated by semicolons (;). The line feed is LF. There is one blank line at the end of the transfer file.
Export data fields
| Column | Field | Ruleset field name | Format | Description |
|---|---|---|---|---|
| A | Business ID | Automatically added | string | Business ID. Can be overridden in a rule set with field SDWorxDifferenceBusinessId. |
| B | Employee number | Automatically added | string | Person's SD Worx ID / employee number. |
| C | Payment group code | Automatically added | string | Payment group code. Can be overridden in a rule set with field SDWorxDifferencePaymentGroupCode. |
| D | Work contract start date | Automatically added | string | Work contract start date, in format DD.MM.YYYY. Can be overridden in a rule set with field SDWorxDifferenceWorkRelationshipStartDate. |
| E | Salary code | SalaryCode | string | Can be overridden in a rule set with field OverrideSalaryCode
|
| F | Amount, hours | "Amount" field if UnitType is 'H' or 'S', otherwise empty | decimal | Amount of hours with accuracy of 2 decimals. , as decimal separator. This field contains information if field is output as hours. |
| G | Amount, days | "Amount" field if UnitType is 'J', otherwise empty | decimal | Amount of days with accuracy of 2 decimals. , as decimal separator. This field contains information if field is output as days. |
| H | Amount, decimal / units | "Amount" field if UnitType is 'U' or 'D', otherwise empty | decimal | Amount with accuracy of 2 decimals. , as decimal separator. This field contains information if field is output as decimal or units. |
| I | Start date | StartDateTime | string | Format DD.MM.YYYY |
| J | End date | EndDateTime | string | Format DD.MM.YYYY |
| K | Amount, currency | "Amount" field if UnitType is 'C', otherwise empty | decimal | Amount of currency with accuracy of 2 decimals. , as decimal separator. This field contains information if field is outputted as currency. |
The data below shows an example of exporting an 8-hour work event excluding lunch
1234567-1;219354;10;01.01.2025;1000;3,50;;;02.06.2025;05.06.2025;
1234567-1;219354;10;01.01.2025;1000;4,00;;;05.06.2025;05.06.2025;
Problem situations
Setting changes
It is not recommended to make settings changes that affect the payroll data afterwards. For example, changing the length of the working day in the calendar view can also change the amount paid. When making such changes, the integration is not run and any previously imported information about the event will remain in SD Worx. In such a situation, the following should be done:
- Delete the event from Nepton. This will send a file containing the difference which should be deleted.
- Delete all the data for the event in SD Worx. There may be multiple rows depending on rule set configuration.
- Add the event again.