SEPA Credit Transfer Instructions

SEPA Credit Transfer Instructions STANDARD ISO 20022 pain.001.001.03 Guideline for SEPA Credit Transfer Instructions transmitted to Société Générale France Version: August 2015 ORDRE DE VIREMENT SEPA STANDARD ISO 20022 PAIN.001.001.03

TABLE OF CONTENT 1 INTRODUCTION... 3 2 GENERAL PRESENTATION OF THE SEPA CREDIT TRANSFER INSTRUCTION IN ISO 20022 STANDARD... 4 2.1 SEPA CREDIT TRANSFER INSTRUCTION... 4 2.2 ISO 20022 STANDARD "PAIN.001.001.03"... 4 3 DETAILED DESCRIPTION OF THE MESSAGE FOR «SEPA CREDIT TRANSFER INSTRUCTION» 6 3.1 DESCRIPTION PRESENTATION... 6 3.2 OPERATING RULES... 6 3.3 CONTROLS PERFORMED AT THE RECEPTION OF THE FILE... 7 3.4 ISO 20022 STANDARD PAIN.001.001.03 FOR SEPA CREDIT TRANSFER INSTRUCTION... 9 3.5 EXAMPLE 1 : ELEMENTARY MESSAGE WITH SCT INSTRUCTIONS FROM FRANCE TO FRANCE... 13 3.6 EXAMPLE 2 : SCT INSTRUCTION FROM FRANCE TO GERMANY AND FRANCE... 16 APPENDIX 1 : SEPA COUNTRY CODES... 19 APPENDIX 2 : FRENCH OVERSEAS TERRITORIES AREA CODES... 19 APPENDIX 3 : RULE FOR ENTERING SEPA PAYMENT DATES... 19 APPENDIX 4: RULES FOR THE DETERMINATION OF THE CREDITOR AGENT S BIC... 20 APPENDIX 5: RULES FOR THE DETERMINATION OF THE DEBTOR AGENT S BIC... 20 Additional information can be consulted on the following web sites : ISO 20 022 : http://www.iso20022.org/ CFONB : http://www.cfonb.org/ ISO (country codes) http://www.iso.org/iso/english_country_names_and_code_elements SEPA Credit Transfer guideline for Société Générale France August 2015 P 2/20

