en (pf.ch/dok.pf) PF. EPO manual Electronic payment order via file transfer

Transcription

1 en (pf.ch/dok.pf) PF EPO manual Electronic payment order via file transfer

2 Customer support Customer support for EPO Consulting & Sales Phone (CHF 0.08/min. from a landline) Customer Service Tel (CHF 0.08/min. from a landline) Fax postfinance.ch Withdrawal requests PostFinance Ltd Payment processing Engehaldenstrasse 35 CH-3030 Berne Tel Fax Enquiries PostFinance Ltd National Enquiries EPO Engehaldenstrasse 35 CH-3030 Berne Tel Fax Publication details PostFinance Ltd CH-3030 Berne Version November 2015 Manual EPO Version November /43

3 Table of contents 1. General information Target group Use of the manual Applicable provisions and manuals Registration Prices and conditions Definitions 7 2. Range of services offered How it works and process steps Data media Processing Multiple debit attempts Preconditions, testing and commissioning Preconditions Test procedures, PostFinance recommendations PostFinance test platform Productive customer test Commissioning Operation Delivery times, express orders and approval deadline Delivery times Express orders and urgent payments Approval deadline Issuing orders Data entry Number of transactions Order coverage Identification of collective orders and double processing checks Initial currency Test sums Checks for duplicates Priority execution type Account notification Salary payments Approval Due date Delayed receipt of data Cancellations/Changes Cancellation of the EPO by PostFinance Order notification Order notification for EPO Delivery time Order confirmation Execution confirmation Individual confirmation Processing message Modification of customer data Enquiries Term and notice 23 Manual EPO Version November /43

4 5. Technical specifications Supported ISO versions Transactions and payment types EPO in TXT format EPO ISO in XML format Authorized characters Additional technical information on consistency, key fields and AOS from PostFinance Sender details Additional technical information on the Swiss Implementation Guidelines (pain.001 and pain.002) Samples and examples Example files of XML formats Order confirmation (only for EPO in TXT format) Execution confirmation Transactions with price electronic payment order EPO (only for EPO in TXT format) Individual confirmation electronic payment order EPO Processing message electronic payment order EPO Processing message (high format) 43 We have marked all the sections that underwent changes to content in November 2015 with a line in the margin. Manual EPO Version November /43

5 1. General information 1.1 Target group PostFinance Ltd provides its customers with the Electronic Payment Order (EPO) service for the transmission of accounts payable payments via file transfer. EPO facilitates processing of all accounts payable payments, including salary payments, in Switzerland as well as abroad. EPO orders can be placed either in TXT or ISO XML format. The EPO via file transfer is aimed at business customers. The EPO via e-finance (upload) can be used by both business and private customers. 1.2 Use of the manual The EPO product characteristics are documented in the present manual. As part of the harmonization of payment transactions in Switzerland, only EPOs in ISO XML format (pain.001) will be processed as of Up until this point, EPO formats will be offered in parallel. PostFinance advises switching to the ISO format in good time. Accounts payable management Accounts receivable management Cash and liquidity management Factsheet EPO Factsheet OSR Factsheet ISR Factsheet CH-DD Factsheet SEPA-DD Factsheet Electronic account documents Management PostFinance Ltd user manual on the harmonization of payment transactions Manual EPO Manual OSR Manual ISR Manual CH-DD Manual SEPA-DD Manual Electronic account documents Specialist Test documents PostFinance Ltd test platform Implementation Swiss financial center Implementation Guidelines for Transfers Implementation Guidelines for CH Direct Debits Swiss Usage Guide Business Rules Implementation Guidelines for SEPA Direct Debits Customer Bank Validation Platform Implementation Guidelines for Cash Management Management and specialist Implementation This overview shows a selection of the most important documents relating to payment transactions. Other documents can be found on the Internet at w ww.postfinance.ch/manuals; version October 2015 The Swiss financial center provisions (Implementation Guidelines for Transfers, and Business Rules) take precedence over the EPO manual. Manual EPO Version November /43

6 1.3 Applicable provisions and manuals Unless otherwise specified in the EPO manual and appendix, the following conditions apply to transactions: Subscriber Conditions for Electronic Services PostFinance General Terms and Conditions and Subscriber Conditions The Subscriber Conditions for Electronic Services and the EPO manual can be consulted and downloaded at w ww.postfinance.ch/epo. PostFinance s General Terms and Conditions and Subscriber Conditions can be downloaded at w ww.postfinance.ch. When transmitting EPO ISO (Payment Customer Credit Transfer Initiation/pain.001), the ISO definitions generally apply as set out in the Swiss Business Rules for Payments and Cash Management for Customer-to-Bank Messages and Implementation Guidelines for Customer-to-Bank messages for payment transactions. In this manual only provisions relating to the processing of pain.001 and that are not covered by the above-mentioned documents will be described. For the sake of convenience, the manual uses the term EPO or order. Unless indicated otherwise, the provisions apply to both formats (TXT and XML). The ISO definitions as set out in the Swiss Business Rules and Implementation Guidelines can be downloaded at w ww.iso-payments.ch. 1.4 Registration Written registration is required for the EPO via file transfer. Authorization for the EPO upload via e-finance can be requested when registering for e-finance or activated directly in e-finance. Please contact your customer advisor to register. 1.5 Prices and conditions The current prices are listed on w ww.postfinance.ch or will be provided on request by your customer advisor. The prices for all PostFinance services that have been used will be charged at the end of each month. Manual EPO Version November /43

7 1.6 Definitions Term Additional Optional Services (AOS) camt.054 International Organization for Standardization (ISO) ISO standard pain.001 pain.002 Swiss Post working day TXT and EPO in TXT format Extensible Markup Language (XML) XML Schema Definition (XSD) Definition Additional optional services in accordance with the ISO standard. These services may vary between various financial institutions. Cash Management Bank To Customer Debit Credit Notification: ISO message containing information on the executed payment orders or transactions. Corresponds to an execution confirmation or individual confirmation at PostFinance. The International Organization for Standardization (ISO) is the international association of organizations for standardization which develops international standards in various fields. The objective of the ISO standard is to accomplish the global harmonization of existing and new message standards across various areas of the financial industry. ISO not only includes payment transaction and account reporting messages, but also covers other areas, including securities trading, foreign trade and treasury. The Customer Credit Transfer Initiation XML message (pain.001) is used for electronic commissioning of transfer orders made by customers to the transferring financial institution. PostFinance uses the ISO message for electronic payment orders (EPO). Payment Initiation Customer Payment Status Report: ISO message used as a response to a pain.001 message. pain.002 is a processing message and contains OK/NOK and warnings. Swiss Post working days are weekdays from Monday to Friday. Exceptions are standard holidays (canton of Berne). If the due date specified by the customer is not a Swiss Post working day, the order/delivery will be executed on the next Swiss Post working day. PostFinance has developed a proprietary standard for transmission of electronic payment orders (see record structures for electronic services), which transmits payment data sequentially in a text file (TXT). Extensible Markup Language (XML) is a file format. An XML schema describes the elements and structure of an XML file. Manual EPO Version November /43

8 2. Range of services offered 2.1 How it works and process steps Customers use the EPO for transfers in Switzerland and abroad. The following diagram gives an initial picture of how an EPO works. 2) Invoice 3) Debtor 1) Creditor 5) Debit 4) EPO 7) Notification documents 6) Credit 1) Creditor Invoice issuer who makes out his invoice to the debtor. 2) Invoice The invoice issuer makes out open amounts by means of inpayment slips (including inpayment slips with reference number). 3) Debtor The debtor (private or business customer) can make use of the Post- Finance EPO service. The debtor can use the EPO to settle open invoices with the creditor (payment recipient). Payment orders can be prepared and entered directly in payment or financial accounting software. Payments can be transferred in a single step, and the software generates an EPO file. The file is generated in either TXT or ISO XML format. 4) EPO The debtor can transfer the EPO file either via e-finance or via file transfer for business customers (File Delivery Services, Telebanking Server TBS, H-Net and SWIFT FileAct). The EPO can be delivered in TXT or XML (ISO standard pain.001) formats until the day prior to the due date (Swiss Post working day). Orders can be withdrawn and modified until the evening before the due date. 5) Debit The total amount of all the payments included in the EPO will be debited from the customer s postal account. 6) Crediting The open invoice amount will be credited to the creditor after the EPO debit has been executed. Manual EPO Version November /43

