new enhancements 0512

New Enhancements Supported by Citi (As of May 24th, 2012)

The following SWIFT SR2012 enhancements to be supported as of November 17th 2012 for Regions A, B and C unless otherwise indicated.

SWIFT definition changes are not included unless they provide a major impact to processing.

Regions

Region A

Asia Australia, Bangladesh, Hong Kong, India, Indonesia, Japan, Korea, Malaysia, New Zealand, Philippines, Singapore, Taiwan, Thailand

Central Europe Bulgaria, Croatia, Estonia, Latvia, Lithuania, Slovakia, Slovenia, Ukraine

Europe Austria, Belgium, Denmark, Finland, France, Germany, Ireland, Italy, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland, UK

Latin America/Central America Argentina, Brazil, Chile, Colombia, Costa Rica, Mexico, Peru, Venezuela

North America Canada

Middle East/Africa Botswana, Israel, Mauritius, South Africa, Zimbabwe

Caribbean Bermuda

Region B

Greece, Czech Republic, Egypt, Hungary, Jordan, Morocco, Pakistan, Poland, Romania, Russia, Sri Lanka, Turkey

Region C

United States

All applicable conditional, network validated and usage rules will be supported.

For Settlement Instruction and Confirmations, Status and Processing Advices, Interposition Movements and Settlement Allegements:

Message Sequence Tag Qualifier / Code Description

MT540-547MT578MT508

Sequence B1Financial Instrument Attributes

22FIndicator

PADIPREF

Requirement 1.0

Deletion of qualifier PREF and PADI from the 22F Indicator field in subsequence B1 (removed text shown as red strike through)

DEFINITIONThis qualified generic field specifies:CFRE Variable Rate Change Frequency IndicatorSpecifies the frequency of change to the variable rate of an interest bearing instrument.FORM Form of Securities IndicatorSpecifies the form of the financial instrument.MICO Method of Interest Computation IndicatorSpecifies the computation method of (accrued) interest of the financial instrument.PADI Payment Direction IndicatorSpecifies the direction of payment for factor securities, that is, whether the repaid capital is distributed (payment direction is down) or capitalized (payment direction is up).PAYS Payment Status IndicatorSpecifies the status of the payment of a financial instrument at a particular time, as agreed with the issuer.PFRE Payment Frequency IndicatorSpecifies the frequency of a payment.PREF Preference to Income IndicatorSpecifies the level of priority on income and assets of the company.

Deletion of codes associated with qualifier PREF in the 22F Indicator field subsequence B1 (removed text shown as red strike through)

CODESIf Qualifier is PREF and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):ORDN Ordinary/Common Indicates an ordinary/common claim on income and assets.PRFD Preferred Claim Indicates a preferred claim upon income and assets.

Deletion of codes associated with qualifier PADI in the 22F Indicator field subsequence B1 (removed text shown as red strike through)

CODESIf Qualifier is PADI and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):PAYD Down Direction of the payment is down.PAYU Up Direction of the payment is up.

Client Impact

Should be of no impact to clients as Citi does not currently support. However, clients should ensure that their settlement instructions no longer contain this information if currently provided.


MT540-547MT578


13aNumber Identification

POOL Requirement 1.1

Change in format options allowed for qualifier POOL in the 13a Number Identification field in subsequence B1. Currently options A and B are allowed for POOL . Only B will be allowed for POOL from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)] (removed text shown as red strike through)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O COUP N A or B Coupon Number2 O POOL N A or B Pool Number

Client Impact



MT540-547

MT578

Sequence C1Quantity Breakdown



LOTS Requirement 1.2

Change in format options allowed for qualifier LOTS in the 13a Number Identification field in subsequence C1. Currently options A and B are allowed for POOL . Option A is being deleted so only B will be allowed from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)] (removed text shown as red strike through)

FORMATOption A :4!c//3!c (Qualifier)(Number Id)Option B :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O LOTS N A or B Lot Number

Client Impact



MT508 Sequence BIntra Position Details



Deletion of qualifier LOTS in the 13a Number Identification field in sequence B and format option A. Currently options A and B are allowed but only B will be allowed from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)] (removed text shown as red strike through)


Client Impact

Should be of no impact to clients as Citi does not currently support.


MT508 Sequence B1Financial Instrument Attributes


POOLLOTS

Requirement 1.4

Change in format options allowed for qualifiers POOL and LOTS in the 13a Number Identification field in subsequence B1. Currently options A and B are allowed for POOL and A, B and K for LOTS. Only B will be allowed for POOL and B and K for LOTS from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number), K = :4!c//3!c/15d (Qualifier)(Number Id)(Quantity)] (removed text shown as red strike through)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O COUP N A or B Coupon Number2 O POOL N A or B Pool Number3 O LOTS N A, B Lot Number or K

Addition to the definition of the Network Validation Rule for field 13a Number Identification in subsequence B1 (addition shown in red bold)

NETWORK VALIDATED RULESNumber (Format Option B) must not start or end with a slash '/' and not contain two consecutive slashes '//' (Error code(s): T26).The integer part of Quantity (Format Option K) must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).

Client Impact

Should be of no impact to clients as Citi does not currently support.


MT540-547

MT548

Sequence ESettlement Details

Sequence BSettlement Transaction

22FIndicatory

SETR / RPTO Requirement 1.5

Deletion of optional code RPTO Reporting from qualifier SETR (Settlement Transaction Type) in the 22F Indicator field in sequence E (removed text shown in red strike through)

CODESIf Qualifier is SETR and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):.....RODE Return of Delivery Without MatchingRelates to the return of financial instruments resulting from a rejected delivery without matching operation.RPTO Reporting Relates to a transaction that is for reporting purposes only.RVPO Reverse Repo Relates to a reverse repurchase agreement transaction......

Client Impact

Although Citi does not support this process, field :22F::SETR//RPTO can be instructed on settlement instructions. Clients should ensure that this code is no longer used in their settlement instructions with qualifier SETR and if required, is now placed with qualifier STCO (see Requirement 1.6).


MT540-543 Sequence ESettlement Details

22FIndicatory

STCO / RPTO Requirement 1.6

Addition of optional new code RPTO Reporting to qualifier STCO (Settlement Transaction Condition Indicator) in the 22F Indicator field in sequence B (addition shown in red bold)

CODESIf Qualifier is STCO and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):.....RESI CSD Payment Only Relates to transaction on a security that is not eligible at the Central Securities Depository (CSD) but for which the payment will be enacted by the CSD.RPTO Reporting Relates to a transaction that is for reporting purposes only.SPDL Special Delivery Settlement transactions to be settled with special delivery.SPST Split Settlement Money and financial instruments settle in different locations.UNEX Unexposed Delivery cannot be performed until money is received.

Client Impact

See Requirement 1.5. Citi will not process this new code with qualifier STCO as happens today with qualifier SETR


MT540-547 Sequence E3Amount

19AAmount

POST Requirement 1.7

Deletion of qualifier POST from the 19A Amount field in subsequence E3 (removed text shown as red strike through)

DEFINITIONThis field specifies an amount of money. This field is part of a sequence which identifies amounts of money such as taxes and charges as well as amounts needed for accounting purposes, for example, original face value traded, broker commission, etc. This qualified generic field specifies:.....OCMT Original Currency AmountPosting/settlement amount in its original currency when conversion from/into another currency has occurred.OTHR Other Amount Amount of money that cannot be categorised.POST Postage Amount Amount of money paid for delivery by regular post mail.REGF Regulatory Fees Amount of money charged by a regulatory authority, for example, Securities and Exchange fees......

Qualifier POST will also be removed from the list of qualifiers available in Conditional Rule C1 of the Settlement Instruction and Confirmation messages (see Requirement 1.9)

Change in definition of qualifier SHIP in the 19A Amount field in subsequence E3 (addition shown in red, removed text shown as red strike through)

SHIP Shipping Amount All costs related to the physical delivery of documents such as stamps, postage, carrier fees, insurances or messenger services. Amount of money (including insurance) paid for delivery by carrier.

Client Impact

