CPD - Clean Payment Data

CPD is the main data table for the Clean Payment contract.
All technical important fields have to be defined here.
Large text blocks should be defined in CPT.

/

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 CPD. The field INR is used to maintain links from other tables into this table and links the two table CPD and CPT 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 clean payment being established. The reference number can have a maximum size of 16 characters. This field can be used to search for any export collection from the database.

This field contains the reference number of the clean payment

This field hold 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 is not modifiable 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 contract amount and main party and is not modifiable by the user.

This field contains the long name of the payee of the clean payment for display purposes.

This field contains the descriptive name of the payee

This field contains the reference of the payee.

This field contains the reference number of the payee

This field contains the long name of the paying bank of the clean payment for display purposes.

This field contains the descriptive name of the paying bank

This field contains the reference of the paying bank

This field contains the reference number of the paying bank

This field contains the long name of party instructing the clean payment for display purposes.

Depending on the type of the clean payment the party can be customer of the bank or a third party.

This field contains the descriptive name of the customer placing the order.

This field contains the reference of the party instructing the clean payment.

This field contains the reference number of the customer placing the order.

This field contains the long name of the ordering institution of the clean payment for display purposes.

This field contains the descriptive name of the institution placing the order.

This field contains the reference of the ordering institution.

This field contains the reference number of the institution placing the order.

This field contains the value date for the settlement.

This field contains the value date of the clean payment

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 defines whether the charges and commissions of the bank are borne by the applicant side (=“U”), by the beneficiary 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 are to be 'borne by client' (='U'), 'borne by' (='B') or borne by other parties. Depending on the selection made in this field, the roles in the second settlement table (own commission / fees) are proposed.

Meaning of 'borne by client' on incoming payment: 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 payee is proposed.

Meaning of 'borne by client' on outgoing or transitory payment: Own fees in the settlement are proposed to the debit of the applicant SIDE

Meaning of 'borne by abroad ' on incoming payment: Own fees in the settlement are proposed to the debit of the applicant SIDE

Meaning of 'borne by abroad' on outgoing or transitory payment: Own fees in the settlement are proposed to the debit of the payee

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

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.

This field holds the user ID of the person which is responsible to handle 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 field holds the version counter to keep track of the version history of a CPD 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 defines which side of the clean payment has to pay the charges.

Depending on the selection and the type of the clean payment CHATO is defaulted by the correct party of the bank.

This field defines which side of the clean payment has to pay the charges.

Depending on the selection and the type of the clean payment field 'Our Charges to' is defaulted by the correct party of the bank.

This field contains the type of the clean payment.

Possible values: Incoming payment Outgoing payment Transit payment

This field contains the payment type of the clean payment

The field can be used for statistical reasons and allows to evaluate clean payments by the types of goods that were shipped under the clean payment. 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 can be used for statistical reasons.

This field can be used for statistical reasons.

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.

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.

Beneficiaries Account number as stored in allNETT.

Beneficiaries Account number as stored in allNETT.

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

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 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 the type of transport document (e.g. bill of lading, airway bill etc.) which is presented under this clean payment.

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

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

This field indicates the unique reference number assigned to the transport document (e.g. bill of lading number or air waybill number).

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

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

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, or air or a combination of different transport modes).

To select from the list of available Incoterms

This field refers to the published version of the Incoterms.

Marks, if shipment details have to be provided or not. Only if the flag is ticked panel shipment details is open for entry of any data.

Marks, if shipment details have to be provided or not. Only if the flag is ticked panel shipment details is open for entry of any data.