9 7) Notification documents The debtor always receives the following documents from PostFinance: Account statement incl. monthly fees Processing message The following order notification documents are also available at the customer s request: order confirmation, execution confirmation, individual confirmation. 2.2 Data media The following media can be used to deliver EPOs: Private customers E-finance Business customers E-finance File Delivery Services (FDS) H-Net Telebanking Server (TBS) SWIFT FileAct Detailed information about data media can be found at w ww.postfinance.ch/filetransfer. 2.3 Processing Standard EPO processing uses the netting principle. EPO transactions refused by PostFinance are deducted from the total order amount and the corresponding net amount is debited to the debit account. At the customer s request, PostFinance can offer EPO processing according to the no-netting principle. This means that it is always the gross total order amount that is debited (incl. transactions that cannot be executed). Cancelled transactions are recredited the same day (same value date). For more information, please contact your customer advisor. Manual EPO Version November /43

10 2.4 Multiple debit attempts With this standard functionality, orders with insufficient cover are subjected to additional debit attempts each day over the next five Swiss Post work ing days. As soon as cover is available, the order is executed. If there is still no cover five Swiss Post working days after the desired due date, the order is rejected. If no multiple debit attempts are desired for all orders, this can be communicated accordingly to your account manager. In this case, the orders will be rejected immediately if there is insufficient cover. Express orders are not sent for multiple debit attempts but are always rejected if there is insufficient cover. Business customers with multiple debit attempts can deactivate the multiple debit once for this order in the order detail on e-finance using Change. In these cases the order is rejected if there is insufficient cover. In case of an EPO ISO in XML format, it is possible to suppress the multiple debit feature once for a certain order (B level) by entering the code NORETRY in the field Instruction For Debtor Agent at each C level (of the corresponding B level). Details are given in section Additional technical information on the Swiss Implementation Guidelines (pain.001 and pain.002). Manual EPO Version November /43

11 3. Preconditions, testing and commissioning 3.1 Preconditions Contractual details for the EPO service must be concluded so that Post- Finance customers can benefit from the test support service. Customers who need test support are recommended to contact the PostFinance Contact Center or their customer advisor directly. 3.2 Test procedures, PostFinance recommendations PostFinance has expanded its testing service with regard to the harmonization of Swiss payment transactions and allows customers to conduct tests independently on the test platform and to use PostFinance s productive customer test facilities. PostFinance advises its customers to complete the following two-stage test process: PostFinance test platform Customers can validate their pain.001 with the XSD schema on the test platform. The test platform automatically generates a report containing a detailed description of the validation results. PostFinance takes all its Additional Optional Services (AOS) into account for validation. After the pain.001 has been uploaded successfully, the customer has access to the pain.002 status report and to camt.054. These can be downloaded and processed. Best practice cases and the necessary resources for successfully switching to the ISO format are made available to customers on the test platform Productive customer test Upon successful completion of the format tests on the test platform, Post- Finance recommends carrying out further tests using the productive customer test (end-to-end) system. The first execution of the tests should be registered with the PostFinance Contact Center or the customer advisor. 3.3 Commissioning Once the recommended test activities have been completed successfully, pain.001 and the associated status and report messages can be put into productive operation. No further formalities are required. If problems arise with productive orders, users can contact PostFinance. Manual EPO Version November /43

12 4. Operation 4.1 Delivery times, express orders and approval deadline Delivery times PostFinance recommends submitting the order as early as possible to allow time for the handling of any errors signalled so that the faulty transactions can still be executed on the desired due date. The delivery, including approval, must be completed at the latest at midnight prior to the due date Express orders and urgent payments An order (with one or several payments) can be delivered via all data media on Swiss Post working days as an express order. This value-added service, which is subject to a charge, initiates an immediate debit attempt. Payment execution depends on the payment type and the order time. International payments can be credited more quickly by also selecting Giro international urgent as the payment type. Users are advised to submit this type of payment as an express order so that it is executed and debited immediately. The following rules apply in individual cases: Express orders Domestic Domestic giro Debit: immediate Execution: by 1 p.m. so that the amount can be credited by the bank with the same value date; by 6 p.m. so that the amount can be credited to the postal account with the same value date. Inpayment slip with Debit: immediate reference number Execution: on the next Swiss Post working day International Giro international Debit: immediate Execution: by p.m. on the issue date so that the amount can be credited to the recipient within one to four Swiss Post working days (depending on the currency). Giro international Debit: immediate urgent Execution: by 4 p.m. on the issue date so that the amount can be credited to the recipient on the same day (depending on the currency). Cash international Debit: immediate Execution: on the next Swiss Post working day so that the amount can be credited to the recipient within five to eight Swiss Post working days. Manual EPO Version November /43

13 EPO with execution on the desired due date Domestic Domestic giro Debit / execution: on the due date with value date 0 Inpayment slip with reference number Debit / execution: on the due date with value date + 1 day International Giro international Debit / execution: on the due date with value date + 1 to 4 days Giro international urgent Debit / execution: on the due date with value date 0 Cash international Debit / execution: on the due date with value date + 5 to 8 days The following points must also be taken into account: In the case of an EPO ISO (XML format), the code HIGH should be entered in the field Instruction Priority (B level) if the order is to be processed as an Express order. Any express designation at the transaction level will be ignored. If the debit account has insufficient funds, the Express order is cancelled immediately. The following restrictions in respect of quantities and times should be observed: Maximum no. of transactions per order Latest transmission and approval time 1, a.m p.m p.m. If these conditions are not met, the orders are executed with priority on the next possible Swiss Post working day (see section 4.2.8) Approval deadline Orders that have not been approved or only partially approved on the foreseen execution date remain pending for a further five Swiss Post working days. The order may still be approved during this time; if not, it will be cancelled. 4.2 Issuing orders Data entry It is the customer s responsibility to ensure that the information is entered correctly. Data errors lead to delays and extensive enquiries. PostFinance checks the account numbers / IBAN, the ISR customer numbers and the reference numbers using check digits and returns payments containing errors. Accuracy Customers are responsible for providing correct data in accordance with the Record Description Electronic services manual (EPO in TXT format) and/or the Implementation Guidelines (EPO ISO XML format). Manual EPO Version November /43

14 Failure to use the correct structure can prevent PostFinance from reading the incoming message with the payment orders (e.g. ISO schema requirement). This may even result in the rejection of complete messages or the cancellation of all the payments contained in them. Reference data The customer is to enter all the relevant invoice issuer reference data in the appropriate boxes. If the customer uses EPO ISO XML format, his own reference data entered in the field EndtoEndID may be transmitted. This information will be forwarded to the creditor if it is supported by the recipient s financial institution. This reference is incorporated into the PostFinance account statement Number of transactions An EPO in TXT and XML format (pain.001) allows up to 99,999 transactions (C levels) to be delivered in one order. PostFinance recommends a maximum of 90,000 transactions to ensure that the order notification works smoothly. For technical reasons, only messages with a maximum size of 90 MB may be processed Order coverage The customer shall ensure that there are sufficient funds in the debit account at all times so that the EPO can be debited at any time after midnight on the due date. If the customer does not want multiple debit attempts, the order is rejected if there is insufficient cover. Coverage is calculated according to the initial currency. It is therefore possible that in one order containing three currencies, only two can be processed. In an EPO ISO 20022, the currency designated in the instructed amount is the initial currency. If the equivalent amount is used, the currency of the debit account is the initial currency Identification of collective orders and double processing checks An EPO is identified by the following characteristics: EPO (TXT format) Debit account number Charge account number Due date Initial currency Order number EPO ISO (XML format) Debtor Account Charges Account Requested Execution Date Instructed Amount (Currency) or Equivalent Amount (Currency of Transfer) Payment Information Identification It is not possible to automatically process several orders with the same identification. These orders will be processed and cancelled in case of doubt (duplicate check). Manual EPO Version November /43

