This transaction is used to send common messages to contract parties or to addresses that can be freely entered.
On the transaction panel, the user has to enter the message type, the receiver and, where necessary, receivers of copies.
Detailed information on common messages can be found under “Common Messages”.
An existing Check contract (can be closed).
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.
For more information see TRNDIA Diaries.
Action | Description | Diary | Subsequent transaction | Remarks |
---|---|---|---|---|
Create | Response to query still open | Today + 5 working days | Common Messages | If “message type” is 'Request to delete' or 'Query' |
Details on creation of messages can be found under DOCEOT Messages. For outgoing allNETT / RIVO messages see Overview of Outgoing messages - allNETT / RIVO.
The respective Common Messages will be created.
No Release required
Common Message
Message Details
Camt.029 Answer Cancel.Request
Free Format Message Details
Message Details MT741
Settlement Details
Settlement
Bookings
DTAEA Fields
DTALC Fields
Completion
Incoming Tag 72/79
Messages
Compliance
Attachments
Checks
Fee Conditions
Camt.056 Cancellation Request
DTAG Fields
Datafield | Description |
---|---|
Reference | cf Appendix A, Table CHD field OWNREF |
Currency | cf Appendix A, Table CBB field CUR |
Maximum Amount | cf Appendix A, Table CBB field AMT |
Opening Date | cf Appendix A, Table CHD field OPNDAT |
Contract Type | cf Appendix A, Table CHD field CONTYP |
Direction | cf Appendix A, Table CHD field DIRTYP |
External Key | cf Appendix A, Table PTS field EXTKEY |
Name | cf Appendix A, Table PTS field NAM |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
External Key | cf Appendix A, Table PTS field EXTKEY |
Name | cf Appendix A, Table PTS field NAM |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
message to be created | This field selects the type of message to be created |
Message Type to send | The type of message to be sent can be selected using this combobox. |
Related Message Type | This field contains the message type of the incoming SWIFT message that has been received and may be refererred to in the outgoing message that is to be generated in this transaction. For example, if a SWIFT MT n96 (Answer) is generated, the field 'Related MT' can contain the message type of the incoming Query (e.g. MT795/ 495) that was received from the correspondent. In this example, the tag 11R of the outgoing SWIFT MT n96 contains the message type that the current message refers to, e.g. a MT 795. |
from | This field contains the date of the related SWIFT message. |
relevant message sent/received | This field allows the user to choose whether the related SWIFT message was RECEIVED or SENT. |
Text of Common Message | Free text for the common message is to be entered in this field . |
Role Message | This field selects the recipient of the message. |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Role Copy | This field selects the recipients of a cc copy of the message. |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Send Message Immediately | If this box is checked, the message in sent immediately - independent of the sequence of data captured. |
Datafield | Description |
---|---|
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Datafield | Description |
---|---|
Check Count | cf Appendix A, Table CHD field CHKCNT |
Status | This column shows where the payment document is located at present. Is set by the application in the course of the various transactions. |