Although Citi does not support this qualifier, field :19A::POST can be instructed on settlement instructions. Clients should ensure that this qualifier is no longer used in their settlement instructions and if required, is now reflected through field :19A::SHIP


MT540-547 Sequence E3Amount

Conditional Rule19A

POST Requirement 1.8

Change in definition of Network Validation Rule C1 to the MT540-3 messages (addition shown in red bold, removed text in bold strike through)

C1 The following amount fields cannot appear in more than one occurrence of the subsequence E3 Amounts (Error code(s): E87).Subsequence E3:19A::ACRU :19A::ANTO :19A::BOOK :19A::CHAR :19A::COUN :19A::DEAL :19A::EXEC :19A::ISDI :19A::LADT :19A::LEVY :19A::LOCL :19A::LOCO:19A::MARG:19A::OTHR:19A::POST:19A::REGF:19A::SETT:19A::SHIP:19A::SPCN:19A::STAM:19A::STEX:19A::TRAN:19A::TRAX:19A::VATA:19A::WITH:19A::COAX:19A::ACCA

Client Impact

See Requirement 1.7. Clients should ensure qualifier POST is no longer included in their settlement instructions


MT540-543 Sequence FOther Parties

Conditional Rule95a97A

EXCHTRRESAFE

Requirement 1.9

Addition of Network Validation Rule C14 to the MT540 and the MT542 messages and Network Validation Rule C16 in the MT541 and MT543 messages (addition shown in red)

C14 or C16 In sequence F, if field :95a::EXCH Stock Exchange or :95a::TRRE Trade Regulator is present, then field :97a:: is not allowed in the same sequence (Error code(s): E63).

Sequence F if field :95a::EXCH or TRRE is ... PresentSequence F then field :97a:: is ... Not allowed within the same occurrence

Sequence F if field :95a::EXCH or TRRE is ... Not PresentSequence F then field :97a:: is ... Optional

Client Impact

Clients should ensure they adhere with the new Network Validation Rules if instructing either of the two parties impacted



Conditional Rule95a97A

EXCHTRRESAFE

Requirement 1.10

Addition of Network Validation Rule C11 to the MT544 and the MT546 messages and Network Validation Rule C12 in the MT545 and MT547 messages (addition shown in red)

C11 or C12In sequence F, if field :95a::EXCH Stock Exchange or :95a::TRRE Trade Regulator is present, then field :97a:: is not allowed in the same sequence (Error code(s): E63).

Sequence F if field :95a::EXCH or TRRE is ... PresentSequence F then field :97a:: is ... Not allowed within the same occurrence

Sequence F if field :95a::EXCH or TRRE is ... Not PresentSequence F then field :97a:: is ... Optional

Client Impact

Should be of no impact to clients as Citi does not support these qualifiers and codes at present. Citi will adhere to the new Network Validation Rules if applicable in the future



97AAccount

SAFE Requirement 1.11

Change in the definition of the "Presence" of field 97A Account in Sequence F (addition shown in red, removed text shown as red strike through)

MT540 and MT542

PRESENCEConditional (see rule C14) Optional in optional sequence F

MT541 and MT543


This now means Network Validation Rule C14 or C16 now applies to field 97A SAFE (Safekeeping Account). See requirement 1.10 for the addition of Network Validation Rule C14 and C16

Client Impact

See Requirement 1.10



97AAccount

SAFE Requirement 1.12

Change in the definition of the "Presence" of field 97A Account in Sequence F (addition shown in bold, removed text shown as red strike through)

MT540 and MT542


MT541 and MT543


This now means Network Validation Rule C14 or C16 now applies to field 97A SAFE (Safekeeping Account). See requirement 1.11 for the addition of Network Validation Rule C14 and C16

Client Impact

See Requirement 1.11


MT544-547

MT508

Sequence AGeneral Information

Sequence BIntra Position Details

22FIndicator

PARS / PARC Requirement 1.13

Change in definition of code PARC Previously Confirmed in field 22F with qualifier PARS Partial Settlement Indicator in sequence A (MT54y) and B (MT508) (addition shown in red, removed text in red strike through)

CODESIf Qualifier is PARS and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):PAIN Partial Settlement Confirmation is for partial settlement. Part of the instruction remains unsettled.PARC Previously Partially ConfirmedConfirmation is for partial settlement. No additional settlement will take place. the remaining part of an instruction that was previously partially confirmed.

Client Impact

Should be of no impact to clients as processing of partial settlements will remain as it is today


MT540-547 Sequence B1Financial Instrument Attributes

92ARate

YTMR Requirement 1.14

Addition of qualifier YTMR Yield to Maturity Rate in field 92A Rate in subsequence B1 (addition shown in red bold). Format option A only [:4!c//[N]15d (Qualifier)(Sign)(Rate)] and non-repetitive

DEFINITIONThis qualified generic field specifies:CUFC Current Factor Rate expressed as a decimal between 0 and 1 defining the outstanding principal of the financial instrument (for factored securities).INDX Index Factor Public index rate used for inflation adjustment.INTR Interest Rate Annual rate of a financial instrument.NWFC Next Factor Rate expressed as a decimal between 0 and 1 that will be applicable as of the next factor date and defines the outstanding principal of the financial instrument (for factored securities).NXRT Next Interest Rate Interest rate applicable to the next interest payment period in relation to variable rate instruments.PRFC Previous Factor Rate expressed as a decimal between 0 and 1 that was applicable before the current factor and defines the outstanding principal of the financial instrument (for factored securities).YTMR Yield To Maturity RateRate of return anticipated on a bond when held until maturity date.

Client Impact

In line with Indian Market Practice requirements, clients should instruct the new qualifier in the following scenario:

YTMR is the rate of return anticipated on a government bond if it is held until the maturity date. YTMR is needed to be calculated / provided by the customer (who sends settlement instruction to the custody bank). This is a critical matching element for government bond transaction using in the Negotiated Dealing System operated by the Reserve Bank of India.

Citi will play back the information on confirmation messages

Citi will NOT be supporting this new qualifier on the MT535 or MT538 Statements


MT540-547

MT548

Sequence E Settlement Detail

Sequence B Settlement Transaction

22FIndicator

SETR / ETFT Requirement 1.15

Addition of optional new code ETFT Exchange Traded Funds to qualifier SETR (Settlement Transaction Type Indicator) in the 22F Indicator field in sequence B (addition shown in red bold)

CODESIf Qualifier is SETR and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):BSBK Buy Sell Back Relates to a buy sell back transaction.COLI Collateral In Relates to a collateral transaction, form the point of view of the collateral taker or its agent.COLO Collateral Out Relates to a collateral transaction, form the point of view of the collateral giver or its agent.CONV DR Conversion Relates to a depository receipt conversion.ETFT Exchange Traded FundsRelates to an exchange traded fund (ETF) creation or redemption. FCTA Factor Update Relates to a factor update......

Client Impact

In line with Australian Market Practice requirements, clients should instruct the new code in the following scenario:

Instruction of field :22F::SETR//ETFT is a requirement imposed by the ASX on settlement of ETF’s traded on the ASX.

Citi will play back the information on confirmation messages and status updates

For Statement Messages:


MT535

MT538

MT586

Sequence B1aFinancial Instrument Attributes



22F PREFPADI

Requirement 2.0

Deletion of qualifier PREF and PADI from the 22F Indicator field in subsequence B1a (removed text shown as red strike through)

DEFINITIONThis qualified generic field specifies:CFRE Variable Rate Change Frequency IndicatorSpecifies the frequency of change to the variable rate of an interest bearing instrument.FORM Form of Securities IndicatorSpecifies the form of the financial instrument.MICO Method of Interest Computation IndicatorSpecifies the computation method of (accrued) interest of the financial instrument.PADI Payment Direction IndicatorSpecifies the direction of payment for factor securities, that is, whether the repaid capital is distributed (payment direction is down) or capitalized (payment direction is up).PAYS Payment Status IndicatorSpecifies the status of the payment of a financial instrument at a particular time, as agreed with the issuer.PFRE Payment Frequency IndicatorSpecifies the frequency of a payment.PREF Preference to Income IndicatorSpecifies the level of priority on income and assets of the company.

