ISO 15022 Catalogue of Messages Request Form
Disclaimer:
The user acknowledges that the registration services offered hereunder are free of charge. The user understands, that neither S.W.I.F.T. nor ISO can assume any responsibility or liability for services provided hereunder. The user agrees and warrants that he will hold S.W.I.F.T. and ISO harmless for any loss or damages resulting from the use of registration services hereunder.
Request for the inclusion of a new message type or version in the Catalogue
If you like to request the creation of a new message type or version in the Catalogue of Messages, fill in all the required information on this form and return it to the ISO 15022 Registration Authority at .
Contact Information
PLEASE NOTE THAT WE WILL NOT BE ABLE TO RESPOND TO YOUR REQUEST IF YOUR CONTACT INFORMATION IS INCOMPLETE.
Name:Company Name:
Company address:
Phone number:
E-mail address:
Message Type or Version Description:
Proposed Message Type or Version Number:Business Justification:
Future Community of Users:
Estimated Number of Users:
Estimated Volume of Messages:
Demonstrate why similar already existing messages, if any, do not accommodate the need:
Describe the purpose, that is, business scope of the message (parties, transaction chain etc.):
Summarise the different functions (for example, instruction, cancellation etc.):
Explain the bilateral/contractual agreements or legal framework needed for the use of the message, if any, and/or the responsibilities of the sender/receiver:
Describe the usage guidelines (for example, relationships between fields representing parties to the transaction, different types of transaction flows, different scenario's etc.), if any:
Give the layout of the message in terms of fields and blocks/segments. This may also be sent to the RA in a separate attachment:
List any message specific details about the usage of fields, and any conditional rules governing the presence and usage of fields in relation to each other, where relevant. This may also be sent to the RA in a separate attachment:
Give an example for the main scenario:
List the mapping details (conversion from an old format into a new one, or correspondence between two different messages that are part of the same information flow):
[Title] Produced by ISO 20022 RA Page 3