en (pf.ch/dok.pf) PF. Manual PostFinance ISO messages for banks [pacs messages]

Transcription

1 en (pf.ch/dok.pf) PF Manual PostFinance ISO messages for banks [pacs messages]

2 Customer service Enquiries concerning service ISO for banks PostFinance Ltd Customer Service Banks Mingerstrasse 20 CH-3030 Berne Tel Investigations PostFinance Ltd Enquiries Domestic PT EPO 3002 Berne Tel Fax Postal address for backup delivery (productive processing) via CD PostFinance Ltd Payment Processing Engehaldenstrasse Berne Tel Fax Opening hours Mondays to Fridays 8 a.m. until 12 noon and 1.30 p.m. until 5 p.m. Version October 2015 Manual PostFinance ISO messages for banks [pacs messages] Version October /32

3 Contents 1. General information Target group Applicable regulations and manuals Application Prices and conditions Definition of terms Legal 7 2. Range of services General Migration and parallel phase Migration scenarios Fallback Incoming and outgoing delivery channels Backup channel Definition of a backup event Services for incoming and outgoing deliveries of backup data Data suppliers Settlement of payments and prices Settlement account for payment orders and payment returns Fee account Number of transactions Currency Reconciliation of account statements Requirements, test and commissioning Participation requirements Testverfahren, Empfehlungen von PostFinance Commissioning Alteration of the bank s master data Cancellation Cancellation of the service by the bank Cancellation of the service by PostFinance Description of the incoming delivery as per ISO service Placing payment orders Payment orders Outpayment orders Data entry Reference information Sender details Requested settlement date / due date Delivery and processing times Cancellations Processing of payment orders Checking of orders Checking for duplicates Status messages for payment orders submitted Sufficient funds in the account and multiple debiting attempts Order processing Payment returns pacs Status messages from banks to PostFinance 25 Manual PostFinance ISO messages for banks [pacs messages] Version October /32

4 5. Description of the outgoing delivery as per ISO service Notification of payment receipts ISR payments Customer payments in general (IS, transfers, etc.) Salary payments Times of outgoing deliveries Entries Status messages from banks to PostFinance Notification of charges Payment returns Entry of pacs Status messages for payment returns Technical specifications Interbank messages Data carriers and recordings for the backup channel Data exchange via SFTP 32 Manual PostFinance ISO messages for banks [pacs messages] Version October /32

5 1. General information 1.1 Target group The present document is relevant to banks in the Swiss financial center that make use of the PostFinance Ltd service ISO messages for banks [pacs messages]. 1.2 Applicable regulations and manuals Unless the manual PostFinance ISO messages for banks [pacs messages] and its attachments contain special provisions, the following and currently valid regulations apply: Conditions of participation in PostFinance ISO messages for banks [pacs messages] General terms and conditions of participation of PostFinance Prices and conditions for banks Details on the technical implementation of ISO messages are described in the Technical definitions Implementation Guidelines PostFinance ISO messages for banks [pacs messages] document. Conditions of participation, manuals, prices and conditions for banks and implementation guidelines can be downloaded from w ww.postfinance.ch/banks-documents. The guidelines in this manual are binding for banks. 1.3 Application Applications for the ISO incoming delivery and ISO outgoing delivery services must be submitted separately by completing the relevant registration forms, which are available at w ww.postfinance.ch/banksdocuments. The application is legally valid as soon as the respective financial institution receives a positive letter of confirmation from PostFinance. 1.4 Prices and conditions PostFinance is entitled to remuneration for the services provided by it, in accordance with the price list for banks, as amended. Currently valid prices for the PostFinance ISO messages for banks [pacs messages] service can be downloaded from w ww.postfinance.ch/ banks-documents. The prices accrued are invoiced on the first bank working day of the following month. The bank must ensure that there are sufficient funds available in the relevant account. Following invoicing of prices, there are several possibilities for settlement (see section 2.6.2) Manual PostFinance ISO messages for banks [pacs messages] Version October /32