Deletion of codes associated with qualifier PREF in the 22F Indicator field subsequence B1a (removed text shown as red strike through)

CODESIf Qualifier is PREF and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):ORDN Ordinary/Common Indicates an ordinary/common claim on income and assets.PRFD Preferred Claim Indicates a preferred claim upon income and assets.

Deletion of codes associated with qualifier PADI in the 22F Indicator field subsequence B1a (removed text shown as red strike through)

CODESIf Qualifier is PADI and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):PAYD Down Direction of the payment is down.PAYU Up Direction of the payment is up.

Client Impact

Should be of no impact to clients as Citi does not support these qualifiers and codes at present


MT535

MT538




LOTSPOOL

Requirement 2.1

Change in format options allowed for qualifiers POOL and LOTS in the 13a Number Identification field in subsequence B1a. Currently options A and B are allowed for POOL and A, B and K for LOTS. Only B will be allowed for POOL and B and K for LOTS from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number), K = :4!c//3!c/15d (Qualifier)(Number Id)(Quantity)] (removed text shown as red strike through)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O COUP N A or B Coupon Number2 O POOL N A or B Pool Number3 O LOTS N B A, B, Lot Number or K

Addition to the definition of the Network Validation Rule for field 13a Number Identification in subsequence B1a (addition shown in red bold)

NETWORK VALIDATED RULESNumber (Format Option B) must not start or end with a slash '/' and not contain two consecutive slashes '//' (Error code(s): T26).The integer part of Quantity (Format Option K) must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).

Client Impact

Should be of no impact to clients as Citi does not support this field at present


MT586 Sequence B2Financial Instrument Attributes


POOL Requirement 2.2

Change in format options allowed for qualifier POOL in the 13a Number Identification field in subsequence B2. Currently options A and B are allowed. Only B will be allowed from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)] (removed text shown as red strike through)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O COUP N A or B Coupon Number2 O POOL N A or B Pool Number

Client Impact



MT535

MT538

Sequence B1b1 and B1cQuantity Breakdown

Sequence B3aQuantity Breakdown



Change in format options allowed for qualifier LOTS in the 13a Number Identification field in subsequences B1b1 and B1c. Currently options A and B are allowed but only B will be allowed from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)] (removed text shown as red strike through)


Client Impact



MT538 Sequence B2aIntra Position



Deletion of qualifier LOTS in the 13a Number Identification field in subsequence B2a and format option A. Currently options A and B are allowed but only B will be allowed from SR2012 [B = :4!c/[8c]/30x (Qualifier)(Data Source Scheme)(Number)] (removed text shown as red strike through)


Client Impact



MT536

MT537

Sequence B1a2Transaction Details

Sequence B2b and C2Transaction Details

22FIndicator

SETR / RPTOSTCO / RPTO

Requirement 2.5

Deletion of optional code RPTO Reporting from qualifier SETR (Settlement Transaction Type) in the 22F Indicator field in sequence B1a2 (removed text shown in bold strike through)

CODESIf Qualifier is SETR and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):.....RODE Return of Delivery Without MatchingRelates to the return of financial instruments resulting from a rejected delivery without matching operation.RPTO Reporting Relates to a transaction that is for reporting purposes only.RVPO Reverse Repo Relates to a reverse repurchase agreement transaction.SBBK Sell Buy Back Relates to a sell buy back transaction......

Addition of optional new code RPTO Reporting to qualifier STCO (Settlement Transaction Condition Indicator) in the 22F Indicator field in sequence B1a2 (addition shown in red bold)

CODESIf Qualifier is STCO and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):.....RHYP Re-hypothecation Collateral position is available for other purposes (for example, onwards delivery).RPTO Reporting Relates to a transaction that is for reporting purposes only.SHOR Short Sale IndicatorSettlement transaction will create a short position.SPDL Special Delivery Settlement transactions to be settled with special delivery.SPST Split Settlement Money and financial instruments settle in different locations......

Client Impact

Should be of no impact to clients as Citi does not support this field at present. Citi will not support the new code on the MT536 and MT537


MT536 Sequence B1a2Transaction Details

Sequence B2b and C2Transaction Details

22FIndicator

SETR / ETFT Requirement 2.6

Addition of optional new code ETFT Exchange Traded Funds to qualifier SETR (Settlement Transaction Type Indicator) in the 22F Indicator field in sequence B1a2 (addition shown in red bold)

CODESIf Qualifier is SETR and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):.....COLI Collateral In Relates to a collateral transaction, form the point of view of the collateral taker or its agent.COLO Collateral Out Relates to a collateral transaction, form the point of view of the collateral giver or its agent.CONV DR Conversion Relates to a depository receipt conversion.ETFT Exchange Traded FundsRelates to an exchange traded fund (ETF) creation or redemption. FCTA Factor Update Relates to a factor update......

Client Impact

See Requirement 1.16.

In line with Australian Market Practice requirements, clients should instruct the new code in the following scenario:

Instruction of field :22F::SETR//ETFT is a requirement imposed by the ASX on settlement of ETF’s traded on the ASX.

Citi will play back the information on the MT536 and MT537 Statements

For Corporate Action Messages:


MT564MT568


28EPage Number / Continuation Indicator

N/A Requirement 3.0

Addition of new field 28E Page Number/Continuation Indicator in sequence A (addition shown in red)

2. Field 28E: Page Number/Continuation Indicator

FORMATOption E 5n/4!c (Page Number)(Continuation Indicator)

PRESENCEOptional in mandatory sequence A

DEFINITIONThis field provides the page number and a continuation indicator to indicate that the multi-parts narrative is to continue or that the message is the last page of the multi-parts narrative.

CODESContinuation Indicator must contain one of the following codes (Error code(s): T97)LAST Last Page Last page of a multi-parts narrative with more than one page.MORE Intermediate Page Intermediate page of a multi-parts narrative which contains additional pages.ONLY Only Page Only page of the narrative.

Client Impact

Citi will apply this change to the MT568 message only. Region C still to be confirmed


MT564MT565MT566MT567MT568


20CReference

COAF Requirement 3.1

Addition of new Market Practice Rules to field 20C Reference in sequence A (addition shown in red)

MARKET PRACTICE RULESThe Securities Market Practice Group (SMPG) has published market practice recommendations on the structure and usage of the Official Corporate Action Event Reference (COAF). Those recommendations are available in the SMPG Global Market Practices Part 1 document on www.smpg.info

Client Impact

Citi will adhere to this new Market Practice Rule when applicable. Client should ensure they also adhere to it when applicable on instructions sent to Citi.

http://www.smpg.info/


MT564 Sequence DCorporate Action Details

98aDate

IFIX Requirement 3.2

DvsE (Dates)

Change in definition of qualifier IFIX Index Fixing Date/Time in field 98a Date/Time in sequence D (addition shown in red, removed text shown in red strike through)

DEFINITIONThis qualified generic field specifies:.....IFIX Index Fixing Date/ TimeDate/time at which an index/rate/price/value index rate will be determined.....

Client Impact

Definition change only. Should be of no impact to clients as Citi does not support this field at present


MT564

MT566

Sequence E2Cash Movement

Sequence D2Cash Movement

98aDate

IFIX Requirement 3.3

DvsE (Dates)

Change in definition to qualifier VALU (Value Date/Time) in the 98a Date/Time field in sequence E2 (addition shown in red, removed text shown in red strike through)

DEFINITIONThis qualified generic field specifies:…..PAYD Payment Date/TimeDate/time at which the movement is due to take place (cash and/or securities).VALU Value Date/Time Date/time when calculating economic benefit for a cash amount. at which cash becomes available to the account owner (in a credit entry), or cease to be available to the account owner (in a debit entry).

Client Impact

Definition change only. Should be of no impact to clients as current use of the qualifier does not change



92aRate

PTSC Requirement 3.4

DvsE (Rates)

Change in definition of qualifier PTSC Percentage Sought in field 92a of sequence D (addition shown in red, removed text in red strike through)

