Use this function to define report codes for different types of payments.

Payment entry types are associated with payment report codes. The Payment/Receipt entry function (GESPAY) and Manual remittance entry function (GESFRM) use an associated payment report code to control which types of report are available for printing a single payment record.

You can use a single payment report code for one or multiple legislations.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Payment report code function contains a single screen in which you define a report code and an internal report code, per legislation.

Entry screen

Use this screen to define the codes that will be used to identify a type of payment report. You can use the same codes for different legislations, if required.

For each payment report code you define you must add an internal identification code to the Processing field (TRT). Your internal code will act as both a link, and a filter for print codes defined in the Print code function (GESARX), so must be specific to the type of payment report. For example, you could define the internal processing code "ADV" for a settlement advice print/report. "ADV" could be a common recognizable internal code used by multiple languages that when combined with a currency code in the Print code function (GESARX) will enable a payment function to print settlement advices in a specific currency.

Once you have defined your payment report codes, you must define print codes (in the Print code function (GESARX)) to be associated with them. The internal print code (INTCOD field) must follow a specific naming pattern so that it can be used by the actual payment functions to identify a particular type of payment report:

  • PAY<processing code><currency code> for Payment/Receipt entry
  • BORREM<processing code><currency code> for Manual remittance entry

For example, the internal print code PAYADV would identify a report that is to be available for printing in the Payment/Receipt entry function (GESPAY).

The Internal code field (INTCOD) in the Print code function (GESARX) must meet the required format which includes the prefix expected by the payment function itself (PAY/BORREM).

You must also associate your payment report codes with payment entry types to control which reports are available for printing. You do this using the Payment report code field (CODEDT) in the Printing block of the function (GESTPY).

Block number 1

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.

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

Payment report code (field CODEDT)

Type in a code to represent a specific type of payment report. This code will be used to link a type of payment with this type of payment report. For example, you could use the code "CHQ" for check.
Legislation (field LEG)

This field displays the legislation code for the country, for example FRA for French legislation.

This code is attached to a company and assigns predetermined rules and parameters necessary to fulfill country-specific legal requirements. It can include calculation rules, legal reports, legal declarations, tax management, and so on.

Legislations are defined in Miscellaneous table 909. General parameters can also be defined at the legislation level.
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.

SEEINFO The connection language must be defined as a default language for thefolder.
Short description (field SHOAXX)

Identification

Processing (field TRT)

Use this field to define a code that can be used to identify this type of payment report. This is an internal code that will be used by the payment functions Payment/Receipt entry (GESPAY) and Manual remittance entry (GESFRM). You can use a combination of letters and numbers, however, to meet print code limitations use a maximum of 6 characters.

In order to present reports for printing, these payment functions select reports that use a specific naming pattern that includes this internal code, as follows:

  • PAY<processing code><currency code> for Payment/Receipt entry
  • BORREM<processing code><currency code> for Manual remittance entry

For example, the Payment/Receipt entry function will present the following payment reports defined in the Print code function (GESARX) for selection and printing:

  • PAYCHKEUR - Check payment in euros, where PAY = a fixed code, CHK = your internal processing code, EUR = a currency code.
  • PAYADV - Settlement advice, where PAY = a fixed code and ADV = your internal processing code. This report is not for a specific currency.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation