Skip to content
English
  • There are no suggestions because the search field is empty.

Export Payroll to Flex Lön or SD Worx

Lön · Steg-för-steg-guide
Uppdaterad 2026-11-19 09:42
Brief answer

Confirm whether the recipient is Flex Lön or SD Worx Salary. Verify the period's entries and the external numbers linking employees, salary types and units. Then create the export and reconcile the contents of the two files with the recipient.

Fördjupning
Before you begin

These profiles deliver schedules and payroll events in separate files but not in the same format. Check the import order and the recipient’s code registers with the person responsible for the payroll system before running live.

Confirm who manages the code mappings in Timeplan and who imports and reconciles the underlying data with the recipient. Handle the files at your designated location for personnel and payroll data and save the originals without changing their format.

Pay special attention to amounts and multiple shifts

The Flex export has known discrepancies for monetary entries and days with multiple separate work shifts. SD Worx does not send regular monetary entries in the amount field. Check such examples with the recipient's responsible person before using the files in a payroll run; a successful download does not guarantee that all compensations have been included correctly.

Steg för steg
Prepare the export
Check the payroll systemVerify according to Configure and troubleshoot the payroll connection that the selected Payroll system is Flex Lön or SD Worx Salary according to your recipient. #### In-depth - Flex Lön uses two tab-separated .dta files for schedules and payroll entries. SD Worx Salary uses instead two files with fixed field positions. Do not rename one profile’s files to import them into the other. - For SD Worx there is a preliminary export with the schedule file excluding payroll events. For a complete payroll export, the file with payroll events must also be present. Therefore, check the export mode before interpreting a missing file as an error.
Check external mappingsCheck employee numbers, salary types, cost centres and additional unit values used by the recipient. #### In-depth - Verify Employee number on the Personnel details page. This number is used to link schedules and payroll entries to the correct employee at the recipient. Ensure it is correct and unique; being able to download a file is not a complete check of the employee register. - The account’s base code is managed under Agreements → Accounts, in External ID, payroll system. For Flex, a specific account mapping for the balance’s work task overrides the base code when present. However, the base code must meet the export’s selection criteria, so a special mapping alone does not include an account with a missing or incorrect base code. It is a salary type mapping for that specific account and work task, not the work task’s own cost centre number. - For Flex, the cost centre is from the External number on the Work task page. The company number in the schedule file is taken from the company’s external number on the Company page. That field misleadingly has the Swedish label Löneart; it refers to the company number, not the account’s salary type. Export ID is a fallback when the external number is missing in storage, but a saved empty number does not reliably trigger this fallback. Have the integration manager check the link if the schedule file’s company number is empty. - SD Worx requires the company’s Export ID and a special SD Worx location attribute on the registered work task. This attribute is not the same as the work task’s regular external number. Check this special integration mapping for the work task with the integration manager. If the location attribute is missing, fields in the payroll file may shift, so a filled regular external number does not substitute this check. - For SD Worx, the payroll line uses the account’s general external payroll account when a value is saved, even if that value is empty. The mapping for the registered work task is only used when the general code is completely lacking in storage. A saved empty base code can therefore block a filled work task mapping and cause the group to be missing in SalaryEvents. Ask the integration manager to check whether the base code is saved as empty or missing entirely, then check the work task mapping if the effective payroll account ends up empty. - Values that are too long for SD Worx fields must not simply be truncated manually. Some overly long salary types or employee numbers may cause payroll lines to be missing without rejecting the whole file. Have the integration manager establish the correct value and compare both the schedule and payroll file; a number may be treated differently in the two parts. - For Flex, the setting Which company the export is based on controls whether the selection follows Work task’s company or Employment contract’s company. The cost centre in the payroll line still comes from the registered work task. Therefore, compare company and cost allocation separately when an employee works across company boundaries. Follow Configure and troubleshoot the payroll connection together with the integration manager to verify the relevant setting in your environment. - For SD Worx, payroll entries and schedule shifts are selected based on the company the registered work task belongs to. Another primary company in the employment contract therefore does not automatically move these entries to that company’s export. Verify the work task if the data seem missing in a certain company’s file.
Steg för steg
Create and follow up the files
Review the payroll periodCheck the period, company and approved entries on Payroll periods. #### In-depth - If a payroll line is missing, start by checking the balance’s date and approval on the Stamps and balances page. Also verify that the employee’s employment contract applies on that day. In Flex, a line is not included when its total value has become zero. SD Worx may include zero values on deviation accounts. Therefore, investigate what the specific entry means instead of assuming both profiles always only contain lines with values. - The checkbox Export to payroll is found under Agreements → Agreements. For Flex payroll lines, it is the collective agreement related to the balance that must be marked. For SD Worx payroll lines, it is the collective agreement on the employment contract valid for the balance day. Changing this choice does not revoke an already created file and is not a common enable or disable for the whole employee. - For schedule shifts, both profiles use the shift’s explicitly selected collective agreement if one exists. Otherwise, the collective agreement on the valid employment contract is used. Check Export to payroll on the correct agreement if a shift is missing in the schedule file; an approved payroll amount does not prove the same shift has been included. - The schedule file and payroll file answer different questions and are not based on exactly the same selection. The schedule does not require the same approval as payroll entries. Flex requires active employees, while SD Worx does not use the same general activity condition. Compare both a work shift and a salary type, not just total amounts. - SD Worx only includes a schedule shift in TaskData when Timeplan has a day task for the same employee and date. Shifts of types On-call shift, Standby shift and Custom shift are also excluded. Flex does not have the same general shift type filter. If the shift is visible in Timeplan but missing in TaskData, then check both the day task and shift type, not just the approval and Export to payroll. - If the collective agreement setting Calculate planned scheduled time for part-time absence is enabled, SD Worx adds the part-time absence once in each group that Timeplan sums in TaskData. With a positive extent, the extent’s portion of the agreement’s weekly working time divided by five is used; without a positive extent, the deviation time in the day task is used. When the setting is disabled, no separate absence time is added. Therefore, compare TaskData with both shifts and part-time absence when hours do not correspond to visible shifts. - SD Worx only fills out a date without schedule time with a zero line when the employee already has at least one selected schedule group in the period and has an employment contract valid for the missing day. An employee without any selected schedule group does not get a full series of zero lines. Therefore, distinguish a zero line from a completely missing employee when troubleshooting TaskData. - For Flex, you need to check a day with multiple shifts and gaps between the shifts. The current export then subtracts the gap an extra time from the working hours. Also compare start and end dates for night shifts, as the next day’s date should appear when the shift passes midnight. - Flex monetary entries may get values in both quantity and amount columns. For SD Worx, normal monetary entries are not sent as corresponding amounts; full-day absence may however produce a date line without numerical values. Confirm with the recipient how these situations should be handled before the payroll run. - Review the SD Worx SalaryEvents file against the number of expected payroll entries, not just its existence. A group can be skipped without rejecting the entire export when its salary type or company number is longer than five characters, or when the employee number is longer than twelve. An empty effective payroll account may cause the same loss. Therefore, compare concrete employees and salary types with the data and correct the identifiers at the source before creating a new file. - Verify separately the fixed field order in the SD Worx schedule file TaskData. There a too-long employee number is truncated to the first twelve characters, whereas a company number over five characters or a schedule hour value over five characters are not reliably rejected. An empty employee number may also be padded as if the field were present. Ask the recipient responsible to check that person, company, date and hours still fall into the correct fields; a valid download alone is not proof. - Compare both hours and quantity on SD Worx lines where the same salary type has entries with different units. The current grouping does not always distinguish by unit, so a later quantity line may retain an earlier hour value or vice versa. Check the individual numeric fields against Timeplan’s data before the recipient imports the file; a correct total sum in the period does not reveal such an error on the line. - Flex payroll line from and to dates currently use the balance day. Which date interpretation the recipient should use is not yet determined. Therefore, do not conclude that a date in the file alone proves the correct pay period at the recipient.
Create the correct exportSelect Create payroll file for the correct company in the locked period. If you only need a preliminary SD Worx schedule during an ongoing period, use the separate action Create schedule file. #### In-depth - Verify the ZIP file contains two parts when making a full export. Compare filenames and content with the profile you have selected before passing the files on. - A successful file retrieval does not mean the recipient accepted all lines. Read the import’s rejected entries and compare a sample of dates, salary types and units. - For SD Worx, Create schedule file appears when the period end date is after today and the company status is Not checked, Checked or Checked, contains errors. Then you only get TaskData, not SalaryEvents. For a company, it is a direct file download. Flex has no corresponding preliminary action on the Payroll periods page. - If the period check shows contains errors, follow the status link to Error report and check the specific cause before proceeding. File creation neither corrects balances, approves entries nor locks the period. The common procedure is found in Check payroll data and create payroll file. - A new export contains the entire selected data, not just changes. Confirm the recipient’s correction procedure before reimporting a previously imported period, so the same entries are not processed twice.
Fördjupning
Check the result

Confirm that employees, schedules, salary types and cost centres appear correctly in Flex Lön or SD Worx. If any part is rejected, save the error message and correct the external mapping before recreating the file.

Steg för steg
Frequently asked questions
Why is there a schedule file but no payroll file for SD Worx?Check whether you used Create schedule file or Create payroll file on the Payroll periods page. The schedule action only generates the preliminary schedule, while a full export provides both schedule and payroll events. An empty payroll event file in a full export is another situation: then you need to compare the period’s balances, agreement conditions and code mappings with what actually arrived.