The financial institution can respond to a customer's order file (pain.001 or pain.008) with one or several messages (pain.002, PSR1). The message informs the customer whether the order file – or part of it – was accepted as syntactically and semantically correct, or whether it was rejected due to errors. For each order file, the customer receives at least one message.
Different systems which have a part in the processing of the order file (EBICS server, bank server, business control application) may send a message. Thus, messages can refer to different phases of the order file processing.
|
Before the financial institution can send a message, the order file must at least have been successfully authorised. A positive message does not necessarily confirm that the order has been executed in the bank systems, i.e. that payments have been booked. |
A message refers to one level of the order file and contains further references and information:
|
Level |
Status |
Information |
References |
|
Transaction (C level) |
Rejected |
Status of the transaction Error code Incorrect element(s) |
Transaction Batch Message |
|
Accepted |
Status of the transaction |
||
|
Logical file (batch) (B level) |
Explicitly rejected: erroneous batch |
Status of the batch Error code Incorrect element(s) |
Batch Message |
|
Implicitly rejected: all included transactions rejected |
Status of the batch |
||
|
Partly accepted: some of the included transactions rejected |
|||
|
Accepted |
|||
|
Complete message (A level) |
Explicitly rejected: erroneous message |
Status of the message Error code Incorrect element(s) |
Message |
|
Implicitly rejected: all included batches rejected |
Status of the message |
||
|
Partly accepted: some of the included batches rejected or only partly accepted |
|||
|
Accepted |
In case of an order file that is authorised and already listed in the customer protocol (HAC) as terminated with a negative result, only a message on the level of the message is sent (as explicitly rejected).
|
→ |
Detailed information on the structure of the messages in Swiss financial institutions can be found in the document Swiss Payment Standards 2021 – Swiss Business Rules for Payments and Cash Management for Customer-to-Bank Messages [1]. |
The customer can download the messages from the bank server via the application. If the corresponding order file was created and/or sent with the application, the message additionally contains the name of the order file as well as additional information such as amounts and accounts.
|
All empty fields in the messages from the financial institution are completed using data from the order file – if it contains such data. |
With the information, the customer can find the errors in a message, batch or transaction, correct them and then send the relevant elements as a new order file. To avoid double submissions, only those elements which were rejected as erroneous and have been corrected may be sent again.
The menu Status report offers the following functions:
|
|
Displaying overview of the messages |
|
|
Displaying details of a message with the corresponding references (message, batch, transaction), including details of the error codes |
|
In the menu Status report you always download the current messages. To download older messages from the financial institution, you can enter a download date. To this end, open the menu , tab Download dates in editing mode and enter the required download date at the business transaction. Please note: The download date may not be older than the retention period for messages. You can define the retention period via the menu , tab Retention periods. |