6 1.5 Definition of terms Term Customer payment Payment return Status message Payment order A level B level C level ECA-F ECA-I ISR EPO IBAN ISO ISO pacs BIC PF FI SIC Bank working day XML Debtor Instructing agent Creditor Instructed agent PT Definition pacs.008 pacs.004 pacs.002 Payment orders are used by the bank to transmit one or more customer payments to PostFinance. Payment orders are transmitted to PostFinance with a pacs.008 message. pacs.008/002/004: Message level, element Group header pacs.008: Payment or transaction level pacs.002: Underlying message and status information, element Original group information and status. pacs.004: Payment return or transaction level, element Transaction information. Electronic credit advice, fully entered Electronic credit advice, with image Inpayment slip with reference number Electronic payment order International bank account number International Organization for Standardization The International Organization for Standardization abbr. ISO is the international association of standardization organizations which works out international standards in various areas. UNIFI Standard (UNIversal Financial Industry message scheme) Under the name of ISO 20022, the International Organization for Standardization (ISO) has issued a library of new message types in the financial sphere on the basis of XML syntax. Payments Clearing & Settlement Bank identifier code, SWIFT address PostFinance Ltd Financial institution SIC payment system, operated by SIX Interbank Clearing Mondays to Fridays, except public holidays for Berne (e. g. 1 May) Extensible markup language (XML) is a file format. An individual or company that is a customer of a financial institution and whose account is being debited. An instructing agent is a participant in payment transactions whose account is being charged with a transaction. Depending on the message flow, this can be a financial institution or PostFinance as the system operator. An individual or company which is a customer of a financial institution and whose account is being credited. An instructed agent is a participant in payment transactions whose account is being credited. Depending on the message flow, this can be a financial institution or PostFinance as the system operator. Payment transactions Manual PostFinance ISO messages for banks [pacs messages] Version October /32

7 1.6 Legal All rights are reserved for the present document, including photo - me chanical reproductions, storage on electronic media and translations into foreign languages. This document has been prepared with the greatest possible care; however, errors and inaccuracies cannot be completely ruled out. PostFinance cannot assume legal responsibility or liability of any kind for errors occurring in this document and their possible consequences. PostFinance reserves the right to modify the present document as required at any time and without prior notice. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

8 2. Range of services 2.1 General All banks in Switzerland will convert their various payment transaction standards to a common and internationally valid standard ISO by the middle of The harmonization of payment transactions in Switzerland is a project being implemented by the entire Swiss financial center. PostFinance is playing an active part in shaping the future of Swiss payment transactions and offers financial institutions the PostFinance ISO messages for banks service with the following characteristics: Incoming delivery as per ISO On this basis, a financial institution can transmit its payment transactions in favour of PostFinance customers and customers of other financial institutions to PostFinance directly. This service corresponds to the current EPO service for banks. Application Input (FI-PF) / Output (PF-FI) ISO message Customer payments Input (FI-PF) pacs.008 Payment return(s) Output (PF-FI) pacs.004 Status message Output (PF-FI) pacs.002 Status message Input (FI-PF) 1 pacs Input (FI-PF) optional: pacs.002 as confirmation of pacs.004 The following illustration shows the message flows between banks and PostFinance with incoming delivery as per ISO 20022: Ordering bank lnstructing agent Interbank payments for channel PostFinance pacs.008 FItoFI CustomerCreditTransfer pacs.002 FItoFI PaymentStatusReport PostFinance Instructed Agent Validation Processing of payment returns pacs.004 PaymentReturn Verarbeitung Processing andund Settlement settlement optional: pacs.002 FItoFI PaymentStatus Report Manual PostFinance ISO messages for banks [pacs messages] Version October /32

9 Outgoing delivery as per ISO On this basis, PostFinance delivers its payment transactions in favour of a financial institution to the financial institution directly. This service corresponds to the current ISR/ECA-F service for banks. Application Input (FI-PF) / Output (PF-FI) ISO message Customer payments Output (PF-FI) pacs.008 Payment return(s) Input (FI-PF) pacs.004 Status message Output (PF-FI ) pacs.002 Status message Input (FI-PF) 1 pacs Input (FI-PF) optional: pacs.002 as confirmation of pacs.008 The following illustration shows the message flows between banks and PostFinance with outgoing delivery as per ISO 20022: PostFinance lnstructing agent Outgoing delivery of interbank payments Processing of payment returns pacs.008 FItoFI CustomerCreditTransfer optional: pacs.002 FItoFI PaymentStatus Report pacs.004 PaymentReturn Receiving bank lnstructed agent Processing of payment receipts via channel PostFinance Validation following receipt Payment returns via channel PostFinance pacs.002 FItoFI PaymentStatusReport Manual PostFinance ISO messages for banks [pacs messages] Version October /32