15 4.2.5 Initial currency Several currencies may be designated for each EPO. Processing, notification, and fees are handled separately for each currency. PostFinance therefore recommends setting up separate orders for each currency. An EPO can be split up according to currency and/or the type of execution Test sums In the case of an EPO in TXT format, a sum is to be created for each currency using the amounts and number of orders in that currency. In the case of international transactions, the type of execution is decisive. If the amount is denoted in Swiss francs, the transaction will be assigned to CHF. If the amount is denoted in a foreign currency, the transaction will be assigned to the corresponding ISO currency code. In the case of an EPO ISO in XML format, the number of transactions and the sum of the amounts (C level) is to be added up for the entire message (A level). The amounts are added up regardless of currency. If the test sums calculated by PostFinance differ from the transmitted information, the order will be refused for security reasons Checks for duplicates In the case of an EPO ISO (XML format) an additional check for duplicates takes place at the message level (A level). The clarity of the pain.001 message is checked within 90 days using Message Identification and Initiating Party. This check is carried out for all delivered customer messages; double messages will be rejected. The event is notified via a processing message Priority execution type Payment orders designated priority will be processed first if the account balance is not sufficient to process all the orders. In the case of an EPO in TXT format, priority transmission via e-finance file transfer is available. The designation priority then applies to all of the orders in the file. In case of an EPO ISO in XML format, the code PRIO can be used for priority in the field Instruction for Debtor Agent. If the individual payments (C level) within one order (B level) show various priorities, the order will be split up by PostFinance. It is advisable to group together any priority payments into one order (B level) and to transmit the normal priority transactions in a separate order. The code PRIO will be ignored when used in conjunction with the execution type Express (Instruction Priority = HIGH). In this case, the order will be executed with Express priority. Manual EPO Version November /43

16 4.2.9 Account notification Business customers see a batch booking for each order and each initial currency on their account statement by default. With ISO the customer can determine, using the Batch Booking field (value true or false) in pain.001, whether a debit should be declared for each transaction (false) or whether a batch booking should be declared for each order and each initial currency (true). Customer preferences are honoured whenever possible. No more than 50 individual transactions are notified on a paper account statement. Large orders are automatically combined in a batch booking on the account statement. It is advisable to execute salary payments with Batch Booking (true), in order to ensure maximum discretion in account notifications. PostFinance advises private customers using EPO ISO to disable Batch Booking (false) so that orders will be listed in detail on the account statement Salary payments Salary payments may be transmitted using any data medium: In the case of EPO in TXT format, the file must be designated as Salary when transmitted. In the case of EPO ISO in XML format, the code SALA should be entered in the field CategoryPurpose if the order should be processed as a salary payment. Designation as salary will be ignored at the transaction level. The customer will be informed of this situation via a processing message (pain.002). Salary payments may only be made in connection with a business account. Issuing salary orders via e-finance requires special signing authority. Salary payments for a postal account or bank account in Switzerland are credited and debited with the same value date. Owing to the special processing involved, salary orders must contain only salary payments and must be delivered separately from other accounts payable payments Approval Different provisions apply for orders: E-finance file transfer, File Delivery Services (FDS) and H-Net: Orders still have to be approved by e-finance after transfer. Exception with regard to e-finance file transfer: Orders transmitted using e-finance containing a single signature are deemed to have been signed and will be processed directly. Telebanking Server: No approval is necessary (customer identification by electronic key pair). SWIFT FileAct: Choose with or without approval via e-finance. Manual EPO Version November /43

17 4.3 Due date The requested execution date must be a Swiss Post working day. The due date is the day on which the customer wishes to have the EPO executed. On the due date for domestic transactions: the customer is debited for the EPO transfers to a postal account (giro) are credited transfers to a bank account (clearing payments) are processed by the bank s Computer Center cash outpayment orders are routed to the post offices and paid out the following day Inpayment slips with reference number (ISR/ISR+) are processed, and the customer is credited on the following working day For transfers involving conversion, the credit can take place two working days later. On the due date for international transactions the payment orders are routed to the designated countries. Orders may be uploaded up to two years in advance. However, this excludes large orders which contain more than 1,000 transactions these may be transferred to Post- Finance at most 90 days before the due date Delayed receipt of data If the data arrive at PostFinance too late, they will be incorporated into the next available processing cycle, as long as the due date has been passed by not more than 90 calendar days. Older orders can no longer be processed. The customer is informed of the revised execution date via processing report. The original due date should always be referenced in any enquiries regarding the order. 4.4 Cancellations/Changes By customers The e-finance user may choose from the following withdrawal options and modifications up to one day before the due date, by no later than midnight (only if the customer has an e-finance connection): Cancellation of entire orders or individual payments Change of an order s due date Alteration of desired order documents Change of salary payment Alteration of batch booking (yes/no) on the account statement (does not apply to EPO ISO in XML format) Manual EPO Version November /43

18 By PostFinance The customer may cancel entire orders or individual transactions up to one Swiss Post working day prior to the due date at 10 p.m. Cancellation instructions must be submitted to Global Payments, Input Electronic Services in writing. Requests submitted by telephone or fax will also be processed if an agreement has been deposited for this purpose. For entire orders the following particulars must be provided: EPO (TXT format) Debit account number Charge account number Due date Order number EPO ISO (XML format) Debtor Account Charges Account Requested Execution Date Payment Information Identification For cancellations of individual transactions of an EPO in TXT format, the sequential transaction number must also be provided. For EPO ISO either the instruction identification (single order number) or the end-toend identification (clear customer reference) must be provided. If an order or transaction cannot be identified on the basis of this information, the cancellation will not be processed. 4.5 Cancellation of the EPO by PostFinance EPO in TXT format Entire collective orders are cancelled if the top record is missing errors are present in the control area of the top record more than 15 currencies are present the currency code in the total record is invalid the total of the number of transactions and/or the amount does not match An order file may contain several collective orders. Each collective order begins with a top record and ends with a total record. Correctly structured collective orders will be sent for processing, incorrect orders will be cancelled. It is therefore possible that not all collective orders in an order file will be processed. Individual transactions will be cancelled if their structure does not correspond to the established standard the control area does not match that of the top record the minimum information (mandatory fields) is incomplete The structural requirements for EPOs in TXT format can be found in the Record Description Electronic services manual at w ww.postfinance.ch/ manuals. Manual EPO Version November /43

19 EPO ISO in XML format An entire pain.001 message (A level) will be rejected if: the pain.001 message does not correspond to the valid version according to the Swiss XSD schema the XML file (pain.001) cannot be validated with a valid XSD schema the schema location does not correspond to what has been agreed the sum (A level) of the number of transactions and/or the amount does not correspond an identical MessageID and InitiatingParty has already been transmitted within the past 90 days A pain.001 file may contain more than one collective order (B level). Entire collective orders are cancelled if more than 15 currencies are present the PostFinance BIC or clearing no. has not been correctly entered under Debtor Agent the field content is not properly formatted an element is inadmissible or is delivered without content Individual transactions (C level) will be cancelled if: the minimum information (mandatory fields) is incomplete the field content is not properly formatted an element is inadmissible The currently supported XSD schemas for pain.001/pain.002 can be downloaded at w ww.iso-payments.ch. 4.6 Order notification PostFinance provides various documents according to the offers transmitted. The documents provided correspond to the transmission format. Documents Formats Transmission with EPO in TXT format EPO ISO (XML format) Order confirmation PDF yes not available XML yes, XML PF 1 not available Paper yes not available Execution confirmation PDF yes yes XML yes, XML PF 1 yes, camt.054 (ISO 20022) Paper yes yes Annex Transactions PDF yes not available with price XML yes, XML PF 1 not available (prices are quoted in camt.054) Paper yes not available Individual confirmation PDF yes yes XML yes, XML PF 1 yes, camt.054 (ISO 20022) Paper yes yes Processing message PDF yes yes XML yes, XML PF 1 yes, pain.002 (ISO 20022) Paper yes yes 1 PostFinance proprietary format Manual EPO Version November /43

20 4.6.1 Order notification for EPO All documents will be provided electronically or in paper form. It is possible to define different formats for EPO in TXT and XML format (e.g. paper for EPO in TXT format, and PDF for pain.001). For EPO in XML format (pain.001), the order notification documents are delivered in ISO format if ISO has been selected as the delivery format. In this case the customer always receives back a pain.002 notification (processing message) per order. If desired, camt.054 notifications (execution confirmation or individual confirmation) can be delivered additionally to ensure customers receive an advice of each file with or without details of transactions booked. Alternatively, notification in PDF or paper form (execution confirmation or individual confirmation) is also possible. Notifications in ISO format are not compiled in the same way as documents in PDF or paper format, as the data are used for further processing. For further information on the structure of pain.002 and camt.054 notifications, please refer to the Implementation Guidelines under w ww.isopayments.ch or section Additional technical information on the Swiss Implementation Guidelines (pain.001 and pain.002) Delivery time The time of delivery of the documents depends on the delivery format: Delivery of EPO TXT: Delivery in PDF and XML PF formats always takes place in the evening or at 6 a.m. on the following day at the latest. Documents in paper form are delivered by mail on the following working day. Exception: for the order delivery, an order confirmation or processing message (for all formats), respectively, is compiled provided the execution date is not less than two and a half days in the future until the time of submission. If the order is due immediately, notification takes place during the execution of the order directly on the execution confirmation (if desired) and/or on the processing message. Delivery of EPO ISO in XML format (pain.001): Delivery in PDF, pain.002 and camt.054 formats takes place continuously upon issue/execution of the order (delivery from 6 a.m., approximately every 15 minutes). Documents in paper form are delivered by mail on the following working day. Exception: for the order delivery, a processing message in paper form is compiled provided the execution date is not less than two days in the future. If the order is due immediately, a processing message is sent during execution of the order Order confirmation (see examples and samples, section 5.4) The document is available for the delivery of EPO in TXT format only. The order confirmation includes a compilation of transactions for each initial currency. It also shows the number of transactions undertaken and whether incorrect/cancelled payments had to be rejected. These are detailed in a separate processing message. The document may be suppressed at the customer s request. Electronic delivery of the document is free of charge; delivery in paper format is subject to a fee. Manual EPO Version November /43

21 4.6.4 Execution confirmation (see examples and samples, section 5.4) The customer receives an execution confirmation for each EPO and each currency. This compilation shows the number of processed payments and the fees for each transaction type. Should incorrect transactions come to light during this processing stage or should transactions be cancelled, they will be detailed in a separate processing message. The order total in CHF (or relevant foreign currency) is the amount that will be charged to the customer s debit account on the due date. The total amount of relevant fees is also noted. The customer may request the annex entitled Transactions with price, which contains details of EPO prices. This annex does not incur any additional cost and is available only if the EPO order has been issued in TXT format. The document may be suppressed at the customer s request. Electronic delivery of the document is free of charge; delivery in paper format is subject to a fee. EPO ISO XML format: The execution confirmation in ISO format corresponds to camt.054. Incorrect payments are notified additionally by means of a pain.002 (processing message in ISO format). This document selection is controlled directly during the EPO order (pain.001) with the batch booking combination true and code CND (Collective Advice no Details), or via the master data at PostFinance (as per EPO registration). camt.054 as an execution confirmation merely shows details of the collective order. The prices incurred by the order are shown as a grand total Individual confirmation (see examples and samples, section 5.4) The customer has the option, for auditing purposes, to be provided with a detailed list of all payments executed via EPO. For a salary EPO, the default is set not to display amounts. Salary details can be displayed if the customer so requests. The document is available if requested by the customer. The document can be supplied free of charge in electronic form, while there is a fee for the paper version. EPO ISO XML format: The individual confirmation in XML format is delivered by means of camt.054. This debit advice is controlled directly during EPO (pain.001) with the batch booking combination true and code CWD (Collective Data with Details) or batch booking false and code SIA (Single Advice), respectively, or via the master data at PostFinance (as per EPO registration). camt.054 as an individual confirmation merely shows details of the individual orders of pain.001. Information on prices incurred is shown with each transaction. Manual EPO Version November /43

22 4.6.6 Processing message (see examples and samples, section 5.4) Orders with errors or transactions that contain field errors are reported on the processing message. Rejected orders or transactions cannot be corrected, therefore the entire transaction will need to be resubmitted. The processing message is free of charge (electronic/on paper) and can not be suppressed; notification of identified errors is always given. Whether the customer has waived the order and execution confirmations is therefore irrelevant when it comes to error notification. If a processing message has already been compiled during the order delivery, the total of any errors already advised of, together with any additional errors, is shown in a new processing message during the order execution. During the order execution, the total of any errors already advised of, together with any additional errors, is shown in a processing message. In this process, transactions already advised of are marked with an asterisk. At the customer s request, there is an option that errors already advised of in a processing message are not notified a second time during the order execution. If a transaction shows more than one error, only the first deviation is shown. EPO ISO XML format: Delivery of a processing message in ISO format takes place by means of pain.002: This status report is always compiled and delivered on issuing an order, both for positive and for incorrect orders/individual orders. Invalid pain.001 messages and orders which contain errors will be reported as Rejected (RJCT). Orders with individual transactions which contain errors will be reported with the status Partially Accepted (PART), as the order is partially correct. The transactions from this order which contain errors will appear as rejected (RJCT). Accepted orders or transactions with notes will be reported as Status Accepted with Change (ACWC) and contain a warning. A correction of rejected messages, orders and transactions is not possible; a new pain.001 (EPO in XML format) will have to be delivered. Error-free orders are confirmed with status Accepted (ACCP) on issuing. Following order execution, only subsequent errors and irregularities are advised of via pain.002. Each order delivered (B level) is always accompanied by at least one pain.002 message. By default, any errors and warnings advised of at the moment of issuing are no longer notified. At the customer s request, there is an option that errors already advised of are notified a second time at the moment of execution. The pain.002 version is determined by the version of the pain.001 delivered. Manual EPO Version November /43

23 4.7 Modification of customer data The following changes must be reported to the customer service department in good time: In writing Debit account Fee account Address changes Change of transmission or reception channel By telephone Multiple debit attempts 4.8 Enquiries If the customer has an e-finance connection, EPO enquiries may be issued directly in e-finance. Different forms must be used for enquiries on paper, depending on the transaction type: Domestic For all enquiries regarding domestic transaction types, the form Enquiry request EPO applies. The EPO customer completes items 1 and 2 and sends the form to: PostFinance Ltd National Enquiries CH-3030 Berne International For enquiries regarding international transaction types, the form Enquiry request for international payment should be used. The form is to be completed as directed and sent to the following address: PostFinance Ltd International Enquiries CH-3030 Berne To order forms we kindly ask you to contact your account manager. 4.9 Term and notice The business relationship between the customer and PostFinance is entered into for an unlimited duration. It can be terminated by either party at any time in writing, unless it is subject to special rules for payment transactions as part of the universal service. For more information, please see the PostFinance General Terms and Conditions and Subscriber Conditions, which can be downloaded at w ww.postfinance.ch. Manual EPO Version November /43