1 INTRODUCTION The guide describes how to implement instructions of SEPA credit transfer under the ISO 20022 standard for cash movements with Société Générale France (which concerns the transactions in the debit of accounts owned in France or in Monaco) within the SEPA area. The message «CustomerCreditTransferInitiation» referenced as «pain.001.001.03» is used in order to allow the SEPA Credit Transfer instructions with the ISO 20022 standard of September, 2009. IMPORTANT To prevent messages from being rejected due to failure to comply with ISO 20022, it is important to use standard, proven applications that automatically generate strictly ISO 20022-compliant messages in XML format using an ISO XSD processor. The guideline complies with : - usage rules for ISO 20022 standard and XML format - usage rules for SCT Rulebook of the European Payment Council (EPC) - the guidelines published by the CFONB and by the GUF (available in French on the website http://www.cfonb.org/ ) This guide is composed of two parts : 1. 1. The general presentation of SEPA credit transfer orders in ISO 20022 format, with a description and explanation of how to complete the order. 2. The detailed description of the ISO 20022 format for SEPA credit transfer orders transmitted to SOCIETE GENERALE, with an example provided first in table form and then in XML format. Société Générale offers the following solutions for issuing SEPA credit transfers: - EBICS T, EBICS TS, Pe SIT - SWIFTNet FileAct, FTP, SFTP - e- banking sites Sogecash Net, Progeliance Net Subscription to the SEPA credit transfer service is done on the basis of the corresponding teletransmission or e-banking contract. Files are handled identically regardless of the transmission protocol except for these cases: Description de la spécificité du téléchargement Sogecash Net Progeliance Net Sogecash Web 1 message maximum par fichier X X X Only 1 Payment Information sequence is allowed Transaction is rejected if the Requested Execution Date is before day date (no replacement with the day date) Wherever is the anomaly positioning (GroupHeader level, PaymentInformation level, CreditTransferTransactionInformation), the whole file is rejected. Refer to 3.3.2 X X X X X X SEPA Credit Transfer guideline for Société Générale France August 2015 P 3/20

2 GENERAL PRESENTATION OF THE SEPA CREDIT TRANSFER INSTRUCTION IN ISO 20022 STANDARD 2.1 SEPA CREDIT TRANSFER INSTRUCTION A SEPA Credit Transfer instruction must be in line with the following specifications: - Euro payment - Between two accounts within the SEPA area.(a) - Amount between 0.01 and 999 999 999.99 euros - Non urgent - With BIC and IBAN codes in order to identify the debtor account and the creditor account (b) - Shared charge bearer option - Without any particular instructions or intermediary banks. Any credit transfer instruction that will not follow the above-mentioned specifications will be rejected. SEPA Credit Transfer instructed send from a non-euro account must be transmitted on the Cross boarder transfer service. (a) The SEPA area includes currently 34 countries (cf Appendix 1 for the list of countries and their corresponding codes). Société Générale also accepts credit transfers to French overseas territories that are not included in the SEPA area : Wallis and Futuna, the New Caledonia and French Polynesia. (cf Appendix 2 for the list of French overseas territories and their corresponding codes) (b) According to the European "end date" regulation (Regulation 260/2012), BIC is no more mandatory - for domestic transactions since 1 February 2014 - for cross-border transactions in euro countries as from 1 February 2016 - for cross-border transactions in non-euro countries as from 31 october 2016 The creditor agent s BIC is not required, specific rule is detailed in Appendix 4. The debtor agent s BIC is advised if the IBAN of the debtor agent contains the country code FR or MC for SCT transmitted by teletransmission or e-banking products. The specific rule is detailed in Appendix 5. 2.2 ISO 20022 STANDARD "pain.001.001.03" There are three levels in the ISO 2022 "pain.001.001.03" message: 1. GroupHeader This building block is mandatory and present once. It contains one or several PaymentInformation blocks. 2. PaymentInformation This building block is mandatory and repetitive. This block is a set of transactions or credit transfer orders that applies to a single account to be debited and to the same execution date. 3. CreditTransferTransactionInformation This building block is mandatory and repetitive. This block is a set of elements providing specific information to each individual transaction(s) included in the Payment Information block. SEPA Credit Transfer guideline for Société Générale France August 2015 P 4/20

MESSAGE ISO 20022 DESCRIPTION FOR A CREDIT TRANSFER INSTRUCTION The sign + on the first column indicates that the element is composed of a set of elements The elements not used for the SEPA Credit Transfer instruction are in grey color (Status N) CustomerCreditTransferInitiation ISO 20022 Standard Message item Statut A. GroupHeader M MessageIdentification M CreationDateTime M Authorisation N NumberOfTransactions M ControlSum R + InitiatingParty M + ForwardingAgent N B. PaymentInformation M PaymentInformationIdentification M PaymentMethod M BatchBooking O NumberOfTransactions R ControlSum R + PaymentTypeInformation R RequestedExecutionDate M PoolingAdjustmentDate N + Debtor M + DebtorAccount M + DebtorAgent M + DebtorAgentAccount N + UltimateDebtor O ChargeBearer O + ChargesAccount N + ChargesAccountAgent N C. CreditTransferTransactionInformation M + PaymentIdentification M + PaymentTypeInformation N + Amount M + ExchangeRateInformation N ChargeBearer N + ChequeInstruction N + UltimateDebtor O + IntermediaryAgent1 N + IntermediaryAgent1Account N + IntermediaryAgent2 N + IntermediaryAgent2Account N + IntermediaryAgent3 N + IntermediaryAgent3Account N + CreditorAgent D + CreditorAgentAccount N + Creditor R + CreditorAccount R + UltimateCreditor O + InstructionForCreditorAgent N InstructionForDebtorAgent N + Purpose O + RegulatoryReporting N + Tax N + RelatedRemittanceInformation N + RemittanceInformation O M Mandatory O Optional D Dependent R Required A Advised N Not used GROUP HEADER PAYMENT INFORMATION TRANSACTION INFORMATION SEPA Credit Transfer guideline for Société Générale France August 2015 P 5/20

3 DETAILED DESCRIPTION OF THE MESSAGE FOR «SEPA CREDIT TRANSFER INSTRUCTION» 3.1 DESCRIPTION PRESENTATION The detailed description is provided in paragraph 3.4 in the form of a table with nine columns and as many lines as elements of information. The table shows the presentation adopted by the ISO 20022, except for the indicator Or that is not shown because no item included in this guide is linked to this indicator. Index : Element index Level : Hierarchy level of the item : + : first level, ++ : second level, etc. Message Item : Name of the item as indicated in the ISO 20022 standard <XML tag> : Name of the XML marker for the item Mult. : Number of minimal and maximal occurrences of the ISO 20022 standard indicated as follows [x..y]. If the minimal number x is zero then the item is optional; if minimal number is one then the item is mandatory. Format : Type and length of the item Amount: the maximum length includes fraction digits and the decimal separator. Decimals are separated by a decimal point. External code table : tables are available on the ISO website with the following url : http://www.iso20022.org/external_code_lists_and_dss.page Status : Indicates if the item is optional or mandatory for a SEPA Credit Transfer instruction sent to Société Générale. Code Signification Comment M Mandatory Mandatory in the ISO 20022 standard message R D A O Required Dependent Advised Optional Item mandatory for this guideline even it is optional for ISO 20022 Standard Mandatory under some conditions, specially depending on other elements in the message Item is highly recommended (the information is useful for some parties or for the beneficiary of the transaction) Can be useful for the beneficiary but not useful for the process of the transaction N Not used The data, if used, is not processed by Société Générale Name and definition of the item. Comment: Specific comments regarding the item. A value described by quote mark specifies the value code to be used for the item. 3.2 OPERATING RULES The matrix shows only the items recommended by Société Générale for the SEPA Credit Transfer instruction. For any specific questions not covered by this document, please contact your regular Societe Generale contact person. The inclusion of items not indicated in this guideline, but which are compliant with "pain.001.001.03", will not prevent the transaction from being processed. In such case, these elements are ignored. The same is true for elements with "IGNORED" indicated in the Comments column. If an item used is a Composed element (group of items), it is mandatory to fill in at least one of the elementary item that is part of the composed element. An individual element in a composite element marked M for mandatory must be provided if the composite element to which it is attached is present. Example: the element 2.87 "Code" (M), be a part of the composed element "Purpose" (O). If you prefer not to fill in the element 2.87, you should not use the element 2.86. If an item is present on both levels, PaymentInformation level and Transaction level (e.g 2.23 et 2.70 "Ultimate Debtor"), it is advised to fill in the information on the PaymentInformation level, if possible. SEPA Credit Transfer guideline for Société Générale France August 2015 P 6/20

3.3 CONTROLS PERFORMED AT THE RECEPTION OF THE FILE The controls are performed on three levels : - Syntax error : compliance with ISO 20022 standards - Banking rules : compliance with the recommendations stipulated by Société Générale (see the column Comment in the matrix 3.4). - Allowed characters 3.3.1 Compliance control with ISO 20022 standard In order to allow a Straight Through Processing, the message should comply with the rules of the "pain.001.001.03" message under the ISO 20022 standard, independently of the presence and relevance of the banking data provided. Otherwise, the GroupHeader, the PaymentInformation and/or the Transaction level will be rejected even if the error is not related to data that is required to issue the Credit Transfer order. It is therefore compulsory to use standard softwares/tools generating automatically XML ISO 20022 messages that are XSD compliant. The controls examine the following: - accuracy of tag names - the hierarchy of the XML marker - consistency of tag arrangement - appropriate use of a closing tag for every opening tag - validity of codes used - use of mandatory characters (or dependent characters where necessary) - etc. The level of rejection depends on the positioning of the anomaly (*): Anomaly positioning Rejection level GroupHeader PaymentInformation CreditTransferTransactionInformation All the message The related PaymentInformation is rejected. The remaining correct PaymentInformations are processed. The related transaction is rejected. The remaining correct transactions are processed 3.3.2 Compliance with banking rules (*) The controls are based on the presence and the correctness of banking data that are mandatory on the «S» column in the matrix : - «M» for Mandatory, - «R» for Required, - «D» for Dependent (ie the element is mandatory if the relevant condition is met). The data must be present and correct. As for the syntax control, depending on whether the anomaly is found in the GroupHeader, at the PaymentInformation level or at the transaction level, the rejection will be related to the GroupHeader,the PaymentInformation or the transaction. (*) Regarding uploaded files through Sogecash Net, Progeliance Net, Sogecash Web, wherever is the anomaly positioning (GroupHeader level, PaymentInformation level, Credit Transfer TransactionInformation), the whole file is rejected. SEPA Credit Transfer guideline for Société Générale France August 2015 P 7/20

3.3.3 Allowed characters The characters accepted by the European clearing systems are those listed below (see list of authorized characters). However, Société Générale does not always reject the messages containing characters that are not listed. If specific XML characters are used (see list of forbidden characters below) the message will be rejected. Other non listed characters will be accepted by Société Générale but they may be changed through the processing. LIST OF THE AUTHORISED CHARACTERS a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / -? : ( )., + Espace LIST OF FORBIDDEN CHARACTERS < > " & Warning: the / (slash) character is forbidden is first and last position of alphanumeric fields. Usage of // (double slash) is forbidden in alphanumeric fields. 3.3.4 Debtor address compliance To comply with regulatory request, Societe Generale fill in Credit Transfer with the address of the debtor. The customer does not have to give this address in XML file, Societe Generale fill in the file with the address in its repository. If these tags are filled in by the client, Credit Transfer will not be rejected, the address will be replaced by Societe Generale. SEPA Credit Transfer guideline for Société Générale France August 2015 P 8/20

3.4 ISO 20022 STANDARD pain.001.001.03 FOR SEPA CREDIT TRANSFER INSTRUCTION Index Level Message Item <XML Tag> Mult. Format S Name and definition Comment 1.0 GroupHeader <GrpHdr> [1..1] Composed M Message header 1.1 + Message Identification <MsgId> [1..1] Max35Text M Message reference IGNORED Date and time at which message was created by the 1.2 + CreationDateTime <CreDtTm> [1..1] Format ISO instructing party M YYYY-MM-DDThh:mm:ss (T is the separator) 1.6 + NumberOf Transactions <NbOfTxs> [1..1] 15 num maxi, sans décimales M Number of transactions contained in the message Total of all individual amounts (instructed amount) 1.7 + ControlSum <CtrlSum> [0..1] 18 num maxi. R included in the message IGNORED 1.8 + InitiatingParty <InitgPty> [1..1] Composite M Party initiating the payment IGNORED 1.8 ++ Name <Nm> [0..1] Max70Text R Name of the Initiating Party IGNORED Rejection in case of incoherence with the number of transactions of the message Rejection in case of incoherence with the global amount of transactions of the message Cents separated by a dot Index Level Message Item <XML Tag> Mult. Format S Name and definition Comment 2.0 2.1 + Payment Information Payment Information Identification Set of characteristics that applies to the debit <PmtInf> [1..n] Composite M side of the payment transactions Reference assigned to identify the payment information <PmtInfId> [1..1] Max35Text M block Highly recommended 2.2 + PaymentMethod <PmtMtd> [1..1] Code M Means of payment used to move the amount of money Use "TRF" Single entry by individual transaction or a batch entry for 2.3 + BatchBooking <BtchBookg> [0..1] TrueFalse O the sum of all transactions 2.4 + NumberOftransactions <NbOfTxs> [0..1] 15 num maxi R Number of transactions contained in the message Total of all individual amounts (instructed amount) 2.5 + ControlSum <CtrlSum> [0..1] 18 num maxi R included in the message 2.6 + PaymentType Information Group of information identifying the service level applied <PmtTpInf> [0..1] Composite R to the payment Agreement under which the transaction should be 2.8 ++ ServiceLevel <SvcLvl> [0..1] Composite R processed 2.9 +++ Code <Cd> [1..1] ExternalServic M Pre-agreed level of service Use "SEPA" SEPA Credit Transfer guideline for Société Générale France August 2015 P 9/20 To be repeated as many times as there is Payment Information (a) This identification appears on the debtor account statement if batchbooking is used "true" = batch booking "false" = booking per transaction Rejection in case of incoherence with the number of transactions of the message Rejection in case of incoherence with the global amount of transactions of the message Cents separated by a dot

Index Level Message Item <XML Tag> Mult. Format S Name and definition Comment 2.17 + Requested ExecutionDate elevel1code <ReqdExctnDt> [1..1] ISODate YYYY-MM-DD M Date requested to process the payment (also the date on which the debtor's account is to be debited). Maximum 30 working days in advance expected. For the definition of the execution date and how to fill it in, please see appendix further in this document. 2.19 + Debtor <Dbtr> [1..1] Composite M Party that owes an amount of money to the creditor The account holder of the account to be debited 2.19 ++ Name <Nm> [0..1] Max140Text R Name of the Debtor Name of the account holder. Max 70 Text. 2.19 ++ Identification <Id> [0..1] Composite O Identification 2.19 +++ OrganisationIdentificati on <OrgId> [1..1] Composite M Type of identification 2.19 ++++ Other <Othr> [1..1] Composite M Debtor identification Only 1 occurrence 2.19 +++++ Identification <Id> [0..1] Max35Text R Debtor identification 2.19 +++++ SchemeName <SchmeNm> [0..1] Composite R Debtor identification Contract number ; 6 characters length To be used if different processing rules apply to the same remittance accounts. 2.19 ++++++ Code <Cd> [1..1] Code M Debtor identification "BANK" if contract number populated 2.20 + DebtorAccount <DbtrAcct> [1..1] Composite M Identification of the account of the debtor 2.20 ++ Identification <Id> [1..1] Composite M Account identification 2.20 +++ IBAN <IBAN> [1..1] IBANIdentifier M International Bank Account Number IBAN code must be 27 characters length 2.21 + DebtorAgent <DbtrAgt> [1..1] Composite M Financial institution servicing an account for the debtor 2.21 ++ FinancialInstitution Identification <FinInstnId> [1..1] Composite M Identification of the bank 2.21 +++ BIC <BIC> [1..1] BICIdentifier 8 or 11 char. A Bank Identifier Code of the Debtor Agent 2.21 +++ Other <Othr> [0..1] Composite D If 2.21 <BIC> is not filled Use "SOGEFRPP" for France, SOGEMCM1 for Monaco. BIC rule in annexe 5 2.21 ++++ Identification <Id> [1..1] Max35Text M If 2.21 <BIC> is not filled Only NOTPROVIDED" is allowed Ultimate party that owes an amount of money to the 2.23 + UltimateDebtor <UltmtDbtr> [0..1] Composite O creditor, notably in the case of a payment factory. 2.23 ++ Name <Nm> [0..1] Max140Text R Name of the Ultimate Debtor Specifies which party/parties will bear the payment 2.24 + ChargeBearer <ChrgBr> [0..1] Code O transaction charges (a) : In the web sites Sogecash Net, Progeliance Net and Sogecash Web, only one Payment Information sequence is allowed. Appears on the debtor account statement. Max 70 Text. Use "SLEV" SEPA Credit Transfer guideline for Société Générale France August 2015 P 10/20

Index Level Message Item <XML Tag> Mult. Format S Name and definition Comment 2.27 + CreditTransfer Transaction Information <CdtTrfTxInf> [1..n] Composed M Set of elements of each individual transaction 2.28 ++ PaymentIdentification <PmtId> [1..1] Composite M Identification of the instruction 2.29 +++ InstructionIdentification <InstrId> [0..1] Max35Text O Reference of the instruction for the debtor 2.30 +++ EndToEnd Identification <EndToEndId> [1..1] Max35Text End to End Reference of the instruction to be carried M to the creditor Amount of money to be moved between the debtor 2.42 ++ Amount <Amt> [1..1] Composite M and creditor 2.43 +++ InstructedAmount <InstdAmt> Montant décimal Currency and amount of the transaction [1..1] M Maxi 12 0.01 to 999 999 999.99. EUR Ultimate party that owes an amount of money to the 2.70 ++ UltimateDebtor <UltmtDbtr> [0..1] Composite O creditor, notably in the case of a payment factory 2.70 +++ Name <Nm> [0..1] Max140Text R Ultimate Debtor Name 2.77 ++ CreditorAgent <CdtrAgt> [0..1] Composite Financial institution servicing an account for the D creditor 2.77 +++ FinancialInstitution Identification <FinInstnId> [1..1] Composite M Identification of the Creditor Agent 2.77 ++++ BIC <BIC> [0..1] BICIdentifier 8 ou 11 car. M BIC of the CreditorAgent 2.79 ++ Creditor <Cdtr> [0..1] Composite R Party to which an amount of money is due 2.79 +++ Name <Nm> [0..1] Max140Text R Name of the Creditor 2.80 ++ CreditorAccount <CdtrAcct> [0..1] Composite R Identification of the account of the creditor 2.80 +++ Identification <Id> [1..1] Composite M Identification of the Creditor Account 2.80 ++++ IBAN <IBAN> [1..1] IBANIdentifier Max 34 car. M IBAN of the Creditor Account 2.81 ++ UltimateCreditor <UltmtCdtr> [0..1] Composite O Ultimate Creditor if it is different from the Creditor To be repeated as many times as there is Transaction It is reported on the debtor account statement in case of unitary booking It is reported on the debtor account statement in case of unitary booking Amount > 0 euros. Cents separated by a dot Prefer index 2.19, except if several "ultimate debtors" are indicated on the PaymentInformation level Reported on the debtor account statement in case of unitary booking BIC is not required if the IBAN country code is FR or MC. See detailed rule in Appendix 4. The country code of the BIC should be in the SEPA area (See Appendix 1). Non SEPA territories are accepted (see Appendix 2) 2.81 +++ Name <Nm> [0..1] Max140Text R Name of the Ultimate Creditor Limité à 70 caractères 2.86 ++ Purpose <Purp> [0..1] Composite O Nature of the payment 2.87 +++ Code <Cd> [1..1] ExternalPurpose Level1Code M Code defining the nature of the payment 2.98 ++ RemittanceInformation <RmtInf> [0..1] Composite O Information forwarded to the creditor 2.99 +++ Unstructured <Ustrd> [0..n] Max140Text A Remittance Information in an unstructured form Remittance Information is destined to the Creditor. Unstructured (advised) or Structured Identification of the payment expected by the creditor (only 1 occurrence) SEPA Credit Transfer guideline for Société Générale France August 2015 P 11/20

Index Level Message Item <XML Tag> Mult. Format S Name and definition Comment 2.100 +++ Structured <Strd> [0..n] Composite Max140Text 2.120 ++++ Creditor Reference Information D Remittance information in a structured form <CdtrRefinf> [0..1] Composite O Reference provided by the creditor 2.121 +++++ Type <Tp> [0..1] Composite R Type of provided reference 2.122 ++++++ CodeOrProprietary <CdOrPrtry> [1..1] Composite M Type of code or reference format 2.123 ++++++ + Identification of the payment expected by the creditor (only 1 occurrence) Code <Cd> [1..1] Composite M Reference type SCOR (StructuredCOmmunicationReference) 2.126 +++++ Reference <Ref> [0..1] Max35text R reference Reference of the SEPA transfer provided by the creditor. SEPA Credit Transfer guideline for Société Générale France August 2015 P 12/20

3.5 EXAMPLE 1 : ELEMENTARY MESSAGE WITH SCT INSTRUCTIONS FROM FRANCE TO FRANCE This first example resumes current elements for the issue of SCT without debtor s agent BIC. Message sent by ABCD TELECOM SA with 1 Payment Information including 2 Transactions. Payment Information - with requested execution date on 28 th January 2011 - to be debited from ABCD TELECOM SA banking account, - IBAN is FR7630003012340001122334489 - with reference Remittance 20080128 No 004578 Transaction 1 - to be credited to BAC IMMOBILIER banking account, - IBAN is FR7612345123450123456789006 - instructed amount is 51 252,98 EUR, - with end to end reference INV20080100348, - and remittance information «January 2011 rent» Transaction 2 - to be credited to CABINET ARTHUR ET ASSOCIES banking account, - IBAN is FR7654321012340001234567816 - instructed amount is 2 500,00 EUR, - with end to end reference 586478954X, - and remittance information «DUCLOS s business advance» 3.5.1 Example with matrix template Index Level Message Item <XML Tag> Mult. S Example 1.0 GroupHeader <GrpHdr> [1..1] M 1.1 + MessageIdentification <MsgId> [1..1] M MESS2011-65897 1.2 + CreationDateTime <CreDtTm> [1..1] M 2011-01-28T10:08:28 1.6 + NumberOfTransactions <NbOfTxs> [1..1] M 2 1.7 + ControlSum <CtrlSum> [0..1] R 53752.98 1.8 + InitiatingParty <InitgPty> [1..1] M 1.8 ++ Name <Nm> [0..1] R ABCD TELECOM SA 2.0 PaymentInformation <PmtInf> [1..n] M Description First payment 2.1 + PaymentInformationIdentification <PmtInfId> [1..1] M Remittance 20110128 No 004578 2.2 + PaymentMethod <PmtMtd> [1..1] M TRF 2.4 + NumberOfTransactions <NbOfTxs> [0..1] R 2 2.5 + ControlSum <CtrlSum> [0..1] R 53752.98 2.6 + PaymentTypeInformation <PmtTpInf> [0..1] R 2.8 ++ ServiceLevel <SvcLvl> [0..1] R 2.9 +++ Code <Cd> [1..1] M SEPA 2.17 + RequestedExecutionDate <ReqdExctnDt> [1..1] M 2011-01-28 2.19 + Debtor <Dbtr> [1..1] M 2.19 ++ Name <Nm> [0..1] R ABCD TELECOM SA 2.20 + DebtorAccount <DbtrAcct> [1..1] M 2.20 ++ Identification <Id> [1..1] M 2.20 +++ IBAN <IBAN> [1..1] M FR7630003012340001122334489 2.21 + DebtorAgent <DbtrAgt> [1..1] M 2.21 ++ FinancialInstitutionIdentification <FinInstnId> [1..1] M 2.21 +++ Other <Othr> [0..1] D 2.21 ++++ Identification <Id> [1..1] M NOTPROVIDED SEPA Credit Transfer guideline for Société Générale France August 2015 P 13/20

Index Level Message Item <XML Tag> Mult. S Example 2.27 + CreditTransferTransactionInformation <CdtTrfTxInf> [1..n] M Description Transaction 1 2.28 ++ PaymentIdentification <PmtId> [1..1] M 2.30 +++ EndToEndIdentification <EndToEndId> [1..1] M INV20080100348, 2.42 ++ Amount <Amt> [1..1] M 2.43 +++ InstructedAmount <InstdAmt> [1..1] M 51252.98 EUR 2.79 ++ Creditor <Cdtr> [0..1] R 2.79 +++ Name <Nm> [0..1] R BAC IMMOBILIER 2.80 ++ CreditorAccount <CdtrAcct> [0..1] R 2.80 +++ Identification <Id> [1..1] M 2.80 ++++ IBAN <IBAN> [1..1] M FR7612345123450123456789006 2.98 ++ RemittanceInformation <RmtInf> [0..1] O 2.99 +++ Unstructured <Ustrd> [0..n] R January 2011 rent 2.23 + CreditTransferTransactionInformation <CdtTrfTxInf> [1..n] M Description Transaction 2 2.28 ++ PaymentIdentification <PmtId> [1..1] M 2.30 +++ EndToEndIdentification <EndToEndId> [1..1] M 586478954X 2.42 ++ Amount <Amt> [1..1] M 2.43 +++ InstructedAmount <InstdAmt> [1..1] M 2500 EUR 2.79 ++ Creditor <Cdtr> [0..1] R 2.79 +++ Name <Nm> [0..1] R 2.80 ++ CreditorAccount <CdtrAcct> [0..1] R 2.80 +++ Identification <Id> [1..1] M CABINET ARTHUR ET ASSOCIES 2.80 ++++ IBAN <IBAN> [1..1] M FR7654321012340001234567816 2.98 ++ RemittanceInformation <RmtInf> [0..1] O 2.99 +++ Unstructured <Ustrd> [0..n] R DUCLOS s business advance SEPA Credit Transfer guideline for Société Générale France August 2015 P 14/20

3.5.2 Example with XML standard <?xml version="1.0" encoding="utf-8" standalone="no"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>MESS2011-65897</MsgId> <CreDtTm>2011-01-28T10:08:28</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>53752.98</CtrlSum> <InitgPty> <Nm>ABCD TELECOM SA</Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId>Remittance 20110128 No 004578</PmtInfId> <PmtMtd>TRF</PmtMtd> <NbOfTxs>2</NbOfTxs> <CtrlSum>53752.98</CtrlSum> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> <ReqdExctnDt>2011-01-28</ReqdExctnDt> <Dbtr> <Nm>ABCD TELECOM SA</Nm> </Dbtr> <DbtrAcct> <Id> <IBAN>FR7630003012340001122334489</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <Othr> <Id>NOTPROVIDED</Id> </Othr> </FinInstnId> </DbtrAgt> <CdtTrfTxInf> <PmtId> <EndToEndId>INV20080100348</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">51252.98</InstdAmt> </Amt> <Cdtr> <Nm>BAC IMMOBILIER</Nm> </Cdtr> <CdtrAcct> <Id> <IBAN>FR7612345123450123456789006</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd> January 2011 rent </Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <EndToEndId>586478954X</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">2500</InstdAmt> </Amt> <Cdtr> <Nm>CABINET ARTHUR ET ASSOCIES</Nm> </Cdtr> <CdtrAcct> <Id> <IBAN>FR7654321012340001234567816</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd> DUCLOS s business advance </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> SEPA Credit Transfer guideline for Société Générale France August 2015 P 15/20

3.6 EXAMPLE 2 : SCT INSTRUCTION FROM FRANCE TO GERMANY AND FRANCE This 2nd example uses the diverse possibilities proposed by the ISO format 20022. A SEPA Credit Transfer message is sent by TRITA Services SA with one Payment Information including one Transaction. Payment - With requested execution date on the 28/01/2011, - To be debited from TRITA Paiements, on behalf of TRITA Industry - BIC/IBAN SOGEFRPP FR7630003012340001234567854 - With reference Remittance 28/1/2011 No 1235874 Transaction 1 - To be credited to TREBOT Finance, - BIC/IBAN DRTJDEFF DE89370400440532013000 - Instructed amount : 51252,98 EUR, - With instruction identification Transfer 485A, - With End to End Id 8752369875, - Remittance information : «invoices: 1259A, 8578M, 47892J, 59874F» Transaction 2 - to be credited to BAC IMMOBILIER banking account, - IBAN: FR7612345123450123456789006 - instructed amount is 20000 EUR, - with end to end reference INV20080100348, - and remittance information «January 2011 rent 3.6.1 Example with matrix template Index Level Message Item <XML Tag> Mult. S Example 1.0 GroupHeader <GrpHdr> [1..1] M 1.1 + MessageIdentification <MsgId> [1..1] M 1256ADHY-65897 1.2 + CreationDateTime <CreDtTm> [1..1] M 2011-01-28T09:07:00 1.6 + NumberOfTransactions <NbOfTxs> [1..1] M 2 1.7 + ControlSum <CtrlSum> [0..1] R 71252.98 1.8 + InitiatingParty <InitgPty> [1..1] M 1.8 ++ Name <Nm> [0..1] R TRITA Services SA 2.0 PaymentInformation <PmtInf> [1..n] M Description First payment 2.1 + PaymentInformationIdentification <PmtInfId> [1..1] M 2.2 + PaymentMethod <PmtMtd> [1..1] M TRF 2.4 + NumberOfTransactions <NbOfTxs> [0..1] R 2 2.5 + ControlSum <CtrlSum> [0..1] R 71252.98 2.6 + PaymentTypeInformation <PmtTpInf> [0..1] R 2.8 ++ ServiceLevel <SvcLvl> [0..1] R 2.9 +++ Code <Cd> [1..1] M SEPA 2.17 + RequestedExecutionDate <ReqdExctnDt> [1..1] M 2011-01-28 2.19 + Debtor <Dbtr> [1..1] M Remittance 28/1/2011 No 1235874 2.19 ++ Name <Nm> [0..1] R TRITA Paiements 2.20 + DebtorAccount <DbtrAcct> [1..1] M 2.20 ++ Identification <Id> [1..1] M 2.20 +++ IBAN <IBAN> [1..1] M FR7630003012340001234567854 2.21 + DebtorAgent <DbtrAgt> [1..1] M 2.21 ++ FinancialInstitutionIdentification <FinInstnId> [1..1] M SEPA Credit Transfer guideline for Société Générale France August 2015 P 16/20

Index Level Message Item <XML Tag> Mult. S Example 2.21 +++ BIC <BIC> [0..1] M SOGEFRPP 2.23 + UltimateDebtor <UltmtDbtr> [0..1] O 2.23 ++ Name <Nm> [0..1] R TRITA Industry SA 2.27 + CreditTransferTransactionInformation <CdtTrfTxInf> [1..n] M Description Transaction 1 2.28 ++ PaymentIdentification <PmtId> [1..1] M 2.29 +++ InstructionIdentification <InstrId> [0..1] O Transfer 4585A 2.30 +++ EndToEndIdentification <EndToEndId> [1..1] M 8752369875 2.42 ++ Amount <Amt> [1..1] M 2.43 +++ InstructedAmount <InstdAmt> [1..1] M 51252.98 EUR 2.77 ++ CreditorAgent <CdtrAgt> [0..1] D 2.77 +++ FinancialInstitutionIdentification <FinInstnId> [1..1] M 2.77 ++++ BIC <BIC> [0..1] M DRTJDEFF 2.79 ++ Creditor <Cdtr> [0..1] R 2.79 +++ Name <Nm> [0..1] R TREBOT Finance 2.80 ++ CreditorAccount <CdtrAcct> [0..1] R 2.80 +++ Identification <Id> [1..1] M 2.80 ++++ IBAN <IBAN> [1..1] M DE89370400440532013000 2.98 ++ RemittanceInformation <RmtInf> [0..1] O 2.99 +++ Unstructured <Ustrd> [0..n] R invoices : 1259A, 8578M, 47892J, 59874F 2.27 + CreditTransferTransactionInformation <CdtTrfTxInf> [1..n] M Description Transaction 2 2.28 ++ PaymentIdentification <PmtId> [1..1] M 2.30 +++ EndToEndIdentification <EndToEndId> [1..1] M INV20080100348 2.42 ++ Amount <Amt> [1..1] M 2.43 +++ InstructedAmount <InstdAmt> [1..1] M 20000 EUR 2.79 ++ Creditor <Cdtr> [0..1] R 2.79 +++ Name <Nm> [0..1] R BAC IMMOBILIER 2.80 ++ CreditorAccount <CdtrAcct> [0..1] R 2.80 +++ Identification <Id> [1..1] M 2.80 ++++ IBAN <IBAN> [1..1] M FR7612345123450123456789006 2.98 ++ RemittanceInformation <RmtInf> [0..1] O 2.99 +++ Unstructured <Ustrd> [0..n] A January 2011 rent SEPA Credit Transfer guideline for Société Générale France August 2015 P 17/20

3.6.2 Sous forme de représentation XML <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>1256ADHY- 65897</MsgId> <CreDtTm>2011-01-28T09:07:00</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>71252.98</CtrlSum> <InitgPty><Nm>TRITA Services SA</Nm></InitgPty> </GrpHdr> <PmtInf> <PmtInfId>Remittance 28/1/2011 No 1235874</PmtInfId> <PmtMtd>TRF</PmtMtd> <NbOfTxs>2</NbOfTxs> <CtrlSum>71252.98 </CtrlSum> <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> </PmtTpInf> <ReqdExctnDt>2011-01-28</ReqdExctnDt> <Dbtr> <Nm>TRITA Paiements</Nm> </Dbtr> <DbtrAcct> <Id> <IBAN>FR7630003012340001234567854</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>SOGEFRPP</BIC> </FinInstnId> </DbtrAgt> <UltmtDbtr> <Nm>TRITA Industry</Nm> </UltmtDbtr> <CdtTrfTxInf> <PmtId> <InstrId>Transfer 4585A</InstrId> <EndToEndId>8752369875</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">51252.98</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>DRTJDEFF</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>TREBOT Finance</Nm> </Cdtr> <CdtrAcct> <Id> <IBAN>DE89370400440532013000</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>invoices : 1259A, 8578M, 47892J, 59874F</Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <EndToEndId>INV20080100348</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">51252.98</InstdAmt> </Amt> <Cdtr> <Nm>BAC IMMOBILIER</Nm> </Cdtr> <CdtrAcct> <Id> <IBAN>FR7612345123450123456789006</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd> January 2011 rent </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document>

APPENDIX 1 : SEPA COUNTRY CODES Austria AT Iceland IS Belgium BE Italy IT Bulgaria BG Latvia LV Croatia HR Lichtenstein LI Cyprus CY Lithuania LT Czech Republic CZ Luxembourg LU Denmark DK Malta MT Estonia EE Monaco MC Finland FI Norway NO France FR Netherlands NL Guadeloupe GP Poland PL Guyana GF Portugal PT Martinique MQ Including Azores and Madeira Mayotte YT Romania RO Réunion RE United Kingdom GB Saint Barthélémy BL Gibraltar GI Saint Martin MF San Marino SM Saint-Pierre et Miquelon PM Slovakia SK Germany DE Slovenia SI Greece GR Spain ES Hungary HU Including Canary Islands, Ceuta and Melilla Ireland IE Sweden SE Switzerland The codes of the other countries are available on http://www.iso.org/iso/english_country_names_and_code_elements CH APPENDIX 2 : FRENCH OVERSEAS TERRITORIES AREA CODES The New Caledonia French Polynesia Wallis et Futuna NC PF WF These French overseas territories are not included in the SEPA area. APPENDIX 3 : RULE FOR ENTERING SEPA PAYMENT DATES The date entered in the Requested ExecutionDate ** index (payment information block) is the execution date which corresponds to the working day before the interbank settlement date and to the booking date of your transaction. In order to pay the banks of your counterparties on day D*, the date to be entered is working day D-1. If the Requested Execution date is before the Societe Generale processing date, a new execution date will be calculated (day date) if the instruction was teletransmited. For e-banking, credit transfer with an execution date before day date will be rejected. * beneficiaries are paid on day D in virtually all cases if instructions are received before the applicable time limit. **index 2.17 in pain.001.001.03 SEPA Credit Transfer guideline for Société Générale France August 2015 P 19/20

APPENDIX 4: RULES FOR THE DETERMINATION OF THE CREDITOR AGENT S BIC Operating rules This rule applies to the creditor agent s BIC. The creditor s agent BIC will be determined from the IBAN populated in the file. The creditor s agent BIC, if transmitted, will be ignored. However, if the BIC cannot be determined by Societe Generale and if the BIC populated in the file exists, then the BIC populated will be taken into account by Societe Generale. Additional comments If the creditor agent s BIC is not transmitted, the item 2.77 Creditor Agent must not be present. APPENDIX 5: RULES FOR THE DETERMINATION OF THE DEBTOR AGENT S BIC Scope The present rule applies to SEPA Credit Transfers with creditor s IBAN containing either the country code FR or the country code MC. Operating rules This rule applies to the debtor agent s BIC. If the debtor agent s BIC is populated, the BIC is kept without any further processing. If the debtor agent s BIC is not populated, the BIC will be determined from the IBAN populated in the file. IBAN must contain a country code with «FR» or «MC». If the debtor agent s BIC cannot be determined from the IBAN or if the BIC isn t transmitted with an IBAN from France or Monaco, the transaction is rejected Additional comments If the debtor agent s BIC is not transmitted, the item 2.21 <BIC> must not be present and must be replaced by items 2.21 <Othr> (composed) and 2.21 <Id>, this one being filled with the only authorized value NOTPROVIDED (refer to the example in 3.5). SEPA Credit Transfer guideline for Société Générale France August 2015 P 20/20