Partial Payment Transfer through Payment Request

While creating a payment transfer request from the Payment Event Summary screen, the system calculates and displays the maximum transfer amount when you transfer one or more payments or all payments of a payment event. The maximum transfer amount is set either to the sum of all frozen payments in the payment event or to the sum of one or more selected payments depending on whether payment transfer is done at the payment event or payment level. Note that the system considers only the positive payments which are in the Frozen status while calculating the maximum transfer amount. All negative payments irrespective of the status and the positive payments which are in the Canceled status are not considered while calculating the maximum transfer amount. By default, the transfer amount is set to the maximum transfer amount. If you want to do a partial payment transfer, you can change the transfer amount. Note that if the payment is negative or maximum transfer amount is zero, then the Transfer Amount field is non-editable. Also, note that the payment transfer amount cannot be more than the maximum transfer amount.

While creating a partial payment transfer request, the system fetches the list of frozen payments depending on whether payment transfer is done at the payment event or payment level. If you partially transfer a single payment through a payment transfer request, the system does the following on the processing the payment transfer request:

• Cancels the old payment

• Creates two new payments in the Frozen status - one with the transfer amount using the specified match type and another with the remaining amount using the match type of the old payment

For example, the P1 payment is created against the contract of the A1 account, as shown in the following table:

Now, when you partially transfer $150 of payment using the match type as Bill from the A1 to A2 account, the system will cancel the old payment and create the new payments as shown in the following table:

If you partially transfer more than one payment or all payments of a payment event through a payment transfer request, the system identifies the payments which are eligible for transfer from the payment list in the following manner:

1. If the payments are created against the contracts, the system considers the following option types of the C1_​CMO feature configuration to determine the payments which are eligible for transfer from the payment list:

   • Suspense Contract Type

   • On Account Contract Type

   • Excess Credit Contract Type

   For more information about the C1_​CMO feature configuration, see Setting the C1_​CMO Feature Configuration.

2. However, if the payments are created against the bills, the system considers the bill date and bill amount to determine the payments which are eligible for transfer from the payment list.

The payments which are eligible for transfer from the payment list are added in the C1_​PAY_​DETAILS table. The system stamps the transfer priority corresponding to eligible payments in the TRANSFER_​PRIORITY column of the C1_​PAY_​DETAILS table. The system assigns transfer priority to each eligible payment in the following sequence:

1. Considers payments against the contracts which are created using the contract type specified in the Suspense Contract Type option type of the C1_​CMO feature configuration. If there are multiple payments which are created on the suspense contracts, the system assigns the same transfer priority to these payments. For example, if you partially transfer P1 and P2 from the A1 account to the A2 account through a payment transfer request where P1 is created against C1, P2 is created against C2, and C1 and C2 are both suspense contracts, then the system sets the transfer priority of P1 and P2 to 1 in the payment transfer request.

2. Considers payments against the contracts which are created using the contract type specified in the On Account Contract Type option type of the C1_​CMO feature configuration. For example, if you partially transfer P1 and P2 from the A1 account to the A2 account through a payment transfer request where P1 is created against C1, P2 is created against C2, C1 is a suspense contract, and C2 is an on account contract, then the system sets the transfer priority of P1 to 1 and P2 to 2 in the payment transfer request. However, if you partially transfer P3 from the A1 account to the A2 account through a payment transfer request where P3 is created against C3 and C3 is an on account contract, then the system sets the transfer priority of P3 to 1 in the payment transfer request. If there are multiple payments on the on account contracts, the system assigns the same transfer priority to these payments. For example, if you partially transfer P1, P2, and P3 from the A1 account to the A2 account through a payment transfer request where P1 is created against C1, P2 is created against C2, P3 is created against C3, C1 is a suspense contract, and C2 and C3 are both on account contracts, then the system sets the transfer priority of P1 to 1 and P2 and P3 to 2 in the payment transfer request.

3. Considers payments against the contracts which are created using the contract type specified in the Excess Credit Contract Type option type of the C1_​CMO feature configuration. For example, if you partially transfer P1 and P2 from the A1 account to the A2 account through a payment transfer request where P1 is created against C1, P2 is created against C2, C1 is an on account contract, and C2 is an excess credit contract, then the system sets the transfer priority of P1 to 1 and P2 to 2 in the payment transfer request. However, if you partially transfer P3 from the A1 account to the A2 account through a payment transfer request where P3 is created against C3 and C3 is an excess credit contract, then the system sets the transfer priority of P3 to 1 in the payment transfer request. If there are multiple payments on the excess credit contracts, the system assigns the same transfer priority to these payments. For example, if you partially transfer P1, P2, and P3 from the A1 account to the A2 account through a payment transfer request where P1 is created against C1, P2 is created against C2, P3 is created against C3, C1 is a suspense contract, and C2 and C3 are both excess credit contracts, then the system sets the transfer priority of P1 to 1 and P2 and P3 to 2 in the payment transfer request.

