Show TOC

 Payments by Payment Card

Use

In the payment run you can also pay open items with payment cards.

Prerequisites

For the payment of open items, you either:

  • Entered the card data in the master data of the business partners, and in the payment data in the master records of the contract accounts, you referenced a card entered in the master data (similar to bank details for incoming payments)

  • Entered the card data in the item in the document

    Note Note

    When you enter card data in the master data of the business partner, the system carries out a formal check to determine the validity of the card number (check digit procedure). There is, however, no authentication. There is also no authentication in the payment run.

    End of the note.

Or you entered a payment card for one-time use on the receivable.

You have also made the following system settings:

  • You indicated at least one payment method as a payment method for payment cards see Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Payments Next navigation step Incoming/Outgoing Payment Creation Next navigation step Payment Method End of the navigation path.

  • You entered the data of the payment card institute and check rules for cards in Customizing for SAP Business Partner under Start of the navigation path Cross Application Components Next navigation step SAP End of the navigation path - Start of the navigation path Business Partner Next navigation step Basic Settings Next navigation step Payment Cards End of the navigation path.

  • You defined the specifications for posting the settlement document in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Payments Next navigation step Incoming/Outgoing Payment Creation Next navigation step Payment Cards End of the navigation path.

  • For each payment card company, you created two G/L accounts and defined them in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Payments Next navigation step Incoming/Outgoing Payment Creation Next navigation step Payment Cards End of the navigation path:

    • A receivables account (receivables to be reported to the institute), called reporting account below

    • A clearing account for receivables reported to the institute

  • For online billing, you executed the Prepare Parallel Processing for Payment Card Data activity (in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Program Enhancements Next navigation step Prepared Enhancements End of the navigation path) and thereby included the Subarea (KEYPP) in the payment card data table (DFKKOPKC).

For more information, see SAP Note 520124.

Features

When receivables are paid with payment cards in the payment run, receivables due to the payment card institution arise. If the payment run has completed processing, you have to report and transfer the receivables arising to the instruction in a subsequent billing run.

On the SAP Easy Access screen under Start of the navigation path Periodic Processing Next navigation step Data for Externals Next navigation step Payment Card Organizations End of the navigation path, you can use the following functions:

Function

Use

Settlement

Billing of data from a payment run or items to payment card institutes.The program creates a file with the selected payments and transfers the items from the receivables account to the clearing account. You can repeat the billing. Items to be billed are items in a receivables account (report account) still to be reported to a payment card institute. Billed items are items in the clearing account that have already been reported. This is the offsetting account for the incoming payment, so the balance of this account is then zero. See the report documentation for further information. Choose the ( Program Documentation ) pushbutton.

Parallel Billing by Direct Call

Parallel processing of payment card payments (as a mass activity). This billing variant does not create a file. Instead, if you define event 1421 for your specific needs, this function allows online billing with immediate return of the results (a message stating whether billing was successful or not). In event 1421, the payments to be billed are grouped by payment card company, company code, agent ID, currency, and value date. This means that the event is called individually for each one of these groups. The system stores any error messages. You can display error messages in the document display for the payment document. The mass activity can select payments with errors, in addition to the payments for billing. These payments with errors are payments for which billing was unsuccessful during the last attempt.

The system stores the results of the billing run in the existing log tables under the ID of the mass activity.

The parallel processing object for this mass activity is the Subarea (KEYPP) field that you added to the payment card data table (DFKKOPKC) (see Prerequisites).

Display Data Media

Display of the contents of the generated data medium (only for billing by file)

List of Payments

List of payments that were billed

List of Bills

List of the invoices paid with the billed payments

List of Card Data

List of all business partners with card data

Using the function Delete Logs (SAP Easy Access screen: Start of the navigation path Periodic Processing Next navigation step Delete Data Next navigation step Payment Card Billing End of the navigation path), you can delete old billing logs.

The following enhancements for the parallel billing of payment card data (transaction FPCS) are now available in Contract Accounts Receivable and Payable:

Classification of non-billable items as containing errors without further processing

At event 1421 (parallel billing of payment cards) used for online billing, you can designate payments as irretrievably non-billable in the new field FINAL_ERROR. An attempt at processing again using transaction FPCS is not permitted, this means a repetition run for such items is not possible.

Automatic return posting of non-billable payments

For payments that were classified as irretrievably non-billable (for example: a credit card had been stolen), a returns lot can be created automatically and posted. This takes place after the most recent interval at event 1799. You can find the related settings in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Payments Next navigation step Incoming/Outgoing Payment Creation Next navigation step Payment Cards Next navigation step Define Specifications for Automatic Returns Posting End of the navigation path. The returns posting for a FPCS run can be repeated using the report RFKKPCDS_RETURN_LOT. You can also access the report using the environment menu in transaction FPCS: Start of the navigation path Environment Next navigation step Create Returns End of the navigation path.

Charge posting for successfully billed payments

At event 1421 (parallel billing of payment cards), charges can be returned for successfully billed payments in the new field CS_CCFAM that were levied by the credit card institute for successful billing. These charges are posted to a separate expense account and automatically deducted from the clearing account of the credit card institute. In this way, the expected incoming payment from the credit card institute is reduced. You can find the related settings in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Business Transactions Next navigation step Payments Next navigation step Incoming/Outgoing Payment Creation Next navigation step Payment Cards Next navigation step Define Specification for Charge Posting End of the navigation path.

Exclusion of payments from processing

At the new event 1425, selected payments can be excluded from further processing.

Activities

Payment run

In the selection parameters of the payment run, specify a payment method that is designated for processing receivables with payment cards. If necessary, you can restrict the selection to one payment card type and thus process each payment card type in a separate payment run; the payment method of the category Card Payment used is the same for every run. If the processing in a payment run takes place only for one specific payment card type, the program creates a corresponding message in the application log and a payment exception for contract accounts where other payment card types are defined.

A bank selection is not necessary for this payment method since there are no transfer postings to bank accounts. The payment program clears the open items and creates open items in the receivables account (reporting account) of the payment card institute.

Functions in Document Display

In the document display, you can display payment card data by choosing Start of the navigation path Extras Next navigation step Payment Card Supplement End of the navigation path.

Enhancement

You can add the format of the payment media in the following events:

Event

What it means

1410

Payment cards: File Header

1411

Payment cards: Payment file

1412

Payment card: Paid item file

For more information see the documentation for the sample modules defined for the events specified in Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Program Enhancements Next navigation step Define Customer-Specific Function Modules End of the navigation path.