Ansicht
Dokumentation

VC_FARP_PAYT_RSN - Define Payment Reasons

General Data in Customer Master   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Allows you to define payment reasons and assign purpose codes to group payment transactions.

In this activity, you define reasons for your payments to classify the type of the payment transaction, such as salary payment, purchase of goods, purchase of services, and so on that you transfer from one bank to the other. The payment reason identifies the payment according to the regulatory reporting requirements of your bank or the local authorities. Two different codes can be sent (for example, one on credit and one debit side). You can specify the combination of the payment reason and the payment reason codes in this activity. The maximum character limit is 70 characters (35 characters for each code).

When you create an invoice, or you post a document to a business partner, you can enter the payment reason.

During the payment run, the payment reason is transferred from the invoice using the Manage Automatic Payments app and based on the mapping specified in the Map Payment Format Data configuration activity, it is inserted in the payment medium.

Enter data as follows:

On the Payment Reason Definitionsscreen, enter a 4-character long payment reason that can be used during the payment processing to identify the payment type, and describe the payment reason, according to legal requirements in your country/region.

Example:

• 0001,,Purchase of Goods

• 0002,,Salary Payment

Select a row and double-click the Payment Reason Code Combinationsscreen. On this screen, assign data as follows to the selected payment reason code:

1. Choose an application area you entered in the payment medium format you are going to use.

The application area is assigned to each payment medium format in the Map Payment Format Data configuration activity. You can (re)define it in your custom payment formats in the app.

1. Assign the payment reason to the application area.
2. Specify the two-character ISO code of the sender and receiver bank's country/region as follows:

• You enter the ISO code of both the sender and the receiver bank. This means that for each payment transferred from then sender bank (in the specified country/region) to the receiver bank (in the specified country/region) the purpose codes are inserted. The sender and receiver bank's country/region can be the same.

Example:

You want to transfer payments from the bank in SK to a bank in DE because both banks require a special set of purpose codes. To identify the payment, the sender and the receiver bank requires different purpose codes. You enter the necessary purpose codes in the Purpose Code of Sender Bank and Purpose Code of Receiver Bank fields in this activity.

• You enter the ISO code of only the sender bank. This means that for each payment transferred from then sender bank (in the specified country/region) to the receiver bank (in any country/region, including domestic payments) the entered purpose codes are inserted.

Example:

You want to transfer payments from the bank in SK to any bank in any country/region because the bank in SK requires a special set of purpose codes. To identify the payment, you enter the purpose codes required by the sender bank in the Purpose Code of Sender Bank field in this activity. The purpose codes are used for each payment from the sender bank to any receiver bank in any country/region.

• You enter the ISO code of only the receiver bank. This means that for each payment transferred from any sender bank to the receiver bank (in the specified country/region), the entered purpose codes are inserted.

Example:

You want to transfer payments from any bank to a bank in DE because the bank in DE requires a special set of purpose codes. To identify the payment, you enter the purpose codes required by the receiver bank in the Purpose Code of Sender Bank and Purpose Code of Receiver Bank fields in this activity. The purpose codes are used for each payment from any sender bank to the receiver bank.

When an invoice is created and the payment file is generated, these code combinations are called using the following priority order:

1. The system searches for assignments of both the sender and the receiver bank.
2. If no entry found, then the system searches for entries of the sender bank.
3. If no entry found, then the system searches for entries of the receiver bank.

Enter the purpose code of the sender and/or receiver bank as follows:

You can enter any of the codes or both of them in all cases. You can also combine both codes into a string that can be up to 70 characters long.

ROGBILLS - Synchronize billing plans   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5855 Date: 20240523 Time: 154441     sap01-206 ( 128 ms )