Tables / Tables / Bank of Hours (CP) / Information

Hour bank

To use the Bank of hours is necessary to register the Bank of hours in this option by setting the periods, situations, events and the coverage of the Bank. The indications valid for all banks are made in Bank > Calculations of Hours > Settings.

The calculation of the hours Bank is held in the calculation of the situations, where they are generated the launches of overtime and absences to the Bank, and in the integration of events, where debit entries are generated for overtime not compensated and that they will be paid, or credit for fouls that were not compensated and that are being discounted.

After held reading markings, you can only perform maintenance releases generated by Checking through the hits of collaborators. In calculations of Bank Hours > > Maintenance you can enter new releases or change already typed releases. This screen also displays the postings generated by calculation, but does not allow you to change them.

In the calculation of integration will be generated the hours that exceeded the limit of credit/debit cards and Bank the hours that were not compensated in the stipulated time frame.

The hours of the Bank can be found through query screen, in calculations of Bank Hours > > queries and report templates, in calculations of Hours > Bank > List.

Below the information flow of the Bank of Hours:

Bank of hours Enter a code for the Hour bank. The Ponto Control and Canteen module allows the registration of up to 999 hours banks.

Description
Enter a description / name for the bank. The description can be up to 30 characters long.

Information

Maximum Daily Work Credit There may be a daily limit of hours to be cashed at the Bank.

Maximum Daily Credit on Days off It is considered for calculation of the Bank of Hours, only for days off.

Maximum Daily Work + Credit Inform the upper limit of the normal hours worked + overtimes on the day. Which exceed the total hours reported in this field will not be stored in the hours and Yes in the table R011EST-Overflows the bounds of the Hour bank, to be generated in the integration of the events to the payroll, which will be paid in the month.

Maximum Daily Debit There may be a daily limit of hours to be charged at the Bank.

Weekly Maximum Credit Can be set for the Bank of hours a weekly limit hours that should go to the Bank.

Weekly Maximum Debit Can be set for the Bank of hours a weekly limit hours that should go to the Bank.

Maximum Monthly Credit Can be set for the Bank of hours a monthly limit of hours that should go to the Bank.

Monthly Maximum Debit Can be set for the Bank of hours a monthly limit of hours that should go to the Bank.

Separate Closings in Periods The hours of the Bank can be administered as follows:

S - Separate Locks in Periods
N - Do not Separate Locks in Periods

Maximum Credit in the Period
Can be set for the Bank of hours a limit per period, the hours we should go to the Bank. This field will only be available if in the field of hours the field Separate Closings in Periods = "S".

Maximum Debit in the Period
Can be set for the Bank of hours a limit per period, the hours we should go to the Bank. This field will only be available if in the field of hours the field Separate Closings in Periods= "S".

Extending Away Periods Inform whether to extend the deadline for compensation when the developer is away.

From the moment it is determined to extend departures to some bank, the system will show the field Extend hours bank, in Tables> Situations> Registration. Should be indicated in which situations the developer must be for the Bank to be extended.

The calculation of the extension can be done in two different ways, according to the Separate Closing in Periods of the Bank of Hours:

"S - Yes": the postings will always be extended for another month.
Example:
Original date of compensation: 10/25/2002
If on this date the employee is removed, the new compensation date will be November 25, 2002.
"N - No": the extension will be carried out taking into account the information registered in the fields Time Limit Credit or Debt Timeout of the time bank:
- If the Credit / Debit Time Limit is monthly, the compensation date will be extended for another month.
  Example:
  Credit / Debit Time Limit = "M".
  Original date of compensation: 11/10/2003.
  If the employee is removed on 11/10/2003, the new date for compensation will be 11/11/03. If the employee is also on 11/11/2003, compensation will be extended for another month, and the new date will be 11/12/2003.
  
  If the removal of the 10/11/2003 day has no end date, the system will extend the compensation always for another month until the next period is reached. In this case, in the above example, the new date of compensation would be 11/11/2003 (whereas the calculation period is 9/26/2003 to 10/25/2003).
- If the Credit / Debit Time Limit is weekly, the clearing date will be extended for another week.
  Example:
  Credit / Debit Time Limit = "S".
  Original date of compensation: 11/10/2003 (Saturday).
  If the employee is retired on 11/10/2003, the new date for compensation will be 10/18/2003. If the employee is also on 18/10/2003, the compensation will be extended by one more week and the new date will be 10/25/2003.
  
  If the removal of the 10/11/2003 day has no end date, the system will extend the compensation always for another week until the following period is reached. In this case, in the above example, the new date of compensation would be 11/1/2003 (whereas the calculation period is 9/26/2003 to 10/25/2003).
- If the Credit / Debit Time Limit is daily, the clearing date will be extended by one more day.
  Example:
  Credit / Debit Time Limit = "D".
  Original date of compensation: 11/10/2003.
  If the employee is removed on 11/10/2003, the new date for compensation will be 12/10/2003. If the employee is also dismissed on 10/12/2003, the compensation will be extended for one more day and the new date will be 10/13/2003.
  If the removal of the 10/11/2003 day has no end date, the system will extend the compensation always for one more day until the following period is reached. In this case, in the example above, the new compensation date would be 10/26/2003 (considering that the calculation period is from 09/26/2003 to 10/25/2003).