DEFINITIONThis qualified generic field specifies:…..PTSC Percentage Sought Percentage of securities the offeror/issuer will purchase or redeem under the terms of the event. This can be a number or the term 'any and all'......

Client Impact

Definition change only. Should be of no impact to clients as current use of the qualifier does not change


MT564

MT566

Sequence ECorporate Action Option

Sequence DCorporate Action Confirmation

92aRate

WITF Requirement 3.5

DvsE (Rates)

Addition of qualifier WITF Withholding of Foreign Tax to field 92a in sequence E. This is a reversal of the removal of the qualifier as part of SR2011 and is for none cash movement related rates (addition shown in red)

DEFINITIONThis qualified generic field specifies:…..WITF Withholding of Foreign TaxRate at which the income will be withheld by the jurisdiction to which the income was originally paid, for which relief at source and/or reclaim may be possible......

The format options allowed are A, F or K and Network Validation Rules C8 and C9 apply to the qualifier

Client Impact

Correction of the deletion that occurred as part of SR2011. When a WIFT rate is applicable to cash movements, the WITF rate may still appear in the E2 / D2 CASHMOVE sequence. This new change allows the population of the WITF rate in a message when NOT applicable to a cash movement


MT564

MT566



92aRate

NETT / Various Requirement 3.6

DvsE (Rates)

Addition of qualifier NETT Net Dividend Rate to field 92a in sequence E. This is a reversal of the removal of the qualifier as part of SR2011 and is for none cash movement related rates (addition shown in red)

DEFINITIONThis qualified generic field specifies:…..NETT Net Dividend Rate Cash dividend amount per equity after deductions or allowances have been made......

The format options allowed are F, J or K and Network Validation Rules C8 and C9 apply to the qualifier

Addition of codes associated with format option J with qualifier NETT Net Dividend Rate in sequence E (addition shown in red)

CODESIn option J, if Qualifier is NETT and Data Source Scheme is not present, Rate Type Code must contain one of the following codes (Error code(s): K92):CAPO Capital Portion Rate relating to the underlying security for which capital is distributed.FLFR Fully Franked Fully franked.INCO Income Portion Rate relating to the underlying security for which income is distributed.INTR Interest Rate relating to the underlying security for which interest is paid.SOIC Sundry/Other IncomeRate relating to the underlying security for which other income is paid.TXBL Taxable Portion Rate relating to the underlying security for which tax is charged.TXDF Tax Deferred Rate relating to the underlying security for which tax is deferred.TXFR Tax Free Rate relating to the underlying security which is not taxable.UNFR Unfranked Unfranked.

Client Impact

Correction of the deletion that occurred as part of SR2011. When a NETT rate is applicable to cash movements, the NETT rate may still appear in the E2 / D2 CASHMOVE sequence. This new change allows the population of the NETT rate in a message when NOT applicable to a cash movement


MT564

MT566





92JRate

TAXE Requirement 3.7

DvsE (Rates)

Deletion of codes associated with format option J in field 92a with qualifier TAXE in sequence E (removed text shown in red strike through)

CODESIn option J, if Qualifier is TAXE and Data Source Scheme is present, the list of available Rate Type Code is to be retrieved from the SMPG website at www.smpg.info.

Client Impact

Clients will no longer receive the codes outlined in the change above.


MT564

MT566

Sequence E1Securities Movement

Sequence D1Securities Movement

92aRate

Format Options Requirement 3.8

DvsE (Rates)

Addition of format options F and J from the 92a Rate field in sequence E1 (addition shown in red)

FORMATOption A :4!c//[N]15d (Qualifier)(Sign)(Rate)Option D :4!c//15d/15d (Qualifier)(Quantity)(Quantity)Option F :4!c//3!a15d (Qualifier)(Currency Code)(Amount)Option J :4!c/[8c]/4!c/3!a15d[/4!c] (Qualifier)(Data Source Scheme)(Rate Type Code)(Currency Code)(Amount)(Rate Status)Option K :4!c//4!c (Qualifier)(Rate Type Code)Option L :4!c//3!a15d/3!a15d (Qualifier)(First Currency Code)(Amount)(Second Currency Code)(Amount)Option N :4!c//15d/3!a15d (Qualifier)(Quantity)(Currency Code)(Amount)

Client Impact

Clients may now see the new format options for Rates in the Securities Movement Sequence (see also Requirement 3.9)


MT564

MT566



92aRate

Various Requirement 3.9

DvsE (Rates)

Addition of new qualifiers CHAR (Charges/Fees), FISC (Fiscal Stamp), RATE (Applicable Rate) and TAXC (Tax Credit Rate) to the 92a Rate field in sequence E1 (addition shown in red)

DEFINITIONThis qualified generic field specifies:ADEX Additional for Existing SecuritiesQuantity of additional securities for a given quantity of underlying securities where underlying securities are not exchanged or debited, for example, 1 for 1: 1 new equity credited for every 1 underlying equity = 2 resulting equities.ADSR Additional for Subscribed Resultant SecuritiesQuantity of additional intermediate securities/new equities awarded for a given quantity of securities derived from subscription.CHAR Charges/Fees Rate used to calculate the amount of the charges/fees that cannot be categorised.FISC Fiscal Stamp Percentage of fiscal tax to apply.NEWO New to Old Quantity of new securities for a given quantity of underlying securities, where the underlying securities will be exchanged or debited, for example, 2 for 1: 2 new equities credited for every 1 underlying equity debited = 2 resulting equities.RATE Applicable Rate Rate applicable to the event announced, for example, redemption rate for a redemption event.TAXC Tax Credit Rate Amount of money per equity allocated as the result of a tax credit.TRAT Transformation RateRate used to determine the cash consideration split across outturn settlement transactions that are the result of a transformation of the parent transaction.

Qualifier TAXC is repetitive, CHAR, FISC and RATE are non-repetitive

The format options allowed are (option K is not allowed for the MT566)CHAR = A, F or KFISC = A or KRATE = A or KTAXC = A, F, J or K

Option A :4!c//[N]15d (Qualifier)(Sign)(Rate)Option F :4!c//3!a15d (Qualifier)(Currency Code)(Amount)Option J :4!c/[8c]/4!c/3!a15d[/4!c] (Qualifier)(Data Source Scheme)(Rate Type Code)(Currency Code)(Amount)(Rate Status)Option K :4!c//4!c (Qualifier)(Rate Type Code)

Addition of codes associated with the 92a Rate field in sequence E1 (additions shown on red)

CODESIn option J, if Qualifier is TAXC and Data Source Scheme is not present, Rate Type Code must contain one of the following codes (Error code(s): K92):IMPU Imputed Tax Imputed tax.PREC Precompte Precompte.TIER One-Tier Tax One-tier tax.

CODESIn option J, if Data Source Scheme is not present, Rate Status, if present, must contain one of the following codes (Error code(s): K92):ACTU Actual Rate Rate is actual.INDI Indicative Rate Rate is indicative.

Client Impact

Clients may now see these Rate qualifiers in Sequence E1 of the MT564 and Sequence D1 of the MT566 where applicable. See also Requirement 3.8


MT564

MT566



92aRate

Network Validation Rule Requirement 3.10

DvsE (Rates) MT564

Change in definition to the Network Validation Rules for field 92a Rate in sequence E1 (addition shown in red, removed text in red strike through)

NETWORK VALIDATED RULESThe integer part of Quantity must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).When Sign is present, Rate must not be zero (Error code(s): T14).Currency Code must be valid ISO 4217 currency codes (Error code(s): T52).Currency Code, First and Second Currency Code must be valid ISO 4217 currency codes (Error code(s):T52).

DvsE (Rates) MT566

Change in definition to the Network Validation Rules for field 92a Rate in sequence D1 (addition shown in red bold, removed text in bold strike through)

NETWORK VALIDATED RULESThe integer part of Quantity must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).When Sign is present, Rate must not be zero (Error code(s): T14).Currency Code must be valid ISO 4217 currency codes (Error code(s): T52).Currency Code, First and Second Currency Code must be valid ISO 4217 currency codes (Error code(s):T52).

Client Impact

Should be of no impact to clients as Citi already complies with this enhancement


MT564

