Payment Proposals - Implementation

Prerequisites

Activity codes

The following activity codes (sorted by type) may have an impact on the way the function operates :

 VII : International transfers

General parameters

The following general parameters may change the way the function is working :

Payroll-X3P

 AMTVIR1 (defined at level Company) : Threshold 1 payment balance

 AMTVIR2 (defined at level Company) : Threshold 2 payment balance

 AMTVIR3 (defined at level Company) : Threshold 3 PB countervalue

Common Data

 CTLPAZ (defined at level User) : Pay approval control

 DEPMGTMOD (defined at level Company) : Discount management mode

 FLGPAZ (defined at level Site) : Payment approval management

Acc Payable/Acc Receivable

 BIDBPENT (defined at level User) : Authorize bank acct. no. entry

 BIDPAYENT (defined at level User) : Authorize bank acct. no. entry

 DATDEP (defined at level Company) : Date for the calc of discounts

 DENCRG (defined at level Company) : Late charge payment attribute

 DENDEP (defined at level Company) : Customer early paymt./discount

 DENINSRCP (defined at level Company) : Prepayment rec accounting code

 DENINSSEN (defined at level Company) : Prepayment iss accounting code

 DENPAY (defined at level Company) : Supplier early paymt./discount

 DENSPG (defined at level Company) : Payment exp accounting code

 DENTAK (defined at level Company) : Payment rec accounting code

 DEPDUDDAT (defined at level Company) : Due dates in discount section

 PAYUNALL (defined at level Company) : Unalloc. payments considered

 PPYCONSCTL (defined at level Company) : Prepayment control

 SOICPT (defined at level Company) : Statement posting

Sequence numbers

The sequence numbers used to number the documents managed by this function are :

 PY1 : Payment Receipts

 PYL : Payment Lot

The sequence number assignment function defines the sequence number which is used

Authorizations

An authorization can be granted for this function to limit the processes to a company or a site.

Miscellaneous prerequisites

Miscellaneous tables

The following miscellaneous tables are used by the function. They must be populated if necessary :

 Miscellaneous table number 3 : Unpaid reason

 Miscellaneous table number 313 : SEPA - Payment nature

Payment transaction

The payment transaction is a grouping key of the payments based on the sense of these payments and their payment mode (miscellaneous table no. 3: Checks, Drafts, Transfers, etc.).

For a payment transaction, x linked payment modes are defined. These links are used to match the open items on the invoice posted upon payment transaction (see the documentation Payment conditions).

The set up of these payment transactions (see the documentation Payment transactions) makes it possible to define:

• The payment entry screens, the mandatory fields (e.g.: entry of Bank Yes/No; mandatory Yes/No)
• The posting and grouping steps. For example, this is the level at which it is determined whether the payment transaction will be managed as an automatic payment proposal.

Whatever the payment transaction, when a payment is automatically generated through the automatic proposal, it is included in an entry batch. This facilitates the transaction tracking and management and also corresponds to a milestone for selection during the management of the next phases.
Depending on the payment transaction setup, the batch number and content can be displayed and adjusted.
It is possible to integrate the user code to the counter using the Complement field.

Bank account/Bank allocations

For each company, and possibly for each site, it is necessary to define the linked bank(s) (refer to the documentation on Bank account and Bank allocations).

Tables used

The following tables are implemented by the function :