10 2.2 Migration and parallel phase The productive introduction of the ISO service for banks will take place in the first quarter of From this time on, a parallel operation of traditional services for incoming and outgoing deliveries and the new ISO service for banks will start. At the end of 2017, this parallel phase will end and the conventional services for incoming and outgoing deliveries will no longer be available. To be able to carry on using the services for incoming and outgoing deliveries from PostFinance, banks must have migrated to the new ISO based service by the end of the parallel phase at the latest. An exception is the outgoing delivery of ECA-I data which will continue to be exclusively offered in the conventional format Migration scenarios To provide banks with the greatest possible flexibility on switching to the ISO service for banks, PostFinance offers the following gradual migration options: a. Migration of incoming deliveries from EPO to ISO By activating the incoming delivery ISO service for banks, along with conventional formats, pacs messages can also be exchanged with PostFinance. b. Migration of outgoing deliveries from ECA-F to ISO By activating the outgoing delivery ISO service for banks, outgoing deliveries of payments received and payment returns will take place via pacs messages only. ISR payments received are an exception (see below). c. Migration of outgoing deliveries from ISR to ISO The migration of outgoing deliveries from ISR participant accounts is implemented via activation of the outgoing delivery ISO service for banks on the ISR participant account. The migration to pacs messages can be implemented on every ISR participant account individually. Incoming and outgoing delivery migrations are independent of one another and can take place at different times. Upon expiry of the parallel phase, incoming and outgoing deliveries will only be possible via pacs messages. PostFinance leaves it up to banks to decide how they will stage the migration to the ISO service for banks Fallback A fallback option exists if, after migrating to ISO messages, message processing problems arise that cannot be immediately resolved. The fallback scenario varies according to the service: a) ISO incoming delivery: A fallback from ISO messages to EPO is possible at any time after migration. If one or more payment orders were successfully processed in ISO format before the fallback, it is important to make sure that these payments are not submitted again in the old format (no multiple-format duplicate verification option). Manual PostFinance ISO messages for banks [pacs messages] Version October /32

11 b) ISO outgoing delivery: The fallback from ISO messages to ECA-F/ISR messages must be arranged with the PostFinance Customer Service. The fallback must be initiated as quickly as possible, and by 10 a.m. at the latest, so that the master data can be migrated in a timely manner. The replication time for the fallback to the old format is two bank working days. This means that on the current and following bank working day, additional ISO messages will be delivered and the processing of these payments must be guaranteed. A new delivery of the payments delivered in ISO format is not possible in ECA-F/ISR format. If the fallback is initiated after 10 a.m., the replication time may be extended by an additional bank working day. 2.3 Incoming and outgoing delivery channels All the supported ISO messages can be exchanged with PostFinance via the following channels: FDS (File Delivery Services) - C:D (Connect:Direct) - SFTP (Secured File Transfer Protocol) SWIFT FileAct CD backup as a backup channel The technical information for data exchange via SFTP is given in section 6.3. Please contact your customer advisor or the Customer Service Banks regarding data exchange via Connect:Direct or SWIFT FileAct. 2.4 Backup channel As an additional service, PostFinance also offers incoming and outgoing deliveries of backup data on compact disc (CD) Definition of a backup event A backup event exists if: the requisite systems of the financial institution for default networkbound data exchange with PostFinance are not available for an indefinite or extended period of time, the systems of the financial institution are available but default network-bound data exchange with PostFinance is not possible for an indefinite or extended period of time for other reasons (problems in the public network, system failure at PostFinance) Services for incoming and outgoing deliveries of backup data The following services are offered: Incoming delivery as per ISO If a backup event occurs, the pacs.008 order data can be sent in on CD. The decision as to whether or not to use incoming deliveries of backup data on CD rests exclusively with the bank. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

12 The following points must be borne in mind: Initialization of incoming deliveries of backup data must always be agreed with the customer service department for banks and must be confirmed in writing (fax or or letter). The CD with the order data must be received by 14:00 on the due date at PostFinance, payment processing department. After the fault has been resolved, orders sent in on CD must not be sent in again via the standard channel or any other channel. Otherwise, double processing cannot be ruled out. Payment returns are sent out on CD. The CD is sent to the delivery address provided by the bank on application. The financial institution is responsible for updating such delivery addresses as required. Delivery usually takes place on the next bank working day. Outgoing delivery as per ISO If a backup event occurs, the credit data can be sent out on CD. The decision as to whether or not to use outgoing deliveries of backup data on CD can be taken either by the bank or PostFinance. The following points must be borne in mind: If the bank wishes to have an outgoing delivery of backup data, it can request this via the customer service department for banks. If PostFinance initializes the outgoing delivery of backup data, the bank will be informed by phone or via beforehand. This information is delivered to the phone number or address provided by the financial institution on application. The bank is responsible for updating such details as required. The CD is sent to the delivery address provided by the bank on application. The financial institution is responsible for updating such delivery addresses as required. In the case of outgoing deliveries of backup data, delivery usually takes place on the next bank working day. Once the backup event ends, the partner must be informed of the following: - Backup initialization by the customer: the customer informs the customer service department for banks by phone. - Backup initialization by PostFinance: PostFinance informs the bank via . Payment returns can be sent in on CD. The CDs with the order data must be received by 14:00 on the due date of the payment return at PostFinance, payment processing department. The exchange of pacs.002 status messages via the backup channel is not supported. The technical framework conditions and features of the backup solution on CD are described in section 6 Technical specifications. 2.5 Data suppliers A financial institution can arrange for transmission and receipt of data to be handled by a third-party provider, a so-called data supplier. Details of the data supplier must be provided on application. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

