12.1.7 Automatic Extension of Guarantee/SBLC
The Automatic Extension of Guarantees/SBLCs batch to be configured as part of LCEOD Batch:
- To be processed during BOD
- To be processed during previous EOD, if Extension date is a holiday.
Undertaking with Automatic Extension Period to be considered for automatic extension.
Automatic extension to be processed similar to amendment of expiry date without beneficiary confirmation.
- AMND event to be trigged
- Guarantee issue date will remain the same
- Revised Expiry Date to be computed based on Extension Period. Calendar Days to be considered for extension
- If Extension Period is Days, revised expiry date to be Current Expiry Date + Number of Days
- If Extension Period is ONEY, revised expiry date will be same day next year
- Tenor to be recomputed based on revised expiry date.
- Claim Expiry Date, Closure Date and Stop Date to be computed based on extended expiry date.
- Commission to be computed for the extended period based on revised Claim Expiry Date.
- Limit Tracking to be done based on the revised Claim Expiry Date.
- No impact on Collateral.
- Default amendment advice, GUA_AMND_INSTR, will be generated.
- Default FFTs defined at Product will be applicable.
Automatic extension will not be applicable beyond Final Expiry Date (Application Date >= Final Expiry Date).
If the newly derived Expiry Date falls beyond the Final Expiry Date, then system will update the New Expiry Date as Final Expiry Date (least of Final Expiry Date and Newly derived Expiry Date).
Automatic Extension will be processed even if notification period is available.
- Non-Extension notification MT785 generation during EOD to be de-supported.
- Automatic extension can be processed only if :
- Non-extension notification ( MT785 ) is not generated, or
- Non-extension notification ( MT785 ) is generated after the notification period
- If MT785 is generated after notification period, automatic extension will not be processed for subsequent extension.
Parent topic: Branch Parameters Details