MT566



92aRate

Usage Rule Requirement 3.11

DvsE (Rates) MT564

Change in definition to the Usage Rules for field 92a Rate in sequence E1 (addition shown in red, removed text in red strike through)

USAGE RULESFor the calculation of the rate itself, the First Currency Code will be the base currency and the Second Currency Code will be the quoted currency. (1,00 of First Currency Code = [Rate] of Second Currency Code).ACTU is the default value for Rate Status.Sign must be present when Rate is negative.Except if notified differently in the rate definition, the rate must be expressed as a percentage, not as a decimal fraction (12% must be identified by 12, and not 0,12).

DvsE (Rates) MT566

Change in definition to the Usage Rules for field 92a Rate in sequence D1 (addition shown in red bold, removed text in bold strike through)

USAGE RULESACTU is the default value for Rate Status.Sign must be present when Rate is negative.Except if notified differently in the rate definition, the rate must be expressed as a percentage, not as a decimal fraction (12% must be identified by 12, and not 0,12).For the calculation of the rate itself, the First Currency Code will be the base currency and the Second Currency Code will be the quoted currency. (1,00 of First Currency Code = [Rate] of Second Currency Code).

Client Impact

Citi will comply with the new Usage Rule additions when applicable


MT564

MT566

Sequence E Corporate Action OptionsSequence E2Cash Movement

Sequence D Corporate Action ConfirmationSequence D2Cash Movement

Conditional Rule92a

NETTTAXC

Requirement 3.12

DvsE (Rates) MT564

Change in definition of Network Validation Rule C8 in the MT564 Message (addition shown in red, removed text shown in red strike through)

C8In each occurrence of sequence E and subsequence E2:• field :92F::GRSS cannot appear more than once, and field :92K::GRSS cannot appear more than once and both :92F::GRSS and :92K::GRSS cannot appear together.• field :92F::NETT cannot appear more than once, and field :92K::NETT cannot appear more than once and both :92F::NETT and :92K::NETT cannot appear together.In each occurrence of subsequence E1 and subsequence E2, field :92A::TAXC cannot appear more than once and field :92F::TAXC cannot appear more than once, and field :92K::TAXC cannot appear more than once and none of the three fields :92A::TAXC, :92F::TAXC and :92K::TAXC can appear in pair or all three together (Error code(s): E77).In each occurrence of subsequence E2:• field :92F::NETT cannot appear more than once, and field :92K::NETT cannot appear more than once and both :92F::NETT and :92K::NETT cannot appear together,• field :92A::TAXC cannot appear more than once and field :92F::TAXC cannot appear more than once, and field :92K::TAXC cannot appear more than once and none of the three fields:92A::TAXC, :92F::TAXC and :92K::TAXC can appear in pair or all three together.(Error code(s): E77).

DvsE (Rates) MT566


C3 In sequence D and in each occurrence of subsequence D2:• field :92F::GRSS cannot appear more than once.• field :92F::NETT cannot appear more than once.In each occurrence of subsequence D1 and subsequence D2, field :92A::TAXC cannot appear more than once and field :92F::TAXC cannot appear more than once and both :92A::TAXC and :92F::TAXCcannot appear together (Error code(s): E77).In each occurrence of subsequence D2:• field :92F::NETT cannot appear more than once,• field :92A::TAXC cannot appear more than once and field :92F::TAXC cannot appear more than once and both :92A::TAXC and :92F::TAXC cannot appear together. (Error code(s): E77).

Client Impact

Citi will comply with the new Network Validation Rule additions when applicable


MT564

MT566

Sequence E Corporate Action OptionsSequence E2Cash Movement

Sequence D Corporate Action ConfirmationSequence D2Cash Movement

Conditional Rule92a

GRSSNETTTAXE

Requirement 3.13

DvsE (Rates) MT564


C9 In each occurrence of sequence E and subsequence E2:• if field :92J::GRSS is present more than once, then for each occurrence of field :92J::GRSS, the Rate Type Code must be different.• if field :92J::TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.• if field :92J::NETT is present more than once, then for each occurrence of field :92J::NETT, the Rate Type Code must be different.In each occurrence of sequence E and subsequence E2:if field :92J::GRSS is present more than once, then for each occurrence of field :92J::GRSS, the Rate Type Code must be different,if field :92J::TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.In each occurrence of subsequence E2:if field :92J::TAXC is present more than once, then for each occurrence of field :92J::TAXC, the Rate Type Code must be different,In each occurrence of subsequence E1 and subsequence E2, if field :92J::TAXC :92J::NETT is present more than once, then for each occurrence of field :92J::TAXC :92J::NETT, the Rate Type Code must be different (Error code(s): E78).

DvsE (Rates) MT566


C4 In sequence D and in each occurrence of subsequence D2:• if field :92J::GRSS is present more than once, then for each occurrence of field :92J::GRSS, the Rate Type Code must be different.• if field :92J::TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.• if field:92J::NETT is present more than once, then for each occurrence of field :92J::NETT, the Rate Type Code must be different.In sequence D and in each occurrence of subsequence D2:if field :92J::GRSS is present more than once, then for each occurrence of field :92J::GRSS, the Rate Type Code must be different,if field :92J::TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.In each occurrence of subsequence D2:if field :92J::TAXC is present more than once, then for each occurrence of field :92J::TAXC, the Rate Type Code must be different,In each occurrence of subsequence D1 and subsequence D2, if field :92J::TAXC if field:92J::NETT is present more than once, then for each occurrence of field :92J::TAXC :92J::NETT, the Rate Type Codemust be different (Error code(s): E78).

Client Impact

Citi will comply with the new Network Validation Rule additions when applicable


MT564

MT566

Sequence ECorporate Action Options


90aPrice

OFFR Requirement 3.14

DvsE (Prices)

Deletion of qualifier OFFR Offer Price from field 90a in sequence E (removed text shown in red strike through)DEFINITIONThis qualified generic field specifies:CINL Cash in Lieu of Shares PriceCash disbursement in lieu of equities; usually in lieu of fractional quantity.OFFR Generic Cash Price Received per ProductGeneric cash price received per product by the underlying security holder either as a percentage or an amount, for example, redemption price.OSUB Over-subscription Deposit PriceAmount of money required per over-subscribed equity as defined by the issuer.

Client Impact

Clients should now expect to see the OFFR Price qualifier in Sequence E1 and/or E2 of the MT564 and MT566 where applicable


MT564

MT566



90aPrice


DvsE (Prices)

Deletion of format options F and J from the 90a Price field in sequence E (removed text shown in bold strike through)

FORMATOption A :4!c//4!c/15d (Qualifier)(Percentage Type Code)(Price)Option B :4!c//4!c/3!a15d (Qualifier)(Amount Type Code)(CurrencyCode)(Price)Option E :4!c//4!c (Qualifier)(Price Code)Option F :4!c//4!c/3!a15d/4!c/15d (Qualifier)(Amount Type Code)(CurrencyCode)(Amount)(Quantity Type Code)(Quantity)Option J :4!c//4!c/3!a15d/3!a15d (Qualifier)(Amount Type Code)(CurrencyCode)(Amount)(Currency Code)(Amount)

Client Impact

Format option deletions from this Sequence as they were only applicable to the OFFR price (see Requirement 3.14)


MT564

MT566



90aPrice


DvsE (Prices)

Deletion of Amount Type Codes associated with the 90a Price field when format options B, F and J were used (removed text shown in red strike through)

CODESIn option B, F, or J, Amount Type Code must contain one of the following codes (Error code(s): K90):ACTU Actual Amount Price expressed as an amount of currency per unit or per share.DISC Discount Price expressed as a discount amount.PLOT Lot Price expressed as an amount of money per lot.PREM Premium Price expressed as a premium.

Client Impact

Code deletions due to the deletion of format options. For option F and J, clients will no longer see these codes used. The codes remain for format option B (see Requirement 3.17)


MT564

MT566



90aPrice


DvsE (Prices)

Addition of Amount Type Codes associated with the 90a Price field when format options B is used (addition shown in red)

