Role | Description | Usage as temporary address allowed? | Address Type | Stoplevel | Automatic copy of address from database contract allowed? | Only main address to be used? |
---|---|---|---|---|---|---|
BUY | Buyer | U | 3 | |||
SUP | Supplier | Y | P | 3 | ||
FND | Funding Institute | A | 3 | |||
OAP | Old Account Party | Z |
The buyer provides invoices that have to be financed to the supplier by the bank. The buyer is usually a customer of the bank and has to be available in the static data. A pairing definition must be set up for the buyer and the supplier in the static data. Any bookings will utilise the Buyer's Limit.
The supplier is the beneficiary of the payment under an approved payable finance. A pairing definition must be set up for the supplier and the buyer in the static data and also the account definition must be available, since the supplier is the payee of the payment. Thus, the supplier has to be defined in the static data of the bank using the application.
The Funding Institute (FND) is the party who is responsible to fund the buyer. The Funding Institute in most cases will be the DOKA bank (OWN) but it is possible that the Funding Institute of a dedicated buyer should be for example a branch of the bank. The Funding Institute entered in the party static data (DBxPTY) for the buyer will be used in subsequent APF offers/fundings.