Explaining the Customer-Initiated Payment Lot

Objective

After completing this lesson, you will be able to explain the customer-initiated payment lot

Payment Lot

The figure highlights the steps in the process step of open item management for customer-initiated payments.

Customer-initiated payments are initiated by the customer because the customer determines when he wants to pay his debts to the company.

Customer-initiated payments are only incoming payments.

Incoming payments that can be assigned to an open item, clear that item as much as possible either by full payment, partial payment, or overpayment. Most of the open items are cleared automatically via the flexible and configurable clearing control.

Incoming payments that can't be assigned to an open item, are placed in the clarification list to be reviewed. From there, you can further process the payment either by posting it to an interim account (if the contract account cannot be found) or on account (if the contract account can be found, but not the open item) or by triggering a repayment.

The clarification processing is explained in the respective lesson of this unit.

Customer-initiated payments are processed by payment lots, check lots or, the cash journal.

The figure visualizes the steps in payment lot processing.

The check lot and payment lot store incoming payments that have a common origin and that should be processed together.

The check lot must be processed manually because checks only exist in written form.

The payment lot is processed manually, if the payment information exists in written form.

The payment lot is processed automatically, if the payments are uploaded from an electronic bank statement file (see next figure).

The payment lot can only be posted after it has been closed. The posting either transfers the payments to individual contract accounts (if payment assignment is successful) or to a clarification account (if payment assignment is not successful). Payment differences are automatically posted to special profit and loss accounts in the general ledger.

The figure illustrates the payment lot creation from a bank statement, using the SAP Fiori apps Upload Bank Statement and Transfer Account Statement.

The SAP Fiori App Upload Bank Statement is used to upload the bank statement file into the bank data memory.

The SAP Fiori App Transfer Account Statement is used to transfer the data from the bank data memory directly to a payment lot or returns lot.

The returns lot is explained in lesson 2 of this unit.

The figure illustrates the payment lot posting logic, as described in the following.

The posting logic of the payment lot is as follows:

  1. The receivable posting in contract accounting creates - after reconciliation key transfer - a posting on the general ledger's receivable-, revenue and tax account.
  2. The incoming bank statement in general ledger accounting post the incoming payment against the bank clearing account and creates a payment lot when it is uploaded.
  3. The payment lot processing for incoming payments in contract accounting distributes all payments of the lot to clear the open items in contract accounting and - after reconciliation key transfer - in the general ledger's receivable account as well.

Log in to track your progress & complete quizzes