LED - Export L/C Data

LED is the main data table for the Export L/C contract.
All technical important fields have to be defined here.
Large text blocks should be defined in LET.

/

INR

Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter LED. The field INR is used to enable links from other tables to this table. It also links the two tables LED and LET as associated entries holding the same INR.

Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

This field contains the own reference number of the export letter of credit. The reference number can have a maximum size of 16 characters. This field can be used to search for any export letter of credit contract from the database.

This field contains the reference number of the L/C being established. The reference number can be up to 16 characters long. This field can be used to search for any L/C from the database.

This field holds the displayed descriptive name used in the application to describe the contract and to search for a contract. Within the default configuration this field is set by a default rule based on contract amount and main party and cannot be modified by the user.

This field holds the descriptive name displayed in the application to describe and to search for a contract. Within the default configuration this field is set by a default rule based on the contract amount and the main party and cannot be modified by the user.

This field holds the user ID of the person who is responsible for handling this contract. This field is an optional field. Within Demobank it is initially filled with the user ID of the user creating/opening the contract.

This field holds the User ID of the person responsible for handling this contract.

This date field holds the date when the entry was physically added to the database. This may happen when opening the contract, when reserving the reference number or when, for other reasons, a contract is added to the database.

This date field identifies the date the entry was physically added to the database.

The field holds the opening/issuing date of a contract. If this field is set, the contract has been legally established and it might be used for business transactions. This date describes the point in time when this contract became legally binding. This might be a date prior to the creation date, when the contract was legally binding before it was stored in the database.

The field holds the opening/issuing date of the contract. If this field is set, the contract has been legally established and it might be used for business transactions. This date describes the point in time when this contract became legally binding. This might be a date prior to the creation date, when the contract was legally binding before it was stored in the database.

This fields holds the closing date of a contract. If this field is set, the contract is closed and may no longer be used for transaction processing of business transactions. The date specifies the date when the closing took place.

This fields indicates the closing date of a contract. If an entry has been made, the contract is closed and may no longer be used to process business transactions except special transactions like Settling Charges or Common Messages.

This field specifies the date on which an Export L/C has been confirmed by the application using bank. In case the L/C is confirmed by us and underlies UCP (latest version), the confirmation date ist set to today.

This field contains the date when the L/C was confirmed.

This field contains the date when the L/C has been advised or the LC data has been entered and saved in the system.

The date is set when the LC has been advised to the beneficiary's side in transaction LETOPN upon saving of the transaction. When documents without LC have been presented in transaction LETDRW, the date is set to mark when the LC data has been entered into the system. Therefore, in LETDRW, the date is defaulted to today's date and cannot be changed by the user.

This field holds the date the L/C was advised, or when L/C was captured and stored in the system.

Long name of issuing bank for display purposes. This field is filled from PTS\NAM of ISS

This field contains the name of the issuing bank.

The reference of the issuing bank for this contract. This field is filled from PTS\REF of ISS

This field contains the reference number of the issuing bank, i.e. the original L/C number.

This field contains the date of the last amendment which has been processed under the L/C.

This field contains the date of the last amendment processed under the contract. If it is empty the contract is still in its original condition. This date is automatically updated by the relevant amendment transactions.

This field counts the number of all initiated amendments under the Export L/C. An amendment is initiated when the first transaction of an amendment is finally stored.

The field is technically incremented after loading of the contract in init of all amending transactions (letamr, letram, letame), if no already existing amendment is further processed.

This field is used to store the number of amendments made to the contract so far. This field is automatically updated from the relevant amendment transaction.

This field indicates whether the L/C is available by sight payment, deferred payment, acceptance, negotiation or mixed payment.

This field indicates whether the contract is available by sight payment, deferred payment, acceptance, negotiation or mixed payment.

This field indicates the bank authorized to pay, accept, negotiate or incur a deferred payment for the L/C.

This field contains the bank/role that is authorized to pay, accept, negotiate or transfer an obligation under a deferred payment for the contract.

