Netting 

Use

Transactions from Money Market, Foreign Exchange and Derivatives can be brought together and paid collectively with Netting. Situations can arise where several transactions are to be paid collectively; this happens especially with transactions with business partners that are not house banks i.e they require the exchange of payments.

Example:

· Fixed-term deposit investment in DEM and fixed-term deposit borrowing in DEM

· You balance the open payment amounts and only pay or receive the net amounts

· Advantage: Saving of transaction costs and/or bank charges

For this purpose, transactions can be brought together in "Netting transactions".

Prerequisites

The transactions must be created in the same company code with the same business partner and in the same currency. They must also have the same value date and identical payment details.

Trigger for a netting transaction:

Activities

The "Netting/proposal list" report supports the selection of transactions that can be netted according to the criteria you have selected. You can process the netting transaction directly from the report and execute it. The allocation of individual transactions for netting means that payment requests are generated that come under one grouping key and are processed collectively in the enhanced payment program. This grouping key controls which payment requests will be separated from others. All payment requests involved in the same netting transaction receive the same unique grouping key and are, therefore, separated from other payment requests. They should not be grouped together with other requests. You cannot make retrospective changes to netting-relevant data in the individual transactions (especially due dates, amounts, house bank and payment data). A transaction linked to a netting transaction is shown as such when processed..

Features

Integration

Transactions linked by netting are referenced with each other via Object links (Reference key: KMP).