BRD - Document Set under Import L/C Data

BRD is the main data table for the Import L/C Document Set contract.
All technical important fields have to be defined here.
Large text blocks should be defined in BRT.

/

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 BRD. The field INR is used to enable links from other tables to this table. It also links the two tables BRD and BRT as associated entries hold 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 reference number of the import L/C document set. The reference number can have a maximum size of 16 characters. This field can be used to search for an import L/C document set in the database.

This field contains the reference number of the document set contract (BR). The reference number can comprise up to 16 characters. This field should be defined as a database key field to optimize performance. It can be used to search for BR contracts in 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 contains the name of the bills received displayed externally to identify a BR contract. The name can comprise up to 40 characters.

This field should be defined as a database key field to optimize performance. It can be used to search for BR contracts in the database.

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 contains the type of the parent contract.

This field contains the type of the parent contract.

This field contains the internal unique ID of the parent contract.

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

The presentation date is the date, on which the DOKA bank presents the documents to the customer (e.g. the applicant or initiating institution).

The presentation date is the date when the bank using the application presents the documents to the customer (e.g. the applicant or initiating institution).

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 the vessel in the beneficiary's country.

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 the vessel in the beneficiary's country.

This field will be filled when settlement was effected before documents have been received. This field triggers the flag for a possible claim back of the document amount (in BRTDCR). This field will be cleared again, when docs are sent to the APL (BRTSND) and docs have no discrepancies resp. discrepancies are ignored

This field is filled when settlement is effected before documents have been presented. If the field is filled, it is possible to claim back the document amount.

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

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

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

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

Date is set when an Advice of Payment (incoming MT754) has been received ( e.g. in TRN LITDAV).

Date contains the datet when an Advice of Payment (incoming MT754) was received (e.g. in transaction 'Advising Documents').

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

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

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

Date when the bank using the application has received the documents from the presenter (date of receipt stamp, NOT date of customer order - that would be the order date).

Date is set when an Advice of Discrepancy (incoming MT750) has been received ( e.g. in TRN LITDAV).

This field indicates the date when an Advice of Discrepancy (incoming MT750) was received (e.g. in transaction 'Advising Documents').

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

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

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

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

This field contains information about how documents are rejected. As this field will be replaced in the future, it should not be used any further.

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

This field specifies if documents are sent on approval basis, meaning that discrepant documents are received which the applicant may pay or reject.

This field specifies whether documents are sent on approval basis, i.e. that discrepant documents can be received which the applicant may pay or reject.

This flag indicates on whose request the goods were released.

This flag indicates the party instigating the release of goods.

This date specifies when the DOKA bank has issued the release of goods.

This date specifies the date when the bank using the application has issued the release of goods.

This field indicates the number of the transport document (e.g. number of bill of lading, airway bill).

This field indicates the number of the transport document (e.g. number of bill of lading, air waybill).

This field specifies if the documents are handled free of payment, meaning that the documents are presented to the applicant without him having to pay for them. In German, this is called “Dokumente ohne Zahlung/wertfrei aushändigen”.

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

This field holds the version counter to keep track of the version history of a BRD 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 specifies if documents have been advised via incoming Payment Advice (e.g. MT754) or Advice of Discrepancy (e.g. MT750).

The Type “Other” can be used for incoming messages other than MT750 or MT754 which might advise a document set as well. Example: The issuing bank has issued the L/C with an authorization to reimburse (L/C is payable abroad and the issuing bank itself is the reimbursing bank). If the bank abroad takes up documents and claims for reimbursement, the issuing bank might receive a MT742 (reimbursement claim).

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

The option “Other” can be used for incoming messages other than MT750 or MT754 which might also advise a document set. Example: The issuing bank has issued the L/C with the authorization to reimburse (L/C is payable abroad and the issuing bank itself is the reimbursing bank). If the bank abroad accepts documents and claims for reimbursement, the issuing bank might receive a MT742 (reimbursement claim).

This field is used to differentiate whether goods are released under shipping guarantee or airwaybill etc.

This field is used to differentiate between goods released under a shipping guarantee or under an air waybill, etc.

In case a shipping guarantee is issued under the L/C, this date specifies the expiry date of the shipping guarantee.

