Employment contracts

• Employee ID (field REFNUM)

Employee associated with the work contract.

• Family name-First name (field SRN)

• Contract chrono (field CTRNUM)

This field is automatically populated with the number of employment contracts when the employee's identity is entered.

• Multicontract employees: they can have several contract chronos as the same time. In that case, totals are managed by contract (different totals for each contract).
  
• Employees subject to a single contract: the initial contract and the additional clauses are archived in a single contract chrono. Totals can be canceled by selecting the 'Reset to zero totals' box.
  It is also possible to create another contract chrono following the previous one, for example in the case of a new arrival after a final exit. Previous totals no longer need to be retrieved.

• Pay after exit (field FLGVAR)

• Date (field CTRDAT)

Specify the date on which the contract mentioned hereafter becomes effective.
The date is the hiring date when the 'Hiring date initialization' field is selected in the Reasons for arrival of an employee function;
Otherwise, it is the date on which a contractual modification which justifies the generation of an additional clause is taken into account.

• Time (field ETRTIM)

Starting time of the employee's contract.

• Site (field ETRFCY)

Indicate the site the employee is assigned to.

• Company (field CPY)

• Legislation (field LEG)

In multi-legislated folders (where the LEG activity code is active), the Legislation fields are displayed.

• If a legislation has been set in the LEGFIL (Legislation selection filter) parameter (SUP chapter, INT group), it is used as the default but can be changed if needed.
• If LEGFIL has no legislation set, there will not be a default, so the Legislation field will have to be entered appropriately.

If a legislation is entered in the record header, other fields entered must follow any rules applicable to the legislation.

If a legislation is not entered in the record header, it might be deduced from another element (such as the company, site, or employee) and again, other fields entered must follow any rules applicable to the legislation.

If a multi-legislation group of companies is selected, other fields entered must follow any rules applicable to the legislation of at least one company in the group.

Example

If you select a group of British (BRI) and French (FRA) legislation companies, you cannot enter a value in a field that is only applicable to the South African (ZAF) legislation.

In single legislation folders (where the LEG activity code is not active), the Legislation fields are not displayed.

• Effective date (field RETDATEFF)

Date from which the additional clause to the work contract is taken into consideration.

• Backpay (field FLGRET)

This check box is selected by default after an amendment with back-pay has been created It specifies that the corresponding effective date is taken into account in the case of a contractual change (amendment) with a retroactive effect (back-pay).

• Start reason (field CTRGRD)

Specify the reason why you have created a new 'Contract' record corresponding to a new activity period. This field is mandatory because it is essential for the French DADS-U generation.
Selecting a reason declared as being automatically taken into account in the employees' departures automatically manages the closing of the previous activity period.
 This entry field is also used to specify the reason for a contractual change justifying the generation of an amendment.

• End date (field XITDAT)

• Final exit (field XITFNL)

• Type (field NATCON)

Enter the code of the employee’s contract nature.
This field is used for the DADS-U and DSN (French declarations) and for Portuguese legal requirement.

 Natures of contract are defined in the miscellaneous table no. 354 - Nature of contract.

• Career follow-up (field SUICAR)

This option box is used to include a contract record to the career management or conversely to exclude it.

If this box is selected, and the Management of Skills and Careers module is available, the contract elements can be viewed in the Career function of the employee.
When creating a record, the box is selected by default. The box can be cleared at any time.
If the box is selected during an update after a creation, a new career event is displayed in the 'Career' tab of the Career function.

If a contract record is deleted or if the box is cleared after creation, the corresponding event no longer appears in the 'Career' function.

• Coll. agreement (field CLLCVT)

Collective agreement the employee is part of.

• Position (field POT)

This optional field is used to specify the code of the employee's position to be selected from the list. When it is entered, it automatically populates the Position function and the 'standard job' field if it is linked to the employee's position. The user can either accept or refuse the update of the fields.

• Standard job (field JOBPOT)

This optional field specifies the standard job code, selected from the list. This field is populated by default if the standard job is linked to the employee’s position. The user can either accept or refuse the update of the fields.

• Profile (field PROPRF)

This field indicates the payroll profile of the employee. This profile, defined in the payroll plan, specifies by default the heading to be calculated for each payslip of the employee.
Calculation exceptions can be defined in the 'Exceptions' menu of the payroll plan.

• Payslip title (field JOB)

Description of the position filled by the employee. This description of the position is displayed on the salary slip and on some official documents. It can correspond to the title of the position, to the title of the reference job, or be completely different.

• Department (field ETRSRV)

Specify the department the employee is linked to.

• Nature of work (field NATWRK)

• Reason (field CDDGRD)

Use this field to select the replacement reason code for a fixed-term employment contract or a temporary employment contract.
 For example, the REM replacement reason code is used for fixed-term employment contracts for replacement periods of less than a month.

It is used to manage people (students for example) replacing employees on annual leave for replacement periods of less than a month.
 The REM replacement code is not taken into account within the framework of the Cerfa 2483 form and the labor movement declaration.

This reason is mandatory for the N4DS (S40.G10.05.019) concerning the following contract natures (S40.G10.05.012.001):
02 - Fixed term contract
27 - Fixed term contract with a set objective
28 - Fixed term contract for senior employees

Concerning the implementation of the interprofessional national agreement dated 11 January 2013, the amount of the unemployment insurance contributions is based on the reason and duration of the fixed-term contracts. The various categories of impacted fixed-term contracts must be identified based on the reasons for appeal.

When the contract is a fixed term contract with a set objective, this field is automatically populated with the FTC with set objective value. You cannot modify this value.

• Duration (field NBRPER)

Indicate the duration of the current contract in days, weeks, months or years.

• Period (field PERCON)

Indicate the duration of the current contract in days, weeks, months or years.

• Contract end (field ENDCON)

• Replaces (field MATREMP)

If the contract nature is not a training period agreement, the title of this field is Replaces. Enter the ID number of the replaced employee. The surname and first name of the replacement are then automatically displayed next to the Replaces field.

If the contract nature is a training period agreement, the title of this field is Tutor. Enter or select the tutor’s ID number. The surname and first name of the tutor are then automatically displayed next to the Tutor field.

• field SRNRPL

• Trial period end (field ENDTRY)

Specify the start date of the trial period.
If the period is renewed, select 'Trial renewed' and specify the end date of the trial period renewal.

• Renewed (field NEWTRY)

• End 2nd test (field ENDTRY2)

• Employment confirmed (field EMPCFM)

• Contract no. (field NUMCON)

Contract number mentioned on the work contract document.

• Register no. (field NUMRGT)

Register number. Update using the Register numbering function.

• CEA signature (field STRCAE)

Field exclusively linked to the French legislation.

• CEA ref. (field REFCAE)

Field exclusively linked to the French legislation.

• Temp agency (field AGNMIDWRK)

Indicate the name of the temp agency the employee ID number depends on.

• Job type (field TYPJOB)

Indicate the position type of the employee.

• Work abroad (field WRKSTG)

Specify if the employee works abroad. If the 'Expatriate worker' standard job is chosen, select 'Yes' in the scroll-down menu.

• Employment status (field DNATYPMOD)

• Working conditions (field DNACODMOD)

• Occupation status (field OCPSTA)

• PT rate (field RATMIDWRK)

Specify the rate corresponding to the part-time work of the employee.
This field is used for DADS-U declarations.

• Full-time contributor (field COTMIDWRK)

This field is only available for the French localization.

It is only available if:

- The employment type is different from a full time

- The part-time rate is different from 0

- The working condition is different from a full time

The values are the following:

- Not applicable

Default value if the reason for the employee's arrival is different from 'PTP' (employee moving to a full time with contribution)

- For the retirement basic scheme

- For the retirement basic and complementary scheme

Default value if the reason for the employee's arrival is equal to 'PTP' (employee moving to a full time with contribution)

• Weekly hours (field HRSWEK)

