• Payment sign (field SNS)

Only open items associated with a type of payment with this sense will be generated.

• Company (field CPY)

Only the open items for this company will be taken into account for the payment generation.
By default the user's company.

• Items from (field DATMIN)

Open items from: (1). to (2).
If a date range is entered, only the open items whose due dates are contained within this range will be taken into account for the payment generation.

Early discount until: (3).
If a date is entered, all the open items without early discount code and the open items with an early discount code lower than the entered date will be taken into account for the payment generation.

In a nutshell, if all the dates are entered, the following open items will be taken into account:

• the open items without early discount code meeting the dates (2) and (3)) and
• the open items with an early discount code included between the minimum date (1) and the maximum date ((2) or (3)).

• To (field DATMAX)

• Discounts up to (field DATDEP)

• Control group (field GRPSAC)

If entered, only the open items whose collective account belongs to this group will be taken into account for the payment generation.

• Control (field SAC)

Only the open items for this collective account will be taken into account for the payment generation.
If a BP type or a specific BP has been entered, it must be compatiblewith the collective account.

• Currency group (field GRPCUR)

If entered, only the open items whose currency belongs to this group will be taken into account for the payment generation.
In any case, the payment remains single-currency.

• Currency (field CUR)

If entered, only the open items for this currency will be taken into account for the payment generation.

• All transactions (field ALLTPY)

Select this check box to include all payment transactions. If not, the Transaction field is required.

When you select this check box, the Bank ID country, IBAN prefix, and Bank ID number columns display in the Details grid on the Payment proposal selection window. In this case, Bank ID number is required and the line is highlighted red if a mandatory field missing.

• Transaction (field TPY)

Enter a single transaction for automatic payment proposals. This field is available when the All transactions check box is not selected.

If the bank details are managed for the specific transaction, the Bank details country, IBAN prefix, and Bank acct. country columns display in the Details grid on the Payment proposal selection window. In this case, the bank account number is required and the line is highlighted red if a mandatory field is missing.

If bank details are not managed for the transaction, these three columns do not display in the Details grid.

Depending on the sign (Expense or Revenue), the payment transaction proposals vary (see the documentation the Payment transactions setup). If no transaction is selected, each payment is created on the first payment transaction found which refers to the payment mode.

A filter can be applied to the payment mode: only the invoices or open items showing the selected payment mode will be taken into account (as a reminder, the payment mode is defined using the payment condition).

Example 1:   

Data:
For 3 payment due dates (customer invoice open items):

• One of them, 30 days end of month (CHQ30JFM payment condition): 100 EUR
• The other, Check with immediate credit (CHQCPT payment condition): 100 EUR
• The last one Cash with immediate credit (VIRCPT payment condition): 100 EUR

The first two payment conditions are linked to the CHQ payment mode (Check). The last one is linked to the VIR payment mode (VIR for Transfer).

The CCHQ (Received checks) and CCHQR (Checks to cash) payment transactions use the CHQ payment mode.

Only the CVIR (Received transfers) payment transaction use the VIR payment mode.

Result:
On automatic payment proposal, if the Payment transactions and Payment method fields are not entered, the following payments are created:

• A payment of 200 EUR on the CCHQ payment transaction (1st transaction found with payment by check).
• A payment of 100 EUR on the CVIR payment transaction.

Various payments are generated for the invoice open items on statement (see the explanations on the specific processings).

Example 2:   

Data:
Same data as for Example 1. But the payment mode is specified: CHQ

Result:
A payment of 200 EUR is generated on the CCHQ payment transaction.

Example 3:   

Data:
Same data as for Example 1, but the CCHQR transaction is selected. Are only accepted open items by checks.

Result:
A payment of 200 EUR is generated on the CCHQR payment transaction.

Conclusion of the examples 1 and 2: the payment mode acts as a filter, either because it is a selection criterion (Example 2) or because, when it is associated with a transaction, it only authorizes open items involved by said payment mode (Example 3).

All validated invoice open items using the payment mode(s) linked to the payment transaction, and meeting the other selection conditions, are submitted for payment WITHIN THE SAME TRANSACTION.Exceptions must be managed either in the control grid (if the "Control" option is activated) or, if the case arises, directly upon payment entry.

