This transaction is used to process checks and other payment documents submitted to the bank using the application by the presenting party, requesting the immediate transfer of the equivalent amount to his customer account.

When entering the data, a distinction is made between import and export checks; i.e., only import or only export checks can be handled within the same check presentation procedure, especially since the check routes are determined separately (the master data transactions “Maintaining a Export Check Routing” and “Maintaining a Import Check Routing” are provided for this purpose).

Checks can either be presented by the customer directly, or by banks as part of a cash-letter procedure.

Export checks presented are of the same type (travelers checks, order checks, debit notes), i.e. the debit advices are always in the same currency and all have the same Check Routes. These check routes are distinguished by the country of the drawee, currency and type of payment documents. If a check route has been defined in the master data for the criteria entered, then the collecting bank and the associated data are loaded automatically.

When entering a presentation of export checks, the collecting bank, the fee code for settling pass through charges with the presenter and the value date provided by the collecting bank all default to the data from the check route entered.

With export checks, too, there is an option to select a different collecting back for individual checks within the batch of checks being presented. To do so, the checkbox “Collecting bank for all checks” must be unchecked. In this case, the check route is determined once the country is entered on the check panel.

The fee code defined in the check route describes a pass through charge immediately charged to the presenter, but credited to the collecting bank at a later time. Amounts credited to the collecting bank are, in many cases, credited to the collecting bank at fixed times, e.g. once a month or once a quarter, and in many cases independent of the contract created. The application handles the credits to the collecting bank as periodic settlements via the “Manual Contracts” (MC) business sector.

For import checks, the check route is determined after the country and the type of payment document have been entered. Since each import check presented can have a different collecting bank, these can be entered in the “Checks” panel. For import checks drawn on banks located in Germany, the collecting bank is determined automatically once the bank clearing code has been entered on the “Checks” panel.
To be able to demonstrate in the standard application how effective automatic check routing can be when large numbers of checks are involved, this facility has been implemented in the standard application using the example of drawee banks located in Germany. Minor adjustments will need to be made for banks located in another country.

An independent check contract is set up each time checks are presented. Individual checks presented together are stored in a check pool.

• With order check or debit notes, the number of checks presented can be entered in the “Number of Checks” field. This then determines the number of lines defaulted in the check pool, ensuring that there is a line in the check pool for each check.
• This is not the case with travelers checks since these are usually issued in fixed denominations and are easier and quicker to enter if the user enters the number of travelers checks per denomination in the check pool.

Because entries in a check pool have to be unique, the individual lines in the check pool may require the check number (or part of the check number). Controls are carried out on all checks stored in the check pool that have not yet been sent.

Depending on the presenter and the check route, the check is debited to a pool account 'subject to payment', minus fees and with a deferred value date. If converted to another currency, checks are settled at the purchase rate.

Debit bookings are borne by an pool account internal to the bank. Pool accounts are to be identified as 'CH' (check dispatch account) accounts. Once the transaction “Processing Presented Checks” has been released, checks stored in the check pool can be handled further as part of a process creating remittances.

Credit and debit dates in the presentation of checks are stored so that they can be accessed in subsequent transactions. For example, if the debit date for the check dispatch account is used for to create remittances, the credit date is needed for returns. In subsequent transactions, warnings are implemented as soon as value dates captured there do not agree with the originally stored value dates.

This transaction creates a new Check contract.
If an existing Check transaction is used, it may not be open or closed.
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.

A check handling fee 'CHFHAN' is charged as a per-thousand fee on the amount presented and billed to the presenter.

In addition, if defined in the check route and not deactivated for presentation, the additional fee is charged to the presenter and placed in the pool for the collecting bank (see Maintaining a Export Check Routing).

For more information see TRNDIA Diaries.

None

Details on creation of messages can be found under DOCEOT Messages. For outgoing allNETT / RIVO messages see Overview of Outgoing messages - allNETT / RIVO.

Signature required

Overview
Checks
Settlement Details
Settlement
Bookings
DTAEA Fields
DTALC Fields
Completion
Incoming Tag 72/79
Messages
Compliance
Attachments
Fee Conditions
DTAG Fields