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

Importing Payslips

Import och integration · Steg-för-steg-guide
Uppdaterad 2026-11-19 10:50
Short answer

First, verify which filename your payroll system can generate and what secure transfer method has been set up for you. Deliver one PDF per employee according to the agreed profile. Then check that each document appears under the correct employee in Documents and in the employee's app before recurring deliveries begin.

Fördjupning
Before you begin

The import module must be enabled to import payslips. Obtain a sample PDF from your payroll system and verify how the filename identifies the employee. Ensure that the employment number or personal identity number in the payroll system matches Timeplan for the employees who should receive documents. Ask the integration manager to confirm your current transfer method, customer-specific recipients, allowed file packages, and who handles errors. Do not use an outdated email address, server address, or filename template without this verification.

Payslips must reach the correct person

These documents contain sensitive payroll information and will be visible to the employee in the app. If two employees share the same identifier, the current import may assign the document to one of them instead of rejecting the file as ambiguous. Therefore, verify personal matching and the transfer with a controlled test delivery before sending a full payroll run. If a document appears to have been linked to the wrong person, the delivery must be stopped and rectified explicitly; changing personal details will not automatically move an already uploaded document.

Steg för steg
Preparing the documents
Choose the correct matching methodCheck with the integration manager which filename profile is used for your payroll system. #### Further details - The import links each PDF to an employee based on the identifier that your specific profile reads from the filename. Depending on the payroll system, this is either the employment number or the personal identity number, and the identifier may be located in different parts of the name. A meaningful filename alone is not sufficient unless it follows the agreed profile. - When the profile matches on the personal identity number, the import searches among active employees with at least one employment contract. The contract does not need to be valid on the import date: even a past or future contract can cause the employee to be found. However, an inactive employee cannot be found via this matching route. If several active employees share the same personal identity number, the current import selects the one whose contract has the latest start date, instead of reliably rejecting the document. - When the profile matches on employment number, neither active status nor an employment contract is required. Thus, an inactive employee or one without a contract can also be a recipient. If there are multiple matches, one may be chosen unpredictably. Therefore, verify the actual recipient after the test delivery; neither matching method provides guaranteed protection against duplicate identifiers. - A filename consisting only of digits before .pdf is intended to use personal identity numbers even if the payroll system’s regular profile matches on employment numbers. The current interpretation is not consistent across all profiles: for Personec S and SD Worx, such a name might still be read according to their specific filename rules and miss the person. Therefore, test a real example for your specific profile and verify the recipient in Timeplan before using numeric names for a full delivery. - If the payroll system cannot create files that can be matched, there is a special recipient-based email flow: one employee per message. This should only be used if that method has been explicitly approved and set up for you. Do not send multiple employees’ documents in one such message.
Check each PDFEnsure each PDF contains a single employee’s payslip and includes the identifier required by the profile. #### Further details - Multiple PDF files may be included in the same package if filenames allow each document to be matched independently. However, a ZIP package or encrypted delivery does not replace the requirement for a correct filename on each PDF. Other files in the package should not be treated as payslips. - Pay particular attention to duplicates in employment numbers and personal identity numbers before submitting files. Current matching does not reliably block duplicate matches: it may assign the document to one employee. Search among inactive employees when investigating older registrations and duplicate identifiers. This is especially important if the profile uses employment numbers, since an inactive registration may still be selected. Finding an inactive registration does not mean a profile using personal identity numbers can place the document there; that path only searches active employees with an employment contract. Let the responsible party resolve duplicates before the next delivery instead of relying on an import error.
Steg för steg
When using secure file transfer
Submit a test file to the correct customer folderHave the payroll manager transfer a controlled test PDF using the customer-specific recipient provided for your import. #### Further details - Your transfer solution should keep your files separate from other organisations’. The person setting up the connection must confirm the correct protocol, directory, and login method through an approved channel. Do not use a recipient from older instructions just because it is still reachable. - In a configured file transfer folder, the import can read a direct .pdf, a .zip containing PDF files at the top level of the archive, and the common file extensions .pdf.pgp and .zip.pgp. A ZIP file inside another ZIP, a PGP file inside a ZIP, a PDF in a subfolder, or files with extensions .gpg and .asc are not included in the package flow. Each PDF still needs to have the filename required by the matching profile. - The email route has stricter package limits: use direct PDFs or ZIPs with independently matchable PDF names. .pdf.pgp and .zip.pgp are not functional email packages for this import, even if the attachment initially appears to have been received. - Ask the integration manager to confirm the actual configured transfer and keep the original test file until you know the document is assigned to the correct employee. The requirements specify package formats but not which host, protocol, port, customer folder, or recipient represents your currently approved production path. That information must come from a version-bound operational instruction and must not be inferred from an older address.
Check the test delivery outcomeOpen the correct employee’s Documents and verify the imported payslip. #### Further details - Compare the correct person, pay period, and document content with the test data. Also check the employee’s app if included in the test. Review the status result for the individual file, but do not use a successful upload status as proof of the right recipient: verify the document actually appears under the intended employee and not under another person with the same identifier. Only when both delivery and display are correct should recurring transfers be activated. - A file can also appear uploaded even if no document was written to the database. If the storage call completes without exception but without saving a row, the import may still report success and treat the file as uploaded. Therefore, check the document in the employee’s Documents, not just the import status or notification, before approving the test delivery. - If the document is missing, find out whether the package did not arrive, could not be opened, had the wrong file type or filename, or did not find a unique employee. Ask the integration manager to verify the status for the specific test file before resending so that a received file is not processed twice.
Steg för steg
When email is specially approved for you
Confirm sender and recipientEnsure your approved sender and the current recipient are linked to the correct company and payroll profile. #### Further details - When sender-based identification is used, the sender must match the company’s Import-id on the Company page. If your payroll system can create matching filenames, multiple PDFs can be sent together. If instead the identifier is in a specific recipient address, one PDF per employee per message applies. - Email is not a standard default method for payslips on your own initiative. It must be explicitly approved for you and have the agreed security level and sender and recipient information. Published older example addresses do not constitute proof that this method is current for your import.
Send and check a test fileSend a controlled test PDF according to the approved email profile and then check the result in the correct employee’s Documents. #### Further details - Sending a message or receiving an automatic notification does not guarantee the PDF was linked to the correct employee. Check both that the document is visible and that the name, pay period, and content are correct. If no payslip is visible, first verify that the message reached the import and the sender was identified as the correct company. - If only some documents are missing, compare their filenames and personal identifiers with Timeplan instead. Do not request a new delivery until you have investigated where the first file went and whether it can be reprocessed without duplicating documents. - Re-delivery is not automatically duplicate-safe. A new attempt may create a second document in Timeplan, while a file with the same name may overwrite a previous file in the import’s file management. In the recipient address flow, two PDF attachments in the same message can also have the same name and the later replace the earlier. Therefore, let the integration manager clarify both saved documents and remaining files before sending again, and use only one PDF per message in that flow.
Fördjupning
Check the result

Reconcile the number of uploaded, unmatched, and rejected PDF files against the expected number of employees. Verify at least one test payslip on the correct employee and in the app. When a file is missing or incorrectly assigned, investigate the cause and document the correction before the next full payroll run is sent.

Steg för steg
Frequently asked questions
Why is one or more payslips missing?First, check if the delivery reached the correct customer recipient. If other files in the same delivery arrived, examine the filename profile, the employee’s employment number or personal identity number, and any duplicate personal records. Ask the integration manager to check the individual file’s status and actual recipient. A duplicate identifier does not necessarily cause an import error; the document may have been assigned to one of the individuals and then requires a traceable correction.
Can we place multiple payslips in the same ZIP file?Yes, when your agreed import profile supports packaging and each PDF can be matched independently by its filename. Each PDF must still contain a single employee’s payslip. The recipient-based email flow is different and uses one employee per message.
Is it enough to correct an incorrect personal identity number and send again?No, not until you know what happened with the first file. Changing the personal identifier does not automatically move a document already saved under someone else. Ask the person responsible for the import to investigate the original run and perform a traceable correction before the file is processed again.