Example 4: For 10 invoice open items having the check as the payment mode (CHQ), all are settled, but only two are placed in intermediate posting These two payments must be entered under the CCHQR transaction. It is then possible to launch the automatic payment proposal for the other open items, by specifying the CCHQ transaction. Another method (using the "Control" mode) consists in generating all the payments on the CCHQ transaction, then refining the obtained result by deselecting the two payments to be recorded as notes payable/receivable. It will then be possible to restart a campaign for the CCHQR transaction.

• All payment methods (field ALLPAM)

All payment modes or a particular payment mode.

• Payment method (field PAM)

Only the open items for this payment mode will be taken into account for the payment generation.
If a payment type has been entered, the entered payment mode must be authorized for this type of payment.

• All sites (field ALLFCY)

Select this check box to include all sites for the selected company.

• Site (field FCY)

Only the open items for this site will be taken into account for the payment generation.
By default the user's site.
This site must belong to thecompany that may have been entered previously.

• All BP types (field ALLTYPBPR)

All BP types or a specific BP.

• BP type (field TYPBPR)

Only the open items with this BP type will be taken into account for the payment generation.

• All BPs (field ALLBPR)

All BPs or a particular BP.
In any case, the payment remains single-BP.

• From BP (field BPRDEB)

The entered BP type must match the BP type that may have been entered previously.
Only the open items for this BP will be taken into account for the payment generation.

• To BP (field BPRFIN)

• All document types (field ALLTYP)

• Entry type (field TYP)

• All users (field ALLUSR)

• User (field USR)

• Prepayments (field INSFLG)

If yes, the pre-payment open items will also be taken into account for the payment generation.

• Maximum item (field DUDMNTMAX)

If entered, only the open items whose amount is lower than this amount will be taken into account for the payment generation.

• field CURDUDMAX

• Minimum payment (field PAYMNTMIN)

If this field is entered, only the payments in reporting currency with an amount greater than this amount are created. Caution, the payment amount depends on the selected payment options (for example: does the payment include all the open items on a single payment transaction? Does it have a range? Is it a payment by site, by open item, etc. ?)

• field CURPAYMIN

• Total maximum (field MNTMAX)

The proposal will be limited to this amount, expressed in reporting currency.

• field CURMNTMAX

• Bank (field BAN)

This field displays the bank to which the payments are assigned. The mentioned bank must necessarily be associated with the company for which the automatic payment proposal is activated.

The entry transaction of Payments determines if the information is mandatory or optional.

• Banking pool (field POO)

Bank allocation to which payments will be allocated. If neither a bank nor a bank allocation have been entered, and the bank is mandatory for a type of payment previously entered, entry of a bank of a bank allocation is requested.

• Application mode (field ALLMOD)

In the event of a maximum proposal amount, if the payments are allocated to a bank allocation, this specifies which priority should be given to the open items to be integrated to a payment. In the other cases, the priority is given to large amounts.

• One item/payment (field PAYDUD)

If yes, a payment will be generated by open item meeting the criteria.

• One due date / payment (field PAYDUDDAT)

If yes, the open items with the same due dates will be grouped together in a single payment.

• One control account / payment (field PAYSAC)

If yes:

• the customer pre-payment open items will be grouped together within a single payment.
• the supplier pre-payment open items will be grouped together within a single payment.
• the open items of journals with the same collective account will be grouped together within a single payment.

• One site / payment (field PAYFCY)

If yes, the open items with the same site will be grouped together in a single payment.

• Site (field FCYPAY)

Site of the generated payments. It must be compatible with the company, bank or bank allocation.

• Curr. (field CURPAY)

Optional field that is used to generated the payments in a specific currency.

• Control (field SACPAY)

Collective account of the generated payments. It must be compatible with the BP that may have been selected previously.

• Accounting date (field ACCDAT)

For the transactions with management by due date and whose first posting is the bank posting, payments are generated at the due dates. In the other cases, payments are generated at the date entered here.

• Remittance reference (field REF)

Note reference.

• Order (field ORDRE)

A log file is displayed at the end of the payment proposal. It draws up the list of the payments that are created or to be created in case of simulation.
In this list, payments can be displayed: 

• by BP code,
• by BP title,
• by payment transaction code
• by payment due date.

• Simulation (field SIM)

If yes, a text file is generated and it displays the list of the submitted payments.
If no, payments are generated.

• Control (field CTLFLG)