24 5. Technical specifications 5.1 Supported ISO versions PostFinance supports the current and most recently valid versions of the Business Rules and Implementation Guidelines published by SIX Interbank Clearing. As no new version has been issued by the Swiss financial centre since the introduction of the EPO ISO range in 2011, PostFinance currently only supports the most up-to-date version. These Swiss recommendations are based on the ISO and EPC documents and provide information about the supported ISO versions. The Swiss Business Rules and Implementation Guidelines can be downloaded from w ww.iso-payments.ch. 5.2 Transactions and payment types EPO in TXT format An EPO can be used for the following transactions: Domestic Transaction type Description 22 Domestic postal account (IS) 24 Domestic cash outpayment orders (OP) 27 Domestic clearing/iban payments (IS) 28 Inpayment slips with reference number (ISR) International Transaction type Description 34 Cash international (CI) 37 Giro international (GI) The Record Description Electronic services manual for TXT format can be downloaded at w ww.postfinance.ch/manuals EPO ISO in XML format At PostFinance the following transactions can be processed using the EPO ISO XML format via pain.001 messages: Domestic transfers Payment type 1 Description 1 Inpayment slips with a reference number (ISR) 2.1 Inpayment slips for credit to a postal account (IS) 2.2 Inpayment slips for credit to a bank account (IS) 3 Bank or postal payment (without a slip) with IBAN / postal account and BIC (IS) 4 Bank or postal payment (without a slip) in a foreign currency (IS) 1 Payment according to the Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (payment transactions) Manual EPO Version November /43

25 Transfers abroad 2 Payment type 1 Description 5 SEPA (GI) payment abroad 6 Payment abroad in any currency (GI) Payments without indication of a financial institution (domestic and abroad 2 ) Payment type 1 Description 7 Domestic outpayment order (OP) 8 Cash international 3 (CI) 1 Payment according to the Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (payment transactions) 2 Detailed information on individual countries can be ordered as a manual from the Electronic Services customer service. A table listing transaction types, payment currencies and additional services for each country can be downloaded at w ww.postfinance.ch/ manuals. 3 Please note that PostFinance does not support Bankcheck Domestic/Abroad for payment type 8. The ISO definitions in the Swiss Implementation Guidelines, including a description of the XML structure and validation rules, can be downloaded at w ww.iso-payments.ch. Section of this manual contains additional information for smooth processing of pain.001 at PostFinance Authorized characters PostFinance uses character set ISO for EPO in TXT format. This set converts other character sets, replacing values that cannot be converted with SPACES so as not to adversely affect in-house processing. When using an EPO ISO in XML format, please comply with the provisions of the Swiss Implementation Guidelines. 5.3 Additional technical information on consistency, key fields and AOS from PostFinance Sender details If a different sender s address is to be transmitted to the beneficiary (e.g. a receivable settled on behalf of a third party), the sender s address can be indicated in the corresponding field with EPO TXT. The Ultimate Debtor element can be used for this purpose with ISO Manual EPO Version November /43

26 5.3.2 Additional technical information on the Swiss Implementation Guidelines (pain.001 and pain.002) In the Swiss Implementation Guidelines (w ww.iso-payments.ch) there are required fields and optional fields that should only be used in consultation with the respective financial institutions (so-called AOS Additional Optional Services). The following table provides information on how PostFinance processes these fields. Additional details to be entered in certain fields in order to facilitate processing of pain.001 are also provided. pain.001 ISO Message Item Index 1.9 Group Header +Forwarding Agent 2.1 Payment Information +Payment Information Identification 2.3 Payment Information +Batch Booking 2.7 Payment Information +Payment Type Information ++Instruction Priority 2.9 Payment Information +Payment Type Information ++Service Level +++Code 2.10 Payment Information +Payment Type Information ++Service Level +++Proprietary 2.15 Payment Information +Payment Type Information ++Category Purpose +++Code 2.20 Payment Information +Debtor Account ++Identification +++IBAN 2.20 Payment Information +Debtor Account ++Identification +++Other ++++Identification 2.20 Payment Information +Debtor Account ++Type +++Code Notes by PostFinance Irrelevant. Will be ignored. In addition to checking for duplicates at A level, additional checks are also conducted at B level. The resulting value is used in combination with Debtor Account, Charges Account, Requested Execution Date and Instructed Amount (Currency) or Equivalent Amount (Currency of Transfer) as a criterion for detecting duplicate entries. Orders bearing identical identification will be refused. True or false; if left empty, this field will be processed as true (batch booking). If a paper account statement is desired, false is only possible for orders with <50 C levels. For orders with >50 C levels, false will be ignored. HIGH corresponds to Express processing. This element can be omitted for normal execution. The type of execution is to be determined at B level; any data at C level will be ignored. Only SEPA and SDVA are accepted. The URGP and PRPT codes will be ignored. SEPA may be used in connection with payment type 5. 1 SDVA = code for Urgent in international transactions (also see 2.34). Irrelevant. Will be ignored. SALA for salary payments or PENS for pension payments. The PENS code may only be used in agreement with PostFinance. Otherwise, the code will be ignored. Postal account in IBAN format. Debit account number may only be transmitted in two different formats: VVXXXXXXC VV = leading character XXXXXX = ordinal number, right-justified, zeros are to be placed on the left side C = check digit according to Modulo 10 recursive Or VV-XXXXXX-C VV = leading character XXXXXX = ordinal number, right-justified, zeros are to be placed on the left side C = check digit according to Modulo 10 recursive It is advisable to use the IBAN when issuing a pain.001 (see 2.20 IBAN). Irrelevant. Will be ignored. Manual EPO Version November /43

27 ISO Message Item Index 2.21 Payment Information +Debtor Agent ++Financial Institution Identification 2.23 Payment Information +Ultimate Debtor 2.23 Payment Information +Ultimate Debtor ++Identification +++Organisation Identification 2.23 Payment Information +Ultimate Debtor ++Identification +++Private Identification 2.25 Payment Information +Charges Account ++Identification +++IBAN 2.25 Payment Information +Charges Account ++Identification +++Other ++++Identification 2.29 Credit Transfer Transaction Information +Payment Identification ++Instruction Identification 2.34 Credit Transfer Transaction Information +Payment Type Information ++Service Level +++Code 2.35 Credit Transfer Transaction Information +Payment Type Information ++Service Level +++Proprietary 2.43 Credit Transfer Transaction Information +Amount ++Instructed Amount 2.44 Credit Transfer Transaction Information +Amount ++Equivalent Amount 2.46 Credit Transfer Transaction Information +Amount ++Equivalent Amount +++Currency of Transfer Notes by PostFinance PostFinance BIC = POFICHBEXXX or clearing no. = 9000 Together with the clearing no., the CHBCC code within the clearing system identification must be delivered. The original ordering customer details can be provided in this element (max. 140 characters, 4 35 characters will be forwarded to the recipient). An original ordering customer is a third person who carries out payments via the EPO customer (e.g. bank customer via a bank or company subsidiary). The element can be provided on level B or C (see 2.70). The original ordering customer s address can be provided in a structured or unstructured manner. For the structuring of addresses, see Irrelevant. Will be ignored. Irrelevant. Will be ignored. Account charged with fees in IBAN format. If no fee debit account is given (element Charges Account), any fees will be debited to the debit account (see 2.20 IBAN). As with the debit account, the fee account may be transmitted in two different formats (see 2.20 Identification). Corresponds to the single order number. This is required information and must be clearly specified. PostFinance only supports the SEPA and SDVA codes. The URGP and PRPT codes will be ignored. Payment type 5 (SEPA International): SEPA code must be used. 1 Payment type 6 (International): SDVA allows for faster processing of international payments (Giro International Urgent, subject to a charge). Please consult IZV manual or IZV list (w ww.postfinance.ch/ manuals). Irrelevant. Will be ignored. In the case of foreign currencies with no or only restricted provision for fractional currency units, PostFinance will round the amount up to the next permissible unit in the currency. In case of payment order (payment type 7): <CHF 1 million Use permitted. Currency code in Currency of Transfer according to the currency overview. When using payment order (payment type 7), only CHF is permitted. Manual EPO Version November /43