13 2.6 Settlement of payments and prices Settlement account for payment orders and payment returns With incoming delivery as per ISO 20022, the settlement of payment orders can be controlled by specifying the settlement account in the pacs.008 message. If no settlement account is provided, the default account provided on application will be used. With outgoing delivery as per ISO 20022, the respective credit postal account of the institution is supplied as the IBAN Fee account All prices are booked in CHF into the CHF fee account specified on application. If no separate fee account is specified, prices will be booked into the settlement / default account of the bank. 2.7 Number of transactions The maximum number of transactions per file is defined as follows: Service characteristics ISO message Number Incoming delivery as per ISO Outgoing delivery as per ISO pacs.008, pacs pacs.008, pacs Currency All messages exchanged with PostFinance must contain one currency only (so-called currency purity). To guarantee smooth processing, the currency of the message must correspond to the currency of the settlement account (currency of the postal account). 2.9 Reconciliation of account statements The bank receives on its account statement a collective debit or credit advice for each incoming/outgoing message (pacs.008/pacs.004). For recon - ciliation purposes, PostFinance additionally supplies on the account statement the message identification of the incoming/outgoing messages. If a bank detects a discrepancy, customer service must be informed of this immediately. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

14 2.10 Investigations Incoming investigation orders must be submitted to PostFinance via MT199. Notification of the result of the investigation is provided via MT196. The following MT199 details must be included with the delivery: Field ID Short description Format Ref. Content / notes 20 Transaction reference 16x ma Transaction reference of the bank number 21 Related reference 16x ma Banks ISO Narrative description of the message to which the query relates Second line Third line Fourth line 35* 50x op /n/ Message about the investigation where n = code, existing SWIFT rules /3/ OUR PAYMENT DATED {DD,MM,YYYY } (due date) Recommended date format {currency submitted} {original amount} IBAN of debit account from original record Fifth line ma Transaction ID from pacs.008 Sixth line IBAN of credit account Seventh line ISR customer number Eighth line Name of contact person for queries and responses Ninth line Telephone number (contact person) Tenth line Fax number If investigation orders cannot be processed as mentioned above, they may exceptionally be transmitted via or fax (see contact point, page 2). Manual PostFinance ISO messages for banks [pacs messages] Version October /32

15 3. Requirements, test and commissioning 3.1 Participation requirements Participation in the PostFinance ISO messages for banks service is only available to financial institutions. To apply for this service, it is mandatory for a financial institution to have at least one active postal account in CHF (for payment processing and/or settlement of fees) and a SWIFT address (BIC). If the financial institution does not wish to have a specific fee account, the default account must be in CHF. 3.2 Test method, recommendations of PostFinance Tests are carried out to check the pacs messages issued by the financial institution and the processing sequence. An end-to-end test on the PostFinance test platform is compulsory before the productive activation of the service. PostFinance can release banks from the testing obligation (for example in cases where the software used has already been tested successfully in a similar configuration). The following testing options are available free of charge: 1. PostFinance validation platform for banks Verification of the formal correctness of ISO interbank messages (pacs messages). Message verification involves ensuring XML schema compliance and the technical correctness of the message. Users can register for the validation platform online at /validation.iso-payments.ch/pf. 2. Test platform for banks Comprehensive test solution that offers the additional option of simulating a range of technical use cases in addition to message verification (as on the validation portal). Register and use the test platform online at /isotest.postfinance.ch/banks. More information about testing options and test conditions can be found in the Testing PostFinance ISO messages for banks factsheet at w ww.postfinance.ch/banks-documents. 3.3 Commissioning Commissioning / activation of incoming delivery as per ISO and outgoing delivery as per ISO services can take place only after successful application (see section 1.3) and successfully conducted tests (see section 3.2). Commissioning / activation is conducted by direct arrangement between the bank and PostFinance. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

16 3.4 Alteration of the bank s master data The following alterations have to be advised to the customer service department for banks in good time: In writing Settlement / default account for debits and credits Fee account Contact details (address / / telephone) Change of incoming / outgoing delivery channel Change of processing point Details of return partner By phone Disabling / enabling multiple debiting attempts 3.5 Cancellation Cancellation of the service by the bank Cancellation must be communicated in writing and include a legally valid signature. The cancellation letter must state the date of termination and, if possible, the reason for cancellation. After the date of cancellation, the bank can no longer transmit orders to PostFinance and no longer receives pacs notifications Cancellation of the service by PostFinance PostFinance reserves the right to cancel the business relationship with the customer at any time. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