Long name of beneficiary for display purposes. This field is filled from PTS\NAM of BEN

This field contains the name of the beneficiary.

The reference of the beneficiary for this contract. This field is filled from PTS\REF of BEN

This field contains the reference number of the beneficiary.

This field defines whether the charges and commissions of the issuing bank are borne by the beneficiary side (=“U”), by the applicant side (=“B”) or others. According to the selection entered in this field, the roles in the second settlement grid (own commission/charges) are defaulted.

This field defines whether the fees and commissions of the bank using using the application is to be borne by the customer or 'Our fees borne by client' (='U'), of the foreign side or 'Our fees borne by abroad' (='B') or by other parties. Depending on the selection made in this field, the roles in the second settlement table (own commission / fees) are proposed.

Meaning 'borne by client': If, in the fee settlement field, 'borne by client' was selected or if the field is not completed, then own fees will be proposed in the settlement to the debit of the customer SIDE. (In the case of an export LC, the BEN or A2B would thus be available).

Meaning of 'borne by abroad': Own fees in the settlement are proposed to the debit of the foreign SIDE (For an export LC, the ISS or ADV/ CON would thus be available).

Meaning of 'Others': No role is proposed on the fees in the settlement panel.

This (invisible) field defines, if the amount or the percentage is confirmed in a partially confirmed contract.

Based on this information, the percentage or amount are protected and calculated from the other field.

This field defines whether if the amount or the percentage has been confirmed in a partially-confirmed contract.

Thus either the percentage or amount is protected and calculated using the other field.

This field contains the confirmation instructions received from the issuing bank. According to SWIFT regulations, one of the following code words must be selected: “Without”, “May add” or “Confirm”.

This field contains confirmation instructions received from the issuing bank. According to SWIFT regulations, one of the following codes must be selected: “Without”, “May add” or “Confirm”.

This field contains the confirmation status of the DOKA bank and therefore indicates whether the bank has added its confirmation (“Y”) to the L/C or not (“”). “S” indicates a silent confirmation which is not disclosed to the issuing bank.

This field contains the confirmation status of the bank using the application and therefore indicates whether the bank has added its confirmation to the L/C or not. “Silent” indicates a silent confirmation which is not disclosed to the issuing bank.

This date field specifies when the L/C expires and therefore indicates the latest date for presentation of documents under the Letter of Credit.

This date field specifies when the L/C expires and therefore indicates the latest date for presentating documents under the L/C.

This field specifies where the L/C expires. The expiry place is closely linked to the expiry date as it specifies more detailed the place where documents have to be presented under the Letter of Credit.

This field specifies where the L/C expires. The expiry place is closely linked to the expiry date as it specifies the place where documents are to be presented under the L/C.

This field specifies the type of L/C. According to UCP, the L/C must indicate whether it is irrevocable. According to SWIFT further specification codes are available, such as transferable, standby and combinations of these.

This field specifies the type of L/C. According to UCP, the L/C has to indicate whether it is irrevocable. According to SWIFT, further specification codes are available, such as transferable, standby and combinations of these. In DTA, the code '…standby' will not be allowed.

This field further qualifies the documentary credit amount and becomes important when checking documents presented under the L/C. If the code “not exceeding” is used, no amount tolerance is allowed. If the code “according to UCP” is used, allowances in credit amount are granted according to what is stipulated in article 39 of the UCP.

This field further qualifies the contract amount and becomes important when checking documents presented under the contract. If the code “not exceeding” is used, no tolerance is permitted. If the code “according to UCP” is used, allowances are granted based on stipulations provided in Article 30 of the UCP.

This field specifies the positive tolerance to the documentary credit amount as percentage plus that amount. In order to calculate the maximum amount (e.g. the maximum risk of the advising bank), the positive tolerance amount is added to the document amount.

