As part of the Swiss-wide harmonization of payment transactions, we recommend that you update your payment software by June 30, 2018.
As part of the Swiss-wide harmonization of payment transactions, we recommend that you adapt your payment software to ISO 20022 by June 30, 2018.
As a general rule, the master data uploaded to UBS determines which notes and reports are created for a pain.001 order.
If other notes and reports are required in an individual case, you can issue the corresponding instruction directly in the pain.001 order. In this case, the settings in the master data will be superseded by the instruction in the pain.001.
Further details on debit note management are available in the UBS Implementation Guidelines for pain.001 at
The software manufacturers only automatically offer new functionalities like ISO 20022 to clients with a valid maintenance contract. If you don’t have a maintenance contract, you have to actively reach out to the manufacturer and apply for a software update, which usually involves a charge. Additionally, your software may still be communicating with UBS through an old e-banking data interface (see separate question).
This is usually the case if you are using software that hasn’t been updated in several years. Clients with software that has accessed this interface recently will have received a separate letter from us. The old interface will be deactivated permanently out of security considerations on June 30, 2018. Most software manufacturers are offering software updates for this. Always keep your operating system and your payment software up to date and make sure to install all security updates. Switch to ISO 20022-compatible software in order to continue using it with UBS without interruption. Of course, you can also do your payments conveniently in UBS e-banking in future.
During the changeover phase, clients can select whether they are uploading a DTA or ISO/XML file in UBS e-banking. As part of the Swiss-wide harmonization of payment transactions, we recommend that you update your payment software by June 30, 2018.
Please contact your software support service to establish a clearer picture of the situation. Alternatively, UBS clients (even in the case of proprietary developments) can access the UBS ISO test platform. This platform will help you to test your payment files for potential errors in the new format. If the test platform detects an error, the payment file used must be corrected.
If the test platform does not return any errors either, please contact the e-banking support team (0848 848 064) and provide them with the test platform findings.
A brief guide on the exact procedure is available at
If you access the UBS e-banking OFX data interface using suitable software, the software will receive a pain.002 status report and the findings will be displayed directly in your software.
No pain.002 status reports are provided if you manually upload your file in UBS e-banking under > Payments > Data transfer. Once the files have been uploaded, the status of the payments can be viewed directly in the e-banking screen under > Payments > Data transfer.
Navigate to Payments > Data transfer > Transmitted payment data in UBS e-banking. Here, you can select the “Display orders” menu for the uploaded payment file on the right-hand side. You will receive the detailed error message for the respective payment by clicking on the pencil symbol next to the respective transaction. This displays the details of the respective payment with the error message above.
The cut-off times for each currency and payment type are listed in the following fact sheet:
(see cut-off times for ..., other channels)
No changes can be made retrospectively in a pain.001 message uploaded in UBS e-banking. An individual payment or an entire message can be deleted and then entered or uploaded again.
A pain.001 message uploaded in UBS e-banking and the payments included in the message will be immediately visible under “Pending payments”.
If a pain.001 message has been uploaded in UBS e-banking and an individual payment is deleted by an employee who only has partial signatory authority, this payment will be assigned the status “part signed”. This means that this individual payment will not be executed upon reaching the execution date. To completely delete the payment, a second employee with at least partial signatory authority has to confirm the deletion of the individual payment.
The feedback component cannot be displayed.