Items
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 topic, make the registration of all items required for calculations. This screen is only available for modules: AP, BS, CP, PLR and TR.
Concepts by module
Personnel Administration and Benefits
All proceeds, advantages and deductions calculated in payroll, must be linked to an item. The items are the basis for all calculations of the system, be they monthly payroll, rescission or vacation. If there is no information of the item or when it is not correct, the calculation is not done or it is done incorrectly.
Important
People Management | HCM uses the event log to generate and send the rubrics to the eSocial layout S-1010. These events belong to the code table 941, which is the system default event table. Therefore it is not necessary to register new events for this purpose.
For example, when it is necessary to take to the eSocial the items related to payment of holidays due and / or proportional due to a termination, the Senior system makes the necessary treatment through the following events:
- 172 - Vacation Terminated Termination (feature 13A)
- 192 - Holiday Rentals Termination (characteristic 13B)
When launching these events on the fly to some collaborator, during the generation of the layouts the system takes care of taking this information to eSocial in the XML file, considering the nature of 6006 (proportional holidays) and 6007 (expired holidays) 03 of eSocial.
Time and Cafeteria Control Module
Items are monthly accumulators of quantity of hours from the evaluation, quantity and values of meals, quantity and values of requests and ID card values, used in the integration calculation.
In each item it is necessary to define if the value will be generated, quantity or hours, considering the purpose of each one.
In the Item information there are attributes and parameters that will define the way on how to generate the values for payroll. The items cam be associated to situations to accumulate the absence hours, overtime, work hours, compensated hours and justified hours that must be generated in the integration according to what has been calculated in the evaluation. But the items may also be associated to the control of ID card vias, to the hour bank, to the routine of requests, to the meal registration, and to the definitions of integration for the calculation of hours for monthly paid workers, hourly monthly paid workers, calculation of weekly paid rest, loss of rest, be treated directly in the rule of final calculation, among other cases.
The items are grouped in a table, so that they can be associated to companies, because there may be a different table of items for each company.
It is common that the closing of hours in the evaluation be done before carrying out the payroll calculation. Therefore, the companies opt by having a period for payroll calculation and another period for time evaluation.
Payroll period: 4/1/2004 to 4/30/2004
Period of time evaluation: 3/26/2004 to 4/25/2004
Therefore, the company has some days to process a payroll, however, the period from 4/26/2004 to 4/30/2004, has not been processed yet . To calculate these hours, the system makes a projection in the integration calculation, taking into account the forecasted schedule for theses days, It is usually projected working hours, weekly paid rest period (WPRP) and absences hours. And it is in the register of each item that it is indicated if the hours will be projected.
The item is comprised by a code that must be in accordance with the code used by the payroll, independently if the payroll is Senior or not, and who provides the code and defines its use is the who administrates the payroll.
For example, for hours of vacation absence, the payroll system will generate the vacation receipt and with that, it automatically generates the absence record. As the vacation are previously paid, the hours related to this absence are generated before the evaluation process in the Time and Cafeteria Control module. With this, the company may opt so that the item that accumulates vacation hours in the Time and Cafeteria Control module does not generate hours for payroll. For this, there is an indication in the item information. Despite the hours are calculated, they will not be generated for payroll.
The time processed in the evaluation calculation are not always passed on to the integration calculation in the same quantity. A practical example is the absences, which can be generated in accordance with what was established in the evaluation or it can be made an average of hours and calculated according to the WPRP of the schedule. Usually this calculation is carried out for the monthly paid workers, which can work 8:48 hours in the day, but when they are absent the calculation is made from the quantity of WPRP schedule hours multiplied by the number of absence days. This treatment is also set in the item information.
Key fields
Enter a code to identify the table of items.
Code and description of the event in the payroll. If the Time and Cafeteria Control module is not integrated to the Personnel Management module, the items with codes from 0001 to 5999 can be registered. Otherwise, the numbering goes up 8999.
Guides
Full Description
Enter the full description of the event to be registered. The information in this field will be used in the reports of Tables> List> 011 - Events - Complete (FPTA011) and Companies> List> Cadastral> 012 - Rubrics - Complete (FPEM012). In the latter case, if the Full Description is not filled, the information entered in the field will be considered. description.
If the payroll system has alphanumeric codes, fill out this datum by using up to 10 positions. Otherwise leave it blank.
The daytime hours and nightly hours units, send the item in hours. The difference between them occurs when item decrease from normal hours, indicating if it will reduce from the normal diurnal or nocturnal hours.
- H - Daytime hours, sends the item in hours
- N - Nightly hours, sends the item in hours
- V - Value, sends the item in value, with two decimal places
- Q - Quantity, sends the item without convert into hours or value
The unit Q can also be used in the item of Cafeteria to send the quantity of meals consumed.
Each item has a feature to be indicated. It identifies the type of item information: If it corresponds to normal hours, overtime, payable values or to be deducted, etc. It is mandatory to report a feature, because many procedures are based on it, for example, time evaluation, average calculations, annuals, etc.
The features of items that are available to the users are (click the link for further information):
13th Indemnified Salary Termination (+ 1/12 avos)
Christmas Bonus in advance
Full Christmas Bonus
13th Salary Proportional Termination
Vacation Pecuniary Bonus
Notice Indemnified
Previous Notice Reavid
RRA Calculation Base
13th Salary Discounts
Holiday Discounts
Union Discounts
Previous Leaf Discounts
Tax Returns
Previous Leaf Discounts
Return Family Salary Discount
Days
Stability Termination
Short Breaks
Holidays Indenizadas
Vacation Termination
13th Salary Discounts
Stability Termination
Vacation Termination
Termination Bonus
Daytime Hours
Overtime
Nighttime hours
Taxes
RRA Taxes
Indemnification End Early Contract by the Company
Indemnity Contract Ended Advance by Employee
Indemnification Previous month Resolution - Termination
Indemnification Time Prior to FGTS Option - Termination
Net Payroll
Others
Other Deductions
Other Earnings
Profit sharing
Alimony
Executive Officers
Closing Closing of the Sheet
Termination Proceeds
INSS Proceeds
Delivery / Returns URV
Maternity Salary
PIS Value Transit
Legal Benefits
When type 02 (proportional to working hours) is informed in the calculation basis of certain events, the module will search the number of hours generated in events that have the "S" mark in this field. If the hours generated in the event are not to be considered useful, indicate "N" in this field.
For each event it is necessary to indicate a rule. It identifies the calculation formula to be applied by Personnel Management module. The Personnel Management module has a series of predefined rules that meet most types of existing calculations in the companies.
When there is no predefined rule to meet a user's specific need, the module introduces the special rules creation feature through a special routine in the Resources> Deployments> Rules Editor. The number to be reported will be, therefore, the same as the rule elaborated oin such item.
Indicate the type of event in question:
- Proceeds, corresponds to a payment amount.
- Advantage, corresponds to a payment amount but without charges.
- Discount is equivalent to a discount event.
- Others, is not a benefit, advantage or discount, and may be a value to be dealt with in some calculation rule, accumulator etc.
- Other Proceeds, will be included in the envelope in the earnings column.
- Other Discounts, will appear on the envelope in the discounts column.
- Event has normal handling by module rules.
- Has differentiated handling, in relation to the rules.
This option is used to associate the event with a group of collaborators. This association is carried out by indicating in Employees> Cadastral File> Employees, folder Selection, the code registered in the following field. In this data, must have the plus signals, in order to consider only the workers who have indication of such selected code, or minus signal, where only workers who did not have such selection code will be valid for the item.
Indicate, when informed (+) or (-) in the previous field, a selection code that will be associated with the employee to receive or not a certain event. To exemplify, it is possible to mention an item of Premium or Fund for Handling Losses. This item will be paid only for certain workers, then, indicate a number in the item selection indicator with plus selection signal and parametrize the employee register.
If desiring to restrict the item calculation for workers bonded to a certain Union, report the code for this Union in this field. The Unions are registered in Tables > Unions > Information.
Note
Watch out! This data is not limited to a type of item. If reporting an union for an item of Regular Hours, for example, the system will calculate such item for workers who have record of this union.
Data that must be combined with the type of item feature. It can refers to a percentage or any other datum necessary to a calculation rule. In the items of overtime, for example, it is indicated the percentage of overtime time to be calculated.
Whenever necessary to limit the module calculation to a cap, the cap value must be used in this field.
Some rules give other handling to the Item Cap. They are:
| Value | Description |
|---|---|
| 03 | Calculates the average through a Record of Wprker’s Premiums, that is, it averages the Percentages and Hours. The system will search for the better average in percentages and hours, for example, can find the best percentage in 6 months and in hours in 12 months or vice-versa. |
| 09 | Overtime - If cap > 0, makes proportionality; |
| 19 | Paid Special Leave - Cap 0 = Payroll Calculation; 1 = Vacation Receipt; |
| 23 | Alimony - The number reported in the Cap indicates how many times the alimony will be recalculated; |
| 25 | Family Salary - If cap > 0, considers the quantity of days in the month; |
| 26 | INSS - Cap = 1, does not calculate INSS on the Christmas Bonus related to the maternity period in the year; |
| 27 | IRRF (**); |
| 29 | Hazard (*); |
| 30 | Unhealthy (***); |
| 32 | Salary Advance - If cap = 1, rounds the item value; |
| 34 | Average of Premium 1 and 2 - Cap indicates if the average will be from Premiums 1 or 2; |
| 45 | Value reported Vs. Calculation Value - If cap > 0, makes proportionality; |
| 47 | Premium of Function - If cap = ), makes proportionality of worked hours; if cap = 1; does not make proportionality; |
| 48 | WPRP Teachers - Cap 0 = Activities and Subjects; 1 = Activities and 2 = Subjects; |
| 50 | Additional Night (*); |
| 51 | Additional Posto - If ceiling = "0", does the proportionality of hours worked; if ceiling = "1", does not proportionality. |
| 64 | Base x% Informed x Vlr. Calc. If ceiling> 0, it indicates the original event to search for fixed events. |
(*) For these rules, the system has three different calculation ways:
- It pays for the average if it has no current right;
- Pay only by the average (does not consider the current right);
- Does not pay average, only the current right (if there is).
(**) If the item has Rule 027 and Feature 40E, the item for Deduction of Vacation Advance can be calculated in two ways, according to the Calculation Cap. For more information, check out the Holiday Down Payment help.
(***) For this rule, the system has the following calculation methods:
- It pays for the average if it has no current right;
- Pay only by the average (does not consider the current right);
- Do not pay average, only the current right (if you have one);
- Calculates the average through a Record of Wprker’s Premiums, that is, it averages the Percentages and Hours. The system will look for the best average in percentages and hours, for example you can find the best percentage in 6 months and in hours in the 12 months or vice versa;
- Default HomologNet.
Enter the accounting CLC code corresponding to this event. The AECs must be registered in Companies > Accounting > Register AEC. Only the AECs which have Basis Type = E - Items will be available in this field.
Note
This item can be left with zeros and can be determined later, according to the accounting definition, through the option Companies > Accounting > Indicate AEC, which brings a column with the items and another column which allows to indicate the AEC corresponding to each one.
Indicate how the event will be considered in prorated sheet calculation:
- Does Not Makes Apportionment. The apportionment will be entered in the worker’s default apportionment, unless if it is in a different accounting code. The posting overlaps the event flag.
- Concept of Default Calculation of the Personnel Management Module This option is used only in working hours items, whose calculation of the apportionment cannot be changed. The possibility of choice in calculating the apportionment is limited to additional items, items that follow the apportionment of working hours.
- Considering the reference of items. The generation of the apportionment of events will be done based on the reference in hours of the business hours events.
- Based on the item values. The apportionment of the items will be made based on the value of working hours.
Worker of Teacher Type (Type of Contract = 10):
| Items | Reference | Value | Apportionment |
|---|---|---|---|
| Concentrated Classes | 25 | 412.50 | 10400 |
| Post-graduate Classes | 18 | 247.50 | 10300 |
| Undergraduate Classes | 18 | 188.10 | 10200 |
Using the R option:
Triennium 32,79 - apportionment 10200
Triennium 32,79 - apportionment 10300
Triennium 33,88 - apportionment 10400
Using the V option:
Triennium 32,10 - apportionment 10200
Triennium 32,76 - apportionment 10300
Triennium 34,60 - apportionment 10400
Note
Only there will be differences between ' R ' and ' V ' options when the items of working hours have the same reference in hours, just with different values.
This field has been created to meet the need for a collaborator who has Type Contract = 01 and has 'A' in the field Teacher Assessment in Employees> Teachers> Teacher> Maintenance, that is, is treated by the system as a normal collaborator and also has additional events of teacher hours in calculating the sheet. Indicated how calculation of the apportionment for items of these workers will be.
- All. Consider the apportionment of items generated worker and teacher.
- Worker. Consider only the apportionment in worker items.
- Teacher. Consider only the apportionments generated in teacher events.
Indicate how the event will be treated in the calculation of the remuneration of Caged and CD Communiqué:
- P: Value of proportional item. The value will be divided by the quantity of worked days and multiplied by 30 days, that is, if the value will be projected as if the worker had worked all the month long. The system will:
- search for the month hours in the employee's time scale;
- divide the value of the event by the reference in hours of the calculated business hour event;
- multiply the result by the month hours.
- search for the month hours in the employee's time scale;
Note
For workers who are hourly paid, this calculation will consider the parameter indicated in the field “Monthly Salary of Hourly Paid Worker”, in the company information.
- V: Value of item. The amount will be added to the remuneration without effecting any proportionality.
- N: Do not consider for the compensation of Caged.
This field will be released for completion only when the active event has a Holiday feature and in the Company record is indicated 'S' in the field Positive / Negative Difference. It is used to indicate the item code which will receive the recalculation positive difference of this vacation item in the integration of the Vacation Receipt with the Payroll, if there is. (See note about Positive/Negative Difference, right below:)
This field will be released for completion only when the active event has a Holiday feature and in the Company record is indicated 'S' in the field Positive / Negative Difference. It is used to indicate the item code which will receive the recalculation negative difference of this vacation item in the integration of the Vacation Receipt with the Payroll, if there is.
Note
About the Positive/Negative Difference:
- Whenever the worker has absence due to Vacation in the month, these hours will be integrated in the Payroll. At this moment, there will be a recalculation of receipt, evaluating the eventual differences due to variable values or salary changes. By definition, this difference is entered in the sheet of items, with Feature 11I (Vacation Difference) or 42D (Vacation Negative Difference), 12F (Allowance Difference) or 42E (Allowance Negative Difference), by the total of the difference found in all vacation items calculated in the receipt.
- For users who wish to calculate a difference event for each Holiday event, the fields Positive / Negative Difference in the company register and Positive Difference and Negative Difference in the event register.
- When in the company register is marked 'N' in the field Positive / Negative Difference, the system will use the standard events (with characteristics 11I, 42D, 12F and 42E) to cast the differences found. When indicated, ' means that the Personnel Management module must always determine the differences in item of difference indicated for every holiday item. For this the system will release the fields Positive Difference and Negative Difference in the registration of the Vacations events.
- These item of Positive/Negative Difference does not need Special Rule or Vacation Feature, because the simple fact to indicate it in the Company which uses positive/negative difference and report an item code in specific fields, already makes the system knows that it must put the difference of the vacation recalculation in these items. The advantage of these difference items have vacation feature is that, the value in the monthly payroll will be handled, in fact, as vacation.
Indicate how the event will be treated in the calculation of the remuneration of the PAT (Worker's Food Program) to be considered for Rais:
- Value of proportional item. The value will be divided by the quantity of worked days and multiplied by 30 days, that is, if the value will be projected as if the worker had worked all the month long. The system will:
- search for the month hours in the employee's time scale;
- divide the value of the event by the reference in hours of the calculated business hour event;
- multiply the result by the month hours.
- search for the month hours in the employee's time scale;
Note
For hourly employees this calculation will consider the parameter indicated in the field Monthly Salary
in the company register.
- Item Value. The value will be added to the remuneration without carrying out any proportionality.
Does not consider for the remuneration of the PAT.
For information on this field, click here.
Inform 'Y' if the hours calculated in this item must decrease the normal hours item, otherwise, inform "N".
If the item is of type "H" it will decrease from the daytime hours item, if it is of type "N" it will decrease from the normal nightly hours item.
This indication will be considered only for workers in the following situations:
- Monthly Paid Workers - They have the closing by the amount of days in the month ( Generation of hourly paid workers field, informed as "M") in the registration of the Union.
- Hourly Paid Workers - They have the closing by the schedule ( Generation of hourly paid workers field, informed as "E"), and normal hours will not be deducted.
Inform 'Y' if this item must be considered for the calendar month, by projecting the hours until the last day of the month. This option can be used for items of normal hours, absences, and the night premium.
It can be used for companies with periods that do not start on day 1 or that start on day 1 and carry out integration before the last day of the month.
When desiring to project normal hours, it is recommended that both the normal hours item as absence item and night premium, have the same value in this field ('Y' or "N"), but they be the same.
Items 1 and 2 (normal hours) and the items 56 and 57 (certificate), with project = 'Y'.
It defines how the item must be generated for the payroll:
- If the item is zeroed, it must not be generated
- Always generate the item, even when it is zeroed
- If the item has values, it must be generated with zeros
- Never enter in the movement, only used in the rules.
Notes
Whenever the Time and Cafeteria Control module is integrated to the Personnel Management module, this field must be indicated with "2". Thus, when the integration is performed via the menu Calculations > Integration > Calculate, the system will always integrate the item, even if there are not hours to be integrated, the item will be generated zeroed, making it impossible for the Personnel Management module calculate any value based on the payroll period.
If the modules are integrated and this field is marked with option "4", it is still necessary that the event has the respective situation informed in the Situations tab of this screen. With this the event will not be integrated, however, the Point Control and Dining will consider these hours to calculate the other events that, in turn, will be integrated.
The periodicity of limits is defined in this field, and may be:
- M - Monthly
- S - Weekly - For that the calculation be automatically processed, use the monthly periodicity, because the weekly periodicity is not released.
Start Validity Period and End Validity Period
These fields define the interval time in which the item is valid. They can be used for the payroll calculations, rescission, vacation, entry of items, and integrations with other modules as Time and Cafeteria Control, Benefits and Skilled Workers, and Legal.
Please provide a note about the event. The content of this field is used for filling out the Legal Basis field of the FPAF010.COL model (TCE_4960 - Advantage/Deduction Table and Totalizers).
Warning
This documentation applies only to the module: AP.
Enter the date of change of incidences by employment relationship.
Sequence
Enter a sequential code that will allow you to report different link ranges with the same change date.
Scope Link
Enter the link codes, which will respect the incidents indicated during the calculation processes. When working with range of binding, it is necessary having another sequence, on the same date, indicating to each type of binding which are the valid incidences.
Item ‘X’ with incidence of Monthly INSS from 1/2010 only for workers with binding 10, we would have the following records:
- 1/2010, sequence 01, Range of Binding = 10
- 1/2010, sequence 02, Range of Binding = 1599
In this field the nature of the event incidence for the eSocial is defined. To consult the natures, use the Table 3 - Nature of Payroll Rubricas*, available in the eSocial Manual.
When there is an eSocial nature of type "9219 - Medical or dental care discount", there must be a discount recorded on the Change Health Plan Discount screen (FR051SAC) (Annual> Report / Dirf> Change) for correct generation of eSocial S-1200, S-1202, S-2299 and S-2399 layouts.
Indicate whether or not the event should be added to the calculation accumulators 9011 and 9012, which can be used in calculations of types 11, 21, 22, 23, 41 and 42.
Considers for Averages
This field makes possible to inform the system if the item must or not be considered in the calculation of averages. By reporting "N - No", the following fields are disabled: Average Val.Variables, Average Additional 1 and Average Additional 2.
Values Variable Values
When "S - Yes" is entered in the field Considers for Averages, this field will be able to inform you:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
When "S - Yes" is entered in the field Consider for Means, this field will be able to inform you:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
For information on Additional Mean 1, check Rule 34 - Additional averages 1 and 2.
When "S - Yes" is entered in the field Consider for Means, this field will be able to inform you:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
For information on Additional Mean 2, check Rule 34 - Additional averages 1 and 2.
For the following conditions, the value of this field should always be "Yes":
- The item is on the base (with plus signal) of any item with WPRP feature (05C, 05D, 05E, 05F, 05I, 05L)
- The item has feature 39D and rule 2
When changing this field from Yes to No, in case such conditions are parametrized, the system alerts that “This item should affect in the WPRP calculation according to its configurations and use. Are you sure you want to continue? ". When clicking Yes, it is possible making the change, but it can cause inconsistencies in the eSocial. When clicking No, the field is with the value adequate to the situation.
For the following conditions, the value of this field should always be "Yes":
- Considers per Averages field equal to Yes
- The item on this base (with plus signal and TipBas = 30) of any item with rule 36, 38, 41 or 90
When changing this field from Yes to No, if such conditions are parametrized, the system alerts that “This item should affect in the rescission calculation according to its configurations and use. Are you sure you want to continue? ". When clicking Yes, it is possible making the change, but it can cause inconsistencies in the eSocial. When clicking No, the field is with the value adequate to the situation.
For the following conditions, the value of this field should always be "Yes":
- Considers per Averages field equal to Yes
- The item on this base (with plus signal and TipBas = 30) of any item with rule 36, 38, 41 or 90
When changing this field from Yes to No, if such conditions are parametrized, the system alerts that “This item should affect in the Christmas Bonus calculation according to its configurations and use. Are you sure you want to continue? ". When clicking Yes, it is possible making the change, but it can cause inconsistencies in the eSocial. When clicking No, the field is with the value adequate to the situation.
For the following conditions, the value of this field should always be "Yes":
- Considers per Averages field equal to Yes
- The item on this base (with plus signal and TipBas = 30) of any item with rule 36, 38, 41 or 90
- The item is reported on the base (plus signal) of any vacation totalizer (in Worker > Vacation > Totalizers)
When changing this field from Yes to No, in case such conditions are parametrized, the system alerts that “This item should affect in the Vacation calculation according to its configurations and use. Are you sure you want to continue? ". When clicking Yes, it is possible making the change, but it can cause inconsistencies in the eSocial. When clicking No, the field is with the value adequate to the situation.
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
INSS 13th Salary
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Inform "S - Yes" in this field if there are international agreements that determine that the event will not serve as a calculation basis with incidence for social security. The information will be presented as "income not taxable according to international agreements" in the file generated for the layout S-1010 of eSocial.
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Inform "S - Yes" in this field if there are international agreements that determine that the event will not serve as a calculation basis with incidence on IRRF. The information will be presented as "income not taxable according to international agreements" in the file generated for the layout S-1010 of eSocial.
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
Indicate if the value:
| Value | Description |
|---|---|
| - | Decreases the base |
| + | Sums in the base |
| N | Does not affect the base |
When in the Company information is indicated PIS* Payroll = Y and PIS* Totalizer = 0, the system will check the items which have indication different from N in this field, in order to form the calculation basis of the DARF and PIS* Payroll. Therefore, indicate if the item in question adds (+) or decreases (-) or does not influence (N) on the calculation basis of the PIS* Payroll. If there is totalizer reported for the company, the calculation basis will be found according to the totalizer.
Note
The routine of PIS* Incidence is only for the new routine of provision. For the old routine, it is necessary using the totalizer of PIS* information.
Indicate whether or not the event in question should be considered in the calculation of the remuneration for Rais, from January to December. The Christmas Bonus items need this indication because they will be considered through the feature in the Christmas Bonus fields of the Rais*.
Average Salt. Related searches
Indicate whether or not the event in question should be considered in the formation of the Average Contractual Salary for Rais.
The information entered in this field will only be considered for eSocial.
For the following conditions, the value of this field should always be "+":
- The item is of proceeds and has features 01A..03Z, 51A..53Z and 61A..63Z
- The item is reported on the base (with plus signal) of any item of union contribution (feature 41B)
When changing this field from Plus to Minus, in case such conditions are parametrized, the system alerts that “This item should influence for union contribution according to its configurations and use. Are you sure you want to continue? ". When clicking Yes, it is possible making the change, but it can cause inconsistencies in the eSocial. When clicking No, the field is with the value adequate to the situation.
Indicate whether or not the event in question should be taken into account in wage composition, as well as whether the event type will be used. Thus, this field has the options "S - Sum in base", "N - No base" and "T - Consider event type" to fill. When the "T - Consider event type" option is selected, the Event Type, of the Events tab, is considered in the calculation of the wage composition.
We remind you that, if the salary composition considers the type of event, it is summed in the calculation basis when it is of types "01 - Provento" or "02 - Advantage". When the event type is "03 - Discount", it is written off in the compound wage.
For the events that use accumulators of the month in their calculation basis, the calculations of the salary composition are taken into account all calculations made in the month to compose the base. As an example, the INSS calculation will be applied considering the basis of the month and discounting the amount already paid in the other calculations.
If the item is indicated as integrating the salary composition, indicate the reason to be presented when the value is superior to the previous month.
Minor Reason
If the item is indicated as integrating the salary composition, indicate the reason to be presented when the value is inferior to the previous month.
Reason Cancellation
If the item is indicated as integrating the salary composition, indicate the reason to be presented when the value is not longer part of the salary composition.
Warning
This documentation applies only to modules: AP, CP.
The module presents this specific window for that be possible reporting which items or accumulators must be part of the calculation basis of each item.
In Point Control and Dining this tab will only be visible to customers who do not have the Personnel Administration module, or who have any events recorded in the 'Refresh Event Time Over DSR' in the integration settings, DSR tab. Customers who have this module must fill the data of this tab in the register of items of the Personnel Management module.
Sign
Indicate if this item/accumulator must be added (+) or subtracted (-) from the calculation basis of the item.
Item
Enter the event codes or accumulators that will be part of the calculation base. Example: for the items of hours, it must be informed, at least, the accumulator code 9002, which represents the value of the salary base hour.
Type
The type allows to indicate how this code, which is being included in the basis formation, must be considered by the Personnel Management module.
Notes
- The 01 to 20 types form the BasVal in special rules.
- The types 21 a 25, 32 and 33 made up the BasRef in special rules.
Worker with schedule of 180 hours/month and in the monthly calculation has 150 worked hours, 5 absence hours and 25 rest hours.
If in the calculation basis there is (considering the Minimum Wage salary of R$ 678):
| Sign | Item | Description | Type | Description | Calculation Way |
|---|---|---|---|---|---|
| + | 9015 | Minimum Wage | 01 | Item Value | R$ 678 / 180h x 180h = R$ 678 |
| + | 9015 | Minimum Wage | 02 | Vlr Event Prop. (h.tiles + h.dsr) | R$ 678 / 180h x 175h = R$ 659.16 |
| + | 9015 | Minimum Wage | 03 | Vlr Event Prop. (useful) | R$ 678 / 180h x 150h = R$ 565 |
There already are defined some accumulators that can be used in calculation rules, formation of item calculation basis, and also internally in programs.
Warning
This documentation applies only to the module: AP.
Indicate which calculation types are valid for the calculation of this event:
| Value | Description |
|---|---|
| 11 | Monthly Calculation |
| 12 | Complementary Leaf * |
| 13 | Supplementary Agreement * |
| 14 | Payment of Bargaining |
| 15 | Complementary Rescission |
| 21 | First Week |
| 22 | Intermediate Week |
| 23 | Last Week |
| 31 | Christmas Bonus Advance |
| 32 | Full Christmas Bonus |
| 41 | First Fortnight |
| 42 | Second Fortnight |
| 91 | Salary Advance |
| 92 | Profit sharing |
| 93 | Special |
| 94 | Labor Demand |
*These calculations do not need to be indicated, because the system finds the difference by the recalculation of items in the origin calculation.
Warning
This documentation applies only to the module: AP.
Indicate which activities will be valid for the calculation of the event. If none activity is reported, the system will understand that the item is valid for all activities registered in Workers > Teachers > Activities. This is because the Item field existing in Workers > Teachers > Activities disappears when using the P or S options from the Teachers field in the Company information.
Important
This handling is valid only for teachers (Type of Contract = 10 or 13 or Type of Contract = 1 with indication for Teacher Evaluation = A in Workers > Teachers > Maintenance).
For more information about teachers' routine, click here.
Warning
This documentation applies only to the module: AP.
Indicate which situations should be excluded from the incident.
Notes
- In this option can be informed the situations registered in Tables> General> Situations.
- When selecting the "7- Dismissed" situation, the event will not be considered in the termination calculation. In this case, the system identifies that the employee is already disconnected and does not calculate the event.
Warning
This documentation applies only to the module: AP.
Allows that some types of contracts be invalid for this item:
- Regular Employee
- Non-Employee Director
- Rural Worker
- Retired
- Trainee
- Apprentice
- Fixed Term
- Retired Director
- Public Agent
- Teacher
- Cooperative Member
- Domestic Worker
- Teacher Fixed Term
Warning
This documentation applies only to modules: AP, CP.
Please indicate which links, previously registered in Links (FR022VIN), will be disregarded for this event and, consequently, in the integration calculation for the employee.
The search is made by the employee's current relationship, as recorded in Link History (FR038HVI), considering the end date of the integration generation period as the base date.
Note
In this option, it is possible to report the binding registered in Tables > General > Binding.
Warning
This documentation applies only to the module: AP.
This guide contains information for the public agencies used to generate the data of the funds (events) and payroll components of the management unit.
Select the state to which the unit belongs and a Competence (DD / MMMM) to enable the other fields, whose options vary according to the selected state.
Santa Catarina
Once this status has been selected, select from the available options Nature of Component which will represent the proceeds or discounts on the sheet. For the state of Santa Catarina, the options are in accordance with Table 74 - Specification of the Nature of Components (Proceeds and Discounts) of the e-Sfinge. InComponent Indicator, state whether the event is permanent or contingent.
Warning
This documentation applies only to the module: CP.
Every situation verified in the Spot Control and Dining Hall settings must be linked to some event, even if this event is parameterized not to launch in the movement (option "4 - Never throw in the movement" of the field Generation).
- Situation
Inform the situations that will compose this item. It can be informed up to 15 situations for each item. - description
It displays the description of the situation selected. - Signal
The signal defines if this situation will add or subtract in the item. Type "+" to add or "-" to subtract. - Treat Hours
It defines the way of calculating the absence time. It may be:- A - Calculation according to the evaluated hours.
- D - Calculation according to the total of days multiplied by the hours from a WPRP (set on the schedule).
- This indication will be considered only if the quantity of hours evaluated in the absence situation is equal to the quantity of hours planned for the date (according to the schedule register). If it is lesser, the absence hours for that day will always be generated based on the evaluation (quantity of hours evaluated in the absence situation);
- It is not possible to change this indication for the following situations: 01 - Work, 16 - Overtime and 15 - Absences. For these situations, it will be always considered the mode A - By Evaluation.
- DSR Removal
Inform 'Y' if the WPRP hours, that are within the absence, must add in this item or "N" for that these hours be added in the WPRP item.
The fields Treat Hours and DSR Removal should have the same value for the daytime situation and its nighttime complement.
Click here to see the integration example with the value of this field equal to "Yes".
Warning
This documentation applies only to the module: CP.
Through this tab it is possible to establish limits to consider the hours of situations in the item. In the Situations tab are informed the codes of situations that make up the base of the item. In some cases, this base must always only be considered in the item if it meets certain requirements.
For example: Payment of hours with cascade effect.
- Consider
- 1: When Total Hours Within Limits
- 2: When Total Hours Greater Than Maximum Limit
- 3: When Total Hours Greater Than Minimum Limit
- Decreas
e Inform if it must reduce the quantity of hours of "Minimum Limit" of the item generated.
Example: Event Generated = Event Generated - Minimum Event Limit. - Minimum limi
t Inform the minimum amount of hours for that the system may compare the total of the Situations basis. - Maximum limi
t Inform the maximum quantity of hours for that the system may compare the total of the Situations basis. - Ranges
Inform if there range of company, branch, job structure, jobs and schedule. If the item must be generated for all workers, leave these fields blank.
English
Español