CODESIn option B, Amount Type Code must contain one of the following codes (Error code(s): K90):ACTU Actual Amount Price expressed as an amount of currency per unit or per share.DISC Discount Price expressed as a discount amount.PLOT Lot Price expressed as an amount of money per lot.PREM Premium Price expressed as a premium.

Client Impact

See Requirement 3.16. The codes used for format option B are not changing. The “addition” is due to the wording in the code list that previously also mentioned format options F and J. Clients may continue to see these codes used with format option B where applicable


MT564 Sequence ECorporate Action Options

90E UKWN Requirement 3.18

DvsE (Prices)

Deletion of Price Code associated with the 90a Price field when the qualifier is not OFFR when format option E was used (removed text shown in red strike through)

CODESIn option E, if Qualifier is not OFFR, Price Code must contain the following code (Error code(s): K90):UKWN Unknown Price Price is unknown by the sender or has not been established.

Client Impact

See also Requirement 3.19. The code UKWN isn’t being deleted but the wording in the SWIFT User Handbook is changing due to the deletion of qualifier OFFR in sequence E of the MT564. No impact to clients



90E UKWN Requirement 3.19

DvsE (Prices)

Addition of Price Code associated with the 90a Price field when format options E is used (addition shown in red)

CODESIn option E, Price Code must contain the following code (Error code(s): K90):UKWN Unknown Price Price is unknown by the sender or has not been established.

Client Impact

See Requirement 3.18. No impact to clients



90E Various Requirement 3.20

DvsE (Prices)

Deletion of Amount Type Codes associated with the 90a Price field when the qualifier is OFFR and format option E was used (removed text shown in red strike through)

CODESIn option E, if Qualifier is OFFR, Price Code must contain one of the following codes (Error code(s): K90):NILP Nil Payment Price will not be paid.TBSP To be Specified Price to be specified by account owner.UNSP Unspecified Price is not required to be specified by account owner.UKWN Unknown Price Price is unknown by the sender or has not been established.

Client Impact

Deletion of codes due to the deletion of qualifier OFFR in sequence E. Clients will no longer see these codes used in this part of the message


MT564

MT566



90FPrice

AMORFAMTUNIT

Requirement 3.21

DvsE (Prices)

Deletion of Quantity Type Codes associated with the 90a Price field when format option F was used (removed text shown in red strike through)

CODESIn option F, Quantity Type Code must contain one of the following codes (Error code(s): K90):AMOR Amortised Value Quantity expressed as an amount representing the current amortised face amount of a bond, for example, a periodic reduction/increase of a bond's principal amount.FAMT Face Amount Quantity expressed as an amount representing the face amount, that is, the principal, of a debt instrument.UNIT Unit Number Quantity expressed as a number, for example, a number of shares.

Client Impact

Deletion of codes due to the deletion of qualifier OFFR and format option F in sequence E. Clients will no longer see these codes used in this part of the message


MT564

MT566



90aPrice

Network Validation RulesUsage Rules

Requirement 3.22

DvsE (Prices)

MT564

Change in definition of the Network Validation Rules for field 90a Price in sequence E (addition shown in red bold, removed text in red strike through)

NETWORK VALIDATED RULESThe integer part of Price, Amount and Quantity must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).Currency Code must be a valid ISO 4217 currency code (Error code(s): T52).

MT566

Change in definition of the Network Validation Rules for field 90a Price in sequence D (addition shown in red bold, removed text in red strike through)

NETWORK VALIDATED RULESThe integer part of Price, Amount, Quantity and Index Point must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).Currency Code must be a valid ISO 4217 currency code (Error code(s): T52).

MT564 and MT566

Change in definition of the Usage Rules for field 90a Price in sequence E (addition shown in red, removed text in red strike through)

USAGE RULESThe number of decimal digits in Price is not validated against the currency specified.Generic Cash Price Received per Product (OFFR) is the price received in the course of an event. The specific meaning (redemption price, subscription price, reinvestment price, ETC.) is derived from the event type.

Client Impact

Definition change takes into account the deletion of format options related to the use of deleted qualifier OFFR. No impact to clients


MT564

MT566



90aPrice

OFFRPRPP

Requirement 3.23

DvsE (Prices)

Addition of new qualifiers CAVA (Cash Value for Tax), OFFR (Generic Cash Price Received per Product) and PRPP (Generic Cash Price Paid per Product) to the 90a Price field in sequence E1 (additions shown in red)

DEFINITIONThis qualified generic field specifies:CAVA Cash Value for Tax Cash value of resulting securities proceeds for tax calculation and/or reporting.CINL Cash in Lieu of Shares PriceCash disbursement in lieu of equities; usually in lieu of fractional quantity.INDC Indicative Price Estimated price, for example, for valuation purposes.MRKT Market Price Last reported/known price of a financial instrument in a market.OFFR Generic Cash Price Received per ProductGeneric cash price received per product by the underlying security holder either as a percentage or an amount, for example, redemption price.PRPP Generic Cash Price Paid per ProductGeneric cash price paid per product by the underlying security holder either as a percentage or an amount, for example, reinvestment price.

The format options allowed are:CAVA = B or EOFFR = A, B, E, F or JPRPP = A, B, E or K

FORMATOption A :4!c//4!c/15d (Qualifier)(Percentage Type Code)(Price)Option B :4!c//4!c/3!a15d (Qualifier)(Amount Type Code)(CurrencyCode)(Price)Option E :4!c//4!c (Qualifier)(Price Code)Option F :4!c//4!c/3!a15d/4!c/15d (Qualifier)(Amount Type Code)(Currency Code)(Amount)(Quantity Type Code)(Quantity)Option J :4!c//4!c/3!a15d/3!a15d (Qualifier)(Amount Type Code)(Currency Code)(Amount)(Currency Code)(Amount)Option K :4!c//15d (Qualifier)(Index Points)

NETWORK VALIDATED RULES The integer part of Price, Amount, and Quantity and Index Points must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).

Client Impact

Client may now see the OFFR and PRPP prices used in this sequence of the MT564 and MT566 where applicable. Qualifier CAVA is not being introduced by CIti


MT564

MT566



90aPrice


DvsE (Prices)

Deletion of codes associated with the 90a Price field in sequence E1 (removed text shown in red strike through). Only option B applies to the MT566.

CODESIn option B, Amount Type Code must contain one of the following codes (Error code(s): K90):ACTU Actual Amount Price expressed as an amount of currency per unit or per share.DISC Discount Price expressed as a discount amount.PLOT Lot Price expressed as an amount of money per lot.PREM Premium Price expressed as a premium.

CODESIn option E, Price Code must contain the following code (Error code(s): K90):UKWN Unknown Price Price is unknown by the sender or has not been established.

Client Impact

See also Requirement 3.25. The deletions and additions are due to the rewording of the use of the codes due to the introduction of new qualifiers into the field. Clients may expect to see the new codes used with their respective qualifiers where applicable.


MT564

MT566



90aPrice


DvsE (Prices)

Addition of codes associated with the 90a Price field in sequence E1 (additions shown in red)

CODESIn option B, if Qualifier is CAVA, Amount Type Code must contain the following code (Error code(s): K90):ACTU Actual Amount Price expressed as an amount of currency per unit or per share.

CODESIn option B, if Qualifier is not CAVA, Amount Type Code must contain one of the following codes (Error code(s): K90):ACTU Actual Amount Price expressed as an amount of currency per unit or per share.DISC Discount Price expressed as a discount amount.PLOT Lot Price expressed as an amount of money per lot.PREM Premium Price expressed as a premium.

CODESIn option F or J, Amount Type Code must contain one of the following codes (Error code(s): K90):ACTU Actual Amount Price expressed as an amount of currency per unit or per share.DISC Discount Price expressed as a discount amount.PLOT Lot Price expressed as an amount of money per lot.PREM Premium Price expressed as a premium.

CODESIn option E, if Qualifier is not OFFR, Price Code must contain the following code (Error code(s): K90):UKWN Unknown Price Price is unknown by the sender or has not been established.