This field specifies the positive tolerance to the nominal amount of the underlying contract as percentage plus that amount. In order to calculate the maximum amount (e.g. the maximum risk of the bank), the positive tolerance amount is added to the nominal amount.

This field specifies the negative tolerance to the documentary credit amount as percentage minus that amount.

This field specifies the negative tolerance to the nominal amount of the underlying contract as percentage minus that amount.

This field indicates the date when the L/C has been pre-advised (e.g. via SWIFT MT705) to the receiver (e.g. the advising bank) before the L/C has been issued.

This field indicates when the L/C was pre-advised (e.g. via SWIFT MT705) to the receiver (e.g. the advising bank) before the L/C was issued.

This date field specifies the latest date of shipment.

Upon checking of documents presented under the L/C, this field is compared with the actual shipment date in order to check for L/C compliance.

The presentation period, being the date difference between latest date of shipment and expiry date, can be calculated from this field.

This date field specifies the latest date of shipment.

When checking the documents presented under the L/C, this field is compared with the actual shipment date to check for L/C compliance.

The presentation period, i.e. the difference between latest date of shipment and expiry date, can be calculated from this field.

This field specifies the place of taking in charge (in case of a multimodal transport document), the place of receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service document), the place of dispatch or the place of shipment to be indicated on the transport document.

This field specifies the place of transfer (in the case of a multimodal transport document), the place of receipt (in the case of a road, rail or inland waterway transport document or a courier or express delivery service document), the place of dispatch or the place of shipment to be indicated on the transport document.

This field indicates whether or not partial shipments (shipment in more than one lot) are allowed under the L/C.

This field indicates whether or not partial shipments (shipment in more than one lot) are permitted under the contract.

This field specifies the final destination or place of delivery to be indicated on the transport document.

This field specifies the final destination of the goods shipped under the underlying contract.

This field indicates whether or not transshipment is allowed under the L/C. Transshipment (German “Umladung”) is the shipment of goods to an intermediate destination, and then from there to yet another destination. One reason for this is that the means of transport can be changed during the journey (eg. from ship to road transport).

This field indicates whether or not transshipment is allowed under the contract. Transshipment is the shipment of goods to an intermediate destination, from where they are transported to another destination. One reason for this is the change in the means of transport during shipment (e.g. from ship to road transport).

This field is defaulted with the country code of the sender of the L/C and therefore indicates the risk country of the L/C. It is used for statistical reasons and allows the advising bank to evaluate the country risks it may have entered by advising/confirming the L/C.

This field is defaulted with the country code of the sender of the L/C and therefore indicates the 'risk country' of the L/C. It is used for statistical purposes and allows the advising bank to evaluate the country risks it may have incurred by advising/confirming the L/C.

The field can be used for statistical reasons and allows the advising bank to evaluate L/C's by the types of goods that were shipped under the L/C. The codetable for this field can be customized by the bank according to their needs.

This field contains the type of goods shipped. The goods code is used to evaluate contracts by the type of goods. The codetable can be customized by the bank according to their needs.

This field counts the number of document sets which have been received (RCVDAT filled) by the advising bank under the L/C. This number is not decreased when the document set is settled or closed.

This field counts the number of document sets received by the advising bank under the L/C. This number does not decrease when the document set is settled or closed.

This field holds the version counter to keep track of the version history of a LED entry. The individual versions are controlled by entries in the SLG table.

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.

This field is used to indicate that the acknowledgment (generated in LETNOT, LETOPN) is sent directly to the Applicant's Bank (APB) instead of Issuing Bank/First Advising Bank.

Sometimes, the L/C states already how the documents shall be sent upon presentation. Therefore this field is defaulting BEDGRP\REC\DOCROLFLG which indicates that documents can be sent to another address than the payer of documents.