28 ISO Message Item Index 2.47 Credit Transfer Transaction Information +Exchange Rate Information 2.51 Credit Transfer Transaction Information +Charge Bearer 2.70 Credit Transfer Transaction Information +Ultimate Debtor 2.71 Credit Transfer Transaction Information +Intermediary Agent Credit Transfer Transaction Information +Creditor Agent 2.77 Credit Transfer Transaction Information +Creditor Agent ++Financial Institution Identification +++Postal Address ++++Country 2.79 Credit Transfer Transaction Information +Creditor ++Identification 2.79 Credit Transfer Transaction Information +Creditor ++Name 2.79 Credit Transfer Transaction Information +Creditor ++Postal Address +++Street Name 2.79 Credit Transfer Transaction Information +Creditor ++Postal Address +++Building Number 2.79 Credit Transfer Transaction Information +Creditor ++Postal Address +++Post Code 2.79 Credit Transfer Transaction Information +Creditor ++Postal Address +++Town Name Creditor ++Postal Address +++Address Line 2.80 Credit Transfer Transaction Information +Creditor Account ++Identification +++IBAN Notes by PostFinance Irrelevant. Will be ignored. Please consult the IZV list (w ww.postfinance.ch/manuals). For OUR, DEBT is used; all other codes will be transmitted internationally as BENs. An original ordering customer is a third person who carries out payments via the EPO customer (e.g. bank customer via a bank). Irrelevant. Will be ignored. This information will be ignored for payment type 8. Compulsory for foreign payments. For the structuring of addresses, see 2.79 Creditor. Irrelevant. Will be ignored. The element can contain max. 70 characters. When forwarding to the recipient, PostFinance automatically inserts a line break after the first 35 characters. The element together with the element Building Number can contain max. 35 characters. Any other characters from position 36 will be ignored. See comment in 2.79 Street Name. The element together with the element Town Name can contain max. 35 characters. Any other characters from position 36 will be ignored. See comment in 2.79 Post Code. The element can be used no more than twice and can contain a maximum of 70 characters per element. When forwarding to the recipient (Creditor), PostFinance automatically inserts a line break after the first 35 characters, provided the element Address has only been used once. If the element is used twice, the first 35 characters will be taken over by the second instance Address Line. Any other characters from position 36 will be ignored. Creditor account in IBAN format Regarding international payments abroad: The first two positions of the IBAN may not include CH or LI. Manual EPO Version November /43

29 ISO Message Item Index 2.80 Credit Transfer Transaction Information +Creditor Account ++Identification +++Other ++++Id Notes by PostFinance Transfer to a postal account: VVXXXXXXC VV = leading character XXXXXX = ordinal number, right-justified, zeros are to be placed on the left side C = check digit according to Modulo 10 recursive Or VV-XXXXXX-C VV = leading character XXXXXX = ordinal number, right-justified, zeros are to be placed on the left side C = check digit according to Modulo 10 recursive In case of transfers to an ISR customer number: ISR or ISR+ with 5-digit customer number: 9999C ISR or ISR+ with a 9-digit customer number: C or C. Examples: or It is advisable to calculate and compare the check digit (Modulo 10 recursive) Credit Transfer Transaction Information +Ultimate Creditor 2.82 Credit Transfer Transaction Information +Instruction for Creditor Agent 2.85 Credit Transfer Transaction Information +Instruction for Debtor Agent Please note: a proprietary, domestic account number (postal account/bank account) may not be transmitted in combination with BIC (Creditor Agent). In this case the clearing number is required under Credit Agent (ISO Index 2.77). This can only be used in conjunction with payment type 7 (payment order). This information will be ignored in the case of payment types 4, 5, 6, and 8. For payment methods 1, 2.1, 2.2 and 3, use of this element will lead to cancellation. Irrelevant. Will be ignored. Possible codes: PRIO for priority payments NORETRY for single deactivation of multiple debits Several values may be entered in the field <InstrForDbtrAgt>. This field is for Additional Optional Services. The PostFinance rules for filling out this field are as follows: 1. Codes first 2. Codes should be separated by a delimiter comma (,) 3. Text should start with a semi-colon (;) 4. Floating text will be ignored Example: <InstrForDbtrAgt>NORETRY,PRIO;floating text </InstrForDbtrAgt> It is advisable to transmit all priority transactions at B level. The PRIO code may only be used with Instruction Priority NORM or without Instruction Priority element. If PRIO is used in conjunction with the Instruction Priority HIGH in a single order, the code PRIO will be ignored Credit Transfer Transaction Information +Purpose ++Code 2.89 Credit Transfer Transaction Information +Regulatory Reporting Credit Transfer Transaction Information +Remittance Information ++Structured +++Creditor Reference Information ++++Type +++++Issuer NORETRY must be entered at the order level for all C level transactions, otherwise the code will be ignored. Irrelevant. Will be ignored. Irrelevant. Will be ignored. Irrelevant. Will be ignored. Manual EPO Version November /43

30 ISO Message Item Index Credit Transfer Transaction Information +Remittance Information ++Structured +++Creditor Reference Information ++++Reference Credit Transfer Transaction Information +Remittance Information ++Invoicer Credit Transfer Transaction Information +Remittance Information ++Invoicee Credit Transfer Transaction Information +Remittance Information ++Structured +++Additional Remittance Information Notes by PostFinance For payment type 1 (ISR): For 5-digit ISR customer numbers (no more than 15 transactions) For 9-digit ISR customer numbers (no more than 27 transactions) C The reference number appears in the processing document in 5-digit blocks, whereby leading zeros can be suppressed. Reference numbers with the value 0 (nil) will be rejected. It is advisable to calculate and compare the check digit (Modulo 11 for 5-digit customer numbers, or Modulo 10 recursive for 9-digit customer numbers). Irrelevant. Will be ignored. Irrelevant. Will be ignored. Payment type 1 (ISR): Individual customer reference for display in e-finance (no more than 35 characters) as well as on the account statement. Recommended if an ISR bank is involved. 9 = numeric C = check digit IBAN = International Bank Account Number 1 For payments abroad, PostFinance automatically chooses the optimal and least expensive option. If the required details (IBAN/BIC/EUR) are given, your payments will be transmitted as a SEPA compliant transfer even without the SEPA code (corresponds to payment type 6). pain.002 PostFinance transmits the ISO Status Reason Codes according to Payments External Code Lists (see w ww.iso20022.org) in the element Status Reason Code. Codes specific to Switzerland that are defined in the Swiss Implementation Guidelines (see w ww.iso-payments.ch) are provided in the element Proprietary. In addition to the Status Reason Codes mentioned above, additional unstructured information is provided in the element Additional Information. The text is always provided in the customer s language (as per the master data). PostFinance always delivers one pain.002 per order (B level). This is why the pain.002 do not receive a group status but rather payment information or transaction status (AOS). The following matrix shows how statuses are used. Manual EPO Version November /43

