Show TOC

 Creation of Open Items for Customer-Initiated Payment Form

Purpose

Enables the processing of payment plans with customer-initiated payment form, for which the incoming payments for the policyholder determine when and how open items, which are cleared with the previously received payment, are created.

Prerequisites

To enable the system to recognize customer-initiated payment form and process the corresponding incoming payments, you must make the following settings for the insurance relationship and the payment plan item:

  • Set the Reserve and record payments on account flag. This flag ensures that payments on account are recorded, and contain a clearing restriction.

  • Mark the payment plan item with the Payment plan item without posting category. This means that no open items are created when executing the Execute payment plans mass activity.

This ensures that no binding dates occur for the customer to make payment of certain (partial) amounts, which would lead to dunning notices if payment is not made on those dates.

Note Note

Also ensure that the payment plan item is not marked as a one-time payment ( One-time payment flag not set in PPI control).

End of the note.

Process Flow

The following activities are important for creating items:

  1. Execute Payment Plans function: SAP menu Start of the navigation path Insurance Next navigation step Collections/Disbursements Next navigation step Payment Plans End of the navigation path

  2. The Payment Lot function for posting incoming payments: SAP menu Start of the navigation path Insurance Next navigation step Collections/Disbursements Next navigation step Payments End of the navigation path

  3. Clearing Customer-Initiated Payments function: SAP menu Start of the navigation path Insurance Next navigation step Collections/Disbursements Next navigation step Payment Plans End of the navigation path

  4. The Execute payment plans function for creating items and for clearing

1. First debit entry (Execute payment plans)

In the result of the first debit entry, payment plan subitemsare created instead of open items, due to the attributes above. Depending on the payment plan key, these may be divided up into partial amounts with certain due dates and marked with document category 31. These installments and due dates have the same format as proposals.

2. Posting an incoming payment (Payment lot)

If an incoming payment is posted through the payment lot, the payment lot program will check whether the payment belongs to a policy with the Reserve and record payment on account indicator. If it does, the incoming payment document is given clearing restriction "U". This means that the payment is protected from being offset, and is written to the table VVSCRESPAYMENT.

The system also checks whether the incoming payment can be assigned to exactly one payment plan item. Unique assignment is possible if there is only one payment plan item for the insurance relationship.

Clearing customer-initiated payments

The events V055 and V056 run when the Customer-initiated payments clearing function is executed. Event V055 deals with the cases for which incoming payments were uniquely assigned to a payment plan item. Event V056 deals with those cases in which no unique assignment could be made.

In the sample module delivered for event V055 , the uniquely assigned incoming payments are processed further as follows: Payment plan subitems with document category 30 are set. The amount of this item is calculated on the basis of the incoming payment and the available variable payment plan subitems: The incoming payment is cleared on the oldest variable payment plan subitems.

If incoming payments cannot be uniquely assigned, clearing does not take place.

In event V056 , either the clarification worklist is filled or event V057 is called up, in which you can define whether in the incoming payment is to be distributed according to an algorithm key or made in an external system. You can process non-assignable incoming payments using a self-defined extension, or clarify them using the Customer-initiated payment assignment function available with Collections/Disbursements.

Note Note

You can make your decision in the Implementation Guide. Choose Start of the navigation path SAP Insurance Next navigation step Collections/Disbursements Next navigation step Basic Functions Next navigation step Activation of Basic Functions End of the navigation path .

End of the note.

In event V056, you can send information to the policy management system, for example, about a payment that has been received, but which could not be assigned uniquely to a payment plan subitem. The policy management system can then return payment plan items from document category 30 to Collections/Disbursements , once it has reached a decision regarding assignment. Items are created from this in the next debit entry and cleared against credit.

In the Customer-initiated payment assignment function, you can define how the incoming payment is distributed across the target premiums. In the SAP Easy Access Menu , choose Start of the navigation path Insurance Next navigation step Collections/Disbursements Next navigation step Payments Next navigation step Clarification Processing End of the navigation path .

All target premiums are displayed. The incoming payment is distributed to the oldest target premium as standard. You can distribute received payments fully to the payment plan items.

The document number for the incoming payment is entered as the reference document number in the variable payment plan subitems when saving.

Note Note

You can also use a clearing algorithm to distribute incoming payments that can not be assigned. In event V057, you can decide whether the incoming payment is distributed with an algorithm key, or if it is sent to the operational system.

End of the note.
3. Execute Payment Plans

Items are created from the payment plan subitems in this debit entry and cleared against credit.