16TH APRIL: LETTER OF CREDIT

1. Import LC , the migration of LC amendments , temenos to confirm the clarification

2. Import LC, Temenos and Karthik ACB to discuss and clarify the migration of LC amount
value.
3. Imran to check how the legacy system is handling the mixed payments and accordingly
mapping need to be finalized.
4. ITD to send the currently available list of DOCUMENT CODE to ACB Karthik, and karthik
will initiate the configuration of those codes in T24.
5. Cash Margin Migration Strategy needs to be discussed and finalized with TFS & FIN and
ITD, Karthik ACB to help with this.

18TH APRIL: COLLECTIONS

1. There are pending status collections in the legacy which needs to be
considered for migration. This requires a separate DMS for migrating these
collections in Pending Status.
2. In general we will migrating all the outstanding active status instruments
through the respective DMS.
3. For the LC instrument (amendments) which are in awaiting authorization
status, LC.AMENDMENTS table. This requires a separate DMS for migration
4. Certain fields which are required for legalization receipt requires creation of
LR fields based on the decision of TFS.
5. Certain fields are not present in the T24 which are important in legacy,
hence below Local Reference fields are proposed, Karthikeyan to
incorporate them in the LRF list.
 L.INVOICE.NUMBER
 L.INVOICE.DATE
 L.REMITTERS.DATE
 L.SHIPMENT.DATE
 L.SHIP.DOC.NO
 L.SHIP.DOC.DATE

MAY 22, 2018 DRAWINGS

1. For existing IMPORT LC DISCOUTING there are only few records in legacy TFS team will input
manually in T24, after go-live of T24 AA Module can be used for import LC discounting.
 2. If there are any outstanding DRAWINGS under transferred LC then TFS need to input manually in
T24 after go-live. Currently there are no outstanding drawings under transfer LC.
3. It is agreed that all PAYMENT.METHOD will be passed as N (NOSTRO), Sumal to share the
NOSTRO account details based on all currencies for DRAWINGS to be credited for
PAYMENT.ACCOUNT field.
4. KARTHIK to check and confirm the migration logic for CURRENT BALANCE in case of any partial
payment done on a drawing. Where to capture the document original amount and current
balance.
5. The installment payments under each negotiation will be captured manually after go-live by the
TFS team.
6. Temenos to confirm the migration of the LC Balance with respect the drawings uploaded against
the same LC.
7. Limit Revaluation – legacy system maintains the rate at which the limit is booked. Whether we
need to migrate this to T24? Temenos to explain the limit booking and refunding functionality.
8. LC Liability reversal during the migration of Drawings and reconciliation method need to confirm
by Temenos.
9. Fields missing DMS but present in T24 model bank, Temenos to check the field and add it in
DMS
a. DOCUMENT.TEXT
b. BASE.DATE
c. TENOR.DAYS
d. SHIPMENT.DATE
e. MODE.OF.SHIPMENT
10. Need an LRF for below fields in DRAWINGS
a. SHIPMENT.TO
b. LEGACY.DRAWING.NUMBER (ILN number from legacy)
c. SHIPMENT.FROM
d. CARRIER NAME
e. VESSEL NAME
f. COUNTRY OF ORIGIN
g. TRANSPORT DOCUMENT NUMBER
h. INVOICE NUMBER
i. INVOICE DATE
11. Fields which will not be migrated from Legacy as discussed and agreed with business
a. GOODS DESCRIPTION
b. BILL OF LADING DATE
c. BENEFICIERY BANK (it will be captured in PAYMENT in T24).
d. CONSIGNOR (AGENT)

May 24 2018 GUARANTEES

Discussion Points:
1. Tender guarantee will be mapped to Bid Bond guarantee.
2. Below fields will not be migrated to T24 as agreed with business
a. OUTWARD GUARANTEE
 i. Confirming Bank, Reference Number
ii. Account With Bank Reference Number
iii. Guarantee Subject To Final Expiry Date Flag
iv. Final Expiry Date
v. Applicant Type
b. INWARD GUARANTEE
i. Applicant Type

Action Points
1. Need to check if we migrate the principal amount of the guarantee or the current balance of the
guarantee. Temenos to give the recommendation.
2. DMS 30.1 to change as BEN.ADDRESS? check with Ridwan
3. AHMED to check if there is any data in the field NOTICE PERIOD IN DAYS in the legacy system.
4. Ahmed to check the data in legacy for charges and subsequent fields under charges and confirm
with Akram for introduction of LRF
5. Do we need to capture the notional expiry date for the OPEN ENDED GUARANTEES? Ahmed
Need to check with Akram.
6. All the labor guarantee will be migrated to Electronic guarantee, karthik to check the feasibility
of introducing a guarantee type for labor guarantee.
7. Karthik to check the feasibility of introducing the guarantee type for “other guarantees” which
are generic guarantees in legacy.
8. DETAILS OF GAURANTEE & TERMS AND CONDITIONS to be discussed with Temenos for the
feasibility of migrating large text using multi-value, karthik to help for confirmation
9. Create an LRF for below as requested by Bank, Karthik to confirm the LRF creation
a. CONFIRMATION.STATUS for outward guarantees (Yes/no).
b. APPLICANT to be added as the LRF in T24 in case of applicant is different than the
customer in guarantee.
c. APPLICANT.BANK, APPLICANT.BANK.REF as LRF where customer bank is different than
the issuing bank for outward guarantee.
d. BENEFICIERY.REF for reference of the beneficiary
e. BENEFICIARY.BANK, BENE.BANK.REF in case of receiving bank is different than the
beneficiary bank in ethix, for outward guarantees
f. AUTO.RENEWAL (yes/no), RENEWAL.PERIOD, RENEWAL.DATE for auto renewal feature
g. PARTIAL.DRAWINGS.ALLOWED (YES/NO)
h. PLACE.OF.EXPIRY
i. COUNTER.GUARANTEE.BANK
j. COUNTER.GTEE.BANK.REF
k. COUNTER.GTEE.EXPIRY
l. INWARD.GTEE.REFERENCE
m. INWARD.GTEE.TYPE
n. REMARKS (instrument remarks)

Still pending to be discussed with Business/Finance

1. Handling Cash Margin
2. Amortized Fees In Legacy
3. E-Guarantee migration approach
4. Guarantee Amount and Amendment migration
5. Shipping Guarantee