17 4. Description of the incoming delivery as per ISO service With its PostFinance ISO messages for banks, incoming delivery as per ISO service, PostFinance provides banks with the option to transmit domestic customer payments to PostFinance directly. 4.1 Placing payment orders Payment orders With a payment order (financial institution customer credit transfer / pacs.008), a bank can trigger the following payment types in one file at the same time: ISR payments (ESRPMT) Customer payments in general (CSTPMT) Salary payments (SLRPMT) Outpayment orders (OUTPMT) The technical definitions of the ISO messages are listed in the Technical definitions Implementation Guidelines PostFinance ISO messages for banks [pacs messages] document and can be downloaded from w ww.postfinance.ch/banks-documents. To ensure the different payment types can be processed correctly, all message elements must be filled in correctly. The following tables show the characteristics of specific payment types at the transaction level (B level of the message). Manual PostFinance ISO messages for banks [pacs messages] Version October /32

18 ISR payments Processing of payments in favour of a PostFinance business customer that has its own ISR participant number (direct ISR participation of the business customer). Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory ESRPMT Creditor Mandatory Name or, if not available, NOTPROVIDED Creditor account Mandatory./Id/Othr/Id/: ISR participant number./id/othr/schmenm/cd/prtry: ISRPT Creditor reference Mandatory ISR reference number Creditor agent Mandatory PostFinance BIC (POFICHBEXXX) or BC number (090002) Processing of payments in favour of a business customer of a bank that processes the ISR service via its bank (indirect ISR participation of the business customer; two-stage document). Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory ESRPMT Creditor agent Mandatory BIC or BC number of creditor agent Creditor reference Mandatory ISR reference number Creditor agent account (proprietary) Mandatory./Id/Othr/Id: ISR participant number of the receiving creditor agent (bank) Creditor Mandatory Name or, if not available, NOTPROVIDED Manual PostFinance ISO messages for banks [pacs messages] Version October /32

19 Customer payments in general (IS, transfers, etc.) Processing of customer payments in favour of a PostFinance business or private customer. Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory CSTPMT Creditor Mandatory Name of creditor Creditor account Mandatory With postal account number:./id/othr/id/: postal account number./id/othr/schmenm/cd/prtry: PCACC With IBAN of the postal account:./id/iban/: IBAN Creditor agent Mandatory PostFinance BIC (POFICHBEXXX) or BC number (090002) Processing of customer payments in favour of a business or private customer of a bank. Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory CSTPMT Creditor Mandatory Name of creditor Creditor account Mandatory With IBAN:./Id/IBAN/: IBAN With proprietary account format:./id/othr/id/: account number in proprietary format./id/othr/schmenm/cd/prtry: PRTRY With IS reference number./id/othr/id/: IS reference number with exactly 27 digits./id/othr/schmenm/cd/prtry: PSREF Creditor agent Mandatory BC number or BIC of the creditor agent Creditor agent account (proprietary) Optional./Id/Othr/Id: postal account number of receiving creditor agent (bank). It is recommended to omit this detail and to send in the details of the creditor agent with the BC number or BIC. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

20 Salary and pension payments Processing of salary and pension payments of private customers of PostFinance and banks. In the event of a transfer to a third-party bank, payments sent by banks to PostFinance with the code SALA are also called salary payments. Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory SLRPMT Category purpose (code) Mandatory Code: SALA (salary payment) or PENS (pension payment) Other message elements are the same as for customer payments (see section ) Outpayment orders Processing of cash payments in Switzerland and Liechtenstein (in CHF only). Please note: this service will be discontinued from 31 December Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory OUTPMT Creditor Mandatory Name and address of creditor Creditor agent Mandatory PostFinance BIC (POFICHBEXXX) or BC number (090002) Data entry The bank is responsible for the content-related and formal correctness of the data delivered by it in accordance with this manual and the Technical definitions Implementation Guidelines PostFinance ISO messages for banks [pacs messages]. PostFinance checks account numbers, ISR customer numbers and reference numbers by means of the respective check digits and rejects incorrect payments. Incorrect data can lead to delays, time-consuming investigations, rejections of the entire order or cancellation of individual or all payments Reference information Orders and notifications contain various references. An overview of these references can be found in the Technical definitions Implementation Guidelines PostFinance ISO messages for banks [pacs messages]. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

