Entering content frame

Procedure documentation Maintaining Details on Payment Transactions Locate the document in its SAP Library structure

Use

On this screen you maintain the payment transaction operations and the check types (check types only for banks).

Procedure

  1. In the section "Blocked functionalities", specify the functionality you wish to block.
  2. You must have maintained the blocking reasons in the (Implementation Guide) IMG by choosing Master data ® Account ® Blocking reasons. Any number of blocking reasons can be assigned to each account. A feature or a payment transaction operation can only be used for an account if this is allowed for the account product, and is not blocked by one of the blocking reasons for the account.

  3. Both the blocked functionalities and the available functionalities are displayed in the section "Functionalities". All existing features and payment transaction operations are always displayed. The following applies:
  4. Red traffic-light = blocked by a blocking reason

    Green traffic-light = assigned by the product

    No traffic-light = not assigned and not blocked.

    To obtain an overview of what is allowed for the account, choose the detail view for the account. See also: Account Blocks.

  5. In the section "Extended functionalities", specify whether the payee is allowed to collect receivables by means of collection authority and specify the dispatch type.
  6. The indicator "Agreement for collecting receivables with debit memos" shows whether the bank has an agreement for debit collection from the account holder. This means that the collection of debits and crediting to this account is possible (the indicator controls the appropriate check with payment transactions).

  7. (Only for banks): In the section "Check types", maintain check number issuing. The following applies:

In the account master record you can define special attributes for every check type possible for an account. These control the issuing of checks for the respective account.

This attribute means that every issued check is entered with a check number in the check (cheque) position table at the time of issue. The indicator is for organizational purposes only, meaning that the employee who issues the checks must enter the checks him/herself in the system. If the indicator is not set, both checks with numbers and checks without numbers can be issued.

This attribute means that every check presented for debit by payment transactions that does not have one of the check numbers existing in check management must be entered in the check position table. Sensibly, this indicator can only be set, if issuing checks without numbers is allowed, meaning that the indicator number on issue is not set.

Both indicators control

  1. the entering of the check numbers in check management both at the time of issue and when cashed.
  2. the checking of the check numbers for check debits for incoming payment transactions and the handling of check numbers not entered.

The checks within payment transactions take place as follows:

You receive a check (cheque) debit with check (cheque) number. The system checks if the check (cheque) number already exists in check (cheque) management.

If this is not the case, the next check is to see if it is possible to issue checks without being entered in the check table (and so without a number issued by the bank). This would mean that the indicator number on issue is not set.

If this is the case, the check can be cashed. Additionally, the system checks if the cashed check is to be transferred to the check table (meaning the indicator number on presentation is set). If this is the case, the check is transferred to check management with check number and the status cashed.

Result

The payment transaction data has been maintained.

 

 

Leaving content frame