Wienerberger : Description ISO20022 SWIFT Messages

BusinessApplica onHeader:

1. The sending MessagingEndpoint (From ) has to be the first account holding Credit Ins tu on ("last intermediary" from the issuers' point of view) for the Rights Holder and has to be iden fied by its "FinancialIns tu onIden fica on" ().

b)The Crea onDate can only be a er the Record Date specified in the Mee ng Invita on(En tlementFixingDate ). As in Austria the DateMode always is "EODY" (End of Day - Vienna Time), the Crea on Date has to be at least one day a er the Record Date.

Message content (seev.003 and seev.004):

1. As reference to the original Issuer Mee ng Invita on the IssuerMee ngIden fica on has to be specified. This specifica on is relevant, as the sending MessagingEndpoint from the BusinessApplicatoinHeader thus confirms, that it is aware of the data from the original Mee ng Invita on and that the data specified in the message, especially with regard to the En tlementFixingDate, refers to the requirements specified in the Issuers Mee ng Invita on.
2. 
   If available the IssuerMee ngIden fica on has been published in the official invita on and the original XML is available for download on the issuers' homepage. If not available please refer to the official seev.001, forwarded by the issuer through the Intermediary Chain.
3. Fields required by law to accept the message as Holding Cer ficate:
4. • 
     Only the RightsHolder (first non-intermediary as per Austrian defini on) will be accepted as legal representa ve of the shares with all the a ached rights. The required fields, regarding the type of person of the shareholder are:
   • LegalPerson : NameAndAddress - Name , Adress consis ng of the following fields: The en re address consis ng of either up to 5 AddressLine's or the separated address fields or both; Iden fica on : At least one of the op ons provided.
   • NaturalPerson : NameAndAdress - Name consis ng of and , Adress in the same way as for a LegalPerson; DateAndPlaceOfBirth - BirthDate . Alterna vely also the Iden fica on can be used for the BirthDate, if the Iden fica onType is CUST, which means the CONCAT Iden fica on type, including the BirthDate.
   • Other fields:

- AccountIden fica on : If applicable, also with SubAccountIden fica on in seev.004

• Financial InstrumentIden fica on
• Balance (seev.003: , seev.004: ): Only balances of the BalanceType "INBA" will be accepted, only as "LONG", only as , frac on of the unit will be rounded down to an integer number. Units of 0 (zero) will not be accepted. The Unit specified in the balance will also be used in seev.004 for the vote instruc ons, as split vote is not allowed, i.e. if split vote is used in the vote instruc ons, the relevant instruc on will not be accepted, only the registra on, if correct. In case of split vo ng for the same account owner, several Posi ons in case of seev.003 or Instruc ons in case of seev.004 must be sent.
• En tlementFixingDate (Record Date): As only seev.003 provides this field but not, as used in seev.001 along with the DateMode (in Austria EODY - EndOfDay), the usage of this field in seev.003 is mandatory but anyway, as already men oned above, the field has to be used along with the correct defini on in order to reference to the seev.001.
• Crea onDate (BusinessApplica onHeader): As already men oned above, this has to be at least one day

1. a er the record date and not later as closing date.

2. Proxy handling: seev.003 and seev.004 can be used to name a proxy for a shareholder. For proper handling it is

recommended to send the message also within the meframe for the Holding Cer ficate, as only one message is required for both purposes (Holding Cer ficate and PoA). If the Proxy is sent in advance of the record date, an extra Holding Cer ficate has to be sent within the meframe men oned above. Proxies can be named usually un l one day before the Mee ng (business hours, Vienna me).

The required fields for the proxy nomina on are the name fields as well as at least the TownName , either included in the AddressLine or in the special field .

Empowering the Chairman of the mee ng or a board member will not be accepted. If several PoAs for the same shareholder are sent, the last one will gain effec veness.

Regarding empowering the proxy named by the issuer please see addi onal informa on below under "Instruc on handling".

1. Instruc on handling: Vote instruc ons can be handled via seev.004. In case the mee ng has no electronic vote op on, instruc ons can only be given altogether with the nomina on of one of the official proxies named by the issuer. Vote instruc ons given without this nomina on will be ignored.
   As men oned before any split vo ng will not be accepted and the instruc on, at least regarding the agenda items with split vo ng, will be ignored. If the official proxy named by the issuer is empowered, absence of vo ng instruc ons, regardless if not available or not acceptable will lead to the denial of the acceptance of the PoA.
   If no VoteInstruc onForMee ngResolu on is given an Absten on will be cast in case of vo ng behavior that is not covered through the instruc ons.
   Regarding the cancella on of Instruc ons, seev.005 is accepted. Regarding cancella on of seev.003, please see below under "Status messaging".
   Regarding VoteExecu onConfirma on please see below.
2. Status messaging: As we only can receive messages, status answers are only possible via another channel. As there is no proper field in the seev messages for the specifica on of an E-Mail - address for whom to contact it is necessary to either send your request via E-Mail to swi @hauptversammlung.ator to make a special agreement with us how to handle status messaging. This also applies to the cancella on of a seev.003 as well as the VoteExecu onConfirma on in seev.004.
3. Addi onal informa on: Filling the Mee ngA endee field will be ignored. Any guest requests have to be made either to the issuer or to the registra on e-mail - address published in the invita on.
   Any other informa on, than those we men oned, contained within the message will be ignored and not be processed (e.g. RightsHolder, other Balance types etc.).