Pay salaries with ISO 20022
Use ISO 20022 File to create a pain.001 payment file for one or more checked payroll runs. Payroll or finance specialists with payment permission export it after checks and release and—if active—approval; they do this before or, depending on the process, at the same time as posting. Uploading and executing the file in e-banking takes place outside SwissSalary.
Prerequisites
- The payroll run has been professionally checked and released. For more information, see Approve, correct, or cancel a payroll run.
- The run is approved if the approval process is active.
- The employees' bank details contain a usable account. For more information, see Set up employees for payroll.
- The bank setup contains a file name, sender name, sender IBAN, and sender clearing number. For more information, see Set up payment methods and employee bank details.
- You have checked the payment method and currency of the employees' bank details.
Hinweis
SwissSalary creates and stores the payment file. Uploading, approving, and executing it in e-banking take place outside the process recorded in SwissSalary.
With the SwissSalary Banking module, you can upload the payments to e-banking from within SwissSalary. You still approve and sign the payments in e-banking.
Select payroll runs
- Open the Payrolls page.
- Select the run to pay or several related runs.
- Choose ISO 20022 File.
- Check the Payroll No. filter.
You can select regular and additional payroll runs. You can combine multiple runs if their bank, payment date, and internal release process match.
Specify payment details
- Check the Payment Date.
- Under Debit to Bank, choose the bank setup from which the salaries are paid.
- Check the Payment Standard Version:
- SPS 2009 (deactivation as of November 2026)
- SPS 2022
- Under Urgency of Processing, choose Normal or High.
- Start the export.
SwissSalary changes a payment date in the past to the current date. If the date falls on a weekend, it moves processing to the preceding Friday.
If the selected payroll runs have different payment dates, SwissSalary displays a message. Decide whether the runs should actually be included in the same file.
Tipp
For a multiple-selection export, use only payroll runs with the same payment purpose and debit bank. This simplifies reconciliation and approval.
Check the export
After exporting:
- Check that the XML file is stored as a file on the payroll run.
- Check the number of bank files on the payroll run.
- Reconcile the payment total and number of payments with the payslips.
- Check employees who use cash payment or another payment method.
- Transfer the file to e-banking according to your internal four-eyes process.
SwissSalary reports when there are no bank entries for a payment file. It also indicates when the payment methods require additional payment orders, cash payments, or ASR payments.
Consider the cancellation block
If Cancellation Block on Payment is set up, SwissSalary sets the cancellation block for the selected runs during export. The runs remain unposted but can't be cancelled accidentally.
Warnung
Reset the cancellation block only after you have confirmed that the bank file wasn't executed. Otherwise, exporting again can result in incorrect or duplicate payments.
For more information, see Approve, correct, or cancel a payroll run.
Common export errors
| Message situation | Check |
|---|---|
| No bank entries available | The employee's bank distribution and payment method |
| No usable account | The IBAN or another supported account identifier in the employee's bank details |
| Missing sender details | Sender name, sender IBAN, clearing number, and file name in the bank setup |
| Missing SWIFT address | The bank master data for the recipient bank used |
| Payroll run not approved | The approval status of the selected run |
| No access to selected payroll runs | The signed-in person's allocation-group filter |
Good to know
- You put runs with different payment dates or banks into one file—the bank rejects it or debits the wrong account.
- You reset the cancellation block after export while the file might still be processing in e-banking—duplicate payments can occur.
- You expect all net amounts in the pain.001 file—cash payments and other methods are missing and remain unpaid unless you process them separately.
- You treat the export as a completed payment—approval and execution in e-banking are still outstanding, so employees are waiting for their money.
- You correct missing sender details, IBANs, or approval only after the export fails—the payment date slips.