Person Level Payment Distribution

Oracle Revenue Management and Billing provides the ability to apply a payment to a person. The system will then distribute the payment amount against the unpaid bills of the person’s accounts and all its child persons’ accounts. This feature is only applicable for person’s and its child persons’ accounts that practice open item accounting. At present, the system supports the person level payment distribution only through the Payment Request feature and not through any other payment methods (such as, inbound web service, EDI 820, or payment upload). You can opt for the person level payment distribution while creating or transferring a payment through the Payment Request feature.

While creating a match type for the person level payment distribution, you must set the entity type of the match type to Person. A new algorithm type named C1-MD-PER is introduced in this releases.

It enables you to fetch all the open bills of the person and its child persons in the hierarchy. If the Invoice Type Characteristic Type and Invoice Type Characteristic Value parameters are defined in the algorithm, the system will retrieve open bills of only those accounts from the person hierarchy where the given characteristic is defined for the account with the respective value. However, if the Invoice Type Characteristic Type and Invoice Type Characteristic Value parameters are not defined in the algorithm, the system will retrieve all the open bills from the person hierarchy. In case you want to match payment against the accounts with different invoice types (i.e., Claims and Admin), you need to define two algorithms using the C1-MD-PER algorithm type with different invoice types (i.e., one with invoice type set to Claims and another with invoice type set to Admin) and then specify both the match types in the payment creation or transfer request. Note that there are few behavioral exceptions while using the person level payment distribution option:

  • You can use multiple match types in the payment creation or transfer request. But, while using the match type where the entity type is set Person, you cannot use any another match type where the entity type is set to Account or Bill. You are only allowed to use additional match types where the entity type is set Person.

  • Any excess amount is applied only to the payor account and not to each payee account.

  • Excess amount is distributed only when the payment is manually distributed by clicking either Distribute or Distribute and Freeze button and not when the payment creation or transfer request is created in the Draft status.

A new algorithm type named C1-DFT-EXS is introduced in this release. To use the person level payment distribution option in the Payment Request feature, you need to attach an algorithm created using the C1-DFT-EXS algorithm type to the Enter system event of the Distribute and Distribute And Freeze status (with highest sequence number) in the C1-PaymentRequest business object.

To implement this feature, the following changes are made to the system:

  • A new option type named Person Level Payment Characteristic Type is added to the C1-ADJ-PAY feature configuration.

  • A new option type named FK Reference for Account is added to the C1-PAYPORTAL feature configuration.

  • Two new algorithm types are introduced in this release - C1-MD-PER and C1-DFT-EXS.

  • Two existing algorithm types named C1-PAY-DFT and C1-PAYREQPOS are enhanced to validate whether all the match types specified in the payment creation or transfer request have entity type set to Person.

  • The C1-PAYCREATE algorithm type is enhanced to stamp person ID as a characteristic on the payment when it applied using a match type where the entity type is set to Person.

Note: You need to set the above-mentioned new option types in the C1-ADJ-PAY and C1-PAYPORTAL feature configurations. In addition, you need to add one more value named DST.UNPAID_​AMT for the Bill option type in the C1-PYREQSRT feature configuration.