This function can be used to generate payslips corresponding to several criteria.

SEEWARNING  This function creates payslips but does notcalculate the payments.

Upon automatically generating payslip headers, the analytical dimensions are initialized with regard to what is set up in the "Acct" tab from the employee form or the contract form. If entered, the parameters defined at contract level take priority over the parameters defined at the employee form level.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Fields

The following fields are present on this tab :

Criteria

  • All companies (field ALLCPY)

Select this checkbox to include all companies. To run this process for a single company, do not select this checkbox.

Alphanumeric characters used to identify a company in a unique manner.
It is possible to define one or several sites within the same company.
It is possible to define a company as not being a legal company (then, it serves for reporting purposes only).

  • All sites (field ALLFCY)

Select this check box to include all sites. To run this process for a single site, leave clear.

This number is used to identify the site in a unique way.
A site belongs to only one company.
A site can represent a geographical location (plant, company, etc. ) or a responsibility center.

SEEWARNING All operating management actions are carried out from a site.

It is possible to associate a default site or one site per module for each user. Depending on the function being used, the default site is submitted automatically. It can be modified with another site which has been authorized for the user, according to this user’s authorizations.

  • field WFILLER

 

 

  • All departments (field ALLSRV)

If this box is checked, the processing is launched for all departments (otherwise, they have to be specified).

This code is used to identify the service for which the processing must be launched. 
You can assign a default service to each user.

  • All profiles (field ALLPRF)

If this box is checked, the processing is launched for all profiles (otherwise, they have to be specified).

This code is used to identify the employee profile for which the processing must be launched.
You can assign a default profile to each user.

This field defines the selection ranges of the registration numbers to be processed by the function.

 

This code is used to identify the employee population for which the processing must be launched.

  • Other criterion (field CRI)

You can select a criterion or enter a formula to complete the selection criteria.

Enter a pay extraction period.

The selection list contains the pay extraction periods corresponding to the pay month.

The details of the pay extraction period are then displayed in the Payroll elements block.


The extraction periods must be active to be selectable in the selection list.


The system will create the payslips for employees whose contracts are linked to this extraction period.

Payroll elements

  • Year (field PERYEA)

 

  • Period number (field PERNUM)

 

  • Tax month (field TAXMON)

 

  • Period in month (field PERMON1)

 

  • Pay date (field DAT)

The pay generation date in the month and year defined by the Pay month. Caution, the pay date must always be a valid date in the month and year defined by the pay month. For example, if the Pay month is February, the Pay date must be between the first and last date in February of the year specified.

If the date is changed:

  • The Payment date is updated automatically to match the new Pay date, if the new Pay date is later than the existing Payment date
  • The Payment date is not changed if the new Pay date is earlier than the existing Payment date
  • Period start (field DATDEB)

Working period corresponding with the pay date. This field defaults to the pay period date defined by the Pay month function. Pay is generated for employees present for at least one day during this period according to their arrival/departure dates. The period start/end dates for new pay is adjusted with regard to the period during which the employee was present and the pay periods already generated.

  • Period end (field DATFIN)

 

  • Payment date (field DATPAI)

Field containing the salary payment date. This field defaults to the payment date defined by the Pay month function. 

This date can be later than the date displayed in the field Pay date and in a different month however, if the Pay date is changed to a date later than the Payment date this field is updated automatically to match the Pay date.

This date is changed automatically to match the Pay date when the parameter JPAY contains a value that results in salary payments being deferred to the following month.

Common features

This field contains the additional profile code if the payslip is an additional payslip.
Use the additional payslip to complete additional payments, for example the payment of profit-sharing amounts. In that case, the code of the additional profile is INT.

SEEINFO The additional profiles are profiles in which the Supplement check box is selected in the header of theProfiles function.

  • Multiple headers authorized (field FLGSEVBUL)

Option authorizing the automatic generation of several payslips for the same pay month and for periods that could overlap.

  • Exclude certificates (field FLGOUTBUL)

If this check box is selected, the payslip is excluded from the data extraction for the generation of certificates (Job center certificate, Social Security certificate, etc.).

Use this option to exclude the profit-sharing pays from these certificates.

Close

 

Batch task

This function can be run in batch mode, but no dedicated standard task is delivered to run it.

Specific Buttons

Is used to retain the criterion values entered, by assigning a name to the memo. Note that the STD memo, if it exists, is automatically recalled at function launch.

Is used to recall an existing memo.

Allows the deletion of an existing memo.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Date not compatible with payroll month

The Pay date must be a valid date in the month and year defined by the Pay month. For example, if the Pay month is February, the Pay date must be between the first and last date in February of the year specified.

Payroll date outside of payroll period

The pay date entered is prior to the first day of the pay month to which has been added a margin of n days defined by the JMAX parameter.

Incorrect period

The end date of the payroll period must not be earlier than its start date.

The Payment date cannot be earlier than the Pay date

The Payment date entered must not be earlier than the date displayed in the field Pay date.

The Payment date is not in the same month as the Pay date

It is possible to enter a Payment date which is later than the date displayed in the field Pay date and in a different month. You will not be prevented from entering this date but this message will be displayed as a warning.

Tables used

SEEREFERTTO Refer to documentation Implementation