12.1.26 STP of MT760 for Guarantees and SBLCs
STP processing of MT760, system will create Advice of Guarantee/Advice of SBLC contract.
Resolution of Advice of Guarantee/Advice of SBLC product will be based on Tag 22D (Form of Undertaking).
Rule Maintenance to be done based on Tag 22D to resolve the product for contract creation. Separate queue to be maintained for Guarantee and SBLC products and product mapping (MSDPRDMP) to be done accordingly.
Each Tag in MT760 will be updated in Guarantee/SBLC contract as below:
Table 12-23 SWIFT tags in MT760 and the fields in the LC Contract
| Status | Tag Value | Description | Oracle Banking Trade Finance |
|---|---|---|---|
| M | 15A | Sequence A | No Impact |
| M | 22A | Purpose of Message | No Impact – STP supported only for normal guarantee (ISSU). Others to be operationally controlled. |
| O | 72Z | Sender to Receiver Information | FFT Upload against FFT code SND2RECMT760 |
| O | 23X | File Identification | FFT Upload against FFT code 23XFILEIDENT |
| M | 15B | Sequence B | No Impact |
| M | 20 | Undertaking Number | Uploaded against Source Reference Number |
| M | 30 | Date of Issue | Issue Date of Undertaking |
| M | 22D | Form of Undertaking | Product Resolution done based on Form of Undertaking: Advice of Guarantee Product will be resolved if Form of Undertaking is DGAR and Purpose of Guarantee is ISSU Advice of SBLC Product will be resolved if Form of Undertaking is STBY and Purpose of Guarantee is ISSU |
| M | 40C | Applicable Rules | Will be uploaded as below : 4a - Applicable Rules in Preference - Other Details 35x - Rule Narrative |
| M | 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 | 50 | Applicant | Uploaded as Applicant details - Party Type – APP |
| O | 51 | Obligor/Instructing Party | Uploaded as Obligor details - Party Type – OBP |
| O | 52a | Issuer | Uploaded as Issuing Bank details - Party Type – ISB |
| 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 ( To be verified in STTM_CUSTOMER) then BIC to be populated in Address1 else details to be populated in Name and Address1, Address2, Address3 |
| M | 56a | Advising Bank | No impact |
| M | 23 | Advising Bank Reference | No impact |
| O | 57a | Advise Through' Bank | Uploaded as ATB Party Type |
| O | 32B | Undertaking Amount | Uploaded in Contract Amount and Currency |
| O | 39D | Additional Amount Information | Uploaded against FFT Code 39DADDAMTINF |
| M | 71D | Charges | Uploaded in Charges from Beneficiary |
| O | 45C | Document and Presentation Instructions | Uploaded Documents against document code : UPLD_DOC_<> |
| O | 77U | Undertaking Terms and Conditions | Uploaded in Terms and Conditions 77U from Extension messages also considered for upload. Type will be Guarantee Terms and Conditions will be populated with details System will extract 32000 characters and upload Maximum possible entries of Guarantee type would be 3 |
| O | 49 | Confirmation Instructions |
Operation code is resolved. Tag 49 is not applicable for Guarantees Operation Code will always be 'ADV' for Guarantees |
| M | 58a | Requested Confirmation Party | Uploaded in Requested Confirmation Party |
| O | 44H | Governing Law and/or Place of Jurisdiction | Uploaded against FFT Code 44HGOVRNLAW |
| O | 23F | Automatic Extension Period | Uploaded in Automatic Extension Period and Automatic Extension Details |
| O | 78 | Automatic Extension Non-Extension Notification | Uploaded in Non-Extension Details |
| O | 26E | Automatic Extension Notification Period | Uploaded in Non-Extension Notification Period |
| O | 31S | Automatic Extension Final Expiry Date | Uploaded in Final Expiry Date |
| O | 48B | Demand Indicator | Uploaded in Claim Indicator |
| O | 48D | Transfer Indicator | Uploaded in Transferable flag |
| O | 39E | Transfer Conditions | Uploaded in Transfer Conditions |
| O | 45L | Underlying Transaction Details | Uploaded against FFT Code : 45LTRNDTLS |
| O | 24E | Delivery of Original Undertaking | Uploaded against FFT Code : 24EDELORGUND |
| 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. |
- FFTs will be available in MT760 ( GUARANTEE ) generated for ATB. If ATB is not a party, FFTs to be viewed from incoming message in All Messages
- For Upload of Tag 45C in sequence B, Document Codes to be maintained in Document Maintenance Screen with Doc Code as UPLD_DOC_<<Number>>
- STP of MT760 for Counter undertaking and Counter-counter undertaking currently not supported
- Contract Linkage from Incoming browser supported as per existing functionality if SWIFT 2020 is disabled
- If SWIFT 2020 is enabled , system will support linking a Counter Counter Guarantee to a Counter Guarantee and linking a Counter Guarantee to a Local Guarantee. Validations will be done based on tag 22A (Purpose of Guarantee).
- Linkage of Counter Guarantee with Local Guarantee
- Counter Guarantee incoming message should have ISCO in Tag 22A
- Local Guarantee should be created with APB. Tag 20 of Counter Guarantee should be provided as Customer reference Number of APB.
- System will validate the same during Linkage and provide appropriate error message
- Linkage of Counter Counter Guarantee with Counter Guarantee
- Counter Counter Guarantee incoming message should have ICCO in Tag 22A
- Counter Guarantee should be created with APB. Tag 20 of Counter Counter Guarantee should be provided as Customer reference Number of APB
- System will validate the same during Linkage and provide appropriate error message
- Contract cannot be linked to multiple messages. System will validate the same and provide appropriate error message
Parent topic: Branch Parameters Details