6.2.2 Detailed Flow
- Guarantee amendment scenarios and related processing
(LCDGUAMD/LIDGUAMD)
- Auto Renewal amendment scenarios :
- Cannot be modified for Open Ended Guarantees
- Auto Renewal should be N for Conditional and Fixed guarantees
- Auto Renewal can be modified from Y to N when Expiry Type is modified from Open Ended to other types namely Conditional or Fixed
- Conditional-Without Expiry Extension flag can be selected only when
Expiry Type is Conditional-Without Expiry
- Extension should be initiated from amendment date :
- For extension of counter guarantee, the local undertaking expiry
date will be extended only if the local guarantee issue date and
expiry date is provided.
Expiry type Applicable Rule Extension Required Extension Conditional-Without Expiry URDG/OTHR Y Based on existing tenor
- Messaging impact :
Table 6-3 MT767
Tag Name Tag Description Generation 23B Expiry Type Generated during change in Expiry Type : - Fixed to Open/Conditional
- Conditional to Open/Fixed
- Open to Fixed/Conditional
- Conditional-With Expiry to Conditional Without-Expiry and vice-versa
31E Date of Expiry Generated : - When 31E was not sent in MT760 and irrespective of
change in expiry date
- Open to Fixed/Conditional-With Expiry
- Conditional-Without Expiry to Fixed/Conditional-With Expiry
Not Generated when Expiry Type is :
- Open Ended
- Conditional-Without Expiry
72Z Sender to Receiver Information Expiry Date related details to be provided when there is extension and 31E is not generated - Open Ended
- Conditional Without Expiry
- Auto Renewal amendment scenarios :
- Override to be provided with expiry date details in below scenarios
- Open (With/Without Auto Renewal) to Conditional-With Expiry
- Open (With/Without Auto Renewal) to Fixed
- Conditional-Without Expiry to Fixed
- Simulation and handoff to support above functionality