4. Considers payments created against the bills in the descending order of the bill date (i.e. bill with the latest date). If there are multiple payments which are created against the bills having the same bill date, the system considers the payments which are created against the bills in the descending order of the bill amount (i.e. bill with the highest amount). However, if there are multiple payments which are created against the bills having the same bill date and bill amount, the system assigns the same transfer priority to these payments. For example, if you partially transfer P1, P2, P3, and P4 from the A1 account to the A2 account through a payment transfer request where P1 is created against B1 (with the bill date 01-Jan-2020 and bill amount $100), P2 is created against B2 (with the bill date 01-Feb-2022 and bill amount $20), P3 is created against B3 (with the bill date 01-Mar-2022 and bill amount $30), and P4 is created against B4 (with the bill date as 01-Mar-2022 and bill amount $40), the system sets the transfer priority of P4 to 1, P3 to 2, P2 to 3, and P1 to 4, respectively, in the payment transfer request.

5. Considers payments which are created against entities other than contracts or bills and assigns the same transfer priority to these payments.

In addition, the system sets the PY_​CANCEL_​SW column corresponding the payments in the C1_​PAY_​DETAILS table to Y or N depending on whether these eligible payments are considered for transfer or not. Let us assume that the following payments are made to the A1 account through the PE1 payment event:

And, let us assume that the Suspense Contract Type, On Account Contract Type, and Excess Credit Contract Type option types of the C1_​CMO feature configuration are set to CT1, CT5, and CT4, respectively.

Now, if you want to partially transfer $450 of payment from the A1 account to the A2 account using the match type as Bill, the system considers the following payments for transfer from the payment list using the given transfer priority:

In above example, the system does not consider the P12 payment for transfer even if it is eligible for transfer simply because the transfer amount is exhausted.

If the remaining transfer amount is greater than zero after considering frozen payments against the above mentioned contracts and bills of the account, the system will randomly consider other payments from the payment list which are created against entities other than the above mentioned contracts and bills of the account and assign the same transfer priority to all such payments.

Once the system identifies the payments eligible for transfer from the payment list, the payment transfer request is created in the Draft status. In other words, the BO_​STATUS_​CD column corresponding to the payment transfer request in the C1_​PAY_​REQ table is set to DRAFT.

The system enables you to edit the transfer amount in the Draft status. You can change the transfer amount using the Update Transfer Amount button in the Record Actions section of the Payment Request screen. On clicking the Update Transfer Amount button, the Update Transfer Amount screen appears where you can change the transfer amount, if required. Note that the updated transfer amount should not be more than the maximum transfer amount. On changing the transfer amount, the system determines the payments which are eligible for transfer once again from the payment list.

You have an option to set the defer payment processing count while defining a payment request type. It is used to determine whether the payments which are eligible for transfer should be derived immediately at the runtime or in the deferred mode (i.e. when the C1-PAYTR batch is executed) from the payment list. You can set this field only when the Transfer option is selected while defining a payment request type. If you do not specify any value in the Defer Payment Processing Count field, the system, by default, sets it to 25.

While creating a payment transfer request or while updating the payment transfer amount in a payment transfer request, the system checks whether the number of payments in the payment list is less than or equal to the value specified in the Defer Payment Processing Count field of the respective payment request type. If the number of payments is less than or equal to the defer payment processing count, the system determines the payments which are eligible for transfer from the payment list immediately at the runtime. However, if the number of payments is greater than the defer payment processing count, the system determines the payments which are eligible for transfer from the payment list in the deferred mode. The status of the payment transfer request is then set to Payment Derivation Pending.

On executing the C1-PAYTR batch, the system checks whether there are any payment transfer requests in the Payment Derivation Pending status. If there are any payment transfer requests in the Payment Derivation Pending status, the system identifies the payments which are eligible for transfer from the payment list of the payment transfer request in the following manner:

1. If the payments are created against the contracts, the system considers the following option types of the C1_​CMO feature configuration to determine the payments which are eligible for transfer from the payment list:

   • Suspense Contract Type

   • On Account Contract Type

   • Excess Credit Contract Type

   For more information about the C1_​CMO feature configuration, see Setting the C1_​CMO Feature Configuration.

2. However, if the payments are created against the bills, the system considers the bill date and bill amount to determine the payments which are eligible for transfer from the payment list.

The payments which are eligible for transfer from the payment list are added in the C1_​PAY_​DETAILS table. The system stamps the transfer priority corresponding to eligible payments in the TRANSFER_​PRIORITY column of the C1_​PAY_​DETAILS table. The system assigns transfer priority to each eligible payment in the above mentioned sequence. Finally, the system changes the status of the payment transfer request from Payment Derivation Pending to Draft. For more information about the batch, refer to Oracle Revenue Management and Billing Batch Guide.

On processing the partial payment transfer request, the system will cancel all payments which are transferred and then create new payments using the match type specified in the payment transfer request. Here, the status of the old payments is changed to Canceled and the status of the new payments is set to Frozen. In addition, if there is a remaining balance on any payment which is considered for transfer, the system will create a new payment for the remaining amount using the match type which is specified in the old payment. The payment for the remaining amount is created in the Frozen status. In the above example, the system will cancel the old payments and create the new payments, as shown in the following table: