PLEASE NOTE THAT WE WILL NOT BE ABLE TO RESPOND TO YOUR
REQUEST IF YOUR CONTACT INFORMATION IS INCOMPLETE.
| 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 accomodate the need: |
|
| Describe the purpose, ie, business scope of the message (parties, transaction chain etc.): |
|
| Summarise the different functions (eg, 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 (eg, 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): |
|