If you are having difficulties viewing this please click here. Home Ordering & Support myswift August 2017

Transcription

1 If you are having difficulties viewing this please click here. Home Ordering & Support myswift August 2017 Dear customer, Welcome to a new edition of the Operational Newsletter, bringing you all the relevant operational news about the SWIFT portfolio. We hope you enjoy this newsletter and welcome your comments to improve it in the future. Follow SWIFT on social YouTube: SlideShare: LinkedIn: check out the Sibos, Supply Chain, Standards Forum, Financial Services Regulation, Innotribe, Business Intelligence, Transaction Banking, and SWIFT Institute groups Connectivity Accord end of service Messaging Security Business Intelligence Services Standards gpi SWIFTRef SWIFT Avenue Adèle 1, B-1310 La Hulpe, Belgium Connectivity 1. Important customer announcement on Mandatory Release 7.2 Last month we regretfully had to inform customers of our decision to delay the general availability of Release 7.2 from June 2017 to August We decided to postpone the Release to allow us the necessary time to complete additional testing we now believe to be necessary to ensure that our software meets the level of quality expected by our customers. The deadline for migration has also been postponed by two months to end of November 2018 to give our customers sufficient time to migrate to Release 7.2. There is however no change to the previously communicated availability date of Release 7.2 on our Integration Testbed (ITB). This remains end of June. Please refer to Knowledge Base Tip

2 We have also issued a communication to our FileAct customers migrating to Release 7.2 confirming they will only be able to exchange files with counterparties that are running Remote File Handler , or higher. As a consequence and pending confirmation from SWIFT, FileAct customers must not install Release 7.2 in their production environment before end November 2017 on systems that are used for FileAct flows. We have provided our customers with the information they will need to ensure their FileAct flows are not disrupted. We are following up on the readiness of impacted customers and will advise about the migration date for FileAct on the production environment. Please refer to FileAct Frequently Asked Questions in the Knowledge Base tip , which outlines the compatibility of the software versions for FileAct transfers. SWIFT is committed to supporting our customers in the implementation of these mandatory releases and we would like to offer our sincere apologies for any inconvenience caused. 2. Alliance Lite2 AutoClient security update: Mandatory since end of June 2017 A new configuration tool replaces the setpassword.cmd and supports all configurable AutoClient options. Manual editing of the autoclient.properties files is prohibited. AutoClient includes a number of security enhancements. 3. Alliance Lite2 and Alliance Lifeline new operating systems supported As of the Standards release 2017 both solutions will support Windows 10 for the Web User Interface and Windows Server 2016, Windows 10 for the Alliance Lite2 AutoClient. 4. Release 7.2 for Alliance Remote Gateway customers Customers who connect Alliance Access or Alliance Entry to Alliance Remote Gateway will be informed when they can migrate their system in the Test and Training environment and in Live. A communication will be sent to the Alliance Remote Gateway community to inform on the exact date. 5. Alliance Lite end of life Alliance Lite service will reach end of support and will be discontinued after the Standards release An upgrade campaign to Alliance Lite2 is running and the Alliance Lite community has been informed. 6. Alliance Lifeline compatibility with Alliance Remote Gateway As of August 2017 Alliance Lifeline and Alliance Remote Gateway will be compatible. 7. Alliance Access/Entry annual standards update Alliance Access / Entry update is our 'normal' scheduled annual Standards MT Maintenance Release 2017 (SR 2017). It bundles all functional changes since , but does introduce no other functional changes and a limited set of fixes. The update is available now. Installation by 18 November 2017 is mandatory. The following packages are available from: SWIFT.com > Ordering & Support > Go to myswift > [login] > Support tools > Download Centre Alliance Access Alliance Entry FIN SR2017 Deployment Package The Standards User Handbooks are available from: SWIFT.com > Ordering & Support > Go to myswift > [login] > A-Z > Standards MT > Standards MT November 2017

3 Access to the software and some User Handbook files is protected and only available if you have subscribed to the User Handbook (UHB) online. 8. Activation of gpi features for all Alliance Lite2 customers gpi fields are now supported to allow message creation and modification. A generate button is available next to the Field 121 in order to create the unique end-to-end transaction reference that will respect the format. This feature has been made available in Alliance Lite2 in Test and Training as of July 8 and in Live from July 15. It is important to note that the gpi fields will be displayed to all Alliance Lite2 customers, even if they are not registered as a gpi bank. The banks not registered in SWIFT gpi Closed User Group (CUG) are not allowed to send gpi payments with these new fields. However, once SR2017 (18 November 2017) is available, all banks must be capable of receiving gpi fields in the Block3 Header of the MT103. SWIFT gpi participants will be able to include these header fields in all MTs 103, MTs 103 STP and MTs 103 REMIT that they send, including to those banks that are not in the CUG. This will allow our gpi Tracker to trace a gpi payment up to the first bank outside of the SWIFT gpi Closed User Group (CUG). SWIFT recommends all Alliance Lite2 customers who automate their FIN flows with their back-office to check back-office compatibility with their back-office application providers. Important note for corporate customers: These new features will not impact you directly. At this stage of the gpi programme, the unique end-to-end transaction reference is only passed on by banks. 9. New Personal token and 3SKey token The previous model (etoken PRO) has been replaced with the etoken 5110 model, and is the only model distributed from now on for new Personal token, 3SKey basic and subscriber token orders. The new token slightly differs in its external aspect, but offers the same technical, security and user functionality as the previous model. The new tokens can be used seamlessly and will not require any software or process changes, thereby ensuring a smooth transition. There will be no change for the previous etoken PRO and, for 3SKey only, etoken NG-Flash tokens which customers can continue to use as before until at least end With support from the token supplier, SWIFT will be providing full support for the previous models guaranteed through end of December In addition, the etoken PRO and etoken NG-Flash tokens will continue to be supported on previous SAC middleware versions through end of December 2020 for critical issues only. After these dates, customers may be required to replace their tokens with the new 5110 model SKey new token password policies By September 2017, three new password policies will become available on the 3SKey portal. Each policy specifies a set of password rules such as minimum length and maximum lifetime. The 3SKey administrators will be able to SELECT the policy that best suits their needs and that will become applicable to all the users they manage. After the administrator has selected the new password policy, the new rules will be enforced for each user only the next time that the user gets activated, reset, recovered or renewed. Through the user management screen, 3SKey administrators will be able to check which rules apply to each of their users' current password. If, by 2018, 3SKey administrators have not selected a new password policy for their users, then SWIFT will assign the less restrictive password policy by default, overwriting the current policy. In this

4 case also, the new rules will be enforced for each user only the next time that the user gets activated, reset, recovered or renewed. Detailed information on the new password policies is available through the What's New section of the 3SKey website ( 11. Alliance Messaging Hub security updates AMH 3.3.4, AMH and AMH are available on the SWIFT download centre. They are highly recommended for all customers and resolve a vulnerability in browser-to-amh communication (CVSSv3 6.5 out of 10) for the previous AMH 3.3.n, AMH 3.4.n and AMH 3.5.n releases. In addition, AMH and AMH also solve an issue with resending feedback and export to CSV. AMH solves a AMH specific issue, which prevents SWIFTRef further upload when the database already contains SWIFTRef entries 12. Alliance Messaging Hub release AMH is available on the SWIFT download centre. It is optional, but highly recommended for all customers. This update of AMH solves issues around SIXBackup, maximum retries and delay for FIN and pretty print functionality. 13. Advance information versions of key release 7.2 documentation available With the availability of release 7.2 and AMH 3.6 re-scheduled to end August many customers are eagerly awaiting more details on the content of the releases to fine tune their planning. In a response to this need SWIFT has made the following available to the community: hardware references for release 7.2 are now available on swift.com advance information versions of key documentation like release letters and installation guides have been made available in the documentation section of swift.com we continue to update the already well developed preliminary migration guide, available in the knowledge base. Accord end-of-service 1. IMPORTANT: Subscribe to the Long Term Archive (LTA) Data Export service now! Data stored under the Accord Long Term Archive 'LTA' option will be exported and delivered to customers for local storage. Subscribe to the LTA Data Export service using this form. This subscription provides for continual on-line access to the LTA data after the Accord October 31 end of service date, up until the actual date (expected early in 2018) when the data is exported and delivered to the customer. The closing date for subscriptions is mid-august as the export process needs to be initiated for all subscribers at the same time, and requires several months to complete. 2. Accord retirement: end of support 31 October 2017 Termination Notices have been sent to all customers as a legal affirmation of the end of service for Accord and LTA on 31 October There will be no Extended Support service or other means to use Accord after this date.

5 3. An updated version of Accord GUI 7.5 is available This version of the Accord GUI (version 7.5.1) is for those users experiencing an incompatibility issue between the Accord GUI 7.5 and the latest java updates from Oracle. All users must upgrade to the appropriate version of Accord GUI 7.5 which is a mandatory release, and enables data export from Accord to a replacement solution. 4. Export File Data Integrity Tool on the Download Centre When a task in the Accord GUI is executed to export data you will be requested to enter a passphrase. This Tool requires you to enter the same passphrase to check against the signature of the export file to confirm its integrity. 5. New Confirmation Copy service Four matching providers are now subscribed to this service that can copy your confirmations to a central matching solution. Use this link to see the current status of the Confirmation Copy service. Messaging New release of SWIFTNet Online Operations Manager Key enhancements will become available on the SWIFTNet Online Operations Manager (O2M) by September The new release will offer a lighter option for the connection to and the use of O2M as users will be able to access the application directly using a Personal token. The reporting capability will be enhanced with new options: it will be possible to include certificate information in the role report and to filter the certificate report based on the status of the certificates. Also the certificate report will include the renewal date in addition to the expiry date. The new release will also make some operations more efficient as it will provide the ability to retrieve 4eyes tokens and to un-grant all the roles assigned to users before granting them the roles of another user through a role copy. Finally it will be possible to monitor pilot services and queues using a lite instead of a business certificate, allowing to better segregate user access between live and pilot environments. Detailed information regarding these updates will be available as part of the O2M User Guide. Security SWIFT opens The KYC Registry Security Attestation Application SWIFT's KYC Registry Security Attestation Application (KYC-SA) is now available as a central application for users to self-attest their level of compliance with SWIFT's Customer Security Controls Framework. The KYC-SA application also enables users to securely exchange their security status information with

6 selected counterparties, supporting cyber risk management, transparency and business due diligence. All SWIFT users must log in to the KYC-SA and submit self-attestations for each of their live BIC8s by the end of December During July, all SWIFT users will receive a welcome providing information on how to access the KYC-SA*. The application is automatically available to all users at no additional charge and users do not have to be a current subscriber to SWIFT KYC Registry services to use it. All SWIFT users must self-attest their level of compliance with the mandatory controls by the end of December 2017, and repeat the process at least every 12 months thereafter. Please ensure that you complete the steps to login to the KYC-SA and submit your self-attestation as early as practicable. For further information visit the KYC Registry Security Attestation pages on swift.com. *SWIFT will assign to all swift.com administrators the role of KYC-SA administrator. In the case of MULTIple users belonging to the same SWIFT traffic aggregation hierarchy, the swift.com administrators of the user heading the traffic aggregation hierarchy will be granted the Administrator role. The KYC -SA administrators will directly receive an invitation to login to the KYC SA. Business Intelligence 1. Watch Traffic Analytics, Watch Banking Analytics and Watch Banking Analytics Premium new enhancements The following enhancements to the Watch series of products have been made: Attribute Forms These forms have been enabled. You can now decide on how you want to show attribute values in your report. For instance, you can show both the code and the description or keep either only the code or the description Traffic Analytics A new metric is available (Working days). Banking Analytics and Banking Analytics Premium A new attribute form (Official Currency Per Country) is available in the country and counterparty country attributes. Banking Analytics Premium The following new attributes are available in the Premium Payments and Treasury wizards: Currency pair Currency Group These attributes refer to the combination of 'Instructed currency' (field 33B) and 'Currency' (field 32A). The attribute (L/C Length Bucket) has been renamed to (L/C Duration Bucket) in the Premium Trade Finance wizard. 2. New Watch e-learning module available on SWIFTSmart: Watch Banking Insights A new Watch e-learning module is now live on SWIFTSmart: Watch Banking Insights. (*) Follow this intermediate course to understand what Watch Banking Insights can do for you. Discover what type of insights you can get from the pre-defined dashboards. To consult the previously

