This transaction is used to process special cases in the handling of checks.
This could involve:
The transaction is primarily controlled through the “Source” and “Target” fields. These determine where the check comes from (source) and where it is to be sent to (target). Bookings in the transaction are generated from the parties entered in these fields. The party entered in the “Source” field is always the party to be credited, while the party captured in the “Target” field is debited. Nothing is booked if source and target are identical.
Credit and debit value days were saved when the check was first captured so that they can be used in transactions such as this. For example, the debit value date is used for the check dispatch account when generating remittances and credit value dates are needed for returns. Warnings are implemented if value dates captured here do not match value dates captured originally.
If this transaction handles just one single check, or if the value date of all checks handled is identical, the value dates for the new contract is determined by taking the presentation date of the check and adding the number of days assigned for the check route.
This transaction is used to handle special cases such as the return of checks without remittance
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.
The check processing fee 'CHFHAN' is charged on per mille basis on the presentation amount and billed to the presenter, if the presenter has been entered in the “Source” field.
The returned check fee 'CHFRET' is charged on a piecemeal basis and billed to the presenter, if the presenter has been entered in the “Target” field.
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.
Name of Message | Receiver | Message ID | Comment |
---|---|---|---|
Return of Check Remittance | Remitter | CHTCHR1 | If “Target of checks” is Remitter |
Check Remittance | Collecting Bank | CHTCOL1 | If “Target of checks” is Collecting Bank |
Signature required
Overview
Checks
Reasons for return
Settlement Details
Settlement
Bookings
DTAEA Fields
DTALC Fields
Completion
Incoming Tag 72/79
Messages
Compliance
Attachments
Fee Conditions
DTAG Fields
Datafield | Description |
---|---|
Reference | cf Appendix A, Table CHD field OWNREF |
Responsible User | cf Appendix A, Table CHD field OWNUSR |
Contract Type | cf Appendix A, Table CHD field CONTYP |
Direction | cf Appendix A, Table CHD field DIRTYP |
Payment Document | cf Appendix A, Table CHD field CHKTYP |
Currency | cf Appendix A, Table CBB field CUR |
Maximum Amount | cf Appendix A, Table CBB field AMT |
Country Code (for Statistics) | cf Appendix A, Table CHD field STACTY |
Check Count | cf Appendix A, Table CHD field CHKCNT |
Default Valuta | cf Appendix A, Table CHD field VALDAY |
Additional Fee | cf Appendix A, Table CHD field FEECOD |
Order Date | cf Appendix A, Table CHD field ORDDAT |
Opening Date | cf Appendix A, Table CHD field OPNDAT |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
Use Collecting Bank for all Checks | cf Appendix A, Table CHD field COLUSE |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
External Key | cf Appendix A, Table PTS field EXTKEY |
Name | cf Appendix A, Table PTS field NAM |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
Datafield | Description |
---|---|
Status | This column shows where the payment document is located at present. Is set by the application in the course of the various transactions. |