CODESIn option E, if Qualifier is OFFR, Price Code must contain one of the following codes (Error code(s): K90):NILP Nil Payment Price will not be paid.TBSP To be Specified Price to be specified by account owner.UKWN Unknown Price Price is unknown by the sender or has not been established.UNSP Unspecified Price is not required to be specified by account owner.

CODESIn option F, Quantity Type Code must contain one of the following codes (Error code(s): K90):

AMOR Amortised Value Quantity expressed as an amount representing the current amortised face amount of a bond, for example, a periodic reduction/increase of a bond's principal amount.FAMT Face Amount Quantity expressed as an amount representing the face amount, that is, the principal, of a debt instrument.UNIT Unit Number Quantity expressed as a number, for example, a number of shares.

Client Impact

See Requirement 3.24. The use of codes with qualifier CAVA is not applicable as Citi won’t be supporting the new qualifier.


MT564

MT566



90aPrice

Network Validation RulesUsage Rules

Requirement 3.26

DvsE (Prices)

Change in definition to the Network Validation Rules for field 90a Price in sequence E1 (addition shown in red, removed text in red strike through)

NETWORK VALIDATED RULESThe integer part of Price, Amount and Quantity must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).Currency Code must be a valid ISO 4217 currency code (Error code(s): T52).

Change in definition to the Usage Rules for field 90a Price in sequence E1 (addition shown in red, removed text in red strike through)

USAGE RULESThe number of decimal digits in Price is not validated against the currency specified.Generic Cash Price Received per Product (OFFR) and Generic Cash Price Paid per Product (PRPP) are prices received or paid in the course of an event. The specific meaning (redemption price, subscription price, reinvestment price, etc.) is derived from the event type.

Client Impact

Change in definition to the Network Validation Rules and Usage Rules due to the addition of qualifiers and format options. Client should ensure they comply with these new rules.


MT564

MT566

MT565



Sequence DCorporate Action Instruction

90aPrice

EXER Requirement 3.27

DvsE (Prices)

Deletion of qualifier EXER (Exercise Price) from the 90a Price field in sequence E2 (removed text shown in red strike through)

DEFINITIONThis qualified generic field specifies:EXER Exercise Price1. Price at which security will be purchased/sold if warrant is exercised, either as an actual amount (option B) or a percentage (option A).2. Price at which a bond is converted to underlying security either as an actual amount (option B) or a percentage (option A).3. Strike price of an option, represented either as an actual amount (option B), a percentage (option A) or a number of points above an index (Option K).OFFR Generic Cash Price Received per ProductGeneric cash price received per product by the underlying security holder either as a percentage or an amount, for example, redemption price.PRPP Generic Cash Price Paid per ProductGeneric cash price paid per product by the underlying security holder either as a percentage or an amount, for example, reinvestment price.

Client Impact

Clients should no longer expect to see the use of Price qualifier EXER in their messages. PRPP will be used instead.


MT564

MT566



90aPrice


DvsE (Prices)

Deletion of format option K from the 90a Price field in sequence E2 (removed text shown in red strike through). This is only applicable to qualifiers EXER (Exercise Price)

FORMATOption A :4!c//4!c/15d (Qualifier)(Percentage Type Code)(Price)Option B :4!c//4!c/3!a15d (Qualifier)(Amount Type Code)(Currency Code)(Price)Option E :4!c//4!c (Qualifier)(Price Code)Option F :4!c//4!c/3!a15d/4!c/15d (Qualifier)(Amount Type Code)(Currency Code)(Amount)(Quantity Type Code)(Quantity)Option J :4!c//4!c/3!a15d/3!a15d (Qualifier)(Amount Type Code)(Currency Code)(Amount)(Currency Code)(Amount)Option K :4!c//15d (Qualifier)(Index Points)

Client Impact

Clients should no longer expect to see the use of Price format option K in their messages due to the deletion of qualifier EXER. See also Requirement 3.29


MT564

MT566



90aPrice

Network Validation Rules Requirement 3.29

DvsE (Prices)

Change in definition of the Network Validation Rules in the 90a Price field (addition shown in red, removed text in red strike through)

NETWORK VALIDATED RULESThe integer part of Price, Amount, Quantity and Quantity Index Points must contain at least one digit. A decimal comma is mandatory and is included in the maximum length (Error code(s): T40,T43).Currency Code must be a valid ISO 4217 currency code (Error code(s): T52).

Client Impact

Change in definition of the Network Validation Rules due to the deletion of format option K from field 90a. See Requirement 3.28


MT564 Sequence DCorporation Action Details

36aQuantity


Addition of format option C for the following qualifiers in field 36a Quantity of Financial Instrument in sequence D (addition shown in red)

Option C :4!c//4!c (Qualifier)(Quantity Code)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O MIEX N B or C Minimum Exercisable Quantity2 O MILT N B or C Minimum Exercisable Multiple Quantity3 O MQSO N B or C Maximum Quantity of Securities4 O QTSO N B or C Minimum Quantity Sought5 O NBLT N B or C New Board Lot Quantity6 O NEWD N B or C New Denomination Quantity7 O BASE N B or C Base Denomination8 O INCR N B or C Incremental Denomination

Client Impact

Clients may now see the other quantity qualifiers use with format option C.


MT564 Sequence DCorporation Action Details

36aQuantity


Change in codeword use for the quantity field 36C

Deletion of codes associated with format option C in field 36a in sequence D (removed text shown in red strike through)

CODESIn option C, Quantity Code must contain the following codes (Error code(s): K36):QALL All Securities Instruction applies to the entire eligible balance of underlying securities.UKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Addition of new codes ANYA and UWKN to qualifiers MIEX, MQSO, QTSO in field 36C in sequence D (addition shown in red)

CODESIn option C, if Qualifier is MIEX or Qualifier is MQSO or Qualifier is QTSO, Quantity Code must contain one of the following codes (Error code(s): K36):ANYA Any and allUKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Addition of new code UWKN if the qualifier is not MIEX, MQSO, QTSO in field 36C in sequence D (addition shown in red)

CODESIn option C, if Qualifier is not MIEX and Qualifier is not MQSO and Qualifier is not QTSO, Quantity Code must contain the following code (Error code(s): K36):UKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Client Impact

Clients may now see the other quantity qualifiers use with format option C with the codes shown



36aQuantity

Usage Rules Requirement 3.32

Change in definition to the Usage Rules for field 36a in sequence D (addition shown in red, removed text in red strike through)

USAGE RULESMIEX and MILT in the sequence D or E are different from the MIEX or MILT used in the financial instrument attributes (sequence B1) as they give indication on quantity of financial instrument in the precise context of the described corporate actions for a given account servicer. In sequence B1, the quantity given are the quantitypertaining to the financial instrument in general, not specifics to the corporate action processing.When MQSO is present, QTSO must be present too. When QTSO is present, MQSO must be present too.When MQSO is used with option B with the value ANYA (Any and all), then QTSO must not be used with the value ANYA. When QTSO is used with option B with the value ANYA, MQSO must not be used with the value ANYA.

Client Impact

Clients should ensure that they comply with the updated Usage Rules for the field


MT564 Sequence ECorporation Action Options

36aQuantity


Addition of format option C for the following qualifiers in field 36a Quantity of Financial Instrument in sequence E (addition shown in red)

Option C :4!c//4!c (Qualifier)(Quantity Code)

QUALIFIER(Error code(s): T89)Order M/O Qualifier R/N CR Options Qualifier Description1 O MAEX N B or C Maximum Exercisable Quantity2 O MIEX N B or C Minimum Exercisable Quantity3 O MILT N B or C Minimum Exercisable Multiple Quantity4 O NBLT N B or C New Board Lot Quantity5 O NEWD N B or C New Denomination Quantity6 O BOLQ N B or C Back End Odd Lot Quantity7 O FOLQ N B or C Front End Odd Lot Quantity

Client Impact

Clients may now see the other quantity qualifiers use with format option C.



36aQuantity


Deletion of codes associated with format option C in field 36a in sequence E (removed text shown in red strike through)

CODESIn option C, Quantity Code must contain the following codes (Error code(s): K36):QALL All Securities Instruction applies to the entire eligible balance of underlying securities.UKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Addition of new codes ANYA and UWKN to qualifiers MIEX and MAEX in field 36C in sequence E (addition shown in red)

