Distributing A Payment Event

CAUTION:

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:

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.

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:

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.

Fastpath:

Refer to Making Payments Using Distribution Rules for information on how to configure your system to use this distribution method.