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 reference number of the import L/C. The reference number can be up to 16 characters long. This field can be used for searching import L/Cs in the database.

This field holds the descriptive name displayed in the application to describe and to search for a contract. in the standard version 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 responsible for handling this contract.

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

This date field identifies the date the entry was physically added to 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 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 contains the name of the advising bank.

This field contains the reference number of the advising bank.

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 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 is a copy of relevant field for the 'Applicant'. This field is only used to speed up search and database access.

This is a copy of relevant field for the 'Applicant'. This field is only used to speed up search and database access.

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

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

This field contains the name of the beneficiary.

This field contains the reference number of the beneficiary.

This field defines whether the fees and commissions of the bank using using the application is to be borne by applicant or 'Our fees borne by client' (='U'), of the beneficiary 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 applicant Side.

Meaning of 'borne by abroad': Own fees in the settlement are proposed to the debit of the beneficiary SIDE

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

This field contains the confirmation instructions for the receiver of the L/C, e.g. the advising bank. According to SWIFT regulations, one of the following code words must be selected: “Without”, “May add” or “Confirm”.

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 the place where the L/C expires. The expiry place is closely linked to the expiry date, as it specifies the place where documents have to be presented under the L/C in more detail.

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

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 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 nominal amount of the underlying contract as percentage minus that amount.

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

Account number of the reimbursing bank in the books of the reimbursing bank.

This field contains the codes for reimbursing bank's charges according to TAG 71A of the outgoing reimbursement authorization (SWIFT MT 740).

If this flag is set, the reimbursement panel becomes visible and reimbursement information can be entered under the Import L/C.

This date field specifies the latest date of shipment.

When the documents presented under the L/C are checked, this field is compared with the actual date of shipment in order to monitor 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 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 specifies the port or airport of departure 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 indicates whether or not partial shipments (shipment in more than one lot) are permitted under the contract.

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 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 for the receiver of the L/C and therefore indicates the 'risk country' of the L/C. It is used for statistical purposes to evaluate the country risks it may have incurred by issuing the L/C.

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 received (Date of Documents Received filled) by the issuing 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 advised (e.g. via SWIFT MT 750 or MT754) to the issuing bank (OWN) where the physical documents have not yet been received (Date Documents Received is empty). When the physical documents have been received (Date Documents Received (RCVDAT) is filled), the number of subcontracts advised decreases.

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 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.

The internal type is set to Back-to-Back, if there is an export L/C which backs this import L/C. Back-to-Back L/Cs can only be issued via 'Opening an Import L/C' from 'Selecting an Export L/C'.

This field contains the unique ID of the export L/C on which this import L/C is based.

This field contains the reference of the export L/C on which this import L/C is based.

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

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

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.

The bank may reserve the right to revolve the L/C after receiving the applicant's instructions and/or credit approval. If not empty, the L/C is not automatically revolving.

This field contains the date when the L/C is next revolved.

'Cumulative' information is relevant for the further processing of a revolving L/C. If the L/C is marked as 'cumulative', 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' (checkbox not checked), any unutilized amount is lost and the available amount is raised to the amount 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 contains the name of the applicant's bank.

Contract status flag. If not empty, the contract has been reserved and only a few basic fields have to be filled in. Visible in 'Pre-Opening an Import L/C' (LITPOP) and 'Info Import L/C' (INFLID). Invisible in all other transactions.

This field specifies the rules governing the contract.

This field specifies the rules governing the reimbursement authorization.

This field specifies details of the applicable rules.

This field contains the date of the original authorization to reimburse.

Order date of incoming message from the applicant's side. Is only used for outgoing messages to the applicant.

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

This selection list contains the type of request. Possible values are 'Pre-Opening' and 'Draft'. In case of 'Draft' no liability is booked and only the message 'LC Draft' to the applicant/ initiating institution is generated. In case of 'Pre-Opening', the LC is preavised to the advising bank / beneficiary side (usually with a SWIFT MT705). Liability is booked accordingly.

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.

The delivery terms may be FOB, CIF or FCR, for example.

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.

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.

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: The LC expires on this date and after this date no further Auto-extensions are allowed.

This field relates to the payment of the freight and depends on the selected Incoterm.

Place of delivery for the incoterms.

Flag to activate assignment of proceeds panel.

Flag to activate participation sold logic.

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 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 receiving bank is avaiable.

This field contains the days of presentation period.

This field contains details to the presentation period.

Draft number to be printed in Score MT 771 Score message. Incremented in LITPOP

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 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

This flag indicates if the L/C is a domestic L/C or not. If the risk country of L/C and the beneficiary's country are same, it is termed as a domestic L/C.

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

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.

The liquidity costs refer to the costs of the bank which occur in order to provide the neccessary liquidity.

This field contains the base rate used to calculate interest.

Costs of procuring the funds on the money market.

The share of the overall interest rate booked as income in the bank's books. Is pre-defined and noted by rate type possible special terms and conditions.

Checkbox to enable Loan details panel. User could provide loan terms and details requested by applicant, which could be considered if finance is created for the contract during settlement.

If not empty the fee for the complete period is defined by the amount OWNAMT instead of the rate OWNRAT.

Document Currency used for display purpose only

Alternative fixed amount for the total term to maturity. (instead of an interest rate for 'Our margin')

The financing period indicates the number of days to be financed.

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)

Denotes if the LC is Usance Payable at Sight (UPAS) or Usance Payable at Usance (UPAU).

This field is enabled only for UPAU LCs. The number of UPAU days is to be given here.

Alternate Reference. I.e. for old reference of migrated contracts.