Binder Payment Creation

Oracle Revenue Management and Billing considers a payment as a binder payment when a characteristic is defined for the payment using the characteristic type specified in the Binder Payment Identification Characteristics Type attribute of the binder payment preference. The system considers the binder payment preference which is specified in the Binder Payment Field Mapping option type of the C1-ASOBLLNG feature configuration. This type of characteristic must be defined when the binder payment is created. It stores the membership identifier to indicate the individual membership for which the binder payment is received.

You can create a binder payment through the following features or interfaces:

• Payment Web Service

• Payment Upload

• Payment Upload Staging

• Payment Request

• Payment Event

• EDI 820 File Upload

While creating a payment through any of the above mechanism except the latter one, you need to ensure that the binder payment identification characteristic is defined for the payment. However, in case of EDI 820 File Upload, the system will extract the data stored in the NM1 tag and store it in the payment characteristics staging table. This is done when the C1-PUPSG batch is executed.

You can view the binder payments received for the membership or financial responsible member person's account through the Payment Event Summary and Customer 360° Information screens.