Unbalanced Payment Events

The system, by default, distributes the sum of a payment event's tenders to the account that remits the tender with a single payment. After distribution the sum of the tenders equals the sum of the payments when the event is first created. We refer to such an event as being balanced.

However, it is possible for an event's tender amount to not equal the sum of the payment allocations (i.e., the event becomes unbalanced). How? Well, there are several ways this can happen:

• While the system DEFAULTS the payment amount to be the tender amount, you can override the payment amount and therefore make a previously balanced event unbalanced.

• While the system DEFAULTS the payment account to be the tender account, you can add additional accounts / amounts and therefore make a previously balanced event unbalanced.

• When you cancel a tender (e.g., because a check bounces), the system cancels ALL payments linked to the tender's payment event. If the payment event has multiple tenders, this will cause the event to become unbalanced. To correct this situation, you must add payment allocations to equal the amount of non-canceled tenders.

• If you cancel a payment and forget to add another payment for the same amount, the event becomes unbalanced. To correct this situation, you must add another payment (or cancel the tender).

• You may delete a tender from an event while its tender control is open. If you delete a tender and don't do anything about the related payments, the event becomes unbalanced.

• You may add a tender to an event at any time. If you don't allocate the tender amount to an account, the event becomes unbalanced.