31 pain.001 pain.002 processing message (status report) Status Original IDs from pain.001 Error on Group Payment Inf Transaction Message Payment Instruction EndToEnd Entire message (A/B/C level) XSD-failed RJCT NOT PROVIDED 1 Error on Group Payment Inf Transaction Message Payment Instruction EndToEnd B level (some or all) RJCT C level (all) RJCT RJCT C level (some from one B level) PART RJCT Warning on Group Payment Inf Transaction Message Payment Instruction EndToEnd B level (some or all) ACWC 2 C level (some or all) ACWC 2 ACWC 2 No errors Group Payment Inf Transaction Message Payment Instruction EndToEnd B level ACCP : Corresponding original reference from relevant pain.001 message is provided ACCP: Accepted RJCT: Rejected PART: Partially Accepted ACWC: Accepted with Change 1 In cases of XSD schema violation, the payment ID cannot be determined. The value NOTPROVIDED will be provided in the OrgnlPmtInfId element. 2 Warnings/notes will only be taken into account/reported upon execution of an order. Along with the processing message upon placement of an order (pain.002) according to the Swiss requirements, PostFinance also transmits a processing message at execution: if the status of the order is cancelled if the status of the order is executed and the individual orders were cancelled during execution and/or warnings were issued For the FDS (File Delivery Services) channel the customer also receives a confirmation of receipt at message level (A level) via pain.002, if the message structure (XSD schema) is correct (GroupStatus = ACTC) or contains errors (GroupStatus = RJCT). The technical confirmation of receipt will only be delivered provided the customer has entered an electronic order notification in the master data which cannot be cancelled. The following matrix shows the use of statuses for the technical FDS confirmation of receipt: pain.001 pain.002: technical confirmation of receipt for FDS channel Status Original IDs from pain.001 Error on Group Payment Inf Transaction Message Payment Instruction EndToEnd A level RJCT No errors Group Payment Inf Transaction Message Payment Instruction EndToEnd A level ACTC : Corresponding original reference from relevant pain.001 message is provided RJCT: Rejected ACTC: Accepted Technical Validation Manual EPO Version November /43

32 Additional technical information on the Swiss Implementation Guidelines (camt.054) The Swiss Implementation Guidelines (w ww.iso-payments.ch) contain mandatory and optional fields which can be used in different ways by the respective financial institutions. The following table provides information on how PostFinance processes these fields. Additional details to be entered in certain fields in order to facilitate processing of camt.054 are also provided. PostFinance supports version 2 for camt.054 in the EPO. The preferred type of debit advice can be selected in the pain.001 message; all the various combinations have a direct influence on the camt.054 structure: Payment Information from pain.001 Batch Booking Debtor Account/ Type/Proprietary camt.054 Information at Entry Level (C level) Execution confirmation True CND 1 1 C level with information of collective order Individual confirmation True CWD² 1 C level False SIA³ with information of collective order Information at Transaction Details Level (D level) 1 D level with information of collective order 1-n D levels with details of individual transactions ¹ CND: Collective Advice No Details ² CWD: Collective Advice With Details ³ SIA: Single Advice Further details of the respective elements are available in the following table. Manual EPO Version November /43

33 camt.054 ISO Index Message Item Notes by PostFinance A level 1.3 Group Header +Message Recipient 1.4 Group Header +Message Pagination B level 2.2 Notification +Electronic Sequence Number 2.6 Notification +Copy Duplicate Indicator 2.10 Notification +Account ++Identification +++IBAN 2.10 Notification +Account ++Identification +++Other 2.10 Notification +Account ++Owner C level Notification +Transactions Summary 2.58 Entry +Amount 2.59 Entry +Credit Debit Indicator 2.60 Entry +Reversal Indicator 2.61 Entry +Status 2.62 Entry +Booking Date ++Date 2.62 Entry +Booking Date ++Date Time 2.63 Entry +Value Date ++Date 2.63 Entry +Value Date ++Date Time 2.64 Entry +Account Servicer Reference 2.81 Entry +Additional Information Indicator 2.94 Entry +Additional Entry Information Irrelevant. Is not delivered. Irrelevant. Is not delivered. Irrelevant. Is not delivered. Only delivered with repeat order; in this case always with the value DUPL. The holder s postal account number is always delivered in IBAN format. There is no delivery of the postal account number in proprietary format (always IBAN format, see element above). Irrelevant. Is not delivered. Irrelevant. Is not delivered. Always 1 C level with collective booking from the original pain.001. Always delivered with value DBIT. Irrelevant. Is not delivered. Always delivered with value BOOK. Booking date delivered with element Date. Date Time is not delivered, as the element Date is always delivered (see element above). Value date delivered with element Date. Date Time is not delivered, as the element Date is always delivered (see element above). Delivered (internal PostFinance reference). Irrelevant. Is not delivered. Is used for the advice of fees. Depending on the advice type selected from the original pain.001: CND: grand total of all fees CWD/SIA: The element is not delivered. The fees for individual transactions are delivered at D level (see element Related Price) Manual EPO Version November /43

34 ISO Index Message Item Notes by PostFinance D level Transaction Details Depending on the advice type selected from the original pain.001: CND: 1 D level with details of the pain.001 collective booking (References from pain.001) CWD/SIA: 1-n D levels with details of the individual bookings from pain.001 (e.g. amounts, details of recipient) Transaction Details Message ID from original pain.001 is delivered (CND, CWD, SIA). +References ++Message Identification Reference Transaction Details Is delivered (CND, CWD/SIA). +References ++Account Servicer Reference Transaction Details +References ++Payment Information Identification Payment information ID from original pain.001 is delivered (CND, CWD/SIA) Transaction Details +References ++Instruction Identification Transaction Details +References ++End To End Identification Transaction Details +References ++Mandate Identification Transaction Details +Amount Details Transaction Details +Amount Details ++Instructed Amount Transaction Details +Amount Details ++Instructed Amount +++Currency Exchange Transaction Details +Amount Details ++Transaction Amount Transaction Details +Amount Details ++Transaction Amount +++Currency Exchange Transaction Details +Amount Details ++Counter Value Amount Transaction Details +Amount Details ++Instructed Amount +++Currency Exchange ++++Source Currency Transaction Details +Amount Details ++Instructed Amount +++Currency Exchange ++++Exchange Rate Transaction Details +Bank Transaction Code Instruction identification from the original pain.001 is only delivered for the use of advice selection CWD/SIA. End-to-end ID from the original pain.001 is only delivered for the use of advice selection CWD/SIA. Irrelevant. Is not delivered. Depending on the advice type selected from the original pain.001: CND: is not delivered CWD/SIA: is delivered; by default, the amounts for salary-pain.001 (SALA) are not advised. Corresponds to Instructed Amount, is always delivered. Irrelevant. Is not delivered. Corresponds to Transaction Amount. Is delivered, if available (only if Equivalent Amount provided in pain.001). Is delivered, if available. Corresponds to the counter value in the account currency. Is delivered, if available. Corresponds to the original currency. Is delivered, if available. Corresponds to the exchange rate. Is delivered, if available. Is delivered. Bank transaction code (BTC) list as per recommendations (Implementation Guidelines, w ww.iso-payments.ch). Manual EPO Version November /43

35 ISO Index Message Item Notes by PostFinance Transaction Details +Charges Transaction Details +Related Parties Transaction Details +Related Parties ++Debtor Transaction Details +Related Parties ++Ultimate Debtor Transaction Details +Related Parties ++Creditor Transaction Details +Related Parties ++Creditor ++Identification Transaction Details +Related Parties ++Creditor Account Transaction Details +Related Parties ++Ultimate Creditor Transaction Details +Related Parties ++Ultimate Creditor +++Identification Transaction Details +Related Parties ++Proprietary Transaction Details +Related Agents ++Debtor Agent Transaction Details +Related Agents ++Creditor Agent Transaction Details +Related Agents ++Intermediary Agent Transaction Details +Related Parties ++Initiating Party Transaction Details +Purpose Transaction Details +Remittance Information ++Unstructured Transaction Details +Remittance Information ++Structured Transaction Details +Remittance Information ++Structured +++Creditor Reference Information ++++Reference Irrelevant. Is not delivered. Is only delivered for the use of advice selection CWD/SIA. Irrelevant. Is not delivered. Irrelevant. Is not delivered. Is only delivered for the use of advice selection CWD/SIA. The Creditor s address is always delivered in an unstructured manner in the element Address Line (irrespective of the delivery). Irrelevant. Is not delivered. Is only delivered for the use of advice selection CWD/SIA, if available. Given in the format corresponding to the data delivered. Exception: Postal account is always given in proprietary format. Is only delivered for the use of advice selection CWD/SIA, if available (only for pain.001 payment type 7, payment order). Irrelevant. Is not delivered. Irrelevant. Is not delivered. Irrelevant. Is not delivered. Is only delivered for the use of advice selection CWD/SIA, if available. Irrelevant. Is not delivered. Irrelevant. Is not delivered. Irrelevant. Is not delivered. Is only delivered for the use of advice selection CWD/SIA, if available (unstructured notifications from pain.001). Is only delivered for the use of advice selection CWD/SIA, if available. Is used for ISR reference number. Manual EPO Version November /43

