Letter of Credit User Guide

12.1.28 STP of MT767 – Guarantees and SBLCs

SWIFT MT767 can be uploaded into Oracle Banking Trade Finance through STP. STP processing of MT767, system will initiate Amendment of Advice of Guarantee or Advice of SBLC contract with Beneficiary Confirmation Required. System will trigger AMNV event. Resolution of Advice of Guarantee or Advice of SBLC Contract Reference Number will be based on Tag 21 (Related Reference).

Rule Maintenance to be done based on Tag 22A to resolve the queue. Each Tag in MT767 will be updated in Guarantee/ SBLC amendment as below:

Table 12-25 SWIFT tags in MT767 and the fields in the LC Contract

Status	Tag Value	Tag Description	Oracle Banking Trade Finance field value
M	15A	Sequence A	No Impact
M	27	Sequence of Total	No Impact
M	21	Related Reference	Used for Contract Reference Number resolution
M	22A	Purpose of Message	No Impact – STP supported for Guarantees/SBLC (ISUA/ACNA/ADVA). Others to be operationally controlled
O	23S	Cancellation Request	Cancellation Request in LCDGUAMD. System will initiate amendment will Cancellation Request.
M	72Z	Sender to Receiver Information	FFT Upload against FFT code SND2RECMT767
M	23X	File Identification	FFT Upload against FFT code 23XFILEIDENT
M	15B	Sequence B	No Impact
M	20	Undertaking Number	No Impact
M	26E	Number of Amendment	Number of Amendment - System will validate if amendment number for underlying contract and amendment number in message are in sync.
M	30	Date of Amendment	Amendment Initiation Date:- System will validate if Amendment Date is less than or equal to application date.
M	52a	Issuer	No Impact
O	32B	Increase of Undertaking Amount	Contract Amount’ and ‘Increase Decrease Contract Amount’ fields will be modified based on increased amount
O	33B	Decrease of Undertaking Amount	Contract Amount’ and ‘Increase Decrease Contract Amount’ fields will be modified based on decreased amount
O	23B	Expiry Type	Validity Type will be Limited if Expiry Type is FIXD Validity Type will be Unlimited if Expiry Type is OPEN or COND
O	31E	Date of Expiry	Uploaded in Expiry Date
O	35G	Expiry Condition/Event	Uploaded in Expiry Condition
O	59a	Beneficiary	Beneficiary Details: If 59 - Parties - BEN - Name and Address1, Address2, Address3 If 59A - If '/' available, details populated in Other Addresses If '/' not available and is a valid BIC , then BIC to be populated in Address1 else details to be populated in Name and Address1, Address2, Address3
O	77U	Other Amendments to Undertaking	Uploaded in Terms and Conditions: If 77U is present, existing terms and conditions in underlying contract will be deleted and value in 77U will be uploaded. 77U from Extension messages also considered for upload. Type will be Guarantee Terms and Conditions will be populated System will extract 32000 characters and upload. Maximum possible count would be 3
O	24E	Delivery of Original Undertaking	Uploaded against FFT Code : 24EDLRYGUAMD
O	24G	Delivery To/Collection By	Specifies to whom the original local undertaking is to be delivered or by whom the original local undertaking is to be collected. No Impact
O	77U	Other Amendments to Undertaking	Uploaded in Terms and Conditions 77U from Extension messages also considered for upload. Type will be Guarantee Terms and Conditions will be populated System will extract 32000 characters and upload. Maximum possible count would be 3
O	24E	Delivery of Original Undertaking	Uploaded against FFT Code : 24EDLRYGUAMD
O	24G	Delivery To/Collection By	Specifies to whom the original local undertaking is to be delivered or by whom the original local undertaking is to be collected. No Impact

FFTs will be available in MT767 ( GUA_AMD_INSTR) generated. STP of MT767 for Counter undertaking and Counter-counter undertaking currently not supported.

Parent topic: Branch Parameters Details