This section deals with the concept distributing a payment amount into payment(s). It does not discuss the distribution of a single payment into segments. For more information about payment distribution, refer to Distributing A Payment Amongst An Account's Obligations.
The base-package, by default, creates a single payment for a payment event. Some business practices require potentially many payments to be created when payment events are added.
A few examples of when multiple payments may be necessary are:
A payment amount needs to be distributed towards different distribution types:
$50 in interest
$60 in collection charges
$70 in taxes
Each of the above distributions is realized as a separate payment identified by its own match type (i.e., there will be one match type called Interest, another called Collection Charges, etc.).
In this example, the debt of a single obligation may be relieved by each of these payments.
In a similar way, you may want to create a separate payment for an overpayment to differentiate it from regular payments (using yet another match type).
In the case of a social service agency that pays for many accounts, a single payment event may be distributed amongst multiple accounts.
The method by which a payment amount is distributed to create payment(s) is contained in Create Payment algorithms plugged in on a distribution rule.
There is yet another aspect to having control over how payment events are created. The default method of creating payment events assumes knowledge of account IDs (of the payor and the payee) when making a payment. In cases where payments are made by and towards business entities other than accounts, knowledge of their corresponding account IDs may not be available at payment time. Consider the following examples:
A payment is made for a taxpayer. The payment is applied to all of the taxpayer's accounts.
A payment is made for a specific filing period.
A court-ordered payment is made for a case. The payment is directed toward the assessments linked to the case, where assessments may cross tax roles, filing periods, etc
A payment is made for a collections notice. The payment is directed toward specific assessments linked to the notice.
A payment is made for a pay plan. The payment is applied to the specific obligations that are covered by the pay plan.
The method by which the tender account is determined by means of an alternate identifier is contained in Determine Tender Account algorithm plugged in on a distribution rule.
Refer to Making Payments Using Distribution Rules for information on how to configure your system to use this distribution method.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.