7 developed Watch e-learnings, click on links below or access it through the swift.com/bi webpage: Watch Traffic Analytics Watch Message Cost Analytics Watch Billing Analytics These interactive 15 minute modules will help you get the most out of our Watch products. To ensure you fully benefit from these e-learnings, we recommend that you follow the 'Introduction to Watch' module first. Click here to read more about SWIFTSmart. (*) Access to this module is only available for swift.com registered users. Services 1. Follow SWIFT Services on LinkedIn SWIFT provides a range of service offerings that includes Consultancy, Training and Operational services. For more information on these offerings, visit the Services section on swift.com or contact your SWIFT Account Manager. For the latest news, success stories and hand-picked articles or to maintain a comprehensive view on all our service offerings in one place follow our Services showcase page now! 2. Training New user interface and features for SWIFTSmart Since July, your elearning platform has been upgraded to version 2.0 with a new interface, an enhanced look and feel and additional features. On top of this, SWIFTSmart lets you now interact with colleagues and create customised training paths. More details here. How to get access to SWIFTSmart? All you need is a valid swift.com account! 1. Go to 2. Your swift.com login page will appear 3. Login using your swift.com credentials (or create a new account) 4. Enter your 2-step verification code 5. Accept the pop up window with the standard terms and conditions. You do not have a swift.com account? Check our video 'How do I become a swift.com user' Download the latest Release Timeline Download Stay informed about planning information on the SWIFT portfolio, scheduled dates for availability and end-of-support, as well as upgrade indications. Visit the Release Timeline page on swift.com or download a PDF version. For information about supported Releases or

8 Updates, and for the Compatibility Matrices see Knowledge Base tip Standards 1. SR 2017 The MT User Handbook (UHB) 2017 is available online and the Test & Training environment for SR 2017 went live on 23 July. Reminder to all users of the MT 103, MT 103 REMIT and MT 103 STP: as of 19 November 2017, all users must be able to receive these messages with the new fields 111 and 121 in header block 3. There is no obligation to conduct any processing on these two fields. If the header fields are passed to your back-office, make sure that all applications are able to receive them. Banks that are not in the SWIFT gpi Closed User Group (CUG) must be able to receive these header fields but will not be allowed to send or forward messages containing fields 111 or SR 2017 Important changes for Non-Deliverable trades in Cat 3 As noted in previous editions of the Operational newsletter, SR 2017 includes updates to the MT 300, MT 304 and MT 305 which will have a mandatory impact on non-deliverable forwards (NDF) and nondeliverable options (NDO). If the required updates are not implemented on 19 November as part of SR 2017 cutover, messages will be NAKed by the network. It is therefore imperative that you implement the required changes as a matter of priority, if you use SWIFT for these instruments. In order to prepare for the cutover, please attend the Non-Deliverable Forwards (NDFs) and Non- Deliverable Options (NDOs) Standards Release 2017 training on SWIFTSmart. Further information is available in the Foreign Exchange, Money Markets and Derivatives - Message Usage Guidelines volume in the User handbook, which has been substantially updated for SR Note that ISDA and EMTA are working jointly on an update to ANNEX A to the 1998 FX and Currency Option Definitions, to include additional rate source mnemonics, for both deliverable and nondeliverable currencies. 3. SR 2018 All the MT change requests for SR 2018 are published on the CR Forum and are open for comments. Take this opportunity to express your opinion, which will be taken into consideration when the maintenance working groups meet to decide on which requests to accept for implementation in SR The High-Level Information documents for MT and for MX are available on the related Standards Release 2018 webpages. 4. SR 2018 and 2019: prepare for the changes related to Category 7 messages Representing the community, the Trade Finance Maintenance Working Group (TFMWG) recognized that a significant overhaul of the Category 7 interbank MTs (Letters of credit, guarantees and standby LCs) was required as in previous years a number of change requests had been postponed. The result of this work will be implemented in SR 2018 for Letters of credit (MT ) and SR 2019 for guarantees and standby LCs (MT ). The revamp of Category 7 is the biggest upgrade ever and will include 9 new messages.