36 ISO Index Message Item Notes by PostFinance Transaction Details +Remittance Information ++Structured +++Additional Remittance Information Transaction Details +Related Dates Transaction Details +Related Price Transaction Details +Related Price ++Prtry +++Type Transaction Details +Related Price ++Prtry +++Price For pain.001 payment type 1 (ISR): Individual client reference is delivered, if available. Irrelevant. Is not delivered. Is used for the advice of fees. Depending on the advice type selected from the original pain.001: CND: grand total of all fees CWD/SIA: Fees from individual transactions Is used for the advice of fees (text). Is used for the advice of fees (price). 5.4 Samples and examples Example files of XML formats Example files for the TXT or XML formats (pain and camt messages) can be downloaded from /e-finance.postfinance.ch/test.html. To do this, customers will require e-finance security elements; if these are not available, please call your customer advisor or the Electronic Services customer service on Manual EPO Version November /43

37 5.4.2 Order confirmation (only for EPO in TXT format) PostFinance Ltd Your account is handled by Priska Röllin and team Telephone Fax w ww.postfinance.ch P.P CH-4808 Zofingen A-PRIORITY Robert Schneider SA Grands magasins Biel/Bienne Robert Schneider SA Ruelle du Lac Biel/Bienne Order confirmation Electronic payment order (EPO) Page: 1 / 1 Date: Debit account: Due date: Fee debit account: Execution date: Order identification: E-finance number: Order reference: POST Transmission per: Online file transfer Order number: 77 Number Transactions delivered 34 Non-executable transactions 2 Transactions deleted 2 Transactions to be booked 28 Transaction type Number Initial currency Amount IS 7 CHF IS 4 CHF ISR 8 CHF OP 2 CHF GI 3 CHF CI 4 CHF Total CHF Not all transactions could be considered. Please note the attached processing message! Yours sincerely PostFinance Manual EPO Version November /43

38 5.4.3 Execution confirmation PostFinance Ltd Your account is handled by Priska Röllin and team Telephone Fax w ww.postfinance.ch P.P CH-4808 Zofingen A-PRIORITY Robert Schneider SA Grands magasins Biel/Bienne Robert Schneider SA Ruelle du Lac Biel/Bienne Execution confirmation Electronic payment order (EPO) Page: 1 / 1 Date: Debit account: Due date: Fee debit account: Execution date: Order identification: E-finance number: Order reference: POST Transmission per: Telebanking Server Order number: Message-ID: 77 MSG8BA4ADF95DC D3C3DE14 E33D8 Number Transactions delivered 5 Transactions booked 5 Initial order Transfer Rate Debit in CHF Transaction type Number Currency Amount Currency Amount Amount in CHF IS 2 CHF EUR OP 1 CHF EUR GI 1 CHF EUR CI 1 CHF EUR Total Price All transactions have been considered. Yours sincerely PostFinance Manual EPO Version November /43

39 5.4.4 Transactions with price electronic payment order EPO (only for EPO in TXT format) Date: Debit account: Due date: Robert Schneider SA Fee debit account: Execution date: Ruelle du Lac 177 Order identification: E-finance number: Biel/Bienne Order reference: 234 Transmission per: Telebanking Server Order number: 78 Page 1 / 1 No. Currency Account recipient Details for beneficiary Additional information Price Type TA Initial amount Recipient ISR reference number in CHF GI CHF Deutsche Postbank AG Peter Beispiel RHEINFELDEN München ) 637) CI CHF Hans Muster Biel-Bienne ) Rue Exemple 2 FRANCE Price for e-finance orders express ) Total Type Number Total in CHF 311) Cash international (SAD/TG/e-finance) ) Price supplementary for Giro international NON-STP ) Giro international (EPO/e-finance) ) Price for payment order EPO/e-finance ) Price for e-finance orders express Yours sincerely PostFinance Manual EPO Version November /43

40 5.4.5 Individual confirmation electronic payment order EPO Date: Debit account: Due date: Robert Schneider SA Ruelle du Lac Biel/Bienne Fee debit account: Execution date: Order identification: E-finance number: Order reference: DSP Transmission per: Online file transfer Order number: Message-ID: 123 MSG8BA4ADF95DC D3C3DE14E33D Page 1 / 1 No. Currency Account recipient Details for beneficiary Additional information Debit TA Initial amount Recipient ISR reference number in CHF IS CHF Robert Schneider SA 2503 Biel/Bienne Miete März OP CHF Robert Schneider SA 2502 Biel/Bienne Reparatur Kundennummer GI CHF PBNKDEFF Deutsche Postbank AG CI CHF Hans Muster Rue Exemple FRANCE REF789 Peter Beispiel RHEINFELDEN Heizkosten 4. Quartal Total Price Number Transactions delivered 4 Transactions booked 4 All transactions have been considered. Manual EPO Version November /43

41 5.4.6 Processing message electronic payment order EPO Date Debit account: Due date: Robert Schneider SA Ruelle du Lac Biel/Bienne Fee debit account: Execution date: Order identification: E-finance number: Order reference: Auftrag Transmission per: Online file transfer Order number: Message-ID: MSG8BA4ADF95DC D3C3DE14E33D Page 1 / 2 Executed & erroneous transactions No./TA Recipient End beneficiary Additional information Currency Initial amount IS Robert Schneider SA 2503 Biel/Bienne Note * End beneficiary name missing. Please check your data input Transactions not executed CHF No./TA Recipient End beneficiary Additional information Currency Initial amount IS Robert Schneider SA 2503 Biel/Bienne Data field Error * Recipient account unknown CI Facture 01/2015 Data field Error * Land BE Kontob: CHF Fremdb: Our Cost not permitted for country and/or service Transactions deleted CHF CHF No./TA Recipient End beneficiary Additional information Currency Initial amount IS PostFinance Engehaldenstrasse Bern Robert Schneider SA 2503 Biel/Bienne Miete März 2015 Note * Single order cancelled by customer CHF Manual EPO Version November /43

42 Processing message electronic payment order EPO Debit account: Due date: Order number: E-finance number: Message-ID: MSG8BA4ADF95DC D3C3DE14E33D8 Page 2 / 2 Transactions deleted No./TA Recipient End beneficiary Additional information Currency Initial amount IS PostFinance Engehaldenstrasse Bern Robert Schneider SA 2503 Biel/Bienne Miete Mai 2015 Note * Single order cancelled by customer CHF Total non-executed or deleted transactions 2 Yours sincerely PostFinance Manual EPO Version November /43

43 5.4.7 Processing message (high format) PostFinance Ltd Your account is handled by Ursula Müller and team Telephone Fax w ww.postfinance.ch P.P CH-4808 Zofingen A-PRIORITY Robert Schneider SA Grands magasins Biel/Bienne Robert Schneider SA Ruelle du Lac Biel/Bienne Processing message Electronic payment order (EPO) Page: 1 / 1 Date: Debit account: Due date: Fee debit account: Execution date: Order identification: E-finance number: Order reference: 234 Transmission per: Telebanking Server Order number: Message-ID: 78 MSG8BA4ADF95DC D3C3DE14 E33D8 Order not executed Note Number of transactions Currency Total amount Collective order with same key term exists 34 CHF Yours sincerely PostFinance Manual EPO Version November /43