Siva: There are three variants of SWIFT standards in use:
1. Owned by SWIFT: Message using the FIN service on the SWIFT network. These are called MT (Message Type) messages and include the MT101, MT103, MT940, etc. There are nine categories of SWIFT MT messages. They range from payments and information (customer to bank and interbank) to specialized securities and trade messages. These are documented in the SWIFT Standards handbook- which indeed has to be purchased. There is a significant amount of information available on the web about the standard MT messages. One such site (http://www.bph.pl/res/docs/korp/DBE/MC/Aktualnosci_instrukcje/file_format_description_rft_mt101_v20050411.pdf#search=%22MT101%22) provides a detailed mapping spec for one bank. A "guide to parsing a SWIFT message" is contained at the following Century 24 Solutions website: http://www.c24.biz/download/c24_white_paper-parsing_a_swift_message.pdf#search=%22swift%20messages%22. IBM has information available on the structure of SWIFT MT messages at: http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/swift/swift70.htm. An inventory from the SWIFT website is attached.These messages are maintained so you should ensure you have the "latest release." In addition, if you are using these messages for corporate use, I would look to the new rulebook associated with the SCORE (Standard Corporate Environment) access model for corporates recently approved by SWIFT.Ultimately, you will have to subscribe to the SWIFT standards releases to keep on top of the MT message world. A side note on the MT 104 which is used for direct debits- I would be looking at the ISO20022 (below) message for direct debits. Use of the MT 104 implies you need to be a member of a special MUG (message user group). I do believe that Mercator and Gentran should support MT messages however worth double checking with the vendors. However, be a little careful about whether the message is intended for use on the SWIFT network or not and what you do about headers. MT messages sometimes lack information because they have a specific context for which they were planned. An easy example is the use of an MT 940 to provide an account statement in a multibank environment. The message assumes that the sending (e.g. - account holding) institution is identified in the header block (which is not part of the message itself). There is no place within the message itself to identify the bank with which the account is held. (A new rule has been proposed for the corporate guidelines to add this information (optionally) to part of the message. 2. Owned by ISO: There are two sets of standards that SWIFT uses which are technically "owned" by ISO- an organisation of which SWIFT is a member. These are ISO15022 and ISO20022 (also known as UNIFI). ISO20022 is expressed as an XML implementation. The ISO15022 (www.iso15022.org )messages referred to in the prior email really relate to securities activity rather than payments and reporting messages. ISO20022 are the XML messages associated with Payments and reporting, a new series of securities messages, trade, etc. The ISO 20022 standard are available (for free) at www.iso20022.org . The ISO20022 process uses Standards Evaluation Groups (SEG) in each business domain. If you need more information on the ISO20022 side, please contact me. When SWIFT uses an ISO20022 message on its network, it refers to these as MX (versus MT) messages. MX messages can be used in two modes on the SWIFT network: as files using the FileAct service (which allows sending of any type of file or document using the SWIFT network or via InterAct, which is intended to be more of a real time/message exchange environment. A high level inventory of MT versus MX exchanges is container don the SWIFT website at:http://www.swift.com/index.cfm?item_id=60135 . ISO20022 payment messages are now accepted as the standard for SEPA in Europe and use is being made available through several vendor/middleware packages including SAP (My ERP 2007 release and the new XI planned release.) 3. Owned by SWIFT (not ISO) but using XML. These are also MX messages (to SWIFT) but have not been submitted (or not submitted yet) to ISO 20022. Several mapping and middleware vendors support the ISO 20022 suite of XML messages. SAP and Oracle have made announcements as well on ISO20022 support. Hope this helps. Please do feel free to let me know separately if you need to look for additional information.I am the Convener of the ISO20022 Payment SEG. Best, Len Schwartz ----- Original Message ----- From: Brian Lehrhoff To: sivasubramaniaraja shanmugasundararaj Cc: [email protected] ; Mike Werner Sent: Tuesday, October 10, 2006 11:45 PM Subject: Re: [EDI-L] SWIFT Standards no. yes(*). definitely no. did you try www.swift.com? www.15022.com? you can't download anything for free. S.W.I.F.T. is not like x12, they don't give anything away. you'll also need special trees for dtx. my suggestion is that you consider outsourcing your translation. you'll save money on hardware, software, the learning curve on the documents and how to translate S.W.I.F.T. and be able to complete your project faster. contact our office for more information. we are an iso 15022 organization. sivasubramaniaraja shanmugasundararaj wrote: > Hi, > > Our company is engaging in SWIFT standards. Can we map SWIFT standards like > MT 101, 104 using standard translators like Gentran or Mercator or > Premenos. > > Where can we download SWIFT implementation guidelines. Any help will be > great. > > Thanks and Regards. > Siva Raja > > > > > -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Brian Lehrhoff, EA ([EMAIL PROTECTED]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://www.brianlehrhoff.com Circular 230 Notice is located at http://www.brianlehrhoff.com/230notice.html %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% [Non-text portions of this message have been removed] ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
