Situations
Warning
This documentation has information that applies only to some modules. Contents that have the icon
indicate each case, position the mouse over this icon and see the description of the modules.
In this option, it is possible to register all situations in which the company's workers are.
Basically, the table is made up by work situations, overtime and absences.
The table of situations is registrable, enabling the user to add or change the already existing situations. It is important to remember that, it is in the table of situations that the important data are defined, as example, for the payroll calculation, vacation, transportation voucher and information for Rais*.
Note
It is in this table that it is determined if the absence or period away will affect the vacation entitlement. The only types of situations that are considered for the deduction of vacation right, as the union specifications, are the types 15 and 17. When the worker is absent on one of these situations, the days will be accumulated and deducted from the vacation right.
Inform the situation sequential code, between 001 and 999.
Codes 01 to 15 are defined according to the situations treated with by the Personnel Management module. The system allows changes and inclusions as the user need.
Report a name for each situation. This name will be presented in all registration windows and reports issued.
Guides
Abbreviation
Report the abbreviation for the situation. This abbreviation can be used in the generation of reports.
Type of Situation
Report how the type of situation registered must be treated by the system. The system presents a list of types of absences already registered.
- For the type of situation 15 (Absences), the system will calculate the hours according to the Loses Monthly Paid Worker Day and Loses Hourly Paid Worker Day fields.
- The situation of type 17 (Situation Evaluation Time and Cafeteria Control) is valid only for the Time and Cafeteria Control module, and has no effect on the Personnel Management module.
Complementary Situation
Inform the complementary situation, daytime or nighttime. The modules are ready to make a differentiated treatment between daytime and nighttime hours. With this, each situation can have a complementary, which will be used to report the hours performed overnight. The complementary night situation must always be greater than its corresponding daytime. That is, the daytime situation is registered with a code lesser than its nighttime complementary. This is because there is no way to indicate to the system which situation is nocturnal and diurnal, and which is therefore, to make this differentiation, the situation of less code will always be considered as daytime. If there is no complementary, inform the situation code itself.
When registering the daytime situation, we it must be informed the code of the night complementary situation and vice-versa.
The situation "005 Daytime Overtime" must be registered, whose complementary situation for night hours is "006 Nighttime Overtime". When registering the 005 situation, the 006 situation must be informed in the Complementary Situation field. When registering the 006 situation, the 005 Complementary Situation must be informed.
The situation of Night Work, complementary to the Daytime Work situation, cannot be informed in the field Situation of Night Premium field, in Calculations > Evaluations > Definitions > Situations".
When registering situations with types 1 - Working or 7 - Laid-off, the system will only allow that complementary situations with the same type be informed. Therefore, when it is registered a new situation of type 1, only a complementary situation which the type is also 1 may be informed, and when registering a new situation of type 7, only a complementary situation which the type is also 7 may be informed .
This field will only be enabled for situations with type 3-Sickness and 4 - Accident Work. Its purpose is to control the calculation in the absence days in different situations.
Loses PLR (Profit Sharing and Results) Inform how the system should proceed for this situation, in relation to the proportionality of the participation values in the PLR module:
- Do not lose to the calculation of the participation;
- Loses proportional, that is, the value corresponding to the days worked;
- It loses the right.
Note
The Personnel Management module does not have handling for this indication, however, the client can handle it via special rule.
Leisure
Inform if the situation in question will be or will not be considered for the Leisure calculation in the profit Sharing Plan module.
Letter Characteristic of Hours
Whenever the type of situation must be entered in any item, it must be indicated which letter of the item feature in which these hours must be entered.
Note
If the user is including an absence situation with type 99 or 15, it may indicate one of the letters available in the features free of diurnal and nocturnal hours, and also create an item to treat this situation:
Features of Available Hours:
01R, S, T, U, V, W, X, Y and Z (Available Hours 01 - 03)
51A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y and Z (Available Hours 51 - 53)
The event should have as characteristic, the same letter indicated in the register of the situation with rule 01 - Hours. The accumulator of salary/hour must be indicated inn the calculation basis.
Length of Service
Inform if the absences in this situation are considered as length of service, including in the calculation of annuities:
- Must be considered as length of service
- It must not be considered in the counting of the length of service.
It Pays Christmas Bonus
Inform if in the checking of the Christmas Bonus fractions payment, this type:
- Consider month worked
- Does not pay the corresponding fraction if 15 days in the month or more.
It loses right to the Vesting Period
Define how the situation informed will affect the vacation right:
| Value | Description |
|---|---|
| To | Loses Right if > 180 Days (Illness Aid); |
| L | Loses Right if > 30 days (Paid Leave); |
| I | Interrupts and Continues in the Return (Military Service); |
| P | You lose the month corresponding to the month (*); |
| N | Does not consider for vacation entitlement calculation; |
- When in the registration of the Employees' Union, Holiday guide, is marked in the field "Holiday Law" = 'Q', you will lose 1/12 avos every 30 days or when it is greater than or equal to 15 consecutive days;
- When in the worker’s Union information,Vacation tab, it is indicated in the Vacation Right field = ‘C’, will lose one-twelfth if within the month there is 15 days or more of this absence.
Situation Valid for Rais
Indicate what type of absence for Rais:
- Considers time worked
- Does not consider time worked for the Rais
Lose the time Indicate how the counting of absence hours for hourly paid must be considered:
| Value | Description |
| N | Do not loses the day |
| To | Loses as the evaluation of the day |
| I | Loses the day as integration with the Time and Cafeteria Control |
| D | Loses as the WPRP hours of the schedule |
Note
Whenever the Personnel Management module is integrated to the Time and Cafeteria Control module, this option must be indicated with 'N' or ‘I’. Otherwise, the item of absence hours will be entered in the movement with the quantity of absence hours of the month and when calculating the payroll, the Personnel Management module will try to deduct again the absence hours, causing the deduction on duplicity.
Lose your day Indicate how the counting of absence hours for monthly paid must be considered:
| Value | Description |
| N | Do not loses the day |
| To | Loses as the evaluation of the day |
| I | Loses the day as integration with the Time and Cafeteria Control |
| D | Loses as the WPRP hours of the schedule |
- Whenever the Personnel Management module is integrated to the Time and Cafeteria Control module, this option must be indicated with 'N' or ‘I’. Otherwise, the item of absence hours will be entered in the movement with the quantity of absence hours of the month and when calculating the payroll, the Personnel Management module will try to deduct again the absence hours, causing the deduction on duplicity.
- If indicating D - Loses the day of absence according to the WPRP of the employee’s Time Scale, the generation of hours will consider for each absence day of the period indicated in Workers > Records > Absences, the quantity of hours according the WPRP hours of the employee’s time scale.
Saturday Compensated
The system does not attributes a quantity of absence hours for compensated Saturday, because it is unaware which would be the quantity of hours to be worked in this day and was distributed in other schedules of the week for compensation.
Thus, if the Saturday in the Time Scale is from the 9998 - Compensated Saturday, on the Saturday which is comprised on the period of justified absences in the record of absences, the system will not consider absence hours for this day. On this account, the adjustment of monthly hours for a Monthly Paid Worker which is done by the Personnel Management module, may find regular hours and WPRP hours to be paid, even if the employee does not have worked days. Therefore, it is recommended that, even for monthly paid, this indication be done with the Letter A - lose the hours of the day, in order that the loss of hours reflects exactly the hours of each day when it did not worked, and at the end do not occur undue payments by the system. It is still important that the time scale be correctly defined with schedules that really represent the hours that each employee works daily.
- Absences of type 15 reported from 12/1 to 12/22, having 3 compensated Saturdays within this period.
- Vacation from 12/23/2011 to 01/10/2012.
- In the generation of hours the system will find the following hours:
01/12 to 03/12 = 3 d x 7:20 = 22 hours
04 (Saturday compensated = 0 hours
05 (lost Sunday) = 7 h and 20 min
12/6 to 12/10 = 5d x 7:20 = 36 h and 40 min
11 (compensated Saturday = 0 hours
12 (lost Sunday) = 7 h and 20 min
12/13 to 12/17 = 5d x 7:20 = 36 h and 40 min
18 (compensated Saturday = 0 hours
19 (lost Sunday) = 7 h and 20 min
12/20 to 12/22 = 3d x 7:20 = 22 hours
|
Total of Absence Hours = 16d x 7:20 = 117 h and 20 min Total of WPRP Absence Hours = 3d x 7:20h = 22 hours |
|
Total of Vacation Hours: |
Total of Month Hours = 117:20 + 22:00 + 66:00 = 205 h and 20 min
Not
e
Because it is a monthly paid, the system will carry out Adjustment for Month Hours from the Time Scale:
Month Hours of Schedule = 220:00h (-) 205 h and 20 min evaluated = 14 h and 40 min
This positive quantity of adjustment hours will be paid as Regular Hours because there is no other type of absence which is not the type of 15, besides the vacation hours.
Important
Vacation Hours and maternity hours are “adjusted” only if there is no other type of absence or regular hours/WPRP being paid in the month.
In the financial statement of the month, there will be the following items:
| Regular Hours =14:40h |
| Absence Hours = 117:20h |
| WPRP Absence Hours = 22:00h |
| Vacation Hours = 66:00h |
Absences of type 15 reported from 12/1 to 12/22, having 3 compensated Saturdays within this period.
Vacation from 12/23/2011 to 01/10/2012.
In the generation of hours the system will find the following hours:
12/1 to 12/3 = 3d x 8:48 = 27:24h
04 (Saturday compensated = 0 hours
05 (lost Sunday) = 7 h and 20 min
12/6 to 12/10 = 5d x 8:48 = 44:00h
11 (compensated Saturday = 0 hours
12 (lost Sunday) = 7 h and 20 min
12/13 to 12/17 = 5d x 8:48 = 44:00h
18 (compensated Saturday = 0 hours
19 (lost Sunday) = 7 h and 20 min
12/20 to 12/22 = 3d x 8:48 = 27:24h
|
Total of Absence Hours = 16d x 8:48 = 140:48h Total of WPRP Absence Hours = 3d x 7:20h = 22 hours |
|
Total of Vacation Hours: |
Total of Month Hours = 140:48 + 22:00 + 66:00 = 228:48h
Note
Because it is a monthly paid, the system will carry out Adjustment for Month Hours from the Time Scale:
Month Hours of Schedule = 220:00h (-) 228:48h evaluated = -8:48h
Usually, the negative adjustment of hours is deducted from the Regular Hours or WPRP Hours, if there is in the month; as there are no Regular Hours or WPRP Hours being paid in the month, the adjustment is carried out in the quantity of hours of the own absence that has been evaluated.
Important
Vacation Hours and maternity hours are “adjusted” only if there is no other type of absence or regular hours being paid in the month.
140:48h absences (-) 8:48h = 132:00 absence hours in the month.
In the financial statement of the month, there will be the following items:
- Absence Hours = 132:00h
- WPRP Absence Hours = 22:00h
- Vacation Hours = 66:00h
- Total of Hours = 220:00
Loses WPRP
Report if the absence generates loss of weekly paid rest period.
Note
Whenever the Personnel Management module is integrated to the Time and Cafeteria Control module, this option must be indicated with 'N'. In this situation, the missing-hours event will be posted in the move with the number of missing hours of the month and when calculating the sheet, will discount the correct value. Using the 'S' option when there is integration with the Point Control, the Personnel Administration will try again to discount the missed hours, resulting in double redundancy.
Loses Transportation Voucher
Determine if the days corresponding to the absence must be disregarded in the distribution of the Transportation Voucher.
Note
When the Transportation Voucher is treated by a fixed quantity in the month, the system does not make any reduction in relation to the absences or about the Calculation Basis reported in the item information, because fixed means fixed.
Lost Vacation
Inform the system if the situation in question must or not be considered in the vacation right. This indication is valid for the type of situation 15 - Absences, where the user can choose if there will be or not the deduction of these absence days of the vacation right, according to what has been defined in the worker’s Union information.
For the Point and Dining Control, inform if, when this situation occurs, the system must carry out a schedule of absence absence for loss of vacation. The table of vacation right, according to the quantity of absences, is registered by the Personnel Management module, in Tables > Unions > Information, Vacation tab.
In order to make the programming, in the register of the situation in the Personnel Management module, the PerDih (Loses Day Hourly Paid Worker) and PerDim (Loses Day Monthly Paid Worker) fields from the Situations table R010SIT), must be equal to N - Does Not Lose the Day.
For workers with type of salary different from Hourly Paid Worker, it will be considered the PerDim (Loses Day Monthly Paid Worker) field. The PerDih (Loses Day Hourly Paid Worker) field will be considered only for Hourly Paid Worker.
- S - This situation must be listed in the report of occurrences, that is sent to the managers.
- N - Must not be listed.
Usually the overtime and absences situations are considered as exceptions because the leadership must make a decision about them (paying or not paying the overtime, deducting or not deducting the absence).
The situations of absence, vacation, normal work and night premium, generally are not considered as exception, because the leadership does not need to make a decision anymore.
If the situation is considered as exception, on the window for worker's adjustments, a "x" will be shown on the date on which a situation of exception has been evaluated. Being that the user can set the window to show only the dates with exception situations.
Skip Tags It is used in the schedules of absence, so that the Time and Cafeteria Control module ignores or not the clock in/out carried out during the period programmed in this situation.
Its use is more frequent when the worker is on vacation.
When using the Time and Cafeteria Control module - Decree 1,510, this field is enabled.
Converts Nocturnes
Inform 'Y' if this situation must be converted into nightly hours, dividing its value by 52,5 minutes and multiplying by 60 minutes. For this option to be respected, it is necessary that the field Daytime Situation with "N" option selected.
There is an indication in Calculations > Evaluation > Definitions > General, that indicates if the conversion of night hours must occur at the beginning or only at the end.
Round Nights Inform 'Y' to round the nightly hours converted. The rounding will be default, always by truncating the value.
| Total amount of hours | Nighttime hours | Converted (with rounding) |
|---|---|---|
| 6 minutes | (6,857) | 7 minutes |
| 5 minutes | (5,714) | 6 minutes |
| 3 minutes | (3,428) | 3 minutes |
| 2 minutes | (2,2857) | 2 minutes |
This field is available only when the It Converts Nightly Hours field is equal to 'Y'.
Block Access Inform if it must block the worker when it is absent in this situation. I will also block the registration of records for temporary and holders ID cards during the period that the worker is absent.
The worker is absent on vacation, so it cannot have access to the company.
When using the Time and Cafeteria Control module - Decree 1,510, this field will not be enabled. In this case, the Generation of Lists will not check if a specific situation blocks the access, the only situation that will block is the Laid-off situation.
Inform if the deadline for hour bank compensation must be extended, when the worker is absent in this situation:
- Y - Yes - The deadline for hour bank compensation must be extended when the worker is absent with this situation on the limit day for compensation.
- N - No - It does not extend the deadline for compensation when the worker is absent in this situation.
- This indication will be visible only if the hour bank information is informed as 'Y' in the Extend Absences field.
- For more information about the calculation of the hour bank extension, see the Manual of the Extend Absences field, in the Hour Bank information.
Required Match Reason Indicate if the system must obligate the user to inform the adjustment reason when including this situation on the adjustments window on the date. When informing 'S', the system will not allow the recording of changes without informing the corresponding reason.
This field will be visible only if it is informed 'Y' in the Control Adjustment Reason indication, in general definitions of the calculation.
Days Block ID Card
Report the quantity of days to block the ID card after the absence beginning. This field is available in the Situation register only when the Personal Administration or Point and Dining Control modules are integrated with Access and Security Management.
In the Administration of Personnel the field also exists in the Register of Causes of Resignation. In this case, firstly, the system considers the value informed in the Lay-off Cause; if zeroed or null it considers the value informed in the absence situation register.
The quantity of days to block the ID card is defined only in situation of type 7 (Laid-off), this value will be considered for all lay-off causes which the Days Block ID Card field be zeroed or null. However, if the customer does not want to block ID card on the transfer of branch, it must to inform Days Block ID Card only in lay-off causes, because the situation of type 7 is also used in the absences by transfer of branch with change of ID number and transfer of company.
Control Extension From this option, it will allow the user to indicate if the current situation allows or not to register extensions in the Extension folder, which will be demonstrated in the absence record.
Note
The extensions reported on this window are informative only. The Personnel Management module does not handle them in any of the system routine.
Loses Holiday
Inform if the absence will result in the loss of the holiday occurred in the same week:
- Do not Lose
It will not be deducted the holidays of the absence week, and they will continue to be paid as WPRP Hours; - Loses Holidays After Absence
Only the holidays posterior to the absence will be deducted. - Discard all existing holidays in the week of absence
- Week from 8/12/2002, being that in 8/14/2002 it is holiday:
The worker will lose only the holiday in question, if the absence occurs on 8/12 or 8/13; - Week from 8/12/2002, being that in 8/14/2002 it is holiday:
Regardless of the day of the week that the absence has occurred, the worker will lose the holiday from 8/14.
Note
Whenever the Personnel Management module is integrated to the Time and Cafeteria Control module, this option must be indicated with 'N'. In this situation the item of hours will be entered in the movement with the amount of absence hours of the month and when calculating the payroll, the Personnel Management module will try to deduct again the absence hours, causing the deduction on duplicity.
Loses Salary Advance
Inform if the system must make proportionality in the value of the salary advance, when this situation occurs in the month:
- Make the proportionality of the salary for the salary advance
- Calculate the salary advance fully
Note
This indication is not valid for type of Situation 22. The handling of this situation must be done in the Table of Items, using the absences exceptions.
Lost Special License Inform how the system must proceed to this situation, as the counting for the loss of the special leave:
| Value | Description |
| I | Interrupts the period |
| F | Sum in the Total of Absences |
| P | Sum in the Total of Loss |
| R | Loses Period |
| N | Does Not Consider |
- When indicated ‘I’, the total number of days that the worker was absent, will be projected at the end of the vesting period.
- Previous Acquisition Period: 01.01.98 to 12.31.98
- Pitch: 01.06.98 to 06.10.98
- Posterior vesting period: 1/1/98 to 1/10/99
- When indicated ‘R’, if finding an absence with this option, independently of the quantity of absence days, the period of special leave will be paid due to lost (Type 5), not changing the Beginning or End Date of the period.
Lost Assiduity Indicate how this absence will be treated in relation to the entitlement to Assiduity days:
- It must add up in the count of the absences that he loses for attendance;
- The days of departure will not be considered for the calculation of the days.
Loses Retirement
Indicate how this absence will be handled in relation to the retirement (Workers > Retirement > Counting of Time):
- The days of removal in this situation will negatively influence the counting of days worked for Retirement purposes.
- The days of removal in this situation do not influence the counting of the days worked, for purposes of Retirement.
Return Examination
Indicate if when returning from absence, a return examination will be required.
Note
When in the absence registration, this data will be automatically transferred to the window of absence record.
Consider Absent Headcount
This indication determines if, when the worker is in this situation, the headcount must or not be counted in the Absents column.
Headcount Grace Period Days
Indicate the grace period before leaving the vacancy.
Important
After the period reported, the absent workers are disregarded in the headcount count.
After 45 days, employees in sick leave should be disregarded in the frame count.
Generate Stability
Indicates if the absence due to this situation must generate stability record. All options different from N automatically generate a stability record in Workers > Records > Stability.
| Value | Description |
| R | The calculation for the end of stability days is done according to the quantity of months reported in the Stability Days/Month field. |
| N | Does not generate stability record. |
| M | The calculation for the beginning of stability days is done according to the quantity of months reported in the Stability Days/Month field. |
| I | The stability beginning date is the beginning date of absence. The Stability Days field is enabled for indicating the quantity of days in which the worker will be under stability. |
| F | The beginning date for stability is the first day after the absence end date. The Stability Days field is enabled for indicating the quantity of days in which the worker will be under stability. |
| To | The stability beginning date is the first day after the absence end date and the quantity of stable days is the total of absence days in the situation indicated or the value reported in Maximum of Stability Days, if filled out. |
Stability Days
Report the quantity of days that will be used to establish the stability period.
Note
For absence of type Labor Accident, the stability will be generated only if the Justified Days field, which is in the record of absences is less than the absence period.
Type
Indicate the type of stability for this situation.
Report the quantity of days when the Generate Stability field has the A indication.
Record Payroll Report if the distances with this situation will be demonstrated on the "Departures" Record Payroll fabric, available in Employees > Concierge > Registration Payroll 41.
Note
According to the ministerial order MTE No. 41, March 28, 2007-I 3/30/2007, it is necessary to demonstrate the distances from for vacation and work accident and occupational diseases. But the user can perform the definition of its base, through this indication.
Calculates Teacher WPRP
The "Miss DSR" and "Missing Holiday" fields will not be used in the teachers' new teacher count. Thus, from this field the user will indicate in the situations whether to calculate the reflection of the DSR or not. When reporting option N - No, the system will pay the WPRP hours of this situation in a situation which calculates WPRP.
Teacher absent for 15 days by reason of absences. If the situation is indicated for not calculate WPRP (N option), in the payroll, the value of the WPRP in the month will be fully paid in the Worked situation, without damages. However, if it is indicate to calculate WPRP (S option), the system will demonstrate these hours in the item of WPRP Absence Hours, decreasing the WPRP payment item.
Note
This field is used only if the Teachers field indicated in the Company informationwith options 'P' or 'S'.
Report if the selected situation will be used in the absence monitoring (Medicine > Services > Absence Monitoring).
- Yes, this will be used in the leave monitoring screen
- This situation will not be used
Show Situation to Workflow
If it is informed 'Y' in this field, the situation will be viewed in flow of the absence record. Otherwise, it will not be displayed. This treatment may also be used in other flows that have the Situation field, and for this, it is necessary to make the adjustments in the PesquisaWF function of the respective flows.
Report if the selected situation will be considered in the inclusion of participants in training groups (Training > Groups > Define) and Items (Training > Items > Define Items).
- Yes, the employee who is in this situation of withdrawal may participate in training and events;
- No, when reporting an absent worker in this situation, in the definition of groups or items, an alert will be presented to the user about the worker absent condition.
Deducts Union Contribution
Defines the handling of the module for union contribution in Situation:
- Discounted
- Do Not Deduct, where the system checks in the month all situations that the worker had. If the sum of the days is equal to 30 days, the union contribution will not be discounted.
- Do Not Consider Situation, which must be used for situations that do not influence for counting the absence days. Examples: situation type 11 (Paternity Leave), type 16 (Extra Hours), type 17 (Situation Determination Round), type 99 (Other);
Loses Union Proceeds
Defines if the union proceeds must or not be lost for this absence situation.
Daytime Situation
Field available only when there is integration with the Point Management module.
Color for the Situation
Set the color for displaying the situation on the time bank posting screen in the Point Management module.
Absenteeism It defines if the situation considers or the absenteeism (Act to be away or absent of a function). The field has the following options
- 1 - Does not consider;
- 2 - Considers - Worked hours;
- 3 - Considers - Unjustified absences;
- 4 - Considers - Justified Absences (except medical certificate);
- 5 - Considers - Justified Absences (medical certificate).
The Absenteeism field will be available only when the user has the Time and Cafeteria Control and BI modules in the license file.
Obligatory attachment to remoteness
Determine whether the inclusion of an attachment to a removal history is mandatory.
Field available only when there is integration with the Point Management module.
New Registration Button
By clicking this button, the system will initiate the registration of a new situation, always suggesting the lowest available code and placing the focus in the field of the situation description.
Warning
This documentation applies only to the module: AP.
Period
Report validity period for Letter of SEFIP* Movement.
Home Code Inform the SEFIP Movement Code, appropriate to the current situation, indicating the beginning of the employee's departure. This code will be considered for generating the Sefip.re text file - register 32, field 10, position 124-125.
Return Code Inform the SEFIP Movement Code appropriate to the current situation, indicating the termination of the employee's departure. This code will be considered for generating the Sefip.re text file - register 32, field 10, position 124-125.
Start Code <60 Days Inform the SEFIP Movement Code appropriate to the current situation, indicating the beginning of the employee's departure. This code will be considered in the Sefip.re text file generation - register 32, field 10, position 124-125.
Note
Field valid only for situations 03 (sickness benefits) and 04 (accidents at work).
Return Code <60 Days Inform the SEFIP Movement Code appropriate to the current situation, indicating the termination of the employee's departure. This code will be considered in the Sefip.re text file generation - register 32, field 10, position 124-125.
Note
Field valid only for situations 03 (sickness benefits) and 04 (accidents at work).
Code Home Extension Inform the SEFIP Movement Code appropriate to the current situation, indicating the beginning of the employee's departure. This code will be considered in the Sefip.re text file generation - register 32, field 10, position 124-125.
Note
Field valid only for situations 06 (maternity aid) and 19(INSS* maternity aid).
Warning
This documentation applies only to the module: AP.
Period
Report the validity period for the worker’s Absence Reasons, in the Rais*, during the basis-year.
Code
Report the RAIS* Absence Reason corresponding to the absence in question.
- This option is necessary because Rais requires that the 3 major withdrawals occurred during the base year be informed.
- When the situation is indicated with N in the Situation Valid for Rais* field, the following message will me issued: “This page can be accessed only when the situation is valid for Rais*”.
Warning
This documentation applies only to the module: AP.
Period
Report the validity period for the eSocial Absence Reasons.
- This tab is available for all modules, since the module is integrated with Personnel Management module;
- During the termination of an Assigned Server, to attribute code 33 - Assignment to a worker in RAIS* generation, the eSocial Reason field must be reported as 16 - Assignment of Worker. The system will identify these type of absence and will perform the due conversion, presenting code 33 - Assignment, for the RAIS*.
ESocial reason Among the options in the list, indicate whether the reason for the removal should not be sent to eSocial or, if sent, select the reason. This information is used to generate layouts
If the reason for the eSocial is "1 - Accident / Work Sickness", it is not mandatory to fill in the fields Days Forecast and End Date (Contributors> Histories> Clearances (FR038AFA)). If these fields are left blank, the tag qtdDiasAfast of the S-2230 layout will be reset to zero.
Send eSocial Remarks Enter whether you want the field Note
, from layout S-2230 - Temporary Removal, be informed to eSocial.
- This mark is valid for the screens History Past (Collaborators> Historical> Departures) and Historical Assignment (Employees> Historical> Assignment), when generated the eSocial file;
- If the eSocial reason is "21- Unpaid or Unpaid Leave", the fieldNote is mandatory in eSocial, with no possibility to change it.
English
Español