In case a shipping guarantee is issued under the L/C, this date specifies the expiry date of the shipping guarantee.

If this flag is set, goods are released to the applicant of the L/C. Otherwise, goods can be released to another party which is entered in BRDGRP\BLK\RELSTOADR.

If this flag is set, goods are released to the applicant of the L/C. Otherwise, goods can be released to another party entered in 'Release to Address'.

This field indicates the type of transport document (e.g. bill of lading, airway bill etc.) which is presented under this L/C.

This field indicates the type of transport document (e.g. bill of lading, air waybill etc.) which is presented under this L/C.

This field indicates the date of the transport document (e.g. bill of lading, airway bill) which is presented under this L/C.

This field indicates the date of the transport document (e.g. bill of lading, air waybill) which is presented under this L/C.

This field indicates how the goods have been shipped (e.g. via sea, air or a combination of different transport modes).

This field indicates how the goods have been shipped (e.g. via sea, air or a combination of different transport modes).

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

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

This checkbox enables the banks to decide whether they want to use a 'slim' version of TRN LITDCK (Documents received) where only minimal information is entered (→ This function is preferred by larger banks). Smaller banks use TRN LITDCK to enter document details, discrepancies, instructions and shipping details. When the checkbox is set to 'not empty' the relevant additional panels are visible.

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

Defines the party who has presented documents and is the receiver of payment. The payee might be the beneficiary.

Defines the party who has presented documents and is the receiver of payment. Exception: In case a stickerbank has been entered, the payment is made to the stickerbank.

The current document set status is stored in this field. The field is set via a default in the panel module.

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

This field is closely linked to the BRDGRP\BLK\DOCDIS where the discrepancies of the document set are listed. If this field (IGNDISFLG) is set to a nonempty value it means that the content of DOCDIS will be ignored. For example: If the field is filled, the discrepancies are not listed in the outgoing correspondence, diaries are not generated to follow up acceptance of discrepant documents.

This field is closely linked to field 'Discrepancies' where the discrepancies of the document set are listed. If this field is set to a non-empty value, the content of 'Discrepancies' will be ignored. For example: If the field is filled, the discrepancies are not listed in the outgoing correspondence, diaries are not generated to follow up acceptance of discrepant documents.

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 TRN lateron (outgoing MT752 in BRTACP or BRTPAY), the field is stored here.

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 subsequent transactions (outgoing MT752 in 'Accept Discrepancies') or 'Send and Settle Documents'), 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 other TRN lateron (outgoing MT752 in BRTACP or BRTPAY), 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 other subsequent transactions (outgoing MT752 in 'Accept Discrepancies' or 'Send, Accept and Settle Documents'), the field is stored here.

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

Formerly PAYROL

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

This field specifies whether documents are taken up and whether liabilities can be booked against the BR.

This field specifies whether documents are to be accepted and whether liabilities can be booked against the BR.

Date of incoming cover letter received from the presenter.

Date of incoming cover letter received from the presenter.

When this flag is set, Documents are returned.

When this flag is set, documents were returned.

This field specifies if the presenter in this contract is used as sticker bank.

When this flag is set, the document presenting bank acts as a Sticker Bank, which means the receivables have been sold to this bank and payment must be effected to the Sticker Bank according to the presenting bank's instructions. Usually, this is documented by a sticker on the document presentation letter.

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 field holds the INR of the transaction which opened the contract.

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

This field is used to trigger the payment and necessary booking entries under an UPAS/ UPAU LC (Usance Payable at Sight/ Usance) when the documents are taken up.

This is applicable only for UPAS/UPAU LCs.

This checkbox denotes if payment to Beneficiary can be remitted or not (by debiting the internal UPF account). If the flag is set, settlement will be made final and payment remitted to the Beneficiary.

This field specifies the interim maturity date of a UPAU (Usance Payable at Usance) Letter of Credit. On this day, the beneficiary side of a UPAU LC is credited with the funds. When documents are taken up, the interim maturity date will be calculated as 'Maturity Date' minus 'UPAU Days (UPAUDS)' defined under the LC.

This field specifies the UPAU Maturity date.