Second-level matching mandatory for transactions with counterparties in CASCADE - instruction formats - additional guidelines - corrected

Note: This Announcement, originally dated 28 February 2014, is republished to include a correction to the matching information. The change is highlighted.

Effective

12 May 2014

and further to our announcement A13167 about the mandatory second-level matching for internal transactions with counterparties in CASCADE (via account 18757) we wish to inform customers of the mandatory format that must be used to identify counterparties.

For the purposes of identifying the counterparty, both the customer and its counterparty in CASCADE must only use field:95R: with account identification details. If one of the parties uses :95P: and the other party uses :95R:, the instructions will be rejected.

Impact on customers

The CBF counterparty can be identified via Data Source Scheme DAKV in the second level matching fields as follows:

Creation Online Delivery to CASCADE (2nd level matching field)

Buyer CLEARSTREAM BANKING FRANKFURT - DE
Party CBF 4-digit customer account in CASCADE Receipt from CASCADE (2nd level matching field)

Seller CLEARSTREAM BANKING FRANKFURT - DE
Party CBF 4-digit customer account in CASCADE

Creation via SWIFT Delivery to CASCADE (2nd level matching field)

:95R::BUYR/DAKV/ CBF 4-digit customer account in CASCADE Receipt from CASCADE (2nd level matching field)

:95R: :SELL/DAKV/CBF 4-digit customer account in CASCADE

Further information

For further information, customers may contact Clearstream Banking Customer Service or their Relationship Officer.