User Tools
Add this page to your book 
Remove this page from your book 
Manage book (
Help Table of Contents
Liability Approval for Amendment
Transaction RMTAMR
This transaction is used to create a liability approval for an amendment.
By default, incoming messages are routed to “Request of Amendment” / “Amending”. If this transaction is to be used, the incoming message needs to be manually routed to the transaction.
For information about handling and presentation of amended fields, refer to Handling of Amendments.
Requirements
An existing Reimbursement contract which is open and not closed.
The open amount must be different from zero.
Incoming Messages
| Channel | Description | MT | Description | Comment |
|---|---|---|---|---|
| S | SWIFT | 747 | Amend Authorization to Reimburse |
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.
Transaction Control
Fees
None
Commissions
Results of this Transaction
In line with entries made, the transaction generates an auto-registration for the “Amending” transaction.
Diaries
For more information see TRNDIA Diaries.
None
Updating/Storing of Amounts (CBS)
Liability (LIA)
An Aval acceptance liability is posted.
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.
| Name of Message | Receiver | Message ID | SWIFT | TCO | DTA/DTE | Comment |
|---|---|---|---|---|---|---|
| Liability Approval for Amendment | Own | RMTINT1 | Internal message |
Release
Transaction Panels
Liability Approval for Amendment
Confirmation
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
Liability Approval for Amendment
Datafields
| 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. |
Confirmation
Datafields
| Datafield | Description |
|---|---|
| Nominal Reimbursement Amount | cf Appendix A, Table CBB field AMT |
| Additional Amount | If this box is checked, additional amounts are available under the contract and an additional panel is available to enter details. |
| Currency | cf Appendix A, Table CBB field CUR |
| Open Amount | cf Appendix A, Table CBB field AMT |
| Available by | cf Appendix A, Table RMD field AVBBY |
| Contract Underlying Article 7 of URR (Latest Version) | cf Appendix A, Table RMD field ERAFLG |
| Date of Expiry | cf Appendix A, Table RMD field EXPDAT |
| Place of Expiry | cf Appendix A, Table RMD field EXPPLC |
| 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 |
Overview
Datafields
| Datafield | Description |
|---|---|
| Responsible User | cf Appendix A, Table RMD field OWNUSR |
| Reserved Contract | cf Appendix A, Table RMD field RESFLG |
| Direct rejection | cf Appendix A, Table RMD field REJFLG |
| 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 |
