The transaction is used to forward a Detrimental Amendments to the claiming bank. The concept 'detrimental' includes all amendments that change a contract to the claiming bank's disadvantage. The “Request of Amendment” panel provides the user with all the fields contained in the amendment message.
The transaction does not update contract data; this is carried out by the “Amending” (RMTAME) transaction.
Each respective amendment transaction is autoregistered in all amendment requesting transactions. After receiving approval, the registered process can be taken up and the actual change can be carried out in the “Amending a Rembursement” transaction. At the same time, all fields are loaded in the amendment transaction that have been entered in this transaction, thus avoiding having to re-enter the data.
On approval, the bank using the application will be informed of their approval by the claiming bank and updates the contract, i.e. in the amendment transaction the data will be stored permanently.
A request of amendment is rejected by sending a “Common Messages” (RMTFRE). It is only possible to delete the autoregistration manually. This deletion has to be done, as otherwise redundant data would remain within the system.
As long as there is still an autoregistration of the contract for the transaction, the application generates a warning at each start of an associated contract/subcontract, indicating that there are still pending amendment requests that have not yet been accepted.
An existing Reimbursement contract which is open, not closed and confirmed.
The number of amendments must be less than 999.
Channel | Description | MT | Description | Comment |
---|---|---|---|---|
S | SWIFT | 747 | Amend Authorization to Reimburse |
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.
None
This transaction creates an auto-registration for “Amending” the reimbursement.
For more information see TRNDIA Diaries.
Action | Description | Diary | Follow-up Transaction | Comment |
---|---|---|---|---|
Create | Pending Request of Amendment | Today + 3 Working Days | Common Messages |
Not applicable.
Details on creation of messages can be found under DOCEOT Messages. For outgoing allNETT / RIVO messages see Overview of Outgoing messages - allNETT / RIVO.
Name of Message | Receiver | Message ID | SWIFT | TCO | DTA/DTE | Comment |
---|---|---|---|---|---|---|
Acknowledgment of Amendment | Issuing Bank | RMTISSL1 | 730 | |||
Information about Amendment | Claming Bank | RMTCLBL1 |
Source in Transaction
Request of Amendment
Overview
Narrative
Additional Amount
Details
Parties
Liability
Settlement Details
Settlement
Bookings
Cash Cover
DTAEA Fields
DTALC Fields
Completion
Incoming Tag 72/79
Messages
Compliance
Attachments
Fee Conditions
DTAG Fields
Datafield | Description |
---|---|
Own Reference | cf Appendix A, Table RMD field OWNREF |
Amendment Date | This field specifies the date on which the relevant party considers the contract to be amended. |
Number of Amendments | cf Appendix A, Table RMD field AMENBR |
Opening Date | cf Appendix A, Table RMD field OPNDAT |
Currency | cf Appendix A, Table CBB field CUR |
Nominal Amount | cf Appendix A, Table CBB field AMT |
Amount Tolerance - Positive | cf Appendix A, Table RMD field NOMTOP |
Amount Tolerance - Negative | cf Appendix A, Table RMD field NOMTON |
Currency | cf Appendix A, Table CBB field CUR |
Maximum Amount | cf Appendix A, Table CBB field AMT |
Amendment Amount | This field contains the amendment amount of the contract. |
New Nominal Amount | This field contains the new nominal amount. This is calculated by adding the amendment amount to the old nominal amount. |
New Positive Tolerance | This field specifies the new positive percentage tolerance for the documentary credit. In order to calculate the new maximum amount, the positive tolerance amount is added to the new nominal amount. |
New Negative Tolerance | This field specifies the new negative percentage tolerance for the documentary credit. |
Amount Specification (Amendment) | This field further qualifies the documentary credit amount. |
Expiry date (Amendment) | This field contains the new (amended) expiry date of the L/C. |
Date of Expiry | cf Appendix A, Table RMD field EXPDAT |
Additional amount covered (Amendment) | This field specifies any amendments to the additional amount covered, such as insurance, freight, interest etc. |
Additional Amount Flag | This flag controls the storage of an additional amount for a contract. Unchecking this flag automatically eliminates existing additional amounts when the transaction is saved. To introduce additional amounts this flag first has to be checked. |
Additional Amount | This field holds the new additional amount if the amount has changed. When the transaction is saved, additional amounts are adjusted to this amount. |
Generate Amendment Message | If checked, the current transaction generates an outgoing amendment message. If an amendment message has been generated in an xxxRAM transaction, the corresponding xxxAME transaction will no longer generate an outgoing amendment message. In this case, when the transaction starts the field is not filled. |
Datafield | Description |
---|---|
Responsible User | cf Appendix A, Table RMD field OWNUSR |
Reserved Contract | cf Appendix A, Table RMD field RESFLG |
Nominal Reimbursement Amount | cf Appendix A, Table CBB field AMT |
Direct rejection | cf Appendix A, Table RMD field REJFLG |
Additional Amount | If this box is checked, additional amounts are available under the contract and an additional panel is available to enter details. |
Amount Specification | cf Appendix A, Table RMD field NOMSPC |
Amount Tolerance - Positive | cf Appendix A, Table RMD field NOMTOP |
Amount Tolerance - Negative | cf Appendix A, Table RMD field NOMTON |
Currency | cf Appendix A, Table CBB field CUR |
Maximum Reimbursement Amount | cf Appendix A, Table CBB field AMT |
Date of Expiry | cf Appendix A, Table RMD field EXPDAT |
Place of Expiry | cf Appendix A, Table RMD field EXPPLC |
Contract Underlying Article 7 of URR (Latest Version) | cf Appendix A, Table RMD field ERAFLG |