Number of weekly hours of the work contract.

• Monthly hours (field HRSMTH)

Number of monthly hours of the work contract.

• Annualized no. days (field NBRDAYCTR)

• Annualized no. hours (field NBRHOUCTR)

This field is only activated for a management based on an annualized number of hours. It is populated using the Company annualized no. of hour general parameter

• Working time unit (field DNACODTIM)

• Title (field PLNDES)

• Contract currency (field CUR)

• Frequency (field PERCOD)

Enter the pay extraction period for the contract. You can select a pay extraction period with the same legislation as the company the contract is linked to.

Pay extraction periods (or frequencies) are managed in the Extraction period function. An employee can move during the tax year from one extraction period to another, but this requires a new chrono contract to be created.

 The first day of the week set on the extraction period must be the same as the first day of the week set on the reference plan in theReference planningsfunction.

• Reference planning (field PLNTYP)

Specify the reference planning the employee is dependent on.

 The first day of the week set on thereference planningmust be the same as the first day of the week set on theextraction period.

• WT smoothing (field MODTPS)

Select this box if the employee qualifies for working time smoothing.

• Student (field SCHJOB)

Indicate whether the position of the employee is a student job.

• Foreign worker (field FOREIGN)

• Contract type (field CTRTYP)

• Qualification code (field CATQLF)

• Qualification (field QLF)

• Level (field LVLQLF)

Specify the professional abilities or the qualification level of the employee           button.

• Executive status (field STAEMP)

• Coefficient (field COE)

• Index (field IND)

• Rank (field GRA)

• Employment type (field EQUEMPTYP)

• Occupation level (field OCPLEV)

• OFO code (field OFOCOD)

• Seniority date (field DATANC)

• Apprentice ref date (field DATANCAPT)

• Company entry date (field DATCPY)

• Site entry date (field DATFCY)

• Free date (field DATLIB)

• Creation date (field DATCRE)

The Creation date and Period end date fields are specific to South Africa and Ghana legislations.

These dates are automatically filled by the system. They are used to know in which pay month the contract was created and terminated in order to determine the employee status for reports, that is to say if the employee is New, Active or Terminated as well as Future terminated, Current termination or Old termination (statuses used in the reports). For example, if the status is New, it means the employee and the contract have never been included in previous reports. If the status is Active, it means the employee and the contract have already been included in reports and continue to be included in reports. If the status is Terminated, it means this is the last time the employee and the contract will be included in reports.

When a new contract is created, the creation date defaults from:

• The creation date of the previous chrono-contract in the case a of new chrono-contract with the same chrono-contract number
• The end date of the pay month in the case of new chrono-contract with a new chrono-contract number

In case of patch installation, the creation date defaults from the seniority date (filled in the Seniority date field in the same block).

• Final exit (field DATXITFNL)

The Creation date and Period enddate fields are specific to South Africa and Ghana legislations.

These dates are automatically filled by the system. They are used to know in which pay month the contract was created and terminated in order to determine the employee status for reports, that is to say if the employee is New, Active or Terminated as well as Future terminated, Current termination or Old termination (statuses used in the reports). For example, if the status is New, it means the employee and the contract have never been included in previous reports. If the status is Active, it means the employee and the contract have already been included in reports and continue to be included in reports. If the status is Terminated, it means this is the last time the employee and the contract will be included in reports.

The period end date is used to see in which period the employee's contract was terminated, irrespective of the employee's contract end date. It defaults from the end date of the pay month, and only if the contract Final exit check box is selected.

In case of patch installation, if the contract Final exit check box is selected, the period end date defaults from the contract end date (filled in the End tab, in the End date field).

• Employment contract (field FLGCRECTR)

• field ICOCTR

• field ICOCTR2

• Appoint. letter (field FLGCRELET)

• field ICOLET

• field ICOLET2

• Revision (field FLGCREAVN)

• field ICOAVN

• field ICOAVN2

• Extracted DUE (field FLGDUE)

• End date (field XITDAT)

In the event of an employee leaving the company, specify the departure date. Otherwise, leave this field empty.
The chronological order of the arrival/departure dates is checked upon completion of the entry.
 If the contract is modified or a clause added, use this field to specify the end date of these contractual situations.

• Final exit (field XITFNL)

In the event of an employee leaving the company, specify:

• the reason for the departure (end of a fixed-term contract, transfer, retirement, resignation, etc.),
• the departure notification date,
• the employee's last working day.

• End reason (field XITGRD)

• Date of death (field DATDTH)

• RTZ of totals in case of departure (field RAZCUM)

If this check box is selected, the totals set up to 'RTZ of totals in case of employee departure', will be reset to zero when the first pay is calculated after the employee’s departure.

• Time events balance (field CLEEVETIM)

When selected, this check box is used, in the case of an employee's long-term leave (parental leave, for example), to close events upon payslip calculation or time transfer.

In this case, the period end date of the events to be taken into account is recalculated: if the departure date is later than the extraction end date of the next period, the period end date is equal to the final departure date.

• Notified on (field NTFDAT)

In the event of an employee leaving the company, specify:

• the reason for the departure (end of a fixed-term contract, transfer, retirement, resignation, etc.),
• the departure notification date,
• the employee's last working day.

• Dismissed on (field DATLIC)

The 'Dismissed on' date is the date of notification signature of the dismissal. This date can therefore be identical to the date of notification of the exit, or, in the case of a dismissal for economic reasons, it can be equal to either the date of the preliminary interview as referred to in article L. 1233-11 of the French labor code, or to the submission date of the notification letter to the first meeting of the personnel representative bodies as set out in articles L. 1233-28 to L. 1233-30 of the French labor code.

• Last presence (field LSTDAY)

In the event of an employee leaving the company, specify:

• the reason for the departure (end of a fixed-term contract, transfer, retirement, resignation, etc.),
• the departure notification date,
• the employee's last working day.

• Date agreement terminated (field DNARUPCON)

This is the date of signature of the contract termination agreement.

• ASSEDIC number (field NUMASS)

• Departure for leave (field XITLEA)

• Non-competition clause (field DNACLC)

• Allowance + stat min (field FLGINDSUP)

• Unemp allowances (field FLGALCCHO)

• Current transaction (field FLGTRN)

This check box is only available for the French localization.

