CHD - Check Handling Contract Data

CHD is the main data table for the Check Handling contract.
All technical important fields have to be defined here.
Large text blocks should be defined in CHT.

/

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 CHD. The field INR is used to enable links from other tables to this table. It also links the two tables CHD and CHT 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 unique reference number of the check contract being established. The reference number can be up to 16 characters long and will be created during save of the initiating transaction. This field can be used to search for any check handling contract in the database.

This field contains the unique reference number of the check contract being established. The reference number can be up to 16 characters long and will be created during save of the initiating transaction. This field can be used to search for any check handling contract in the database.

The name of the contract will automatically be created when a new contract is stored in the database. Currency, amount, country and name of the remitter are part of the contract name. Any information within this field may be used for search within the info-system.

The name of the contract will automatically be created when a new contract is stored in the database. Currency, amount, country and name of the remitter are part of the contract name. Any information within this field may be used for search within the info system.

This field holds the User ID of the person responsible for handling this contract. An optional field, in the Demobank the field is initially filled with the 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.

When checks are presented by the remitter, this date contains the opening date of the presentation contract. When the checks are remitted to the collecting bank, this date contains the opening date of the remittance contract.

If a payment document is submitted by the presenter, this field will contain the opening date of the submission contract. If the payment document is forwarded to the collecting bank, this field will contain the opening date of the remittance. 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 order date of the remitter's presentation. Under a remittance contract, i.e. when the payment documents are sent out to the collecting bank), there is no order date.

This field contains the order date of the check remittance from the remitter. Under a check remittance contract, i.e. if the payment documents are sent to the collecting bank, there will be no order date.

Contract status flag. If not empty, contract is reserved. That means, only a few basic fields have to be filled in. Visible on CHTP in CHTPOP and INFCHD. 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.

This field represents the type of the payment document and is part of the determination for the collecting bank.

This field represents the type of the payment document, e.g traveller checks, order checks or debit notes. Based on this field, the country and currency of the payment document, a collecting bank is determined automatically when a check routing definition has been set up in the static data.

Describes, which kind of check contract this contract is.

This field describes the kind of check contract: Differentiation is dones between Presentation (i.e. presentation of checks), Remittance (i.e. remittance of checks) and Special Handling.

This field contains the country code of the collecting bank.

This field contains the country code of the collecting bank.

This field is for the total number of checks remitted by the presenting institution within a single remittance.

This field is for the total number of checks remitted by the presenter within a single remittance.

The number of value days entered will be used to calculate future settlement dates. The field contains the number of future working days for which the Collecting Bank either promised to pay the equivalent of remitted payment documents or authorized the sender of the payment documents to debit their account.

This field contains the number of future working days for which the Collecting Bank promised to pay the equivalent of remitted payment documents resp. authorized the sender of the payment documents to debit their account. The number of days entered will be used within the check-transactions to calculate future value dates.

This field is for foreign fees, i.e. Collecting Bank's fee. This fee will be charged to the Remitter of checks and credited to the Collecting Bank when the check presentation contract is opened. The charge is loaded from the check routing definition in the static data.

This field is for foreign fees, i.e. Collecting Bank's fee. This fee will be charged to the Remitter of checks and credited to the Collecting Bank when the check presentation contract is opened. The charge is loaded from the check routing definition in the static data.

This field holds the version counter used to keep track of the history of a CHD entry. The individual versions are managed 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.

The value date will be stored from the initializing transaction to be used again in future transactions. For example it will be used for return of payment documents to reverse booking entries.

The value date of the credit booking towards the remitter is stored in this field. The value date will be stored from the initializing transaction to be used again in future transactions. For example it will be used for return of payment documents to reverse booking entries.

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.

Direction of Check

A check presentation is distinguished between import and export checks. Export Checks are payment documents which are sent for collection to a bank abroad. Import Checks are payment documents which are sent by the bank using the application to the collecting bank which has issued the payment document.

This field represents the type of the payment document and is part of the determination for the collecting bank.

For handling import check presentations, each check could have its own collecting bank. This can entered on the check panel. In case all checks are drawn on the same collecting bank, this checkbox can be checked. As a consequence, the collecting bank is set for all checks of the presentation.

Date of Check

This field contains the date of the individual check.