CODESIn option C, if Qualifier is MIEX or Qualifier is MAEX, Quantity Code must contain one of the following codes (Error code(s): K36):ANYA Any and AllUKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Addition of new code UWKN if the qualifier is not MIEX or MAEX in field 36C in sequence E (addition shown in red)

CODESIn option C, if Qualifier is not MIEX and Qualifier is not MAEX, Quantity Code must contain the following code (Error code(s): K36):UKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Addition of new code UWKN if the qualifier is not MIEX or MAEX in field 36C in sequence E (addition shown in red)

CODESIn option C, if Qualifier is not MIEX and Qualifier is not MAEX, Quantity Code must contain the following code (Error code(s): K36):UKWN Unknown Quantity Quantity is unknown by the sender or has not been established.

Client Impact

Clients may now see the other quantity qualifiers use with format option C with the codes shown



22FIndicator

CETI Requirement 3.35

Change in definition of qualifier CERT Certification Type Indicator in field 22F in sequence E (addition shown in red bold, removed text in red strike through)

DEFINITIONThis qualified generic field specifies:…..CETI Certification/Breakdown Certification Type IndicatorSpecifies the type of certification/breakdown certification required......

Client Impact

Definition change only, no impact to clients



22FIndicator

CETI / NARR Requirement 3.36

Deletion of code NARR Narrative Description with qualifier CETI Certification/Breakdown Type Indicator in field 22F in sequence E (removed text in red strike through)

CODESIf Qualifier is CETI and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):…..NARR Narrative DescriptionSee narrative field for certification requirements......

Client Impact

Client will no longer see the use of code NARR with qualifier CETI where used previously


MT565 Sequence CBeneficial Owner Details

22FIndicator

CETI / NARRUsage Rules

Requirement 3.37

Deletion of code NARR Narrative Description and associated Usage Rule from qualifier CETI in field 22F in sequence C (addition shown in red bold, removed text in red strike through)

CODESIf Qualifier is CETI and Data Source Scheme is not present, Indicator must contain one of the following codes (Error code(s): K22):ACCI Accredited Investor The holder of the security irrevocably certifies that it is an Accredited Investor as defined in US Securities and Exchange Commission Regulation D.NCOM Non-Company RelatedThe holder of the security is certifying he is a Non-Company related person.QIBB QIB Certification The holder of the security irrevocably certifies that it is a Qualified Institutional Buyer as defined in US Securities and Exchange Commission Rule 144A.NARR Narrative DescriptionSee narrative field for certification details.

USAGE RULESNARR should only be used when all the other code possibilities under qualifier CETI are not appropriate.

Client Impact

Clients should no longer use code NARR with qualifier CETI in their MT565 instructions


MT564

MT566

Sequence DCorporate Action Details

Sequence CCorporate Action Details

17BFlag

CERT Requirement 3.38

Change in definition of qualifier CERT Certification Flag in field 17B in sequence D (addition shown in red, removed text in red strike through)

DEFINITIONThis qualified generic field specifies:ACIN Accrued Interest IndicatorIndicates whether the holder is entitled to accrued interest.CERT Certification/Breakdown Certification FlagIndicates whether certification/breakdown is required. certification is required from the account owner.COMP Information to be Complied WithIndicates whether restrictions apply to the event.RCHG Charges Flag Indicates whether charges apply to the holder, for instance redemption charges.

Client Impact




17BFlag

CERT Requirement 3.39

Change in definition of qualifier CERT Certification Flag in field 17B in sequence E (addition shown in red, removed text in red strike through)

DEFINITIONThis qualified generic field specifies:CERT Certification/Breakdown Certification FlagIndicates whether certification/breakdown is required. certification is required from the account owner......

Client Impact



MT564

MT565


Sequence EAdditional Information

70ENarrative

CETI Requirement 3.40

Addition of new qualifier CETI (Certification/Breakdown Narrative) to the 70E Narrative field in sequence E with format option E (addition shown in red)

DEFINITIONThis qualified generic field specifies:ADTX Additional Text Provides additional information or specifies in more detail the content of a message. This field may only be used when the information to be transmitted, cannot be coded.CETI Certification/Breakdown NarrativeProvides additional information about the type of certification/breakdown required.COMP Information to be Complied WithProvides information conditions to the account owner that are to be complied with, for example, not open to US/Canadian residents, QIB or SIL to be provided......

Client Impact

Clients may now see this narrative qualifier used when applicable



22FIndicator


Change in definition of the Usage Rules for field 22F in sequence E (addition shown in red, removed text in red strike through)

USAGE RULESWhen used, the corporate action option code PRUN should be maintained throughout the full lifecycle of the event.NARR should only be used when all the other code possibilities under qualifier CETI are not appropriate.

Client Impact

Should be of no impact to clients as Citi does not support the option PRUN. Citi will comply with the deletion of the Usage Rules for code NARR


MT564 Sequence E2Cash Movement

22FIndicator


Addition of new Usage Rule to the 22a Indicator field in sequence E2 (addition shown in red)

USAGE RULESThe Issuer/Offeror Taxability Indicator (TXAP) may only be used when no tax rate is provided in the message.It must not be used in events such as dividend or interest .

Client Impact

Should be of no impact to clients as the indicator is not supported by Citi


MT564 Sequence AGeneral Information

23GMessage Function


Change in definition of the Usage Rules for field 23G Message Function in sequence A (addition shown in red bold, removed text shown in bold strike through)

USAGE RULESTo cancel or withdraw a previously announced corporate action event, Function is respectively CANC or WITH. The presence of the Sender's reference of the message to be cancelled (PREV) is not required in the linkages sequence. A copy of at least the mandatory fields of the message to be cancelled must be present; optional fields need not be present for SWIFT validation.To cancel a previously sent Preliminary Advice of Payment message (:22F::ADDB//CAPA in sequence D), Function is CANC and the field :22F::ADDB//CAPA must be present in sequence D of the MT 564 CANC message. The reference in the linkages sequence must contain the Sender's reference of the message to be cancelled (PREV). A copy of at least the mandatory fields of the message to be cancelled must be present; optional fields need not be present for SWIFT validation.REPL is used to replace a previously sent message that was reported as preliminary or complete, for example, processing status was :25D::PROC//PREU, PREC or COMP.REPE is considered as simply a confirmation of an eligible balance when :22F::ADDB//CAPA is not present in sequence D and is considered as a movement preliminary advice when :22F::ADDB//CAPA is present in sequence D.

Client Impact

Should be of no impact to clients as definition change only and Citi already compliant with the requirement


MT564

MT566

MT567



Sequence BCorporate Action Details

19BAmount

POSTSHIP

Requirement 3.44

Deletion of qualifier POST (Postage Amount) from the 19B Amount field in sequence E2 (removed text shown in bold strike through)

DEFINITIONThis qualified generic field specifies:…..PAMM Paying/Sub-paying Agent CommissionAmount of paying/sub-paying agent commission.POST Postage Amount Amount of money paid for delivery by regular post mail.PRIN Principal or Corpus Amount of money representing a distribution of a bond's principal, for example, repayment of outstanding debt......

Change in definition to qualifier SHIP (Shipping) in the 19B Amount field in sequence E2 (addition shown in red bold, removed text shown in bold strike through)

DEFINITIONThis qualified generic field specifies:…..RESU Resulting Amount Amount of money resulting from a foreign exchange conversion.SHIP Shipping All costs related to the physical delivery of documents such as stamps, postage, carrier fees, insurances or messenger services. Amount of money (including insurance) paid for delivery by carrier.SOFE Solicitation Fee Amount of cash premium made available in order to encourage participation in the offer. Payment is made to a third party who has solicited an entity to take part in the offer......

Client Impact

Clients will no longer receive the POST amount in their messages when applicable. If a Postage Amount is required it will be used with qualifier SHIP as this now covers the Postage Amount as well

new enhancements 0512

Documents

data source

corporation

intra position

corporate

depository

tag 22f indicatory

corporate

network validation