Published on

Published in: Economy & Finance, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • In practice, banks and their corporate clients must often manage and use multiple and different types of personal signing mechanisms (for example, multiple tokens or smartcards with different passwords). Using and maintaining different authentication methods in parallel adds to the complexity and leads to higher operational risk and cost.
  • banking-communication-swift

    1. 1. Banking communication<br />PWC: Treasury hot topics conference<br />Elie Lasker<br />Head of Corporate market – SWIFT<br /> Thursday: 24 Feb 2011<br />
    2. 2. 2<br />Agenda<br />Corporates on SWIFT – status update<br />Bank certification programme<br />Additional services<br />PWC - 24 February 2011<br />
    3. 3. Breakdown by region and annual revenues<br />Total: 726<br /># corporates<br /><500M<br />500M-1B<br />Emergence of mid’ market adoption in EMEA<br />PWC - 24 February 2011<br />3<br />
    4. 4. Typical implementation<br />FIN (individual messages)Payments (MT101), statements (MT940/2) and FX confirmations (MT3xx)<br />SWIFTNet<br />FileAct (File transfer)Transport any format; payments files, iDOC, ISO 20022, ACHs, BAI formats, …<br />Treasury Workstation<br />Paymentfactory/middleware<br />ERP(s)<br />ERP(s)<br />ERP<br />Connectivity<br />PWC - 24 February 2011<br />4<br />
    5. 5. Distribution of connectivity per corporate size<br />5<br />Annual turnover<br />PWC - 24 February 2011<br />
    6. 6. 6<br />Agenda<br />Corporates on SWIFT – status update<br />Bank certification programme<br />Additional services<br />PWC - 24 February 2011<br />
    7. 7. Bank readiness certification programme: background<br />Reason<br />Early 2010 bank and corporatesurveyresults<br />Goal<br />Increasebanks' (operational and commercial) readinessstatus<br />Increasevisibility of banks' readinessstatustowardscorporates<br />Scope<br />Operational:<br />correct offer of essential message standards<br />availability of documentation<br />efficient support during roll-out<br />Commercial:<br />availability of collateral<br />qualified sales force<br />7<br />PWC - 24 February 2011<br />
    8. 8. Bank readinesswebsite<br />PWC - 24 February 2011<br />8<br />
    9. 9. 9<br />Agenda<br />Corporates on SWIFT – status update<br />Bank certification programme<br />Additional services<br />PWC - 24 February 2011<br />
    10. 10. Treasury deals confirmations and SWIFT AccordCentral Matching Service<br />Deal<br />1<br />FIN<br />MT 3xx<br />MT 3xx<br />Corporate<br />Broker / Dealer<br />Copies of<br />confirmations<br />Real-time interactive Reporting and Exception handling<br />2<br />4<br />Accord<br />Confirmation Matching<br />3<br />10<br />PWC - 24 February 2011<br />
    11. 11. SWIFT flows FIN MT798 <br />SWIFT flows FileAct <br />SWIFT flows FIN MT7xx <br />Any format<br />Any format<br />MT798s<br />MT798s<br />1<br />2<br />3<br />Seller<br />Buyer<br />Buyer’s bank(s)<br />Seller’s<br />bank(s)<br />FIN MT7xx<br />1 Buyer sends Application for a Letter of Credit to its bank either via FIN (MT798) or via FileAct (eg, other format)<br />2 Buyer’s bank extracts the appropriate data from the incoming Application flows (eg, MT798), putting them into an Issue of Letter of Credit and sends them to the seller’s bank over FIN (eg, MT700)<br />3 Seller’s bank forwards the MT700 to the Seller as an Advice of Letter of Credit using FIN (MT798) or FileAct (eg, other format)<br />Trade for Corporates<br />11<br />PWC - 24 February 2011<br />
    12. 12. Current Landscape – The Corporate View<br />12<br />We have !!!<br />Wewant<br />ALL BANKS<br /><ul><li>Multi-Bank
    13. 13. Multi-Application
    14. 14. Multi-Network
    15. 15. Multi-Country</li></ul>No uniform mechanism<br />Different system per bank<br />Costly & difficult to maintain<br />PWC - 24 February 2011<br />
    16. 16. Electronic Bank Account Management (EBAM)Solution objectives<br />Today<br />Tomorrow<br />Paper<br />XML messages<br />Supporting documents<br />Personal Digital Signature<br />Fax<br /><ul><li>Dematerialised
    17. 17. Automated/STP
    18. 18. Slow
    19. 19. Low integration
    20. 20. Faster/cheaper
    21. 21. Standardised
    22. 22. Expensive
    23. 23. Low satisfaction</li></ul>13<br />PWC - 24 February 2011<br />
    24. 24. The EBAM Central Utility - being investigated<br />14<br />Banks<br />Corporates<br />EBAM central utility<br />Administrator database<br />app-to-appmessaging<br />Bank and countryrequirements database <br />Messaging and validation module<br />GUI<br />SWIFTNet<br />browsing<br />Internet<br />Key features and benefitsCentral Utility validates XML instructions, incl. bank and country specific implementations<br />Banks offer a single “source of truth” for bank/country requirements, to vendors and customers<br />Corporates offer an "administrators database", with the legal representatives of an organisation<br />A GUI allows to manually initiate EBAM transactions<br />Access through SWIFTNet and/or internet<br />Registration and access control is 3SKey-based<br />PWC - 24 February 2011<br />
    25. 25. BPO: new inter-bank instrument in support of Open Account services<br />PWC - 24 February 2011<br />Physical presentation of <br />compliant documents<br />Electronic presentation of <br />compliant data<br />15<br />
    26. 26. Q&A<br />?<br />16<br />PWC - 24 February 2011<br />