15.2.38 AMND: LC Amendments

Table 15-39 AMND: LC Amendments

Event Message/Advice From To
AMND LC_AMD_MSG ISB ABK
AMND AMD_EXP_CR ABK ATB
AMND AMD_EXP_CR ABK BEN
AMND LC_ACK_AMND ABK ISB
AMND LC_CASH_COL_ADV ABK ISB
AMND LC_DR_MSG ABK BEN
AMND LC_AMD_AUTH_REB ISB RIB
AMND AMD_IMP_CR ISB BEN
AMND GUA_AMD_INSTR ISB ABK
AMND LC_AMND_INSTR ISB ABK/BEN
AMND LC_CHC_MSG ISB/ABK ISB/ABK
AMND LC_DR_MSG ISB/ABK APP/BEN
AMND LC_INSTRUMENT ISB ABK/BEN
AMND GUA_AMD_INSTR ISB ABK/BEN
AMND LC_REIMB_ADV ISB ABK
AMND LC_REIMB_ADV ISB RIB
AMND LC_AM_INST_COPY ISB BEN
AMND LC_BEN_RESPONSE ABK ISB
AMND GUA_BEN_RESP ABK ISB
For the generation of outgoing MT707 from an incoming MT707, you need to link the message type ‘AMD_EXP_CR’ to the ‘AMND’ event of the product. In case of LC amendment, if the media is ‘SWIFT’ and message type is ‘AMD_- EXP_CR’, the system will generate MT707. During generation of MT707 to the advice through bank, field 30 will be updated with the date in ‘Issuing Bank Amendment Date’ field. If the amendment date is null, then field 30 will not updated.

In response to MT700 and MT707, Oracle Banking FLEXCUBE also allows you to generate MT730 as an acknowledgment of LC creation or amendment respectively. During LC amendment, MT730 is generated along with the advise ‘LC_ACK_AMND’ if the media is ‘SWIFT’ and message type is ‘LC_ACK_AMND’.