21 4.1.5 Sender details If differing sender details are to be transmitted to the beneficiary (e. g. settlement of a debt on behalf of a third party), details of the ordering party can be provided in the Ultimate debtor element. Depending on the format of the outgoing delivery, it is not always guaranteed that such informa tion will be forwarded. Additional information can be found in the Technical definitions Implementation Guidelines PostFinance ISO messages for banks [pacs messages] Requested settlement date / due date The debit value date (requested settlement date) can be 90 calendar days in the past and a maximum of five bank working days in the future. Messages which do not comply with this rule will be rejected. For messages with the requested settlement date in the past, the value date will be changed to the current bank working day. If the requested settlement date is not a bank working day, the value date of the message will be changed to the next possible bank working day Delivery and processing times pacs.008 with due date Delivery including checking of the order must be completed by 24:00 on the day preceding the due date. It should be noted that orders take longer to check the higher the number of customer payments in the order. pacs.008 same day Messages can be delivered with the notation same day on bank working days. To ensure that processing can be carried out immediately on the day of incoming delivery, the interbank settlement date must be identical to the day of the incoming delivery. Delivery including checking of the order must be completed by 17:00 on the due date and sufficient funds must be available, accordingly. It should be noted that orders take longer to check the higher the number of customer payments in the order. If these requirements are not observed, orders will be executed on the next possible bank working day. Processing takes place from midnight up until 17:00 on an ongoing basis, with the exception of the period from 12:30 until the end of the Post- Finance end-of-day processing (TEV) at around 14:30/15:00. Messages delivered during this period will be processed immediately after the end of TEV Cancellations To cancel an entire order or individual payments, SWIFT message MT199 must be used. PostFinance responds to this query with a SWIFT MT196 message. Cancelling is not possible if PostFinance has already executed the payment order for which cancellation has been requested. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

22 4.2 Processing of payment orders The following illustration shows how payment orders submitted are checked and processed. PostFinance Bank pacs.008 Order checking Order checking Order correct? yes no pacs.002 RJCT pacs.002 ACCP Internal processing Internal processing Checking for availability of funds Sufficient funds available? yes no MDA activated? yes no yes no First check? no Further check? yes pacs.002 RJCT pacs.002 PDNG Availability of funds in the account and multiple debiting attempts (MDA) Internal processing Internal processing MDA carried out? pacs.002 RJCT Internal processing no yes pacs.002 ACSC Internal processing Collective debit Total Interbank Settlement Amount Order processing Checking of single transaction Can payment be processed? yes no pacs.004* Payment return Internal processing Processing of single transaction Further single transactions? yes no * For pacs.004: All single transactions from one or more orders (pacs.008) which cannot be processed are collected and returned to the bank as a payment return package (pacs.004). Manual PostFinance ISO messages for banks [pacs messages] Version October /32

23 4.2.1 Checking of orders On checking an order, various aspects of the message are examined. To ensure an order can be checked, it must be syntactically correct, i. e. the order must comply with the latest version of the current pacs.008 XML matrix (XSD). If this requirement is not met, the order cannot be machineprocessed. Syntactically correct orders undergo further checking. If one of these checks fails, the message will be rejected as a whole with a corresponding status message (pacs.002). The following checks are carried out: Instructing agent/ instructed agent Additional checking Checking the currency A check is performed as to whether the participant s details provided are clear and correct. A check is performed as to whether the number of transactions provided (A level) corresponds to the actual number of transactions in the payment order (B level) and are within the defined limits. A check is also performed as to whether the total amount of all single transactions (B level) matches the total settlement amount (A level) of the order. A check is performed as to whether the currency specified is correct and whether the message is pure in currency terms Checking for duplicates To prevent multiple processing, each message is checked for possible duplicates. Checking for possible duplicates takes place at the message level and single transaction level. The following element combination may occur no more than once each over a period of five pre-value dates, the actual value date, and 30 value dates in the past 1 : Level Message (A level) Element combination Message Identification (<MsgId>) and instructing agent (<InstrgAgt>) Several messages with the same identifiers as mentioned above cannot be processed automatically. Such messages will be processed later by Post- Finance and, in case of doubt, cancelled (via pacs.002). Level Single transaction (B level) Element combination Transaction Identification (<TxId>) and instructing agent (<InstrgAgt>) Several messages with the same identifiers as mentioned above cannot be processed automatically. Such payments will be processed later by Post- Finance and, in case of doubt, cancelled (via pacs.004). 1 For a definition of elements, please refer to the technical definitions PostFinance ISO messages for banks Manual PostFinance ISO messages for banks [pacs messages] Version October /32

24 4.2.3 Status messages for payment orders submitted Status messages (pacs.002) are used to notify the processing status of a pacs.008. A status message does not provide information on the status of a single transaction of a payment order. PostFinance sends a pacs.002 message for each pacs.008. The following status types are possible: Accepted (ACCP): the message is correct and can be processed. Rejected (RJCT): the message is not correct and cannot be processed, or the message was cancelled before execution, or there are insufficient funds available in the account (if multiple debiting attempts are not requested, see section 4.2.4). Pending (PDNG): there are insufficient funds in the account and a further attempt at processing will be made (see also section for more on this). Accepted settlement completed (ACSC): there are now sufficient funds in the account and the order can be processed. PostFinance provides the information on the status reason of ISO as per the Payments external code lists (see w ww.iso20022.org) in the Status reason information element Sufficient funds in the account and multiple debiting attempts The customer undertakes to ensure at all times that the balance of its debit account is such that incoming orders can be debited. A check is carried out for each message as to whether there are sufficient funds in the account. With the multiple debiting functionality, orders with insufficient funds in the account undergo further debiting attempts at regular intervals on a daily basis. At the first unsuccessful attempt at debiting, a status message with PDNG status is generated. As soon as sufficient funds are available in the account, the order will be executed and a status message with ACSC status will be generated. If insufficient funds are available on the requested due date, the order will be rejected and a status message with RJCT status will be generated. If multiple debiting attempts are not required for certain orders, please contact your account manager. In such cases, orders with insufficient funds available will be rejected Order processing After successful checking of the order and the availability of funds in the account, the total settlement amount will be debited from the account of the instructing agent. Debiting is carried out according to the gross principle, i.e. inclusive of all single transactions, even ones that cannot be executed. Cancelled transactions are credited again via pacs.004. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