This check box is available only if the Final exit check box is selected. It is used to inform, as early as contract level, that the employee has signed a transaction. This information is used within the framework of the contract end DSN extraction (the Current transaction check box will be automatically selected during the extraction process in the Contract data function.

• Compl. retirement contribution agreement (field COTRETCOM)

The Compl. retirement contribution agreement check box only applies to the French legislation. It is available only if the Final exit check box is selected.

For the DSN, the regulations of the French AGIRC and ARRCO complementary health schemes provide for the transfer of information concerning employees whose work contracts are terminated but who keep contributing to these complementary health schemes.

Select this check box if a complementary retirement contribution agreement has been signed with the employee. This information is used to extract data on "Affiliated former employees".

You must enter the start and end dates of the agreement.

• Period start (field STRRETCOM)

The Period from andPeriod to fields only apply to the French legislation.

If the Compl. retirement contribution agreement check box is selected, you can enter the start and end dates of the agreement (the start date must be later than the final end date of the contract.

These dates are used for the French DSN to extract data for the "Affiliated former employees".

• Period end (field ENDRETCOM)

• Usage FTC exemption (field DERCDD)

• Affiliation to the contract preserved (field MNTAFFCON)

• Completed and paid (field FLGPRV)

This indicator, which cannot be entered, is automatically activated when creating the asset when it is a legacy asset (entry or import legacy asset).
A legacy asset is an asset whose accounting allocation (matching) date is prior to the current fiscal year start date when the asset is created or having a depreciation expense total at the start of the FY forced on creation or having a depreciation total at period start entered on creation.

• Period start (field STRTIMNTC)

• Period end (field ENDTIMNTC)

• Not completed and paid (field FLGPRV2)

• Period start (field STRNTC2)

• Period end (field ENDNTC2)

• Neither completed nor paid (field FLGPRV3)

• Period start (field STRNTC3)

• Period end (field ENDNTC3)

• Departure before advance notice (field FLGXITPRV)

Departure before advance notice

Select this check box if the advance notice has not been complied with (termination of the trial period, for example).

• Period start (field STRXITPRV)

• Period end (field ENDXITPRV)

• Notice payment (field NTCPAY)

• Socio-professional category (field CATCSP)

Indicate to which socio-professional group the employee belongs to, with respect to the social balance sheet.
This field is used for DADS-U declarations.

• Federal ID code (field CTRCODSEE)

• PCS information (field PSNJOB)

Field exclusively linked to the French legislation.

• Categ. status (field STACAT)

Specify the category status the employee belongs to (senior executives, other executives, etc.) according to the collective agreement of the company. This field is used for DADS-U declarations.

• IRC status (field STACAT2)

Specify the category status the employee belongs to within the framework of the AGIRC-ARRCO complementary welfare scheme. This field is used for DADS-U declarations.

• Professional status (field CATJOB)

Specify the professional status of the employee.This field is used for DADS-U declarations.

• WA risk (field RSKWRK)

The AT code identifies the type of work-related accident the employee encountered.
This field is used for DADS-U declarations.

• BOETH status (field HDCSTA)

• Business expenses (field EXSPFL)

This field specifies the payment procedure for professional expenses:

• F for fixed allowance,
• R for reimbursement against vouchers
• P for direct payment by the employer,
• D for reimbursement of expenses that have already been paid for by the employee and do not have the characteristics of professional expenses usually paid for by the company.

These 4 letters can be combined, for instance: RD:

• Deduction (field DED)

When an employee is granted a specific fixed deduction for business expenses, the deduction rate and the "Fixed" and "Actual" option must be specified. 
In the payroll preparation, if a specific fixed deduction for business expenses is entered, a capped deduction of contribution bases is applied.
if the option is set to "Fixed", the FRAIS_PROF heading is activated. This heading is added to the gross amount and completes the DADS-U 'Amount of business expenses' US41010044 total amount. The amount of the capped deduction is substracted from the gross tax basis (BRUT_FISC heading) and the new amount completes the DAD-U 'Gross tax basis' - S40.G40.00.035.001 total amount.

• Option (field OPEDED)

• Deduction category (field CATDED)

This category must be present only if the fixed deduction coefficient is different from zero.

It is used in the N4DS in the S40.G28.05.029.005 structure.

• Benefits by type (field AVNNAT)

This field identifies the type of the benefits in kind.

• F for food
• L for Accommodation ((L for French Logement)
• C for car
• O for others.

These 4 letters can be combined, for instance FA.
This field is used for French DADS-U declarations.

• ICT (field NTIC)

Assessment of the benefits from the tools linked to the Information and Communication Technologies (ICT).

• Tip (field TIP)

Specify if the employee is paid with tips.This field is used for DADS-U declarations.

• Part-time activity organization (field PTLACT)

• Salary periodicity (field WAGPAYPER)

• CNBF code (field CODCNB)

Field exclusively linked to the French legislation.

• DSN ground for exclusion (field GRDEXUDSN)

Use this field to specify:

• whether the employee's contract is part of the DSN scheme, but subject to a special status (in that case, specify the status),
• or the employee's contract is not part of the DSN scheme (in that case, the value is set to Total DSN exclusion).

Not impacted

If the employee record is activated at payroll management level, in other words, the Payroll management box is selected in the Employees function, the value is Not impacted (default value automatically populated): the contract is impacted the full DSN scheme.

Total DSN exclusion

If the employee record is not activated at payroll management level, in other words, the Payroll management box is cleared in the Employees function, the value is Total DSN exclusion (default value automatically populated): the contract is excluded from any DSN scheme.

Other values

Employees with a special status (staff members belonging to one of the three public services, fishermen, etc.) are impacted by the DSN scheme, but with a special treatment.

• Employee type (field EMPTYP)

• Additional public policy scheme (field PUBDTFCPT)

• Sickness (field SYSMAL)

Specify the employee's social security scheme(s): if all the risks (sickness, maternity, WA, pension) are covered by the membership to a single basic scheme, then enter only the basic scheme. If not, enter all the schemes one by one. These fields are used for French DADS-U declarations.

• SL (field SYSAT)

Specify the employee's social security scheme(s): if all the risks (sickness, maternity, WA, pension) are covered by the membership to a single basic scheme, then enter only the basic scheme. If not, enter all the schemes one by one. These fields are used for French DADS-U declarations.

• Pension (field SYSVIP)

• Extension (field SYSFLG)

Extension code for the Alsace/Moselle region: add this heading if the employee qualifies for the Alsace/Moselle regional scheme in addition to the mandatory Social Security basic scheme.

• DON'T USE (field MODCTR)

This field is dedicated to the Portuguese legislation.
This field is only available when the PCOM - Social security communication activity code is active.

For a new contract, you have to enter manually the contract modality.
For existing contracts, use the UTI009131 process to populate this field automatically with the contract modality.

The contract modality depends on the values of the Type and Job type fields on the employee contract as listed below:

The contract modality is part of the data that is communicated to the Portuguese Social Security (through the Communication function available from the Actions panel).

• Communicated (field SSCCOM)

• Multi-employer (field SEVEMP)

Indicate whether the employee has worked or is working for several employers simultaneously and specify the period of time during which this employee has been in this multi-employer situation.

• Period start (field STRDATSEV)

• Period end (field ENDDATSEV)

• Admin situation (field DNASITADM)

Employee's or public servant's administrative situation code that identifies if private law or public law applies to the employee's contract.

• Foreign company (field DNACPYSTG)

Status of the employees working for the benefit of a foreign company

• Liable for Assedic (field DNAACTASS)

Field exclusively linked to the French legislation.

• Unemployment exemption (field DNAEXOASS)

• Liable for AGS (field DNAAGS)

• Holiday fund (field DNACCP)

Field exclusively linked to the French legislation.

• AL fund no. (field NUMCCP)

Field exclusively linked to the French legislation.

• Object number (field NUMOBJ)

Object number assigned by the CNCS (French national center for movies and entertainment) and transferred to the MEC (Monthly Employer Certificate) of the casual workers that are hired to carry out this object (show, production, movie, etc.).

• Kinship (field LNK)

• Link (field TYPLNK)

• Multiple jobs (field SEVCTR)

Indicate whether the employee has several work contracts at the same time.

• Main site (field MAIFCY)

This box is used to specify the main site in the case where an employee has several contracts in the same company and for different sites.
The main site is used to define, for instance, in which site the employee will vote for works council elections.

• Body of electors (field PRUCOL)

• Sector (field PRUACV)

• Polling place (field PRUVOT)

• Contract right (field PRUCTR)

• Category (field CATFRT)

• Pension fund (field RETFDSNUM)

• Category (field CAICAT)

• Rate 1 (field CAIRATPS)

• Rate 2 (field CAIRATPP)

• Compl. health ins. scheme (field AFFMUT)

Enter or select the complementary health insurance scheme code.

Complementary health insurance scheme codes are stored in the miscellaneous table no. 329 - Complementary welfare scheme. A code corresponds to a number/beneficiary type pair (for example, 1 adult + 1 child).
Beneficiaries are entered in the fields of the Beneficiaries block (number of children, adults or other persons).

The complementary health insurance scheme code is used in the payslip:

• If the code ‘1’ is entered (‘No’ value), no complementary health insurance contribution heading is calculated in the payslip.
• If a code different from ‘1’ is entered, the corresponding complementary health insurance contribution heading is calculated and available in the payslip.
  
  

• No compl health affiliation (field NOTAFFMUT)

• Beneficiary no. (field NUMBNF)

Enter the employee’s beneficiary number to the health insurance organization.

• Children (field NBRPEO2)

• Adults (field NBRPEO3)

• Others (field NBRPEO4)

• Health ins. body (field ORGMAL)

This field is only available for the French and Portuguese legislations.

Enter the name of the health insurance body.

• Without welfare membership (field NOTAFFPREV)

• State pension number (field SATCAI)

• National health insurance number (field HLTNSSNUM)

• Registration date (field HOUREGDAT)

• Occupation date (field HOUOCCDAT)

• Social security contribution type (field SOCCTBTYP)

• Social security non-contr. reason (field SOCCTBREA)

• Social security status (field SOCSTA)

• Floor area (field FLRARE)

• Emp tax number (field EMPTAXNR)

• Emp tax number (field EMPTAXNUM)

• Housing fund number (field HOUFUNNUM)

• Title (field CIVCTRA)

• Housing type (field HOUTYP)

• field SSCT1

• field PENT2

• field PENT3

• Social Security number (field SSCNUM)

• Tickets restaurant card (field CARTIKRES)

• NITA member number (field NITAMEMNUM)

• Event (field EVECTRCOD)

This grid is used by the company to notify the welfare organization of the events that occurred in the employee's contractual situation (registration, membership cancellation, etc.).

In a declaration containing contribution periods (annual or quarterly declaration), if the start or end date of the S45 contribution period is different from the start or end date of the S41 work period, the corresponding event(s) must be entered.

The event with code 70 ‘Deferred contributions’ is reserved for periodic annual or quarterly declarations. It is used to declare a contribution period later than the generating event (for example, case of a registration followed by a period without contribution).

The events associated with codes 80 and 81 are reserved for event declarations:

• Code 80 is used to declare a new list of beneficiaries linked to the employee for the mentioned contract(s).
• Code 81 is used to notify one or several changes in the employee's administrative data, which are included in structures S30 or S41 (employee's address, site the employee is assigned to), when this/these change(s) do not imply any other event.

• Date (field EVECTRDAT)

• Case of external availablity (field DTNXTN)

• Site (field WRKFLGADD)

This block contains information on the workplace for contracts for interim missions or interim permanent contracts.

• If the employee works in the site mentioned on their contract (specified at header level), select the Site check box. In that case, it is not necessary to enter the other fields because the workplace data is recovered from the site on the contract.
• If the employee does not work on the site mentioned on their contract, do not select the Site check box and enter the other fields.
  

• Site tax ID no. (field WRKCRN)

For those legislations different from the French legislation:

• In the Site tax ID number field, enter the site tax ID number of the company being the customer of the interim agency.
• Populate the other fields with the data relating to the site where the employee works.

For the French legislation:

• In the Site tax ID number field, enter the site tax ID number of the company being the customer of the interim agency.
• In the User site tax ID no, enter the site tax ID number of the site where the employee is completing their interim mission.
  This field can only be accessed if a site tax ID number has been entered in the Site tax ID no field.

If the site where the employee is completing their interim mission is identical to the site of the company being the customer of the interim agency,
these two fields contain the same site tax ID number.

There is an icon next to the Site tax ID no. and User site tax ID no. fields.

• Click the icon next to the Site tax ID no. field to enable the other fields to be entered for this site (APE/SIC, Legal nature, etc.).
• Click the icon next to User site tax ID no.field to enable the other fields to be entered for this site
  (APE/SIC, Legal nature, etc.). The fields relating to this site are on a green background to differentiate them from the fields concerning the other site.
  

• field ICOCRN

• User site tax ID no./Free code (field WRKUSRCRN)

• field ICOCRNUSR

• APE/SIC code (field NAFWRK)

• Legal nature (field WRKNATLEG)

This field indicates the legal nature of the place of work if said place of work is different from the assignment site.

Not impacted

Default value.

Site

Value populated automatically if the site tax ID number is entered in the Site tax ID number field.

• Country code (field WRKCRY)

• Country (field WRKCRYNAM)

• Workplace name (field WRKNAM)

• Additional info (field WRKADD1)

• Address (field WRKADD2)

• Municipality (field WRKADD3)

• Municipality code (field WRKCODSEE)

• Postal code (field WRKCODPOS)

• City (field WRKCTY)

• Non-UK address (field NUKADD)

• Priority (field PIO)

• Type (field TYP)

• Address line 1 (field ADDLIN1)

• Address line 2 (field ADDLIN2)

• Town (field TWN)

• County (field CUY)

• Postal code (field POS)

• Country code (field CRYCNT)

• Telephone (field TEL)

• Mobile phone (field MOB)

• Work mobile (field WRKMOB)

• Fax (field FAX)

• Extension (field ETS)

• Email (field EML)

• Other email (field OTHEML)

• Set as default (field SETDEF)

• Priority (field ADDPRI)

• Type (field ADDTYP)

• Service type (field ADDSRVTYP)

• Other PO (field ADDPOSOTH)

• Unit/postal number (field ADDPOSNUM)

• Post office name (field ADDPOSNAM)

• Postal agency (field ADDPOSAGN)

• Complex (field ADDCPX)

• Street number (field ADDSTRNUM)

• Street (field ADDSTRNAM)

• Suburb/District (field ADDSUB)

• City (field ADDTWN)

• Country code (field ADDCNTCDE)

• Postal code (field ADDPOSCDE)

• Province (field ADDPRV)

• Care of postal address (field ADDPOSCOF)

• Care of intermediary (field ADDPOSINM)

• Active (field ADDSTA)

• Set as default (field ADDCOR)

• Priority (field AFRPRI)

• Type (field AFRTYP)

• Unit/postal number (field AFRPOSNUM)

• Complex (field AFRCPX)

• Street number (field AFRSTRNUM)

• Street (field AFRSTRNAM)

• Suburb/District (field AFRSUB)

• City (field AFRTWN)

• Village (field AFRVIG)

• Traditional authority (field AFRTRDAUZ)

• Postal code (field AFRPOSCDE)

• Country code (field AFRCNTCDE)

• State/province (field AFRPRV)

• Local government area (field LOCALGOV)

• Active (field AFRSTA)

• Set as default (field AFRCOR)

• Priority (field MIDPRI)

• Type (field MIDTYP)

• Unit/postal number (field MIDPOSNUM)

• Postal code (field MIDPOSCDE)

• Building (field MIDBUINUM)

• Complex (field MIDCPX)

• Street number (field MIDSTRNUM)

• Street (field MIDSTRNAM)

• Suburb/District (field MIDSUB)

• Country code (field MIDCNTCDE)

• Province (field MIDPRV)

• Care of postal address (field MIDPOSCOF)

• Care of intermediary (field MIDPOSINM)

• Active (field MIDSTA)

• Set as default (field MIDCOR)

• Marital status (field SITFAMA)

• Marriage date (field MRGDAT)

• Spouse's registration number (field JNTREFNUM)

• Spouse's name (field JNTNAM)

• Spouse's maiden name (field SPOMDNNAM)

• First name (field JNTSRN)

• Born (field JNTDATBRN)

• Country code (field JNTCRY)

• Country name (field JNTCRYNAM)

• Telephone (field JNTTEL)

• Dependent adult(s) (field ADT)

• Dependent child(ren) (field CHD)

• Child disability (field CHDDIS)

• Number of holders (field NBRHLD)

• Spouse disability (field JNTDIS)

• Pension (field COIPLN)

• Partner title (field PARTTL)

• Partner second name (field PARSECNAM)

• Partner initials (field PARINI)

• Partner NI number (field PARNIN)

• Car registration no. (field CARREG)

This field is only available for the United Kingdom (BRI) legislation.
Use this field to enter, or select, the registration number of a car that you want to allocate to this employee as a company car. Details of the car should have been added using the UK Legal data screen of the Companies function. A company car can only be allocated to one employee, although an employee may have more than one company car.

• Make of car (field MAKCAR)

This field is only available for the United Kingdom (BRI) legislation.
This field displays the manufacturer of the car with the registration entered in the Car registration no. field. Details cannot be entered or amended, they are taken from the UK Legal data screen of the Companies function.

• Model of car (field CARMOD)

This field is only available for the United Kingdom (BRI) legislation.
This field displays the model of the car with the registration entered in the Car registration no. field. Details cannot be entered or amended, they are taken from the UK Legal data screen of the Companies function.

• Fuel type (field FUETYP)

This field is only available for the United Kingdom (BRI) legislation.
This field displays the type of fuel used by the car with the registration entered in the Car registration no. field. Details cannot be entered or amended, they are taken from the UK Legal data screen of the Companies function.

• CO2 emissions (field EMISSI)

This field is only available for the United Kingdom (BRI) legislation.
This field displays the CO2 emissions of the car with the registration entered in the Car registration no. field. Details cannot be entered or amended, they are taken from the UK Legal data screen of the Companies function.

• List price (field LISPRI)

This field is only available for the United Kingdom (BRI) legislation.
This field displays the list price of the car with the registration entered in the Car registration no. field. Details cannot be entered or amended, they are taken from the UK Legal data screen of the Companies function. This is the manufacturer’s original list price of the car and all standard accessories, including VAT. This may be different to the price paid for the vehicle.

• Date first registered (field DATREG)

This field is only available for the United Kingdom (BRI) legislation.
This field displays the date the car was first registered. Details cannot be entered or amended, they are taken from the UK Legal data screen of the Companies function.

• Available start date (field DATAVA)

This field is only available for the United Kingdom (BRI) legislation.
Use this field to enter the date the car was made available to the employee as a company car.

• Available end date (field DATAVAEND)

This field is only available for the United Kingdom (BRI) legislation.
Use this field to enter the date the car stopped being available to the employee as a company car.

• Cash equivalent of car (field CASEQU)

This field is only available for the United Kingdom (BRI) legislation.
Use this field to enter the current value of the car if it is a classic car, more than 15 years old with a value of £15,000 or more and that value is greater than the car’s original list price.

• Free fuel provided (field FUEPRO)

This field is only available for the United Kingdom (BRI) legislation.
Use this drop-down list to select ‘Yes’ or ‘No’ to indicate whether the company pays for all the vehicle’s fuel including any of the employee’s private mileage. If the company provides fuel for any private mileage at all, this field must be set to ‘Yes’.

• Fuel provided date (field FUEPRODAT)

This field is only available for the United Kingdom (BRI) legislation.
Use this field to enter the date the employee starts receiving free fuel.
This field is mandatory if the Free fuel provided field is set to ‘Yes’.

• Fuel withdrawn date (field FUEPROWTH)

This field is only available for the United Kingdom (BRI) legislation.
Use this field to enter the date the employee ceases to be provided with free fuel during the tax year.

• Fuel cash equivalent (field FUECASEQU)

This field is only available for the United Kingdom (BRI) legislation.

Use this field to enter the cash equivalent of the fuel provided to the employee for private mileage while driving this car.

This value is required if you have registered to use the HMRC Payrolling Benefits in Kind (PBIK) online service for the current tax year. The PBIK service is optional; employers can continue to report expenses and benefits using the form P11D. Benefits that are registered as PBIK do not go on a form P11D. Once a tax year has started the employer must continue to payroll all PBIK registered benefits for the remainder of that tax year.

Employers can choose which benefits they want to payroll. Employers must still file a P11D(b) at year end, regardless of whether they are payrolling benefits or submitting them on P11D forms.

When a benefit is payrolled the cash equivalent of that benefit should be calculated and then split across the tax year as applicable. Tax is then charged on each payrolled benefit and is reported in the Full Payment Submission (FPS) for that period.

From April 2018 details of cars that have been included in the PBIK system must be included in the FPS.

Employers that choose to payroll company car benefits must no longer submit form P46(Car) when providing an employee with a new car.

When an employer registers for PBIK the applicable benefits will be removed from an employee’s tax code. The employee will be issued with an amended tax code to reflect this change.

This field is mandatory if the Free fuel provided field is set to ‘Yes’.

• Withholding (field SRCRET)

• ASSEDIC beneficiary (field BUICODASS)

• Contributor status (field BUISTAPAY)

• Reduc rate Exp (field BUIRATEXS)

Specify the reduction rate applied to the employee for business expenses.This field is also used for the DADS-U declarations.

• PF and welfare membership (field BUIRETPRV)

Enter the code that specifies the membership type to a supplementary pension institution and a welfare institution that may differ from the employee's collective agreement assignment.This field is used for French DADS-U.

• Unit (field BUICODTIM)

Specify:

• the unit in which the working time is expressed,

• Day type of time unit (calendar/worked),

• the working time (total paid working time during the period. Exclude paid leave and other absences regardless of their nature (unpaid leave, sickness, WA leave, etc.). Express this total time using an integer, with a maximum of 6 digits. For instance: 1600 hours = 160000; 755 hours and 30 minutes = 75550).

• Day type (field BUIDAYTYP)

• Unit (field BUICODSAL)

• Type (field BUICODHRS)

• Profession (field BUICODJOB)

Specify the BTP (French construction industry) profession code of the employee.

 The list of BTP profession codes is available on the following web site:www.cnsbtp.fr.

 This field is also used for French DADS-U declarations.

• Qualification (field BUICODQLY)

Specify the classification-qualification code of the employee.

• Category (field BUICAT)

• Level (field BUILEV)

• Qualification (field PSNTYP)

Field exclusively linked to the French legislation.

• Fee type (field TYPCAC)

Field exclusively linked to the French legislation.

• MEC no. (field AEMNUM)

Field exclusively linked to the French legislation.

• Contract status (field STACTR)

Field exclusively linked to the French legislation.

• Payroll calculation (field CALPAY)

• Object of contract (field OBJCTR)

Field exclusively linked to the French legislation.

• Place of show (field LIEU)

Field exclusively linked to the French legislation.

• Provider IDCC no. (field IDCCP)

• Start date (field PSNSTRDAT)

Field exclusively linked to the French legislation.

• End date (field PSNENDDAT)

• Duration (field NBRDAY)

Field exclusively linked to the French legislation.

• Start time (field PSNSTRTIM)

Field exclusively linked to the French legislation.

• End time (field PSNENDTIM)

• Duration (field NBRTIM)

Field exclusively linked to the French legislation.

• No. fees (field NBRCAC)

Field exclusively linked to the French legislation.

• Expense (field AMTCRG)

Field exclusively linked to the French legislation.

• Exempt expenses (field AMTCRGEXO)

Field exclusively linked to the French legislation.

• Budget (field AMTBUD)

Field exclusively linked to the French legislation.

• Slip (field BUL)

Field exclusively linked to the French legislation.

• Certificate (field NUMCER)

Field exclusively linked to the French legislation.

• Payslip (field RPTBUL)

Enter the code of the employee's payslip, if it is different from the code defined in the parameter value management, BUL chapter, NOMRPTBUL parameter, for the employee's site or company.

• Payslip break (field FLGCREBUL)

Select this box if a new payslip needs to be generated for this specific contract record. For example, if the role of an employee is changed in the middle of the month, two payslips can be generated : A payslip for the start of the month (or the period of activity) on the last date corresponding to the initial role (defined by the end date);and a payslip from their transfer date to their new role (defined by the transfer reason and the effective date)until the end of the month.

Clear this box if the payment details for this contract record must be consolidated on the same payslip as the previous contract record. For example, if the employee's contract is modified in the middle of the month with the start reason code for an hourly capacity change, two payslips will not be needed.

This check box has no impact on the actual pay of the employee. At the end of the payment period, the employee will receive a single consolidated payment for this record and all previous contracts.

The default value is defined by the value of the 'Payslip break' box in the Reasons for arrival of an employee function.

This check box has a default value for the start reason code that is displayed at the start of each new period of activity. This variable cannot be modified.

This check box displays a value specific to the payroll for the selected contract records that cannot be modified. The following default values are pre-set:

• Blank - For 'Casual worker' type employees
• Selected -

• For those employees signing their first employment contracts
• For back-pay payments (the Back-pay box is selected)
• For a payment made after an employee has left the company (the Start reason code is set to 'VAR' (Payment after exit))

• Paperless payslip (field BULDEMAFF)

• Hide time references (field FLGTIMREF)

• Net to gross payroll (field TWDPAY)

Select 'Yes' if the payslip of the employee must be calculated from the net to the gross amount. In that event, the back-pay parameters need to be entered.
Otherwise, leave the field as it is, with the 'No' value.

• Objective heading (field OBJRUB)

Net to gross payroll calculation.
Performing this payroll calculation will generate a payslip having an 'objective' heading set to a given value, by varying the value of a secondary variable. For instance, the aim can be to vary payslips with a net salary set according to the employee, by modifying their basic salary. In this case:

• The 'objective' heading is SAL_NET (net salary).
• The 'variable' element is SALAIRE (basic salary).
• The 'objective' variable, for instance NET_PAE, is used to enter the value of the required net salary for each employee.

 By default, the 'objective heading', 'objective variable' and 'secondary variable' elements are submitted based on the parameters entered in the payroll plan.

• Objective variable (field OBJVAR)

• Secondary variable (field INCVAR)

Net to gross payroll calculation.
Performing this payroll calculation will generate a payslip having an 'objective' heading set to a given value, by varying the value of a secondary variable. For instance, the aim can be to vary payslips with a net salary set according to the employee, by modifying their basic salary. In this case:

• The 'objective' heading is SAL_NET (net salary).
• The 'variable' element is SALAIRE (basic salary).
• The 'objective' variable, for instance NET_PAE, is used to enter the value of the required net salary for each employee.

 By default, the 'objective heading', 'objective variable' and 'secondary variable' elements are submitted based on the parameters entered in the payroll plan.

• Usual prepayment (field INSAMT)

If the employee benefits from a regular prepayment (each month), specify the amount of this prepayment and the day of payment.

• Day (field INSDAY)

• Code (field EXOCOD1)

• Period start (field EXOSTR1)

• Period end (field EXOEND1)

• Code (field EXOCOD2)

• Period start (field EXOSTR2)

• Period end (field EXOEND2)

• Code (field EXOCOD3)

• Period start (field EXOSTR3)

• Period end (field EXOEND3)

• Code (field EXOCOD4)

• Period start (field EXOSTR4)

• Period end (field EXOEND4)

• Initial basic salary (field MTH)

Enter a decimal value in this field. This value is then linked to a variable on the payslip. This variable is the one that you have set in the VARMTH – Initial base salary general parameter (chapter BUL, group MIS).

Example:

• You have set the VARMTH - Initial base salary parameter to VENCIMENTO (the VENCIMENTO variable).
• In the Initial base salary field, you have entered 1700.00.
  = The value of the VENCIMENTO variable on the payslip is then 1700.00.

• Initial contractual hours (field HRS)

Enter a decimal value in this field. This value is linked to a variable on the payslip. This variable is the one that you have set in the VARHRS – Initial contractual hours general parameter (chapter BUL, group MIS).

• field ZON1

You can set the description you want for this field in the FLDCTR1 - Title of field in work contract general parameter (chapter PAY, group PER).

Enter a decimal value in this field. This value is linked to a variable on the payslip. This variable is the one that you have set in the VARZON1 – Free field general parameter (chapter BUL, group MIS).

Example:

• You have set the FLDCTR1 - Title of field in work contract parameter to ‘Fixed allowance’.
  = The Free field (ZON1) field is then named Fixed allowance.
• You have set the VARZON1 – Free field parameter to T_SUBALIM (the T_SUBALIM variable).
• In the Free field (ZON1) field, you have entered 240.00.
  = The value of the T_SUBALIM variable on the payslip is then 240.00.
  

• field ZON2

You can set the description you want for this field in the FLDCTR2 - Title of field in work contract general parameter (chapter PAY, group PER).

Enter a decimal value in this field. This value is linked to a variable on the payslip. This variable is the one that you have set in the VARZON2 - Free field general parameter (chapter BUL, group MIS).

Example:

• You have set the FLDCTR2 - Title of field in work contract parameter to ‘Fixed bonus’.
  = The Free field (ZON2) field is then named Fixed bonus.
• You have set the VARZON2 – Free field parameter to ISENCAO_H (the ISENCAO_H variable).
• In the Free field (ZON2) field, you have entered 240.00
  = The value of the ISENCAO_H variable on the payslip is then 240.00.
  

• Date (field SALDAT)

Date upon which the salary has been modified. This information is updated using the History extraction function.

• field SALVAL

The history extraction function is used to update this column, which contains all the successive changes in the salary variable set up in the VARSAL - Salary variable parameter (PAY chapter - EVO group).

• field SALVAL1

The history extraction function is used to update this column, which contains all the successive changes in the salary variable set up in the VARSAL2 - Salary variable parameter (PAY chapter - EVO group).

• field SALVAL2

The history extraction function is used to update this column, which contains all the successive changes in the salary variable set up in the VARSAL3 - Salary variable parameter (PAY chapter - EVO group).

• field SALRUB

The history extraction function is used to update this column, which contains all the successive changes in the salary heading set up in the RUBSAL - Salary heading parameter (PAY chapter - EVO group).

• field SALRUB1

The history extraction function is used to update this column, which contains all the successive changes in the salary heading set up in the RUBSAL2 - Salary heading parameter (PAY chapter - EVO group).

• field SALRUB2

The history extraction function is used to update this column, which contains all the successive changes in the salary heading set up in the RUBSAL3 - Salary heading parameter (PAY chapter - EVO group).

• Reason (field SALGRD)

Specify the reason for the modification of the salary element.

• field CUM1

• field CUM19

• field CUM2

• field CUM20

• field CUM21

• field CUM3

• field CUM22

• field CUM4

• field CUM23

• field CUM5

• field CUM24

• field CUM6

• field CUM25

• field CUM7

• field CUM8

• field CUM9

• Profession code (field OCPCOD)

This field is used to specify the profession code corresponding to this employment contract.

The list of profession codes is defined in Miscellaneous table 11552.

• Professional cat. (field PFLCATCOD)

In this field, specify the code of the professional category for this employee.

The validated codes are delivered by the Portuguese office for Strategy and Planning.

The list of validated professional category codes for the current fiscal year is provided in the miscellaneous table no. 11554/.

• Working time duration (field WRKTIMLNG)

This field is used to specify the collective agreement code for the specific working hours in the work contract.

The validated codes are delivered by the Portuguese office for Strategy and Planning.

The list of collective agreement codes is defined in Miscellaneous table 11555.

• Working time mgmt. (field WRKTIMMGT)

This field is used to specify the collective agreement code for the specific working days in the work contract.

The validated codes are delivered by the Portuguese office for Strategy and Planning.

The list of collective agreement codes is defined in Miscellaneous table 11556.

• IRCT Code (field IRCTCOD)

Use this field to provide the collective bargaining agreement code that covers this contract of employment. This number is issued by the government.

The list of collective agreement codes is defined in Miscellaneous table 11557.

• IRCT Applicability (field IRCTAPL)

Use this field to specify the current extension applied to the collective agreement code defined in the IRCT code field.

The list of the collective agreement extension codes is provided in the miscellaneous table no. 11558/.

• IRP5 start date (field IRPSTRDAT)

The field is exclusively linked to African legislations.

The IRP5 start and end dates are reset with new values when a year-end program is performed.

• IRP5 end date (field IRPENDDAT)

• Tax status (field TAXSTA)

• Legally retired (field TAXLEGRET)

• Deemed remuneration (field TAXDMDAMT)

• Directive number (field TAXDIRNUM)

• Foreign income (field TAXFORFLG)

• Directive percentage (field TAXDIRPRC)

• Directive amount (field TAXDIRAMT)

• Withhold shares tax (field TAXWTHSHR)

• UIF status (field UIFSTA)

• Learner/Excluded for skills levy (field LNRSKL)

• Manual IRP5 (field MANIRP)

• Excluded from OID (field OIDFLG)

• Voluntary over deduction (field VOLDED)

• Tax cycle start date (field TAXSTRDAT)

This field is exclusively linked to African legislations.

The Tax info block contains the tax data. This data is used on the tax record line in the Employees function, Additional tab, Tax info block.

The tax cycle start and end dates specify when the employee’s financial data must start and end to accumulate for the purpose of tax calculation and statutory reports.
The tax cycle start date is used to calculate the employees’ correct tax deductions for the applicable tax year.

• Tax cycle end date (field TAXENDDAT)

• Tax status (field TAXSTAAFR)

This field is exclusively linked to African legislations.

Specify the tax status of the employee.
This status indicates the calculation and tax deduction method to apply to an employee. It is used to calculate the tax and benefits on the Payslip screen.

The list of statuses available from the drop down list is linked to the legislation of your folder. The possible values are:

• Statutory tables:
  - For Nigeria: PAYE is calculated according to statutory tax tables.
  For other countries, tax is calculated according to the latest statutory rates.
• Tax directive (directive fixed amount): Tax should be calculated according to a fixed amount as per the directive.
• Temporary/Part time: Tax is calculated according to the latest statutory rates, but rebates should not be applied. Tax deductible deductions are allowed for temporary or part time employees.
• Independent contractor: No tax should be calculated for a true independent contractor.
• No tax: No tax is calculated. This option is only allowed in prescribed cases and should not be used on a general basis.
• Resident: Tax is calculated according to the latest statutory rates.
• Non-resident: Tax is calculated according to the latest statutory rates for non-residents.
• Exempt:   No PAYE is calculated.
• Directive %:   Use this option to enter the percentage according to a Directive from the Commissioner. This percentage will be used to tax the employee’s income. The system will prompt you for a directive number when you enter the percentage. The "Directive number" field is a mandatory field.
• Labor broker - Natural person: Tax should be calculated according to normal tax rates for a labor broker (natural person). Tax rebates should be applied and tax deductible deductions are allowed.
• Labor broker - Other: Tax should be calculated according to normal tax rates for a labor broker (other). Tax rebates should not be applied and tax deductible deductions are not allowed.
• Personal service company: Tax should be calculated at 30%. The percentage must be applied before taking allowable deductions into account. Rebates should not be applied.
• Personal service trust: Tax should be calculated at 33%. The percentage must be applied before taking allowable deductions into account. Rebates should not be applied.
• Non-executive director: Tax should be calculated at a flat rate of 33%. This percentage represents the highest marginal rate applicable to individuals. The percentage must be applied after taking allowable deductions into account, if applicable. Rebates should not be applied.
• Secondary job: Tax is calculated at a flat rate of 30%, This percentage represents the highest marginal rate applicable to individuals. Tax credit should not be applied.
• Permanent/Temporary resident
• Permanent/Temporary non-resident
• Part time resident
• Part time non-resident
• Casual Worker

• Part-time director (field PARTIMDIR)

• Vehicle rate (field VEHRAT)

• Car registration no. (field CARRGSNUM)

• Make of car (field CARMAK)

• Directive number (field DIRNUM)

This field is exclusively linked to African legislations.

If the employee is associated with a directive, the number and percentage or amount of the directive must be entered in the related fields.
This data is used to calculate tax on the Payslip screen.
It is reset with new values when a year-end program is conducted.

• Directive percentage (field DIRPRC)

• Directive amount (field DIRAMT)

• Exclude VET levy (field EXUVETLVY)

This field is exclusively linked to African legislations.

Select this check box if the employee must be excluded from the calculation of the VET levy.
This data is used to calculate values on the Payslip screen.

• Exempt certificate (field EXOCERNUM)

• Tax dependents (field TAXDEP)

• Tax class (field MLTTAXCLS)

This field is exclusively linked to African legislations.

Select the employee’s tax class.
This field is dedicated to the Swaziland legislation.

• Excluded from WCF (field EXCWCF)

• Employee position (field EMPPOS)

• Non-qualifying emp. (field NONQLFEMP)

This field is exclusively linked to African legislations.

• ETI calculation type (field ETICLCTYP)

This field is exclusively linked to African legislations.

• Permanent (field ETISTA)

• Std. industrial class. (field SICSUBCLS)

This field is exclusively linked to African legislations.

• Special econ. zone (field SEZCOD)

• Employee provided form (field PRVFRM)

• Starting declaration (field STRDLC)

• Occupational pension (field OCCPEN)

• Recently bereaved (field RECBEROCCP)

• Annual pension amount (field ANNPENAMTO)

• EEA citizen (field EEACIT)

• EPM 6 scheme (field EPMSCH)

• Intention to live in the UK for 183 days or more (field LIVMOR)

• Intention to live in the UK for less than 183 days (field LIVLES)

• Working in/out of the UK, but living abroad (field WRKIUKLIVA)

• Tax code (field TAXCOD)

• Tax code amount (field TAXCODAMT)

• Tax code label (field TAXLBE)

• Payroll process status (field PAYPROSTA)

• Scottish tax (field SCTTAX)

• Week 1 / month 1 (field WK1MH1)

• Welfare to work (field WELWRK)

• Manual NI entry (field MANNIENT)

• Right to work (field RITWRK)

• NI number (field NINNUM)

• NI category (field NICAT)

• Student loan (field STULOA)

• Student loan type (field STULOATYP)

• Student loan start date (field STULOADAT)

• Student loan end date (field STULOADATE)

• Student loan priority (field STULOAPIO)

• Director status (field DIRSTA)

• Status start date (field DIRSTASTR)

• Tax year start (field TAXYEASTR)

• Tax year end (field TAXYEAEND)

• Apprentice (field APR)

• Apprentice start date (field APRDAT)

• Apprentice end date (field APRDATEND)

• Net foreign tax credit relief (field NETFRNTAX)

• FPS employee details resubmission (field RTIEMPRSB)

• Late PAYE reporting reason (field LTEPAYREA)

• RTI payroll ID (field RTIPAYIDT)

• Changed RTI ID (field CHGPAY)

• Old payroll ID (field OLDPAY)

• On strike within the RTI payment period (field RTISTK)

• Been on an unpaid abs during the RTI pay period (field RTIABS)

• Insurance (field NSSCPY)

Use this field to specify the insurance policy code which applies to the work contract, in the event when the insurance linked to the contract is different from the insurance company.

When the field is empty, the insurance policy specified in the company record is used.

• Insurance policy (field NSSPOL)

The Social Security Number identifies the policy number of the insurance company mentioned in the Insurance field.
This number, and the Insurance field, is mandatory information.

• Labor union (field SYNCOD)

This field is used to specify the syndicate code corresponding to this work contract.

This field is mandatory if you are a member of a syndicate.

• Number (field SYNNBR)

This field is used to specify the work union membership code corresponding to this work contract.

This information is provided by the work union.

• Tickets restaurant card (field CARTIKRES)

• Contact (relationship) (field RESPO)

• Supervisors (field CHEFCTR)

• Family name-First name (field NAMCHEF)

• Employee ID (field RPL)

Employee able to replace the employee in question in the latter's absence.

• Family name-First name (field NAMSUPPL)

• Comment (field CMTRPL)

It possible to enter the tasks carried out by the replacement in the employee's absence.

• Code (field POP)

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

• Update type (field MAJTYP)

This field, which cannot be accessed, displays the update type for an employee.

Manual update
Manual update means that you have manually added an employee to the population using the Employee selection action or the Others tab of the Employee record.

If the update is a manual process, the employee can only be removed from the population in a manual way.
 This deletion will impact the Employee record.

Automatic update
Automatic update means that you have used the update population functionality (Population update button in the action panel): the employees who meet the membership criteria defined in the Rule field are automatically upload in the table.

If the update is an automatic process, the deletion of the employee from the current population, which is performed in this function or the employee record, is only temporary. To permanently delete an employee from a population group, you should modify the membership criteria, then refresh the list.

• Hierarchy (field LISTHIERAR)

• Accounting information in contract (field FLGCTRCPT)

• If this box is selected, the rest of the tab can be accessed, entered and:
• upon contract creation, the values are initialized with the ones defined for the employee,
• upon contract duplication, the values are initialized with the ones defined in the original contract.
• If this box is not selected, no information is initialized and none can be entered, the tab is erased and grayed out.  
  

According to the value of the CTRCPT - Accounting info in contract parameter (CPT chapter, MIS group), the 'Accounting information in contract' box can be selected or not:

• if the parameter is set to 'Yes': this box, which is not selected by default when creating a new contract, can be selected;
• if the parameter is set to 'All': this box, which is selected by default when creating a new contract, can be selected or cleared;
• if the parameter is set to 'No': this box cannot be selected.

• Private account (field BPR)

The individual account associated with an ID number is used in the following three cases:

 When the payroll MO is calculated, if control accounts are set up in the payroll heading accounting interface.

 When the payment slips are validated, if control accounts are set up in the accounts associated with the payment type.

 When the profit-sharing elements are posted, if control accounts are set up in the accounts associated with the profit-sharing codes.

If this field is entered and an accounting is associated with the folder, this field must match a BP-type account.

• Accounting code (field ACCCOD)

The accounting modifier associated with an employee ID is a code referenced in the Access codes table. An employee-type accounting code, with the form xxx10, and which applies to a 64100 account, will return the 64110 account.

• Distribution key (field DSP)

Use the analytical distribution keys to automatically distribute the amount of a general accounting posting line onto several analytical lines based on weighing coefficients.

The analytical distribution key contains one to ten alphanumeric characters.

• Title (field DSPDES)

• Dimension type (field DIE)

An analytical axis is defined by a code of 3 characters. It corresponds to a particular subdivision of the enterprise for analytical purposes. In fact for a given axis, it is possible to associate a chart of analytical dimensions.

There are 1 to 9 analytical axis available in a given accounting reference as well as a chart of accounts (often called a chart of natures).

A company can use 1 to 9 accounting references (some analytical, some not). The analytical references can share the analytical charts or use different ones. It is the accounting template that defines the combination of references used by a group of companies.

• Dimension (field CCE)

An analytical dimension is an element of the analytical chart of accounts on which accounting entries can be posted.

Each analytical dimension type represents a specific division of the company into a set of analytical payment attributes.

An analytical dimension is thus an analytical payment attribute within a dimension type.

• Initialization (field INICCE)

Specify the default allocation key or dimension for each dimension type. These elements can be used to initialize the analytical time entry and the analytical entry of each salary slip, based on the initialization type associated with each dimension type.

The four initialization types are the following:

Conservation

The analytical allocation is identical to that of the previous payroll.

Cancellation

No analytical distribution

Standard

Default dimension

Time upd

Based on the analytical allocation of the time entered over a given period.

• Backpay (field FLGRET)

• Type (field RETTYP)

• Status (field RETSTATUT)

This field can take the following values:

• 'Inactive': in the case of a standard amendment,
• 'In progress': in the case of an amendment with backpay, the status remains in progress until the creation of the associated backpay record (in the Backpay function),
• 'Validated': when the amendment with backpay has been processed as part of the payroll process. The information in the grid is then grayed out and cannot be modified.

• field RETNUMICO

• Effective date (field RETDATEFF)

Date from which the additional clause to the work contract is taken into consideration.

• Reason (field RETGRD)

• Loading (field LOAD)

This button is used to load the grid containing the fields used for the back-pay.

• Field (field FLD)

The fields that appear in the grid correspond to those fields with their 'Backpay' box selected in the 'Employee field dictionary' function (see the Miscellaneous prerequisites

• Table (field TBL)

• Description (field TIT)

• Period start date (field STRDAT)

The date of the period corresponds to the date previously entered and used as the basis for the back-pay.

• To (field ENDDAT)

• Type (field TYP)

• Payroll dated (field STRPAY)

• To (field ENDPAY)

• Slip (field STRBUL)

• To (field ENDBUL)

• Source (field VALORI)

This variable specifies by default the original values in the various contracts (the original dates or the other values before they are modified for the backpay).

• Destination (field VALDEN)

This variable specifies by default the destination values in the various contracts (the effective dates or the other values after the modification is performed for the backpay).

The destination values can be modified here. These new values are then taken into account for records and calculations.

• Leave cycle type (field LEACYCTYP)

• Leave resume date (field LEARSMDAT)

• Excp. hazardous conditions (field FLGEXCPEN)

If the Excp. hazardous cond in cont box is selected, hazardous work conditions can be managed at contract level.

The Excp. hazardous cond in cont box must be selected in the Positions function, Position hazardous conditions tab.

 Hazardous work conditions are managed by default at position level. Managing hazardous work conditions at contract level is possible but it must remain an exception.

To print the individual record to be provided to the employee, data is read at contract level, not a position level.

• Risk factor (field WPEN)

This field is only available for the French legislation.

The risk factor and the validity start and end dates entered in the Hazardous conditions criteria table are initialized in the Detail block based on the line of the table where you are positioned.

• Validity from (field WSTRDATPEN)

• Validity to (field WENDDATPEN)

• Org. prev. measures (field WPRVORG)

This field is only available for the French legislation.

You can enter comments on the work strain factor (organizational, collective or individual preventive measures, or global comment).

• Coll. prev. measures (field WPRVCOL)

• Ind. prev. measures (field WPRVIND)

• Comments (field WCOMMENT)

• APE/SIC (field NAFWRK)

• APE/SIC (field NAFWRKUSR)

• Legal nature (field WRKNATLEG)

• Legal nature (field WRKNATLEGU)

• Country code (field WRKCRY)

• Country code (field WRKCRYUSR)

• Country name (field WRKCRYNAM)

• Country name (field WRKCRYNAMU)

• Workplace name (field WRKNAM)

• Workplace name (field WRKNAMUSR)

• Additional info (field WRKADD1)

• Additional info (field WRKADD1USR)

• Address (field WRKADD2)

• Address (field WRKADD2USR)

• Municipality (field WRKADD3)

• Municipality (field WRKADD3USR)

• Municipality code (field WRKCODSEE)

• Municipality code (field WRKCODSEEU)

• Postal code (field WRKCODPOS)

• Postal code (field WRKCODPOSU)

• City (field WRKCTY)

• City (field WRKCTYUSR)

• Code (field CODLST)

• Start date (field STRDATLVE)

• End date (field ENDDATLVE)

• Code (field CODLST)

• Start date (field STRDATLVE)

• End date (field ENDDATLVE)

• Employee ID (field REFNUM)

• field SRN

• Contract (field CTRNUM)

• Date of contract (field CTRDAT)

• Back-pay type (field AVTRETTYP)

Select the back-pay type: individual or Exempt.

• Date of contract (field AVTCTRDAT)

This field is automatically populated when the back-pay type is selected. The date of the last activated contract is submitted by default. It can be modified, if necessary.

• Start reason (field AVTCTRGRD)

The reason for the last activated contract is submitted as default.

• Back-pay effective date (field AVTRETDATE)

The start date of the last active contract of the employee is submitted by default.
You need to modify the effective date with a date prior to the last active contract for the backpay to be effective up to this date. The backpay can be applied to several periods of activity for the same contract.

• Reason for back-pay (field AVTRETGRD)

Specify the reason for the back-pay (for example, COR, code for the error correction).