9 In line with the annual release timeline, testing facilities will be available in May of the SR (Standards Year) for the Vendor Test Bed (VTB) and Test and Training (T&T) in July of the SR. An additional testing facility, integrated as a Readiness Portal in MyStandards has been available since 2016 where the new MT's can be tested. Advance documentation is available on swift.com Final documentation for Letters of Credit will be published in December 2017 (SRG document) and final documentation for guarantees / standby LCs will be published in December More information can be found here. gpi gpi Standards release As of the 2017 Standards Release all FIN users can expect to receive the gpi field tags in MT 103 messages sent by gpi participants. The gpi field tags will also be included in block 4 of MT 096 copy messages generated by FINCopy and FINInform services. MT 103 Single Customer Credit Transfer As approved during the 2017 Standards approval process, the gpi fields which are currently only exchanged between gpi participant BICs may be sent to all FIN customers who receive MT 103 messages. These fields are found in block 3 user header of MT 103. Several gpi banks have indicated that they intend to populate all of the MT 103 messages that they send with fields 111 and 121, regardless of the gpi status of the receiver, which means that non-gpi banks should expect to receive these fields. Non-gpi banks who wish to test receipt of an MT 103 with the gpi fields can download an example from the Test and Training tank file using an MT 073 Message Sample Request in local test mode future as of 22 July MT 096 FINCopy/FINInform Message The MT 096 contains all the blocks of the original message, including the user header in block 3. On an exceptional basis, the gpi fields are currently not copied into MT 096 messages. This changes with the 2017 Standards release as of which normal service operation will be restored and gpi fields present in an MT 103 will be copied into block 4 of the MT 096. Market Infrastructures and financial institutions that receive MT 096 messages can test receipt of an MT 096 with the gpi fields by downloading an example from the Test and Training tank file using an MT 073 Message Sample Request in local test mode future as of 22 July For more information refer to the FIN Operations Guide Advance Information and FIN System Messages Advance Information. SWIFTRef A new Operational Status Notification has been created to inform you of any issues affecting delivery of SWIFTRef files. Any user with a registered swift.com account can subscribe to this service free of charge.

10 If an issue which affects the operations of SWIFTRef occurs, users will receive a notification via or SMS message. How to subscribe to the service? Log in to Go to the operational status page SELECT the Subscribe to notifications SELECT edit Configure the SWIFTRef notification to receive an or sms message If you SELECT sms, you must enter a mobile phone number within your swift.com profile. For which type of issues on SWIFTRef will this be used? The Operational Status Notifications service will notify you of any issues that affect the SWIFTRef APIS and Automatic Download Service as well as the Directories over FileAct. It will not be used to report issues related to the SWIFTRef Portal which includes: Manual Download pages Manual Download pages For more information related to the Operational Status Notifications, please consult our dedicated page on swift.com and the Standards Support Service Description. About SWIFT SWIFT is a global member-owned cooperative and the world's leading provider of secure financial messaging services. We provide our community with a platform for messaging, standards for communicating and we offer products and services to facilitate access and integration; identification, analysis and financial crime compliance. Our messaging platform, products and services connect more than 11,000 banking and securities organisations, market infrastructures and corporate customers in more than 200 countries and territories, enabling them to communicate securely and exchange standardised financial messages in a reliable way. As their trusted provider, we facilitate global and local financial flows, support trade and commerce all around the world; we relentlessly pursue operational excellence and continually seek ways to lower costs, reduce risks and eliminate operational inefficiencies. Headquartered in Belgium, SWIFT's international governance and oversight reinforces the neutral, global character of its cooperative structure. SWIFT's global office network ensures an active presence in all the major financial centres. Visit to learn more about SWIFT. Unsubscribe: If you do not wish to receive our s anymore, click here to manage your subscription to the newsletter.