search form
home

BKB-E-Banking Help

Exchange of Data

Harmonization of Payments

Introduction of ISO 20022 Standard

ISO-20022 Notices

  • What are pain notices and how are they different?

    The pain.001 notice constitutes the actual payment order, while the pain.002 notice represents an error/status feedback.
    The two pain notices differ with respect to their use as follows:

    ISO 20022 Notice Use
    pain.001 Payment order (Customer Credit Transfer Initiation)
    pain.002 Error/status feedback (Customer Payment Status Report)
  • How can I upload a pain.001 payment file to BKB E-Banking?

    Select the menu point “Payments“/“Upload Payment File“ to access the menu from which you can select and upload an appropriate file. Various software programs also allow outstanding payments to be transmitted directly to E-Banking.

  • Can I make changes to pain.001 subsequently?

    Changes to pain.001 in E-Banking are limited to the execution date and the deletion of individual items or entire files.

  • How can a pain.002 notice be downloaded from BKB E-Banking?

    Click on the relevant row under "Uploaded Payment Files" and from there, click on "Download".

  • What programs do I need to open the notices in ISO 20022 format?

    ISO 20022 notices (pain.001 and pain.002) are conventional text files that can be opened with any text editor (NotePad, TextEdit, etc.).

  • What do the rejection reasons in a pain.002 mean?

    Rejections can have various causes. We have listed the most frequent error codes and their meaning for you in the table below.

    ISO Code
    Error
    AC01 Incorrect account number
    AGNT Incorrect agent
    AM01 Amount is zero
    AM02 Inadmissible amount
    AM03 Inadmissible currency
    AM10Incorrect checksum
    AM18Value for «Number Of Transactions» does not correspond to the number of transactions
    BE01Customer identification does not match the stated account
    BE09Invalid country
    CH03Value for «Requested Execution Date» and/or «Requested Collection Date» is too far in the future
    CH04Value for «Requested Execution Date» and/or «Requested Collection Date» is too far in the past
    CH07Element cannot be used in B and C level
    CH11Value for «Creditor Identifier» is incorrect
    CH15Content of «Remittance Information/Structured» is more than 140 characters
    CH16Element content is formally incorrect
    CH17Element is not permitted
    CH20Number of decimal points is not compatible with the currency
    CH21Required mandatory element missing
    CURRIncorrect currency
    DT01Invalid date
    DT06Execution date is set to the next possible bank workday/postal workday (this code does not lead to a rejection and serves only for information purposes)
    DU01Value «Message Identification» is not unequivocal
    DU02Value «Payment Information Identification» is not unequivocal
    DU05Value «Instruction Identification» is not unequivocal
    NARRIncorrect file format
    RC01Incorrect Bank Identifier

    If the error code shown for you is not included in the list, please contact us:
    E-Serviceline: +41 61 266 36 36

  • What are camt notices and how are they different?

    Camt notices (Cash Management notices) are used for reporting to the customers. They supplement the previous SWIFT notice types. Up to now there are three different cash management notices:

    ISO 20022 notice
    Use
    SWIFT equivalent
    camt.052
    Account activity
    MT942, MT941
    camt.053 Daily statement
    MT940, MT950
    camt.054 Debit / credit memo
    MT900, MT910
  • Can I still retrieve notices in SWIFT format?

    The previous SWIFT notices (e.g., MT940, MT571, etc.) will continue to exist and will not be replaced. The data available in E-Banking can be requested/retrieved as SWIFT or camt notices.

BESR Download

  • How can I collect BESR data?

    The BESR incoming payments can be collected as BESR data. The BESR data of a specified account are available as required by the person authorised under the therefore decisive agreements for BKB E-Banking and can be collected by him or her. BESR data already received can be downloaded again under the function “Old Data”. Data from at least 270 days, can be received once again.