If you change the registration of a situation, understanding that it should be part of the extension, or change some distance, simply recalculate the integration of the period in question and the hour bank releases will be updated. There will be no problems in calculating the integration more than once. The bank will control not to add twice the same gap.

Notes

This treatment will be performed for both the positive hours of the bank and the negative hours.

When a compensation date is extended, to return to the original date, you must delete the offset and calculate the integration again.

If the Recalculation of Hours is executed, shall be recalculated the dates of default form, i.e., no overtime.

Consider first closing in overtime
Consider the first month of closure for the calculation of the extension of the compensation deadline. Only enabled when field Extending Away Periods is set to "Y - Yes".

Periods

Periods The time will be valid the Bank of time is set in this folder.

Can be one of the following ways:

S - Separate Locks in Periods
N - Do not Separate Locks in Periods

Situations

Situations
The Bank of time is processed along with the verification of situations. So when the developer lacks work or performs an extra hour, in calculating the system calculates those hours in different situations.

Note

By decreasing the period of situation, either increasing or decreasing the start date end date, the system checks if there is a release that will be in invalid date, i.e. the date after the end date of the situation or the release date prior to the date of beginning of the situation.

In this case, the system will display a warning indicating that "there are releases the Bank of hours X X situation that will be invalid. Recalculate the Hour bank and check the typed entries ".

Base Situation
In this field should be informed of codes shall be credited or debited from the Bank of hours.

Initial date
Enter the start date for treatment at the Bank of hours of this situation;

Final date
Enter the end date that this situation will be dealt with at the Bank of hours. After that date, the situation is no longer considered in the calculation of the hours.

Note

If this same situation at some point part of the routine at the Bank of hours, must be included a new row in the grid with the same, stating a new start date.

Sign
This field must be informed if the situation should be added (+) or minus (-) from the Bank of hours.

Order
Indicates the order of compensation releases at the same time or in the same period. Depending on the item Compensation Type of the time bank settings, this order will be respected to make the offsets.

Conversion to Bank (%)
The times may be posted with a different percentage.

Conversion to Events (%)
If the employee did not compensate for an overtime performed, which had the conversion rate to the bank of 200% (two hours in the bank to compensate), this time will be generated in an integration event. The percentage of this conversion notice from the Bank to the event can also be set.

Note

As there are several situations registered with different values and percentages for events, the system calculates the conversion of the hours on top of each release, not the final amount.

When setting the percentage, it is necessary to remember that this will be applied on the hours already added of the percentage applied in the conversion to the bank.

Items

Events The hours are for the Bank or are not compensated are generated in the integration.

For this it is necessary to inform an event to pay the hours for each situation that was registered in the Situations tab. In this way, at the time of integration, the system will check which event is associated with the unmatched launch situation, and will generate the launch times for this event.

To use only two events, one positive and one negative for hours, simply inform the same positive hours event for all credit situations and the same negative hours event for all debt situations. All registered for the Bank must have an event posted. Otherwise, the Bank releases that occur with that situation and are not compensated, will not be raised in the integration.

Important:

The reported event table should be the same as that associated with the active company. Otherwise, these situations will not be integrated when generating employee integration.

If the time bank is used by more than one company using different event tables, it is recommended that the two event tables be reported in the grid or register a time bank for each company and link the corresponding event table to each company .

Situation
Inform the situation of the time bank to which the event will be associated.

Events Tab
Inform the event table used by the company that contains the event that will be associated with the situation.

Event (of Credit)
Inform the code of the event where the payment of the hours must be generated.

Event (of Debit
Enter the code of the event where the discount of the hours should be generated.

Range

Company
Enter the codes of the companies that will use this bank. If the bank is used for all companies, or has another scope, leave this field blank.

Contributor Type
Inform the types of employees (Employee, Third, Partner) that will use this bank. If the bank is used by all employees, or has another scope, leave this field blank.

Worker Inform the records of employees who will use this bank. If the bank is used by all employees, or has another scope, leave this field blank.

Branch
Enter the codes of the branches that will use this bank. If the bank is used by all branches, or has another scope, leave this field blank.

Union
Inform the codes of the unions that will use this bank. If the bank is used by all unions, or has another scope, leave this field blank.

Bond Enter the codes of the links that will use this bank. If the bank is used by all links, or has another scope, leave this field blank.

Org. Unit
Inform the local codes that will use this bank. If the Bank is used for all sites, or have another scope, leave this field blank.

Note

There is consistency in the scope of location not to allow local information to be Company companies with different organizational chart structures are informed. In this case you will need to register a Bank for each company.

Type Salary Inform the types of salaries that will use this bank. If the bank is used by all types of salaries, or has another scope, leave this field blank.

Job
Enter the job codes that will use this bank. If the bank is used for all positions, or has another scope, leave this field blank.

Cost center
Inform the cost center codes that will use this bank. If the Bank is used for all cost centers, or have another scope, leave this field blank.

Important

In the Calculation Results screen, in Miscellaneous> Users> Scope, it is possible to define a Bank of Hours scope that will be applied only in the Bank of Hours Maintenance screen.