Payment terms

• Payment term (field PTE)

Code associated by default with the current BP, used to define the payment conditions.
This code defines the payment method, open item type, as well as the payment schedule (one or several open items cash, 30 days, end of month etc.).
When managing this table, it is possible to simulate the calculation rules that will be applied in entry mode.

• Legislation (field LEG)

In creation mode, the legislation code can be initialized via the user parameter LEGFIL - Legislation (selection filter) (SUP chapter, INT group). This parameter is also used to filter the selection panel in order to present only the codes defined for this legislation and those defined at the All legislations level.
If a legislation is entered, the payment condition can only be used on documents associated to the companies set up with this legislation.
 For further information, refer to the documentation on general principles linked to the multi-legislation setup.

Notes:

• If a legislation is specified, only payment methods defined for this legislation can be associated to this payment condition.
• If no legislation is specified, only the payment methods defined as All legislations can be associated to this payment condition.

• Description (field DESAXX)

This long description is used as a title in screens and reports.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Short description (field SHOAXX)

Short title used in the screens and reports. This title is recorded in your connection language.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Group (field GFY)

By entering a company group, you can limit the scope to companies in the selected group only. When this data is used for another record or with a setup element also defined in the group, a control checks that the groups have at least one company in common when the groups are different.  

In addition, a consistency check is performed for the legislations of the companies in the selected group.
At least one of these companies must have the same legislation as the one entered in the Legislation field. If  not, a warning message displays.

If a group is entered, the payment condition can only be used on documents associated to the companies of this group.
There is a control to check the coherence between the legislation/group specified for the payment condition and the legislation/group of the document.
 For further information, refer to the documentation on general principles linked to the multi-legislation setup.

Peculiarity linked to the use of a payment condition in the Customer BP and Supplier BP setup:
Using a payment condition in the BP/Companies setup is only possible if the group indicated on the payment condition matches the group to which the BP company belongs. The All groups notion is not taken into account.

Note:

• If a group is specified, only payment methods defined for this group can be associated to this payment condition.
• If no group is specified, only the payment methods defined in All groups can be associated to this payment condition.

• No. (field PTELIN)

• Method (field PAM)

The payment method defines the payment means (check, cash, bank card, instrument etc.).

• SEPA (field TAMSDDFLG)

This indicator is automatically activated when at least one of the payment methods is SEPA-type.

• Due date % (field DUDPRC)

Specify, for each open item line to calculate, the part of the tax inc. amount of the document that has to be assigned to this open item line. This proportion is expressed in percentage. If there is only one open item to calculate, enter 100% in this field.

• Sales tax % (field VATPRC)

• If the activity code TPT - Payment conditions with VAT is active, the column Sales tax % is displayed in addition to the column Due date % .
  If the payment is of the Prepayment type and if the Sales tax % field has for value 0, the calculation of the automatically generated prepayment will be based on the excluding tax amount of the order.
  If the payment is of the Prepayment type and if the Sales tax % field has for value 100, the calculation of the automatically generated prepayment will be based on the tax-including amount of the order.
• If this TPT activity code is not active, only the column Due date % is displayed.
  The calculation of the automatically generated prepayment is based on the tax-including amount of the order.
  

• Payment type (field PAMTYP)

Specify the open item payment type.

Prepayment

The open items are paid before the invoice is issued.

Open item

The open items are paid on the invoice issue date.

Holdback

The invoice is considered as closed, although no payment has been made. No specific set of accounting entries is triggered.

• Months (field NBRMON)

Specify the number of months to be added to the start date during the due date calculation so to determine the due date.
For example, the following results will be obtained with a time-lag equal to 1 month:

• 15/12/1997 + 1 month = 15/01/1998 (31 days month)
• 30/06/1998 + 1 month = 30/07/1998 (30 days month)
• 30/01/1998 + 1 month = 28/02/1998 (28 days month)

• Days (field NBRDAY)

Specify the number of days to be added to the start date during the due date calculation so to determine the due date.
It is the exact number of days.

• Month end (field ENDMONFLG)

The three values for this field are:

No

The flag is not taken into account.

End of next month:

The due date calculated after applying the number of months and days is postponed until a month end (ex: 45 days and on month end).

End of current month:

The due date start is postponed up to the end of month first and then the additional number of months and days are applied to determine the final due date (ex: End of month and 45 days).

• Day 1 (field J1)

The value entered must be a date in the month (between 1 and 30) or 99 which corresponds to the last day of the month.
The use of this date is used to automatically postpone the due date calculated up to the nearest day of the month.
There can be up to 6 days on a same scheduled invoice line.

• Day 2 (field J2)

• Day 3 (field J3)

• Day 4 (field J4)

• Day 5 (field J5)

• Day 6 (field J6)

• Minimum due date amount (field DUDMINAMT)

Specify the minimum amount for this open item.
If the amount is not reached the concerned open item date is postponed to the following due date.

• Currency (field AFFCURDUD)

• SDD management (field SDDFLG)

The management of this field is subject to the activity code SDD - SDD management.
This flag cannot be entered. It is automatically activated when at least one of the payment methods is SEPA-type.

• Alt. payment terms (field RPLPTE)

Specify the code of the payment term to be used when the total amount of the journal entry is lower that a given threshold.

A substitute payment method applies if the total payment amount is lower than the threshold. This is a cascading process: for example, a payment by draft is replaced with a payment by check when the amount is below the threshold, and then replaced with a payment in cash if the amount is even lower.

• If amount less than (field PTEMINAMT)

Minimum amount under which the conditions of replacement payment are used.
This value is only entered when the condition of replacement payment has been entered.

• field AFFCUR

• Holidays excluded (field FBDHLYFLG)

Specify if the due date calculated can correspond to a bank holiday. If the due date calculated corresponds to a forbidden day, the due date is systematically postponed to the next authorized day. This check is combined with the authorized days of the week.

• Statement due date (field SOIFLG)

If this box is checked, the due dates calculated from these payment conditions are taken into account by the automatic generation of customer statements (knowing that each payment method has a statement code used to refine the rules, which can be modified due date by due date).

• field FBDDAYFLG

Specify for which days of the week a due date calculation is authorized. If the due date calculated corresponds to a forbidden day, the due date is systematically postponed to the next authorized day.
This control is combined with the bank holidays.