This field is used to indicate that the acknowledgment (generated in Pre-Advising/Notifying an Export L/C, Advising/Confirming is sent directly to the Applicant's Bank rather than the Issuing Bank/First Advising Bank.

Sometimes the L/C already states how documents are to be sent when presented. The field therefore defaults the 'Send Documents to Another Address' field in the document set, which indicates that documents can be sent to an address other than the payer of documents.

This field is used to calculate the maximum maturity of the export L/C when the L/C is confirmed (open or silent). If filled, the maximum tenor is added to the expiry date and the result is entered as maturity date in the liability grid for the liability booking of the L/C.

This field is used to calculate the maximum maturity of the export L/C when the L/C has been confirmed (open or silent). If filled, the maximum tenor is added to the expiry date and the result is entered as the maturity date in the liability grid for the liability booking of the L/C.

This fields indicates the confirmation status of the first advising bank (ADV) to the DOKA bank, which is advising the L/C to the beneficiary or another second advising bank (A2B).

The value can be: C - The sender has added his confirmation to the credit W - The sender has not added his confirmation to the credit Empty - not used

This field provides the bank using the application (which is advising the L/C to the beneficary or to another second advising bank (A2B)) with the confirmation status of the first advising bank.

Possible values: - The sender has added his confirmation to the credit - The sender has not added his confirmation to the credit

This field indicates if a L/C is revolving. If this flag is set, the revolving panel is visible and revolving details can be entered.

This field indicates whether the L/C is a revolving L/C. If this flag is set, the revolving panel is visible and revolving details can be entered.

This field counts the actual number of revolvings processed under the L/C.

This field counts the actual number of times the revolving L/C has been processed.

This field indicates the maximum number of revolvings allowed under the L/C.

This field indicates the number of times a revolving L/C can be processed.

This field contains the date when the next revolving should take place.

This field indicates when the L/C is next revolved.

The 'cumulative' information is relevant for the further processing of the revolving L/C. If the L/C is marked as 'cumulative', this means that irrespective of what was drawn previously, the remaining available amount is retained and increased with the full revolving amount on the revolving date. If the L/C is marked 'non cumulative' (REVCUM empty), any unutilized amount is lost and the available amount is raised to the value of the next shipment.

The 'cumulative' information is relevant for the further processing of the revolving L/C. If the L/C is marked as 'cumulative', it means that irrespective of what was drawn previously, the remaining available amount is retained and increased with the full revolving amount on the revolving date. If the L/C is marked 'non cumulative', any unutilized amount is lost and the available amount is raised to the value of the next shipment.

This field indicates whether the L/C revolves at the time of utilization (e.g. when documents are presented) or periodically on a specific date.

This field indicates whether the L/C revolves at the time of utilization (e.g. when documents are presented), or periodically on a specific date.

When the L/C is further advised to a second advising bank (A2B), this field indicates the confirmation instructions to the bank and is for example used in tag 49 of the outgoing MT710.

If the L/C is advised to another advising bank (2nd advising bank of the bank of the beneficiary), this field shows the confirmation instructions to this bank (e.g. in Tag 49 of an outgoing MT 710).

This flag is used to indicate whether the L/C is a red or green clause L/C. For these types of L/C the beneficiary is entitled to receive advances (so called Packing Credit).

This flag is used to indicate whether the L/C is a red or green clause L/C. For these types of L/C, the beneficiary is entitled to receive advances (so-called Packing Credit).

This field counts the number of document sets which have been advised (e.g. via SWIFT MT 750 or MT754) to the advising bank (OWN) but the physical documents have not been presented by the beneficiary yet (ORDDAT empty).

At the moment, the number of advised documents is not decreased when the physical documents are received.

This field counts the number of incoming document sets advised (e.g. via SWIFT MT 750 or MT754) to the bank using the application, but where the physical documents have not yet been received.

Contract status flag. If not empty, contract is reserved. That means, only a few basic fields have to be filled in. Visible on LETP in LETRSV and INFLED. Invisible in all other transactions.

Contract status flag. If not empty, the contract has been reserved and only a few basic fields have to be filled in. Visible in 'Reserving an Export L/C' (LETRSV) and 'Info Export L/C' (INFLED). Invisible in all other transactions.

Mark this box if the incoming L/C is transferred to us. To control the outgoing messages.

The 'Incoming Transfer' checkbox is checked when a transferred L/C has been received. It is used in message management. and is automatically checked if the receipt was notified via an MT 720 SWIFT message.

This field specifies the rules the credit is subject to.

This field specifies the rules governing the contract.

This field contains details to the applicable rules if no rules are specified.

This field contains details of the applicable rules, if 'other' rules have been specified. The field is only enabled if 'Any Other Rule' was selected previously.

This field specifies the port of discharge or airport of destination to be indicated on the transport document.

This field contains the port or airport of destination, where the goods shipped under the L/C are unloaded. This is not necessarily the place of delivery.

This field specifies the port of loading or airport of departure to be indicated on the transport document.

This field specifies the port or airport of departure indicated on the transport document.

Defines whether the issuer of the L/C is a bank or not. A non-empty content marks this L/C as being issued by a non-bank.

The field defines whether the issuer of the L/C is a bank or not. A non-empty content marks this L/C as being issued by an institute other than a bank.

Set in LETNOT, if incoming message is rejected / contract closed directly.

This flag is set in the (pre)opening transaction in case an incoming message is rejected. The contract is closed directly.

This table is defined on entity level with separate entries for each entity. This field holds the EXTKEY of the owning entity to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.

This field holds the external key of the owning entity to identify the logical owner of this entry.

This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.

This fields contains the percentage of the partial confirmation if any. It is enabled for user entries, only if the L/C is confirmed by the bank using the application.

This fields contains the percentage of any partial confirmation. It is only enabled for user entries, if the L/C has been confirmed by the bank using the application.

This field is automatically set when Cash Cover is booked on a 'hold account' under the L/C.

This field is automatically set when Cash Cover is booked to a 'hold account' under the L/C.

This field holds the INR of the transaction which opened the contract.

This field holds the INR of the transaction which opened/issued the contract.

A “peak amount” is understood to be the remaining liability balance under a Letter of Credit that remains unutilized after payment of documents. The checkbox “Book out Peak Amount” can be activated when documents are taken up. If set, the application checks the contract for other pending document sets and calculates the liability amount which should be booked out under the Letter of Credit. The calculation of the amount is displayed in the warnings for the user.

A “peak amount” is understood to be the remaining liability balance under a Letter of Credit that remains unutilized after payment of documents. The checkbox “Book out Peak Amount” can be activated when documents are taken up. If set, the application checks the contract for other pending document sets and calculates the liability amount which should be booked out under the Letter of Credit. The calculation of the amount is displayed in the warnings for the user.

For Auto-Extension: The LC expires on this date and after this date no further Auto-extensions are allowed.

For Auto-Extension: The LC expires on this date and after this date no further Auto-extensions are allowed.

For Auto-Extension: Period for the next extension of the LC.

For Auto-Extension: Period for the next extension of the LC.

For Auto-Extension: Period of advance notification about the next renewal.

For Auto-Extension: Period of advance notification about the next renewal.

Flag for activation of auto extension checkbox. If selected, a new panel for auto extension details opens.

Flag for activation of auto extension checkbox. If selected, a new panel for auto extension details opens.

This field is used to refine the logical meaning of an empty value in EXPDAT.

This field may only be set, when EXPDAT is empty.

When set to a non-empty value, this identifies an unlimited validity of the contract.

This field is used to refine the logical meaning of an empty value in EXPDAT.

This field may only be set, when EXPDAT is empty.

When set to a non-empty value, this identifies an unlimited validity of the contract.

This field indicates whether or not partial shipments (shipment in more than one lot) are allowed under the L/C.

This field indicates whether or not partial shipments (shipment in more than one lot) are allowed under the contract. Other conditions must be stated elsewhere in the message.

This field indicates whether or not transshipments are allowed under the L/C. Transshipment (German “Umladung”) is the shipment of goods to an intermediate destination, and then from there to yet another destination. One reason for this is, that the means of transport can be changed during the journey (eg. from ship to road transport).

This field indicates whether or not transshipment is allowed under the contract. Transshipment is the shipment of goods to an intermediate destination, from where they are transported to another destination. One reason for this is the change in the means of transport during shipment (e.g. from ship to road transport). Other conditions must be stated elsewhere in the message.

This flag is used to indicate whether for this L/C a special payment condition for beneficiary is avaiable.

This flag is used to indicate whether for this L/C a special payment condition for beneficiary is avaiable.

This flag is used to indicate whether for this L/C a special payment condition for receiving bank is avaiable.

This flag is used to indicate whether for this L/C a special payment condition for receiving bank is avaiable.

This field contains the days of presentation period.

This field contains the days of presentation period.

This field contains details to the presentation period.

This field contains details to the presentation period.

Flag to activate assignment of proceeds panel.

Flag to activate assignment of proceeds panel.

Flag to activate participation sold logic.

Flag to activate participation sold logic.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the PRDCOD shall identify the business sector together with some key criteria like confirmed or unconfirmed LC in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the PRDCOD shall identify the business sector together with some key criteria like confirmed or unconfirmed LC in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the PRDSUB shall identify the business sector specific bankside defined products adding some key sub criteria in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the PRDSUB shall identify the business sector specific bankside defined products adding some key sub criteria in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the product variant is intended as possible extension to setup specific variants below the product and subproduct code.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the product variant is intended as possible extension to setup specific variants below the product and subproduct code.

Unique internal ID of a linked facility record.

Unique internal ID of a linked facility record.

This denotes the amount out of the LC contract amount that is available for red/green clause advance.

This is the currency of the red/green clause amount.

This field denotes the red/green clause currency. It is usually same as the LC contract currency.

This denotes the percentage out of the LC contract amount that is available for red/green clause advance.

This (invisible) field defines, if the amount or the percentage is used for red/green clause.

Based on this information, the percentage or amount are protected and calculated from the other field.

This (invisible) field defines, if the amount or the percentage is used for red/green clause.

Based on this information, the percentage or amount are protected and calculated from the other field.

Domestic L/C - set if advising Bank and applicant belong to same country.Otherwise it is empty and means International L/C.

This flag indicates if the L/C is a domestic L/C or not. If the country of the DOKA-NG Bank and the applicant's country are same, it is termed as a domestic L/C.

The bank using DOKA must issue the ALADI Reimbursement code on customer request when a contract is opened.

The bank using DOKA must issue the ALADI Reimbursement code on customer request when a contract is opened.

This flag will be visible only if entity group is in the LATAM region.

Also, this will be enabled for input only if the current entity has an ALADI member ID and the counter-party bank is also defined as an ALADI member in the party table.

Checking this flag denotes this contract is under ALADI Inter-bank Settlement and therefore: a) System auto generates the ALADI Reimbursement code for (Import LC and Export Collection contracts). b) System allows the user to manually input the ALADI Reimbursement code for (Export LC and Import Collection contracts)

Alternate reference number, can i.e. contain the old reference for migrated contracts.

Alternate reference number, can i.e. contain the old reference for migrated contracts.

Introduced with Swift Release 2023 This field specifies the place of taking in charge (in case of a multimodal transport document), the place of receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service document), the place of dispatch or the place of shipment to be indicated on the transport docum

Introduced with Swift Release 2023 This field specifies the final destination or place of delivery to be indicated on the transport document.

Introduced with Swift Release 2023 This field specifies the port of discharge or airport of destination to be indicated on the transport document.

Introduced with Swift Release 2023 This field specifies the port of loading or airport of departure to be indicated on the transport document.

This flag is used to indicate whether for this L/C a special instructions from 3rd Bank (:78D: ) is available.