This transaction is used to maintain check routes for export checks in the business sector “Check Handling” (CH).
The following transactions can be started from here by clicking the icons in the list below for:
A check route indicates via which foreign collecting bank a payment document can be collected.
Depending on the currency of the payment document, the country it is drawn on and the type of document (e.g. order check, travelers check, etc.) an address for the collecting bank can be selected from the system. All payment documents that have the same criteria for “currency”, “country” and “payment document” can then be sent to this collecting bank.
For settlement, it is also possible to indicate the number of value days to be added to the order date for the collection. These value days take into account the currency calendar. For example, if the payment document is presented on a Friday and if the check route is defined at four value days, the Thursday is proposed as default for settlement with the collecting bank in the Handling Checks business sector.
Furthermore, the agreement with the collecting bank usually defines the fee it is entitled to charge for collecting payment documents. This is a pass-through fee charged to the presenter when the checks are presented and directly deducted from the check amount, then credited to the collecting bank when the checks are sent or at later intervals. In many cases this is a unit fee charged for each check presented. This fee has to be set up in the definition of fees and marked as a check fee, so that the fee can be entered in the “Handling Check Presentation” transaction in the second settlement grid to be immediately debited to the presenter and at the same time marked as a credit for the collecting bank in the pool.
If the collecting bank does not have a direct account, a different account can be entered in the field “Default Account” that is then used to settle payment documents.
The field “Max. Number of Checks (per Remittance)” defines the maximum number of checks permitted to be pooled in a check remittance contract. If the maximum number is exceeded in the “Handling Check Presentation” or in the “Generate Remittance” transaction, an error message is generated, and the user must adjust the contract data before processing of the contract can be completed.
Datafield | Description |
---|---|
Currency | cf Appendix A, Table CRO field CUR |
Collecting Bank's Country Code | cf Appendix A, Table CRO field COLCTY |
Type of payment document | cf Appendix A, Table CRO field COD |
Alternate Technical Key of Associated Address | cf Appendix A, Table PTA field OBJKEY |
Name | cf Appendix A, Table PTA field NAM |
Value Days Defaulting | cf Appendix A, Table CRO field VALDAY |
Fee Code | cf Appendix A, Table FEE field COD |
External Key | cf Appendix A, Table ACT field EXTKEY |
Name | cf Appendix A, Table ACT field NAM |
Maximum Number of Checks per Remittance | cf Appendix A, Table CRO field MAXCHK |