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 instructions in the pain.001.
You can find more precise information on managing debit notes in the UBS Implementation Guidelines.
- Ensure that your payment software is ready by no later than the middle of 2020 to pay (by means of pain.001) the new QR-bills. If you have questions, contact your software partner directly.
- Update any readers so that they can read the Swiss QR code.
- If needed, fill in your account payable master data with the QR-IBAN of the beneficiary.
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 contact the manufacturer and apply for a software update, which usually involves a charge.
Migration to QR-bill
For entering payments, your software must support the QR-bill together with its additional volume of data. It must also be able to generate payment order pain.001 for all three variants of the QR-bill. This is the only way to make trouble-free payments. You can look up recommendations for bill recipients and billers in the UBS handbook for QR-bills.
Please contact your software support service to find out the exact reason. 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.
When manually uploading in UBS E-Banking under “Payments >Transferring and paying bills > Reenter > File transfer,” no pain.002 is sent back. Once the files have been uploaded, the status of the payments can be viewed directly in the E-Banking screen under “File transfer.”
Navigate to “Payments > Transferring and paying bills > Entered files” 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 following limitations exist for manually uploading a pain.001 payment message:
Number of transactions per file: 9,999
Maximum file size: 50 MB
The following limitations exist for uploading a pain.001 payment message over the direct interface OFX:
Number of transactions per file: 9,999
Maximum file size: 20 MB
The cut-off times for each currency and payment type are listed in the following fact sheet:
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. Now payments can be individually processed with the “Pay again” function and be initiated for payment.
When doing so, the following information cannot be carried over from the file-transfer file due to the different format:
- Ultimate debtor
- Ultimate creditor
- Purpose code
- Max. address 140 characters
- Max. remittance info 140 characters
- Payment instructions: Individual/collective debits; salary payments; notification instructions
How long does it take until a pain.001 message uploaded in UBS E-Banking and the payments included in the message appear under “Pending payments?”
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 employee who has partial signatory authority deletes an individual payment, this payment will now 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 signatory authority with at least partial signatory authority has to confirm the deletion of the individual payment.
The QR-bill: biller
Reconciliation takes place using the structured reference.
In the case of QR-bill variant 1, a QR-IBAN and QR-reference are used. For QR-bills variant 2, an IBAN and creditor reference are used.
For details on reporting options, see the following link:
Yes, when invoicing with the existing orange payment slips, clients have the option to obtain the BESR credit memo data in the ISO 20022 standard as a camt message or, as in the past, as a v11 ESR credit memo file. However, we recommend switching to camt format at an early stage.
Our price list for private clients can be found under the following link:
Our price list for companies can be found under the following link:
The QR-bill: bill payers
If the client uses one of the UBS interfaces and therefore enters the bill in a software program first, they need to update their software and if necessary update any bill scanner or entire accounts payable processes in good time. The main requirements are:
- It must be possible to process every type of QR-bill.
- Payment parts with QR-IBAN and QR reference cannot be paid as ESR. Payment as ESR can lead to a rejection or to an incorrect credit at the beneficiary’s bank.
- Checking of accounts payable master data. Make sure that the addresses are stored in a structured way, if possible, and that accounts can be entered in IBAN format plus several IBANs per account payable.
- If document scanners (readers) are in use, they must be able to read the Swiss QR code and record it correctly. In the future, all data will be imported via the QR code.
Numerous ERP software providers have launched software modules and are committed to a timely and successful changeover. SIX has set up a readiness section on its official page for this purpose.
The UBS handbook on QR-bills or the QR-bill processing rules published by SIX are helpful for this.
The Swiss QR Code specifies two fields for possible alternative procedures. They are available for other payment solution providers. Any provider who wishes to use an alternative procedure must also provide the appropriate specifications.
Until then, eBill will be the only alternative procedure available for QR-bills.The “Alternative procedure” field can be filled out according to the eBill specification when creating the QR-bill. To do so, the biller must have its client’s eBill information. This is then used for triage in order to send bill effectively. You either send an eBill to the client if the client’s data are filled out in it or a physical QR-bill. This information is not of use to the payer when paying the invoice.
Clients and software partners can create a test QR-bill with the UBS test platform from the biller view, and from the payer view they can thoroughly test whether the QR-bill is entered and whether the payment of the QR-bill via pain.001 was made.