This transaction is used to send checks to the collecting bank (generating remittances). The transaction is started from the “Generate Remittance” panel in the Display a Check Contract transaction. All checks stored in the check pool for the selected check route (across entity groups) which have not been dispatched are defaulted on the panel. Single checks can be excluded from the process. Remittances are generated separately for import and export checks.
As well as sending checks to the collecting bank, at the same time the international bank is debited and the clearing account “Checks Subject to Payment” identified. Pass through charges from the international bank can be offset directly.
Correspondence accompanying the remittance contains a list of the checks that make up this dispatch and/or a list of denominations for travelers' checks. A separate contract is created for each remittance. The transaction debits the account of the collecting bank and credits the pool account with the values defined for the check route. These values are determined by the check presentation contracts. If checks from a variety of presentation contracts with different values come together for dispatch when generating remittances, a corresponding warning is issued and the value of the remittance has to be entered manually.
If the bank using the application simultaneously is the collecting bank for the checks, then the check issuer can be recorded as an additional party to the contract. In this case, a debit booking will be made to the issuer instead of the collecting bank.
This transaction is used to remit checks to the Collecting Bank
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.
For more information see TRNDIA Diaries.
None
No liability is booked.
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 |
---|---|---|---|
Remittance | Collecting bank | CHTCOL1 | Dispatch is by letter only because the payment records are enclosed in the envelope. If the issuer is established, no remittance letter will be generated. |
Signature required
Overview
Checks
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. |