Initially, the build program generates payments by combining invoices/credit memos that have the same:

Supplier ID

Supplier Site ID

Due Date (if Group by Due Date is selected)

Payment Category Code

Product Group/Article No

Nature of Payment

If there are negative payments, the system tries to combine invoices for one Supplier Site. That will happen if:

Group by Due Date is not enabled.

Payment Separation at Application level is No or Overrule Payment Separation at Application Level is Yes.

More then one payment for the Supplier Site is not Pay Alone and is valid.

Set the Overrule Payment Separation profile option to Yes to override the Payment Separation profile for negative payments only. You can then generate payment separation as standard by setting the application option to Yes, but you can also instruct the system to combine payments so as to avoid negative payments.

If you configure the system as described, the system combines all payments for one Supplier and Supplier Site when the resulting payment is positive. If summing all payments for one Supplier Site still produces a negative payment, the payments generated by the initial stage remain in place.

After payments are combined to achieve a positive result for Foreign Payments, the information in the additional invoice information for Payment Category Code, Product Group, and Nature of Payment may not be unique across all invoice/credit. This is only an issue if the payment exceeds 25,000 NLG. If so, the details of the payment must be forwarded to the Dutch National Bank.

An extra check is performed during validation: If a payment exceeds 25,000 NLG, all invoices that comprise the payment must have identical values for the additional invoice data. If this is not true, the payment is invalidated and the reason is reported.