25 On the execution date: Orders (pacs.008) of the bank are debited as a collective entry Credit transfers / salary payments are credited to a postal (giro) account Credit transfers / salary payments in favour of bank customers are credited to the bank s postal account or sent to SIC for processing Inpayment slips with reference number (ISR / ISR+) are processed and credited to customers on the next working day Outpayment orders are forwarded to post offices and paid out on the following day Payment returns (pacs.004) are credited to the bank as a collective entry Payment returns pacs.004 PostFinance sends payment returns (pacs.004) to a bank to advise it of customer payments that have already been debited from an account via a collective debit during order processing but which could not subsequently be processed (e. g. invalid account number). Payment returns are always collected in the form of packages, returned to a bank at regular intervals (hourly basis) and then booked into the postal account of the bank by means of a collective credit. A payment return package may contain payment returns from several payment orders submitted. A financial institution can, by arrangement with PostFinance, define the delivery of payment return data to a specific return partner. PostFinance delivers the information on the reason for the payment return of ISO in accordance with the Payments external code lists (see w ww.iso20022.org) in the Return reason information element. The reason is also provided in text form Identification of the original payment To ensure that the original payment can be identified as transmitted in the payment order, PostFinance provides the following information on the original payment with the payment return: Original message identification Original message name identification Original instruction identification Original transaction identification Original settlement amount Status messages from banks to PostFinance Status messages (payment status report / pacs.002) can be used by banks for outgoing deliveries of payment returns to report back to PostFinance the status of the message received. If a message is free of errors, sending a status message is optional. If a message contains errors, a corresponding status message can be sent to PostFinance or operational support can be contacted. The following status types are possible: Accepted (ACCP): the message is correct and can be processed. Rejected (RJCT): the message is incorrect and cannot be processed. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

26 5. Description of the outgoing delivery as per ISO service With its PostFinance ISO messages for banks, outgoing delivery as per ISO service, PostFinance offers banks the option of notification of customer payments by PostFinance via pacs.008 directly. PostFinance Bank IS, ISR, etc. Entry Outgoing delivery pacs.008 Checking Error handling pacs.002 RJCT or call PostFinance yes File incorrect? no Processing pacs.002 ACCP Internal processing Entry pacs.004 (payment return) of all unprocessable payments no Could all payments be processed? yes pacs.002 ACCP Manual PostFinance ISO messages for banks [pacs messages] Version October /32

27 5.1 Notification of payment receipts Notification of payment receipts into a postal account takes place via the ISO message Financial institution customer credit transfer / pacs.008. PostFinance notifies banks via pacs.008 of credits from: electronic PostFinance channels banking networks (SIC/euroSIC, EUROGIRO, SWIFT) post offices and payment orders (ISR and fully entered red inpayment slips) For this purpose, the following payment types are possible: ISR payments (ISRPMT) Customer payments generally (CSTPMT) Salary payments (SLRPMT) All payments notified via pacs.008 are documented in the message individually (B level). The bank receives notifications for each settlement account (postal account including attached ISR participant s account number) on a daily basis. The following tables show the characteristics of specific payment types at transaction level (B level of the message) of transactions sent out ISR payments Processing of payments in favour of a business customer of a bank that processes the ISR service via its bank (indirect ISR participation of the business customer; two-stage inpayment slip). Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory ESRPMT Creditor agent Mandatory BIC or BC number of the creditor agent Creditor reference Mandatory ISR reference number Creditor agent account (proprietary) Mandatory./Id/Othr/Id: ISR participant number of the receiving creditor agent (bank) Creditor Mandatory Name or, if not available, NOTPROVIDED Manual PostFinance ISO messages for banks [pacs messages] Version October /32

