Payment methods

• Payment method (field PAM)

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

• Legislation (field LEG)

In creation mode, the legislation code is initialized by default via the user parameter LEGFIL - Legislation (selection filter) (SUP chapter, INT group). You can also use this parameter to filter the selection panel and only display the codes defined for this legislation and those defined for All legislations.
When a legislation code is applied, the setup can only be used by companies under thislegislation.

General principles for legislation:

• When a record exists for a legislation, for example French legislation (FRA), it can only be used in other files (setups, movement entry, etc.) containing the same legislation (FRA) or no legislation at all. It cannot be used in a record containing a different legislation.
• When a record exists without legislation, or all the legislations, it can be used in other records regardless of their legislation.

This behavior is modifiedwhen a record has several legislations:

If a record (same code) exists for a legislation, for example FRA, and also without legislation, the behavior is as follows:

• For a record with a legislation different from the legislation defined in the data (FRA in the example):
  Only the data set up without legislation can be used.
   
• For a record containing an identical legislation (FRA in the example):
  Only the date set up with this legislation can be used, as long as it is active.
  The data set up without legislation cannot be used even if it is active, and the data set up with legislation is inactive.
   
• For a record for which there is no legislation entered:
  Only the data set up without legislation can be used.
  The data with a legislation is not available for selection and cannot be used.
  However, if the data without legislation does not exist, all data containing a legislation is available for selection and can be used.
  
  When using data available for several legislations that is set up with a group of companies, an additional control is carried out to maintain consistency within the  group of companies. It is a control between the legislation of the element (setup, flows, etc.) in which the data is used and the legislation of  group of companies entered on the  data and the reverse.
   
  Example: The Tax rate  setup element uses the Tax rule data.

If the Tax rate is linked to a legislation, the control ensures that the group of the Tax rule contains at least one company with the same legislation as the legislation of the Tax rate.

If the Tax rate is defined for a group has no legislation, the control ensures that the legislation of the Tax rule corresponds to at least one of the companies of the group entered on the Tax rate.

The list of selection of data does not take into account this control because it is only carried out when the data is selected. 

• Description (field DESAXX)

This long title is used as title in screens and reports. Both long and short titles are mandatory.

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.

• Active (field ENAFLG)

Select this check box so that the data can be used in other records (documents, parameters, etc.) or during a mass processing.If not selected, the data is considered to be inactive and it cannot be used in other records.

• SDD management (field SDDFLG)

The management of this field is subject to the activity code SDD - SDD management.
Select the box to indicate that the current payment method is linked to the SDD mandate management mode (Sepa Direct Debits). When this box is selected, the "Statement" field becomes inactive. Conversely, the "Statement" field becomes active when the box is unselected.

• Statement (field SOI)

This field can only be accessed when the "SDD management" box is not selected.
When this box is selected, the "Statement" field becomes inactive. Conversely, the "Statement" field becomes active when the box is unselected.
The Statement field is used to define how the open item statements are generated. If this field is empty, the payments using this method never appear on a statement. If this field is not empty, the open items are grouped by this statement code (in other words, the open items with payment methods using the same statement code are grouped together if the other generation parameters permit it). It is also possible, at the time of the statement generation, to only select a single statement code, which makes it possible to only process the payment methods concerned.

• Type (field TYP)

Specific use for Swiss payment types:
The code entered here is used to control the payment transaction type within the corresponding file format. This value is evaluated when writing the transactions to the bank file. The value has to correspond to the type codes of the EZAG/OPAE and DTA formats. Please refer to the format descriptions available from Postfinance and SIX Interbank Clearing.

• Paper draft (field PAPTRT)

A Paper form that is equal to 2 if a form is printed with the status "Form" for this payment method (another value prevents the printing of the form for this payment method).

• Acceptance (field ACCEPT)

An Acceptancecode takes numeric values defined with respect to the contents of local menu 682, which values can be modified. This value is taken into account as a function of the acceptance return, to display a value indicating the acceptance type as a function of the payment method. It also serves to assign the acceptance code in the bank interface files.

• Credit card processing (field SEPFLG)

Select this check box if the payment method is a credit card payment. This button is available if the activity code SEPP - Credit card integrationis activated.

• Swiss payment type (field SWIPAMBVR)

This field is related to the KSW – Switzerland activity code.
It is used to control the use of the payment methods. The following settings are available:

Non-ISR

For payment types not related to ISR payments like cash payments, for example, or payment processes outside of the Swiss banking

Print

For payment types used to print on sales invoices, for example ISR printing with ISR reference line

DTA

For payment types used to generate Swiss banks bank files (DTA format)

EZAG

For payment types used to generate Postfinance bank files (EZAG/OPAE format)

ISO

For Swiss ISO payment types based on the ISO 20022 format. This selection is also required to print QR-bill customer invoices.

• SAF-T payment method (field SFTPAYMET)

This field defines the payment type reported in the SAF-T file for fiscal authorities.