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 subcontract created for the set of documents received. The number is created automatically when the subcontract is created.

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 main party, and cannot be modified by the user.

This field contains the type of the parent contract.

This field contains the unique identifcation number of the parent contract.

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

The presentation date is the date on which the bank using the application presents the documents to the payer (e.g. issuing bank or 1st advising bank).

Date on which the bank using the application received the documents from the presenter (date of receipt stamp, NOT date of customer order - that is the order date).

This date specifies when the goods have been shipped. If goods are shipped by sea, this field specifies the date when the goods are taken on board of the vessel in the beneficiary's country.

Date is set when an Advice of Payment (incoming MT754) has been received (e.g. in the 'Advising Documents' transaction).

This field specifies the maturity date of a usance document set presented under the L/C.

This field specifies the type of documents which have been received under the L/C. The selection made in this field strongly influences the processing options available in BE.

For example, if “sight documents” (= P) has been selected, the document set can be settled in the 'Send and Settle Documents' transaction, while for usance documents (= A, D) only liabilities can be booked in 'Send and Settle Documents'.

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 date field identifies the date the entry was physically added to the database.

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

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.

Check this box if documents are to be handled on approval basis, i.e. whether documents have been received which the applicant may pay or reject.

This field specifies whether the documents are handled free of payment, i.e. whether documents are presented to the applicant without them having to be settled.

Defines the party who has presented documents and is the receipient of payment.

This field specifies the debit party who is paying the document set (e.g. issuing bank).

Date of incoming cover letter received from the presenter.

This field is set to a non-empty value, if the document set holds more than one tenor.

his checkbox allows banks to decide whether they want to use a 'slim' version of transaction 'Documents received', where only minimal information is entered.

This function is preferred by larger banks. Smaller banks use the 'Documents received' transaction to enter details, discrepanies, instructions and shipping details. If the checkbox is checked, relevant additional panels are visible.

This flag specifies that documents have been taken up for payment, acceptance, negotiation. The selection made in this field strongly influences the processing options available in Export Documents. The flag is used in the 'Send and Settle Documents' transaction to pay sight documents or to book in the liability with usance documents.

This field specifies whether documents have been advised via an incoming Payment Advice (e.g. MT754) or Advice of Discrepancy (e.g. MT750).

Date is set when an Advice of Discrepancy (incoming MT750) has been received.

This field contains the currency of the total amount of the MT750 message to be remitted to the sender of the message. As this field is required in other subsequent transactions (outgoing MT752), the field is stored here.

This field contains the total amount of the MT750 message to be remitted to the sender of the message. As this field is required in subsequent transactions (outgoing MT752), the field is stored here.

This field is necessary should an Advice of Payment (MT754) be received under the L/C where TAG 34A has been specified. According to SWIFT regulations, TAG 34A can contain a value date, i.e. the date when the document set should be paid or has been paid. The information received is stored in this field.

The current status of the document set is stored in this field.

This field can be used to send the documents (e.g. Document Presentation 1st/ 2nd mail) to an address other than the payer of documents.

This checkbox can be used to indicate that documents are to be sent to another address. The address is selected in 'Receiver of Documents'.

If 'Send Directly to Applicant's Bank' was set under the LE, this field is defaulted accordingly.

This fields indicates if an acknowledgment message for received documents was send either in 'Receiving Documents', in 'Send and Settle Documents' or in 'Sending Documents'. A field filled means that the message was sent on the date stored in the field.

When this flag is set, the documents have been returned.

This triggers the debitting of an liability if authorization documents have been sent.

This field specifies the date when the documents are starting to be past-due/ overdue. This happens when a set of documents has been presented and the bank is obliged to pay. For some reasons, the bank cannot debit the payer's account in return and so gives (unwillingly) a credit to the payer. If the bank is lateron able to recover the document amount from the payer, they may collect interest from this day on.

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.

Flag is set, if an MT 742 has been sent out.

The customer reference no. assigned for this negotiation.