28 5.1.2 Customer payments in general (IS, transfers, etc.) Processing of customer payments in favour of a business customer or private customer of a bank. Message element at single transaction level Mandatory/ optional Content Payment type (proprietary) Mandatory CSTPMT Creditor Mandatory Name (or BIC) of creditor Creditor account Mandatory With IBAN:./Id/IBAN/: IBAN With proprietary account format:./id/othr/id/: account number in proprietary format or IS reference number./id/othr/schmenm/cd/prtry: PRTRY Creditor agent Mandatory BC number or BIC of the creditor agent Creditor agent account (proprietary) Optional./Id/Othr/Id: postal account number of the receiving creditor agent (bank) Salary payments Salary payments of private bank customers are usually processed via the SIC channel. 5.2 Times of outgoing deliveries PostFinance books and notifies payment receipts in several cycles of outgoing deliveries: First outgoing delivery: start at 00:01, collection of data by 3:00 at the latest Second outgoing delivery: start at 5:00, collection of data by 8:00 at the latest Third outgoing delivery: start at 10:00, collection of data by 11:00 at the latest Fourth outgoing delivery: start at 14:00, collection of data by 15:00 at the latest 5.3 Entries Payment receipts (collective credit for each pacs.008 sent out) go into the postal account defined by the bank. All transactions in favour of banks received after 16:00 have their value dates changed to the next bank working day. The value date is basically identical to the date of the outgoing delivery. If, in certain constellations, different value dates are generated (e. g., receipts after the last outgoing delivery with a value date of the same day, which are not notified until the following day with the first outgoing delivery only), a collective entry is generated for each value date. Manual PostFinance ISO messages for banks [pacs messages] Version October /32

29 5.4 Status messages from banks to PostFinance Status messages (payment status report / pacs.002) can be used by banks for outgoing deliveries of notification messages to report back to PostFinance the status of the message received. If a message is free of errors, sending a status message is optional. If a message contains errors, a corresponding status message can be sent to PostFinance or the operating support department can be contacted. The following status types are possible: Accepted (ACCP): the message is correct and can be processed. Rejected (RJCT): the message is incorrect and cannot be processed. Please note: payment receipts that have been notified for which a bank is unable to proceed with a credit (beneficiary unknown) must be returned to PostFinance as a payment return (pacs.004, see section Payment returns ). 5.5 Notification of charges Charges for rejections, cash deposits, full IS entries and subsequent processing of ISR+ are notified to the bank in the field for unstructured messages at the single transaction level (B level). The following combinations of rejection codes / payment types are possible: Price type Code Possible payment types Rejections RJC CSTPMT, ESRPMT Cash deposit fees CDC CSTPMT, ESRPMT Subsequent processing of ISR+ PPC ESRPMT Full IS entry FRC CSTPMT Invoicing and notification of prices takes place for each price type and not separately for each payment type. Details on the composition and structure of charging information can be found in the Technical definitions Implementation Guidelines PostFinance ISO messages for banks [pacs messages]. If the debtor has already left an unstructured message, this can be found in the first element for unstructured messages, and any charging information is found in the second element. If the debtor has not left a message, the charging information can be found in the first element. If the debtor transmits two elements with messages, the second element can be overwritten by information on charges. Message transmitted to PostFinance Auction xxx (up to a maximum of 140 characters) Message forwarded to a bank Element 1: Trainer auction Element 2: //CHRGS/CDC CHF 2.95/ No messages Element 1: //CHRGS/CDC CHF 2.95/ PPC CHF 0.70/ Manual PostFinance ISO messages for banks [pacs messages] Version October /32

30 5.6 Payment returns Banks can return payments that were received in pacs.008 messages to PostFinance via pacs.004 directly. If the payment return is free of errors and can be processed, the bank will be credited with the payment return amount. To ensure that the payment return can be processed by PostFinance as smoothly as possible, the following references from the original payment must be included with the delivery: Original message identification Original instruction identification Original transaction identification Furthermore, the following information must be contained in the Additional information field: Element pacs.004 (C level) Additional information Structure <Error text. Value date of original payment. (Additional investigation ID for ISR payments at the counter in the format NF-ID ZZZZZZZZZNX)> Example: BENEFICIARY UNKNOWN. VAL NF-ID NX Direct payment returns to PostFinance are free of charge. Payment returns with the ISO service can also be initiated via third parties (e.g. as A11 with advice code 9 via SIC/EuroSIC). Payment returns transmitted to PostFinance via a third party may incur additional costs. The instructions on how payment returns can be processed via third parties can be found in their corresponding specifications Entry of pacs.004 On the execution date: Payment returns (pacs.004) are debited from the bank as a collective entry. Returned transfers are credited to the sender s account or returned cash deposits are forwarded to a postal office for payment Status messages for payment returns PostFinance sends the bank a corresponding status message (pacs.002) for each payment return (pacs.004) transmitted. The following status types are possible: Accepted (ACCP): the message is correct and can be processed. Rejected (RJCT): the message is incorrect and cannot be processed. Manual PostFinance ISO messages for banks [pacs messages] Version October /32