Table of Contents
Common Messages
Transaction PUTFRE
This transaction is used to send common messages to the contract party/contract parties or to another address, which can be entered freely.
On the transaction panel the user has to define the message type, the receiver of the message, and, if necessary, the receiver of copies.
Detailed information about common messages can be found under “Common Messages”.
Requirements
An existing Payment Undertaking contract (can be closed).
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.
Transaction Control
Fees
None
Commissions
Results of this Transaction
Diaries
For more information see TRNDIA Diaries.
| Action | Description | Diary | Follow-up Transaction | Comment |
|---|---|---|---|---|
| Create | Reply to Query pending | 5 Working days | Common Messages |
Updating/Storing of Amounts (CBS)
Liability (LIA)
Outgoing Correspondence
Details on creation of messages can be found under DOCEOT Messages. For outgoing allNETT / RIVO messages see Overview of Outgoing messages - allNETT / RIVO.
Release
Signature required
Transaction Panels
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
Fee Conditions
Camt.056 Cancellation Request
DTAG Fields
Common Message
Datafields
| Datafield | Description |
|---|---|
| Currency | cf Appendix A, Table CBB field CUR |
| Maximum Amount | cf Appendix A, Table CBB field AMT |
| Currency | cf Appendix A, Table CBB field CUR |
| Open Amount | cf Appendix A, Table CBB field AMT |
| Opening Date | cf Appendix A, Table PUD field OPNDAT |
| Document Set Status | cf Appendix A, Table PUD field DOCSTA |
| Name | cf Appendix A, Table PTS field NAM |
| Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
| Name | cf Appendix A, Table PTS field NAM |
| Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
| 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. |
Message Details
Camt.029 Answer Cancel.Request
Datafields
Free Format Message Details
Datafields
| Datafield | Description |
|---|---|
| External Key | cf Appendix A, Table PTS field EXTKEY |
| Address Block | cf Appendix A, Table PTS field ADRBLK |
Message Details MT741
Compliance
Camt.056 Cancellation Request
DTAG Fields
