• Collective Records
It allows the collective registration of each employee's records.
- In the control module of Point and Dining are not available the collective histories of Time, Stability and Nature of Expenditure.
- By collectively deleting a history, all fields populated by the user will be scanned. For example, by collectively deleting a scaling history, only records whose "Range Range" field have the same value entered by the user on the screen will be deleted. If this field is left zeroed, it will not be considered for filtering the records that will be deleted.
Clearance Guide
The collective history of Clearances allows the use of user fields in their rules by process inclusion / alteration / exclusion (19, 20 and 21, respectively).
Inform employee start date of departure.
Indicate the time of the dismissal of the employee, on the day of removal, for the module to calculate the hours worked on that day. It can be left zero, so the system considers the total period of a working day.
Indicate the type of removal, according to the coding, or according to the situation code created in the item Tables> General> Situations.
Clerk This field brings the information you have entered into the attendants (Tables> General> Medical Assistants (2)) and is authorized for situations of types: 3 - Sickness, 6 - Maternity Leave, 10 - Paid Employee Leave, 14 - Medical Leave (company pay) or 19 - Maternity.
Name Attendee Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the fiel
d Clerk, or you can be informed manually when you do not choose to register.
Class Organ Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the field Clerk, or can be manually informed according to the following options: 1 - Regional Council of Medicine (CRM) and 2 - Regional Council of Dentistry (CRO).
Professional Board Registration
Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the fiel
d Clerk, or can be manually entered the registration number in the professional council.
UF Professional Council Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the field Clerk, or the acronym of the home state of the professional council may be entered manually.
ICD
This field is enabled for situations of types: 3 - Sickness, 4 - Work Accident, 6 - Maternity Leave, 10 - Paid Employee Leave, 14 - Medical Leave (paid company), 19 - Maternity Assistance or 23 - Work Accident License (Pgto Empresa).
Requested only in the schedule of dismissal.
For situations of type 03 (sickness benefit) or 04 (accident at work), this data will appear, where we can indicate the number of days of paid medical leave, which must be paid by the company. This number of days will be taken for pay as a leaf, in the event code that contains the characteristic 01N or 02N, being disregarded as days of remoteness.
Requested only for fault schedules. It is currently used by the Personnel Administration when the employee did not miss the full day.
If you enter a number of days, based on this value the system will automatically feed the field Expected Completion.
This field will be disabled when the situation type is 15 - Faults.
Inform the end date of the removal.
End Time
End time of the removal. If you are informed 00:00 in this field and also in the HOUR FACE field, People Management | HCM ignores these two information, considering the departure only for the dates.
Inform the expected end date of the removal. This information will be used to control the termination of the removal and listed in reports. The date foreseen for termination of leave will be requested only for leave schedules of types 06 (maternity leave), 11 (paternity leave), 12 (collective holidays), 13 (prior notice worked) and 14 (Medical Leave company)).
The date entered for the forecast of termination of the departure, will also be used for the count in the distribution of the Transportation Ticket.
For the control of compulsory exams after leave of absence 03 (sick leave), 04 (work accident), 05 (military service), 06 (maternity leave), 08 (unpaid leave), 10 , 13 (prior notice worked) and 14 (Medical Leave (company pay)).
Note
Space to type any message related to the spacing, which can be listed in the reports through the variable ObsAfa in the Generator.
Scale Guide
Enter the date of the change of scale.
Indicate the new code of the timescale to be fulfilled by the employee. Click the enter button to select a registered time scale.
For "Automatic Generation" scales it will be necessary to inform the team and the category in which the employee will be allocated, so the employee will be part of a Team> Turno> Category where the service scale will be generated.
Indicate the new class code to be fulfilled by the employee.
Inform the Interval Class code for this employee.
Inform the team in which the employee will be part from the date of change.
Inform the category in which the employee will be part from the date of change.
Local Guide
Change Date
Inform location transfer date.
New Location
Enter the code of the new place of work of the collaborator (s).
Location Work RAI
S Inform the code of the city where the collaborator (s) effectively performs his / her function. This information will be considered in register 02, position 469 to 475 of the RAIS export file.
Field valid only for the Personnel Administration module.
Reason for Site Change Enter the reason code for the change of location. The reasons are registered in Tables / Reasons / Salary Adjustment.
Cost Center tab
Date Change
Inform the date of transfer of cost center.
New Cost Center Enter the new cost center.
Only the records of the active company will be displayed in the field search.
Cargo Guide
Date Change
Inform date of transfer of charge.
The cargo structure will be respected according to the date informed.
New Position
Enter the new job code.
New Job Position
(This field is displayed only when the company uses Vacancy Position. In the QL: Miscellaneous> Signals, field Cargo Position = 'S') Indicate the new job position code. The job that the worker will have must be reported in this field, that is, the job to which the vacancy will be considered.
Reason Change
Enter the reason code for the charge change.
Branch Guide
Through this folder can be made a collective transfer of employees to another branch, within the same company or to another company, changing or not registration code.
When the employee is transferred to another branch with a different register, or is transferred to another company, all their information, such as history, postings, financial statement, calculation, etc. will also be transferred to the new company and / or new registration.
- The destination company must use the same Event table and the same Organizational Chart and Charge structures as the company of origin;
- The collective affiliate transfer is only available for Inclusion. If necessary, the exclusion must be done individually, using the option Collaborators> Histories> Branch.
This information is saved to be used in the CAGED, DIRF and RAIS.
Click here for more information about the Branch Transfer routine.
Change Date
Enter the expiration date of the transfer of the employee.
New Company Enter the company code.
Actuation type
Job type of the new job. This information is automatically updated in the job history, based on the date of the branch transfer.
Workstation
If there is a change, please inform the workstation. A new job history is created automatically with the date of the branch transfer.
Reason for changing the Post
If there is a change, please inform the new reason for changing the position. This information is automatically updated in the job history, based on the date of the branch transfer.
New Branch Enter the code of the new branch.
New Location
Enter the code of the place.
New Cost Center Enter the code of the Cost Center.
New Nature of Expense Inform the new Nature of Expenditure.
Home Inform the initial register of the employees that will undergo branch change.
Example:
If five employees are transferred simultaneously, with 100 being entered in this field, the first employee transferred will have the register 100, the second employee will have 101, the third with 102, the fourth with 103 and the fifth with 104.
Type of Admission
Inform the Type of Admission in the new subsidiary.
Record Payroll Inform the initial number for the Registration Form.
New Position
If there is a change, please inform the new charge. A new job history is created automatically with the date of the branch transfer.
Reason for Charge Change
If there is a change, please inform the new reason. This information is automatically updated in the job history, based on the date of the branch transfer.
Note
The fields below are only available if the Proprietária, the job routine is enabled:
- Actuation type;
- Workstation;
- Reason for changing the Post;
- New Position;
- Reason for Charge Change.
When informing a new workstation, the system suggests the other fields according to the characteristics configured at the station.
Treat Bank of Hours Positive Balance
Determine the treatment for employees with positive balance hours:
- "1 - Transfer Only": bank hours are only transferred to the new register;
- "3 - Pay": the hours are sent to the destination register and paid on the next sheet; Example:
- Transfer of employee: 01/02
- Period of verification of the company of origin: 21 to 20
- Register:
- Origin: 5 in company 001
- Destination: 5000 in company 1000
Register of origin - postings before the transfer, opening balance: 20:00:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours A - Determination -02: 00 6 PM 03/01 309 - Bank of Hours Credit A - Determination 01:00 19:00 1/5 310 - Debit Bank of Hours A - Determination -01:00 6 PM 1/15 309 - Bank of Hours Credit A - Determination 01:00 19:00 Register of origin - postings after the transfer:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours A - Determination -02: 00 6 PM 03/01 309 - Bank of Hours Credit A - Determination 01:00 19:00 1/5 310 - Debit Bank of Hours A - Determination -01:00 6 PM 1/15 309 - Bank of Hours Credit A - Determination 01:00 19:00 20/01 310 - Debit Bank of Hours F - Transfer of affiliate -19: 00 00:00 Destination registration - postings after the transfer:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours F - Transfer of affiliate -02: 00 6 PM 03/01 309 - Bank of Hours Credit F - Transfer of affiliate 01:00 19:00 1/5 310 - Debit Bank of Hours F - Transfer of affiliate -01:00 6 PM 1/15 309 - Bank of Hours Credit F - Transfer of affiliate 01:00 19:00 1/1 309 - Bank of Hours Credit B - Anticipate Abono -19: 00 00:00 - "5 - Migrate": Migrate the balance from the current time bank to the new time bank in the destination register. Example:
- Transfer of employee: 01/02
- Bank of hours:
- Origin: 001
- Destination: 100
- Period of verification of the company of origin: 21 to 20
- Register:
- Origin: 5 in company 001
- Destination: 5000 in company 1000
Register of origin - postings before the transfer, opening balance: 20:00:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours A - Determination -02: 00 6 PM 03/01 309 - Bank of Hours Credit A - Determination 01:00 19:00 1/5 310 - Debit Bank of Hours A - Determination -01:00 6 PM 1/15 309 - Bank of Hours Credit A - Determination 01:00 19:00 Source record - postings after transfer in the bank hours 001:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours A - Determination -02: 00 6 PM 03/01 309 - Bank of Hours Credit A - Determination 01:00 19:00 1/5 310 - Debit Bank of Hours A - Determination -01:00 6 PM 1/15 309 - Bank of Hours Credit A - Determination 01:00 19:00 20/01 310 - Debit Bank of Hours F - Transfer of affiliate -19: 00 00:00 Destination register - postings after the transfer in the bank 001:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours F - Transfer of affiliate -02: 00 6 PM 03/01 309 - Bank of Hours Credit F - Transfer of affiliate 01:00 19:00 1/5 310 - Debit Bank of Hours F - Transfer of affiliate -01:00 6 PM 1/15 309 - Bank of Hours Credit F - Transfer of affiliate 01:00 19:00 1/1 309 - Bank of Hours Credit F - Transfer of affiliate -19: 00 00:00 Destination register - postings after the transfer in the bank 100:
Date Situation Origin Amount of hours Balance 1/1 309 - Bank of Hours Credit M - Migration 19:00 19:00
The remaining options are not valid for a bank with positive balance hours.
Treat Bank of Hours Negative Balance
Determine the treatment for employees with negative balance of hours:
- "1 - Transfer Only ': bank hours are only transferred to the new register;
- "2 - Forgive": the bank hours are zeroed in the source register;
- "4 - Discount": the hours are sent to the destination register and paid on the next sheet; Example:
- Transfer of employee: 01/02
- Period of verification of the company of origin: 21 to 20
- Register:
- Origin: 5 in company 001
- Destination: 5000 in company 1000
Register of origin - postings before transfer, opening balance: -06: 00:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours A - Determination -02: 00 -8 o'clock 03/01 309 - Bank of Hours Credit A - Determination 01:00 -07: 00 1/5 310 - Debit Bank of Hours A - Determination -01:00 -8 o'clock 1/15 309 - Bank of Hours Credit A - Determination 01:00 -07: 00 Register of origin - postings after the transfer:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours A - Determination -02: 00 -8 o'clock 03/01 309 - Bank of Hours Credit A - Determination 01:00 -07: 00 1/5 310 - Debit Bank of Hours A - Determination -01:00 -8 o'clock 1/15 309 - Bank of Hours Credit A - Determination 01:00 -07: 00 20/01 309 - Bank of Hours Credit F - Transfer of affiliate 07:00 00:00 Register Destination - Postings after the transfer:
Date Situation Origin Amount of hours Balance 12/21 310 - Debit Bank of Hours F - Transfer of affiliate -02: 00 -8 o'clock 03/01 309 - Bank of Hours Credit F - Transfer of affiliate 01:00 -07: 00 1/5 310 - Debit Bank of Hours F - Transfer of affiliate -01:00 -8 o'clock 1/15 309 - Bank of Hours Credit F - Transfer of affiliate 01:00 -07: 00 1/1 309 - Bank of Hours Credit N - Cancel Debit 07:00 00:00 - "5 - Migrate": Migrate the balance from the current time bank to the new time bank in the destination register.
The other options are not valid for a bank with negative balance hours.
Note
The treatment for the hours bank in a transfer is only available to employees belonging to the Point Management.
Destination Bank of Hours
Choose the time bank that will receive the hours migrated from the source bank. This field is enabled only when one of the fields Treat Bank of Hours Positive Balance and / or Treat Bank of Hours Negative Balance option "5 - Migrate". Only the time banks belonging to Point Management are displayed.
Note
The fields Treat Bank of Hours Positive Balance, Treat Bank of Hours Negative Balance and Destination Bank of Hours are enabled only when this module is integrated with the Point Management and the employee has an open bank account at the transfer date. In addition, it is necessary that the field Dealing with time bank on branch transfer, of the screen Miscellaneous Ticketing - Point tab, select "S - Yes".
If the employee does not have a bank account of open hours on the transfer date, the transfer occurs normally, without considering the time bank.
For transferring the time bank information, the starting date of the calculation period is used. This code conforms to the transfer date.
Example:
| Calculation | Period | Sheet period | Calculation period |
|---|---|---|---|
| 01 | 02/9999 | 2/1 to 2/28 | 1/16 to 2/15 |
| 02 | 03/9999 | 01/03 to 31/03 | 2/16 to 3/15 |
| 03 | 04/9999 | 4/1 to 4/30 | 3/16 to 4/15/04 |
| 04 | 05/9999 | 05/05 to 05/05 | 4/16 to 5/15/05 |
In a branch transfer carried out on 01/03, the date used as the basis for transferring the information from the time bank will be 2/16.
Important
When you have the Personnel Administration module installed, the search is done by the start date of the sheet / competency, not the start date of the calculation.
The calculation code is always identified using the source company, even if the destination company has calculation codes with different periods.
You can not perform a migration of employee time bank for company and / or branch transfers at different times. This occurs because the processes are based on the initial date of the calculation code found with the transfer date. That is, the time bank is zeroed in at the origin company at date -1 and the information is transferred considering the date for the new company.
Therefore, in order to avoid inconsistencies between the calculation of the old company and the new one, such as transfers in the middle of the calculation of the new company, within a period that is still being determined, we suggest not to migrate the time bank in different periods.
Stability Guide
Home Stability
Inform the initial period for generating the Stability history.
End Stability
Inform the final period for generating the Stability history.
Type
Inform the type of stability due.
Annotations Tab
Date Annotation
Enter the date of the note.
Sequence
Report the code to identify the sequence of notes.
Type Annotation
It enables to register several ways of notes in the form. Only a given type may be listed in the templates of Register Form. The types are tabled in Tables > General > Notes or Types of Notes, depending of the module.
No. Document
It allows to inform the document number, useful mainly in public bodies, in which may be saved the law number or decree of public service promotions.
description
Space intended to describe the note in details.
Responsible Company
Code of the company responsible for the note.
When including a register, it will be automatically suggested the company of the worker associated to the active user, if there is.
When including a register, it will be automatically suggested the type of worker associated to the active user, if there is.
Responsible Annotation
Report the code of register of the responsible for the note.
When including a register, it will be automatically suggested the register of the worker associated to the active user, if there is.
Nature Guide Expense
Date Change
Inform the transfer date of the Nature of Expenditure.
Nature Expenses
Enter the code of Nature Desired expenditure. These codes can be registered through the menu Companies> Accounting> Nature Expenses.
Schedule tab
Date Change
Enter the date of the time transfer.
Base Time
Inform the employee's new base time code.
Opening hours Saturday
Enter the code for the new time on Saturday.
Week hours
Indicate the number of weekly hours of the employee.
DSR Hours
Indicate the number of hours of weekly rest of the employee.
Calculation Tab
Beginning of the Calculation
Inform the start date for the collective calculation history.
Type of Calculation
Indicate the form of verification from the developer:
- Normal. You can make frequency and / or cafeteria markings.
- Dismissed from Point. No markings. The system calculates working hours, according to time, for calculating the Event Integration. If the employee makes the markings, they are considered for the calculation, as well as the correct ones. The Cafeteria control is normal.
- Only Canteen. Never make frequency markings. Despite the developer have working hours, in the calculation does not compute hours. Control of the cafeteria is normal. File generation for payroll, employees with finding 3 will have available only the Final calculation rule.
- Dismissed from the Point. Dismiss All Tags. This type of investigation has the same purpose of type 2-relieved of point, but does not consider for calculating electronic clocking events (source ' and '). The typed and Generated will be displayed on the screen of balls and will be considered for the calculation.
- No Point Control and Dining Room. As of the date of this record, the employee is no longer in control of Ponto and Canteen. Will not be generated integration of events for the payroll from the period following the inclusion of the history. For example: the day 7/10/2001 was registered the history of Calculation with 5 Type for a specific employee. The calculation and the cafeteria will be valid until the day 7/9/2001, and the calculation of integration will be considered for the entire period of July/2001. In August/2001 this contributor will no longer be considered in integration.
- Missed Point - Disregard Point Markings. Disregards electronic point markings, calculating work whenever faults occur. The user can type clocking events on the screen of hits. In the cafeteria, the routine works in standard form, i.e. they are considered electronic clocking events and typed.
The "Participate Process Set", "Set Point" and "Approve Own Point" fields are only available when integrated with the Point Management module.
Contact Us
Date of Amendment
Inform the start date for the union change.
Syndicate
Enter the code of the new union.
Syndicated
Inform if the employee is a member of your union. If there is change in this indication, even if there is not change of union, the system will create a new union record.
Contract tab
Date Change
Enter the start date of the contract.
The contract history is only valid for third-party and partner types.
Company Sub-Contracted
Enter the code of the contracted company, that is, the code of the Other Company.
Contract Number
Report the number of the contract to which the worker belongs. This field is optional.
The number of the contract reported must be associated to another company.
Final date
Report the end date of the contract.
Position
Through this tab you can change the collective job history.
The tab displays panels of the other histories affected by the change of job that can also be modified.
Transportation Voucher Schedule
Historic Open
The options in this field are:
- Finish with the day before the transfer - The routine finalizes the open transport ticket scale history (end date zeroed) for each employee who has it, assigning the date of the previous day to the new history.
Example:
If the new history has an initial date 05/04/2013, the current history is finalized with the date 04/04/2013;
- Do not generate transfer and inform in the log - With this option, when trying to insert a new transport value scale history the routine check if there is an open registered date (dead date zeroed) for the employee. In this case, the history entry is aborted (only for the employee being processed) and an error message appears in the log.
Filter Button
Displays a screen with all employees based on what was set in the Selection.
Example:
I need to make a site transfer to the employees of branch 1, with the exception of some employees. In this case, clicking the Filter the system will show a list of the employees of the branch 1 so that the user can clear the employees that should not be part of the transfer.
Veja também:
English
Español
