en:app:030bsi:180pu:0220putame

Amending a Payment Undertaking

Transaction PUTAME

This transaction is used to carry out amendments to the conditions of an existing undertaking. An amendment number is assigned every time an amendment is stored under the contract.

The Amendment panel comprises of undertaking amount and expiry date, other fields can be updated on the existing panels. Any changes made during this transaction automatically update the corresponding field in the contract.

An advice is sent to the buyer acknowledging the instructions sent by him along with the details of amendment. An advice is also sent to the seller's side notifying him of the amendment and the corresponding changes to the undertaking. Details of the amended undertaking including the old and new values of the terms and conditions (if changed) are sent to the buyer and seller's side.

Requirements

An existing Payment Undertaking contract which is open and not closed.
The number of amendments has to be less than 99.
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.

Transaction Control

Fees

Commissions

Results of this Transaction

Diaries

For more information see TRNDIA Diaries.

Action Description Diary Follow-up Transaction Comment
Replace BPU reminder 1 working day before expiry Common Messages

Updating/Storing of Amounts (CBS)

Liability (LIA)

The liability gets updated according to the change of amount/maturity date.

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 Comment
Advice of Amendment Seller's Bank/Seller PUTSEL1
Advice Buyer PUTBUY1

Release

Source in Transaction

Transaction Panels

Amendment



Datafields

Datafield Description
Amendment Date This field specifies the date on which the relevant party considers the
contract to be amended.
Amendment Number Number of the current amendment to be used in external communication.
Originally set either from incoming message or from actual AMENBR of contract.
This field was used in outgoing amendment messages.
Number of Amendments cf Appendix A, Table PUD field AMENBR
Currency cf Appendix A, Table CBB field CUR
Nominal Amount cf Appendix A, Table CBB field AMT
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.
Expiry date (Amendment) This field contains the new (amended) expiry date of the L/C.
Currency cf Appendix A, Table CBB field CUR
Nominal Amount cf Appendix A, Table CBB field AMT


Overview



Datafields

Datafield Description
Currency cf Appendix A, Table CBB field CUR
Maximum Amount cf Appendix A, Table CBB field AMT
Direct rejection cf Appendix A, Table PUD field REJFLG
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
Goods Code (for Statistics) cf Appendix A, Table PUD field STAGOD
External Key cf Appendix A, Table PTS field EXTKEY
Address Block cf Appendix A, Table PTS field ADRBLK
Reference for Address (Optional) cf Appendix A, Table PTS field REF
External Key cf Appendix A, Table PTS field EXTKEY
Address Block cf Appendix A, Table PTS field ADRBLK
Reference for Address (Optional) cf Appendix A, Table PTS field REF
External Key cf Appendix A, Table PTS field EXTKEY
Address Block cf Appendix A, Table PTS field ADRBLK
Reference for Address (Optional) cf Appendix A, Table PTS field REF


Parties




Compliance




DTAG Fields




en/app/030bsi/180pu/0220putame.txt · Last modified: 2024/02/29 13:06 (external edit)