36
36
assigned for the day.
38
38
.. i18n: .. _fig-servtimlis:
40
.. i18n: .. figure:: images/service_timesheet_list.png
42
.. i18n: :align: center
44
.. i18n: *Timesheet for a working day*
40
48
.. figure:: images/service_timesheet_list.png
44
.. i18n: .. figure:: images/service_timesheet_list.png
46
.. i18n: :align: center
48
*Timesheet for a working day*
50
.. i18n: *Timesheet for a working day*
52
52
*Timesheet for a working day*
54
54
.. i18n: The figure :ref:`fig-servtimlis` gives an example of a timesheet for an employee.
56
56
The figure :ref:`fig-servtimlis` gives an example of a timesheet for an employee.
58
58
.. i18n: .. index::
59
.. i18n: pair: cost; allocation
59
.. i18n: pair: cost; allocation
62
62
pair: cost; allocation
64
64
.. i18n: .. note:: Don't confuse timesheets and attendence compliance
66
.. i18n: The timesheet system isn't intended to be a disguised attendance form. There's no control over the
67
.. i18n: service times and the employee is free to encode 8 or 9 hours or more of services each day if they
70
.. i18n: If you decide to put such a system into place, it's important to clarify this point with your
71
.. i18n: staff. The objective here isn't to control hours, because the employees decide for themselves what
72
.. i18n: they'll be entering – but to track the tasks running and the allocation of costs between them.
74
.. note:: Don't confuse timesheets and attendence compliance
66
76
The timesheet system isn't intended to be a disguised attendance form. There's no control over the
67
77
service times and the employee is free to encode 8 or 9 hours or more of services each day if they
70
.. i18n: The timesheet system isn't intended to be a disguised attendance form. There's no control over the
71
.. i18n: service times and the employee is free to encode 8 or 9 hours or more of services each day if they
74
If you decide to put such a system into place, it's important to clarify this point with your
75
staff. The objective here isn't to control hours, because the employees decide for themselves what
76
they'll be entering – but to track the tasks running and the allocation of costs between them.
78
.. i18n: If you decide to put such a system into place, it's important to clarify this point with your
79
.. i18n: staff. The objective here isn't to control hours, because the employees decide for themselves what
80
.. i18n: they'll be entering – but to track the tasks running and the allocation of costs between them.
82
80
If you decide to put such a system into place, it's important to clarify this point with your
83
81
staff. The objective here isn't to control hours, because the employees decide for themselves what
84
82
they'll be entering – but to track the tasks running and the allocation of costs between them.
88
86
Amongst the many uses of such a timesheet system for a company, here are some of the most important:
90
88
.. i18n: * enabling tracking of the true costs of a project by accounting for the time used on it,
92
* tracking the services provided by different employees,
94
90
.. i18n: * tracking the services provided by different employees,
96
* comparing the hours really used on a project with the initial planning estimates,
98
92
.. i18n: * comparing the hours really used on a project with the initial planning estimates,
100
* automatically invoicing based on the service hours provided,
102
94
.. i18n: * automatically invoicing based on the service hours provided,
104
* obtaining a list of the service hours for a given client,
106
96
.. i18n: * obtaining a list of the service hours for a given client,
108
* knowing the costs needed to run the company, such as the marketing costs, the training costs for a
109
new employee, and the invoicing rates for a client.
111
98
.. i18n: * knowing the costs needed to run the company, such as the marketing costs, the training costs for a
112
.. i18n: new employee, and the invoicing rates for a client.
99
.. i18n: new employee, and the invoicing rates for a client.
101
* enabling tracking of the true costs of a project by accounting for the time used on it,
103
* tracking the services provided by different employees,
105
* comparing the hours really used on a project with the initial planning estimates,
107
* automatically invoicing based on the service hours provided,
109
* obtaining a list of the service hours for a given client,
114
111
* knowing the costs needed to run the company, such as the marketing costs, the training costs for a
115
112
new employee, and the invoicing rates for a client.
129
126
one of the groups there such as :guilabel:`38 Hours/Week`.
131
128
.. i18n: .. figure:: images/service_timesheet_def.png
133
.. i18n: :align: center
135
*Timesheet category for full time 38 hours per week*
137
.. i18n: *Timesheet category for full time 38 hours per week*
130
.. i18n: :align: center
132
.. i18n: *Timesheet category for full time 38 hours per week*
134
.. figure:: images/service_timesheet_def.png
139
138
*Timesheet category for full time 38 hours per week*
141
140
.. i18n: .. index::
142
.. i18n: single: employee; configuring
141
.. i18n: single: employee; configuring
189
188
The following information is important in the product form:
191
190
.. i18n: * :guilabel:`Name` : \ ``Secretary``\ \ ``Salesperson``\ \ ``Project Manager``\
193
* :guilabel:`Product Type` : \ ``Service``\
195
192
.. i18n: * :guilabel:`Product Type` : \ ``Service``\
197
* :guilabel:`Unit of Measure` : \ ``Hour``\ \ ``Day``\
199
194
.. i18n: * :guilabel:`Unit of Measure` : \ ``Hour``\ \ ``Day``\
201
* :guilabel:`List Price`
203
196
.. i18n: * :guilabel:`List Price`
205
* :guilabel:`Standard Price`
207
198
.. i18n: * :guilabel:`Standard Price`
200
* :guilabel:`Name` : \ ``Secretary``\ \ ``Salesperson``\ \ ``Project Manager``\
202
* :guilabel:`Product Type` : \ ``Service``\
204
* :guilabel:`Unit of Measure` : \ ``Hour``\ \ ``Day``\
206
* :guilabel:`List Price`
209
208
* :guilabel:`Standard Price`
211
210
.. i18n: .. index::
212
.. i18n: single: module; product_index
211
.. i18n: single: module; product_index
215
214
single: module; product_index
217
216
.. i18n: .. tip:: Price Indexation
218
.. i18n: The module :mod:`product_index` lets you generate indexes connected to the change of purchase or sale
219
.. i18n: price for individual products.
221
.. i18n: In human resources, this module can be used to change your prices or costs in step with a national
224
.. tip:: Price Indexation
219
226
The module :mod:`product_index` lets you generate indexes connected to the change of purchase or sale
220
227
price for individual products.
222
.. i18n: The module :mod:`product_index` lets you generate indexes connected to the change of purchase or sale
223
.. i18n: price for individual products.
225
In human resources, this module can be used to change your prices or costs in step with a national
228
.. i18n: In human resources, this module can be used to change your prices or costs in step with a national
231
229
In human resources, this module can be used to change your prices or costs in step with a national
236
234
In summary, each company employee corresponds, in most cases, to:
238
236
.. i18n: * :guilabel:`Partner`
240
* an :guilabel:`Employee` form,
242
238
.. i18n: * an :guilabel:`Employee` form,
244
* :guilabel:`System User`.
246
240
.. i18n: * :guilabel:`System User`.
242
* :guilabel:`Partner`
244
* an :guilabel:`Employee` form,
248
246
* :guilabel:`System User`.
250
248
.. i18n: And each company job position corresponds to a :guilabel:`Product`.
252
250
And each company job position corresponds to a :guilabel:`Product`.
254
252
.. i18n: .. index::
255
.. i18n: single: module; hr_contract
253
.. i18n: single: module; hr_contract
258
256
single: module; hr_contract
260
258
.. i18n: .. note:: Time charge rates
260
.. i18n: By default the hourly cost of an employee is given by the standard cost of the product linked to
261
.. i18n: that employee.
262
.. i18n: But if you install the :mod:`hr_contract` module it's possible to manage contracts differently.
263
.. i18n: The hourly cost of the employee is then automatically calculated from their employment contract
264
.. i18n: when they enter their timesheet data.
266
.. i18n: To do this, the software uses a factor defined in the contract type
267
.. i18n: (for example, the gross monthly salary, calculated per day).
268
.. i18n: Ideally this factor should take into account the salary costs, and the taxes, insurances and other
269
.. i18n: overheads associated with pay.
271
.. note:: Time charge rates
262
273
By default the hourly cost of an employee is given by the standard cost of the product linked to
265
276
The hourly cost of the employee is then automatically calculated from their employment contract
266
277
when they enter their timesheet data.
268
.. i18n: By default the hourly cost of an employee is given by the standard cost of the product linked to
269
.. i18n: that employee.
270
.. i18n: But if you install the :mod:`hr_contract` module it's possible to manage contracts differently.
271
.. i18n: The hourly cost of the employee is then automatically calculated from their employment contract
272
.. i18n: when they enter their timesheet data.
274
To do this, the software uses a factor defined in the contract type
275
(for example, the gross monthly salary, calculated per day).
276
Ideally this factor should take into account the salary costs, and the taxes, insurances and other
277
overheads associated with pay.
279
.. i18n: To do this, the software uses a factor defined in the contract type
280
.. i18n: (for example, the gross monthly salary, calculated per day).
281
.. i18n: Ideally this factor should take into account the salary costs, and the taxes, insurances and other
282
.. i18n: overheads associated with pay.
284
279
To do this, the software uses a factor defined in the contract type
285
280
(for example, the gross monthly salary, calculated per day).
286
281
Ideally this factor should take into account the salary costs, and the taxes, insurances and other
287
282
overheads associated with pay.
289
284
.. i18n: .. index::
290
.. i18n: single: timesheet; entering data
285
.. i18n: single: timesheet; entering data
319
314
the click :guilabel:`New`.
321
316
.. i18n: .. tip:: Shortcut to timesheets
323
It's a good idea if all employees who use timesheets place this menu in their shortcuts.
324
That's because they'll need to return to them several times each day.
326
.. i18n: It's a good idea if all employees who use timesheets place this menu in their shortcuts.
327
.. i18n: That's because they'll need to return to them several times each day.
318
.. i18n: It's a good idea if all employees who use timesheets place this menu in their shortcuts.
319
.. i18n: That's because they'll need to return to them several times each day.
321
.. tip:: Shortcut to timesheets
329
323
It's a good idea if all employees who use timesheets place this menu in their shortcuts.
330
324
That's because they'll need to return to them several times each day.
336
.. i18n: #. The :guilabel:`User` : proposed by default, but you can change it if you're encoding the first timesheet
337
.. i18n: for another company employee.
339
#. The :guilabel:`Date` : automatically proposed as today's date, but it's possible to change it if you're
340
encoding the timesheet for a prior day.
342
.. i18n: #. The :guilabel:`Date` : automatically proposed as today's date, but it's possible to change it if you're
343
.. i18n: encoding the timesheet for a prior day.
345
#. :guilabel:`Analytic Account` : for the project you've been working on - obviously it should be predefined.
347
.. i18n: #. :guilabel:`Analytic Account` : for the project you've been working on - obviously it should be predefined.
349
#. :guilabel:`Description` : a free text description of the work done in the time.
351
.. i18n: #. :guilabel:`Description` : a free text description of the work done in the time.
353
#. :guilabel:`Quantity` : number of units of time (the units are defined as part of the product).
355
The other fields are automatically completed but can be modified: the :guilabel:`Product`
356
which is the service product such as consultancy, the
357
:guilabel:`Unit of Measure` (predefined, and could perhaps be minutes, hours or days),
358
the :guilabel:`Cost` of the service (which is calculated by default),
359
and the associated :guilabel:`General Account`.
361
.. i18n: #. :guilabel:`Quantity` : number of units of time (the units are defined as part of the product).
330
.. i18n: #. The :guilabel:`User` : proposed by default, but you can change it if you're encoding the first timesheet
331
.. i18n: for another company employee.
333
.. i18n: #. The :guilabel:`Date` : automatically proposed as today's date, but it's possible to change it if you're
334
.. i18n: encoding the timesheet for a prior day.
336
.. i18n: #. :guilabel:`Analytic Account` : for the project you've been working on - obviously it should be predefined.
338
.. i18n: #. :guilabel:`Description` : a free text description of the work done in the time.
340
.. i18n: #. :guilabel:`Quantity` : number of units of time (the units are defined as part of the product).
363
342
.. i18n: The other fields are automatically completed but can be modified: the :guilabel:`Product`
364
343
.. i18n: which is the service product such as consultancy, the
365
344
.. i18n: :guilabel:`Unit of Measure` (predefined, and could perhaps be minutes, hours or days),
366
345
.. i18n: the :guilabel:`Cost` of the service (which is calculated by default),
367
346
.. i18n: and the associated :guilabel:`General Account`.
348
#. The :guilabel:`User` : proposed by default, but you can change it if you're encoding the first timesheet
349
for another company employee.
351
#. The :guilabel:`Date` : automatically proposed as today's date, but it's possible to change it if you're
352
encoding the timesheet for a prior day.
354
#. :guilabel:`Analytic Account` : for the project you've been working on - obviously it should be predefined.
356
#. :guilabel:`Description` : a free text description of the work done in the time.
369
358
#. :guilabel:`Quantity` : number of units of time (the units are defined as part of the product).
371
360
The other fields are automatically completed but can be modified: the :guilabel:`Product`
391
380
employees' data entry. Employees can verify their own timesheet using the following reports:
393
382
.. i18n: * Printing the timesheets per month, using the menu :menuselection:`Human Resources --> Reporting
394
.. i18n: --> Timesheet --> Print my timesheet`.
396
* Reviewing all service entries using the menu :menuselection:`Human Resources --> Timesheets
397
--> My Timesheets --> My timesheets to confirm`.
398
You can then use the filters to analyze your services by project, by
399
period or by product.
383
.. i18n: --> Timesheet --> Print my timesheet`.
401
385
.. i18n: * Reviewing all service entries using the menu :menuselection:`Human Resources --> Timesheets
402
.. i18n: --> My Timesheets --> My timesheets to confirm`.
403
.. i18n: You can then use the filters to analyze your services by project, by
404
.. i18n: period or by product.
386
.. i18n: --> My Timesheets --> My timesheets to confirm`.
387
.. i18n: You can then use the filters to analyze your services by project, by
388
.. i18n: period or by product.
390
* Printing the timesheets per month, using the menu :menuselection:`Human Resources --> Reporting
391
--> Timesheet --> Print my timesheet`.
406
393
* Reviewing all service entries using the menu :menuselection:`Human Resources --> Timesheets
407
394
--> My Timesheets --> My timesheets to confirm`.
409
396
period or by product.
411
398
.. i18n: .. tip:: Hiding service costs
400
.. i18n: By default, Open ERP is configured to show the cost of each service when an employee encodes the
401
.. i18n: number of hours per project.
402
.. i18n: You can modify this field by adding the attribute invisible=True in the timesheet view.
404
.. i18n: (And the way to do that is either to modify the view on the filesystem, or
405
.. i18n: to use the web client to modify the view in the current database.
406
.. i18n: For the latter, there's a pale grey :guilabel:`[CUSTOMIZE]` label
407
.. i18n: to the bottom left of each form that gives you access to the
408
.. i18n: :guilabel:`Manage Views` option.
409
.. i18n: If you have sufficient permissions you can edit the XML that defines the current view.)
411
.. i18n: The value in the cost field shows employees the cost of their time used in the company, so masking this
412
.. i18n: field might not always be the best option.
414
.. tip:: Hiding service costs
413
416
By default, Open ERP is configured to show the cost of each service when an employee encodes the
414
417
number of hours per project.
421
424
:guilabel:`Manage Views` option.
422
425
If you have sufficient permissions you can edit the XML that defines the current view.)
424
.. i18n: By default, Open ERP is configured to show the cost of each service when an employee encodes the
425
.. i18n: number of hours per project.
426
.. i18n: You can modify this field by adding the attribute invisible=True in the timesheet view.
428
.. i18n: (And the way to do that is either to modify the view on the filesystem, or
429
.. i18n: to use the web client to modify the view in the current database.
430
.. i18n: For the latter, there's a pale grey :guilabel:`[CUSTOMIZE]` label
431
.. i18n: to the bottom left of each form that gives you access to the
432
.. i18n: :guilabel:`Manage Views` option.
433
.. i18n: If you have sufficient permissions you can edit the XML that defines the current view.)
435
The value in the cost field shows employees the cost of their time used in the company, so masking this
436
field might not always be the best option.
438
.. i18n: The value in the cost field shows employees the cost of their time used in the company, so masking this
439
.. i18n: field might not always be the best option.
441
427
The value in the cost field shows employees the cost of their time used in the company, so masking this
442
428
field might not always be the best option.
452
438
forgotten to enter her timesheet details on a certain day.
454
440
.. i18n: .. figure:: images/service_timesheet_all.png
456
.. i18n: :align: center
458
*Employees' monthly summary timesheet*
460
.. i18n: *Employees' monthly summary timesheet*
442
.. i18n: :align: center
444
.. i18n: *Employees' monthly summary timesheet*
446
.. figure:: images/service_timesheet_all.png
462
450
*Employees' monthly summary timesheet*
472
460
:menuselection:`Human Resources --> Reporting --> All Months`, for example:
474
462
.. i18n: * :guilabel:`Timesheet by User`
476
* :guilabel:`Timesheet by Invoice`
478
464
.. i18n: * :guilabel:`Timesheet by Invoice`
480
* :guilabel:`Daily Timesheet by Account`
482
466
.. i18n: * :guilabel:`Daily Timesheet by Account`
484
* :guilabel:`Timesheet by Account`
486
468
.. i18n: * :guilabel:`Timesheet by Account`
470
* :guilabel:`Timesheet by User`
472
* :guilabel:`Timesheet by Invoice`
474
* :guilabel:`Daily Timesheet by Account`
488
476
* :guilabel:`Timesheet by Account`
490
478
.. i18n: .. figure:: images/service_timesheet_graph.png
492
.. i18n: :align: center
494
*Chart of timesheet by account*
496
.. i18n: *Chart of timesheet by account*
480
.. i18n: :align: center
482
.. i18n: *Chart of timesheet by account*
484
.. figure:: images/service_timesheet_graph.png
498
488
*Chart of timesheet by account*
504
494
screen. If you want to see more detail, switch to the list view.
506
496
.. i18n: .. note:: Project dashboard when signing in
498
.. i18n: The dashboard for managing projects has a graphical view that summarizes the current user's
499
.. i18n: timesheet for the last seven days.
501
.. i18n: you can assign a dashboard to users so that it appears when they sign into Open ERP.
502
.. i18n: Then each employee will be able to see if they forgot to complete their timesheet next time
503
.. i18n: they sign into the system.
506
.. i18n: single: module; board_project
508
.. i18n: To use this dashboard, install the module :mod:`board_project`.
510
.. note:: Project dashboard when signing in
508
512
The dashboard for managing projects has a graphical view that summarizes the current user's
509
513
timesheet for the last seven days.
511
.. i18n: The dashboard for managing projects has a graphical view that summarizes the current user's
512
.. i18n: timesheet for the last seven days.
514
515
you can assign a dashboard to users so that it appears when they sign into Open ERP.
515
516
Then each employee will be able to see if they forgot to complete their timesheet next time
516
517
they sign into the system.
519
520
single: module; board_project
521
.. i18n: you can assign a dashboard to users so that it appears when they sign into Open ERP.
522
.. i18n: Then each employee will be able to see if they forgot to complete their timesheet next time
523
.. i18n: they sign into the system.
526
.. i18n: single: module; board_project
528
To use this dashboard, install the module :mod:`board_project`.
530
.. i18n: To use this dashboard, install the module :mod:`board_project`.
532
522
To use this dashboard, install the module :mod:`board_project`.
534
524
.. i18n: .. index::
535
.. i18n: single: timesheets; evaluation
525
.. i18n: single: timesheets; evaluation
566
556
.. i18n: .. note:: Timesheets and analytical data
558
.. i18n: The implementation of timesheets in Open ERP relating to analytic entries is managed by an
559
.. i18n: inheritance mechanism:
560
.. i18n: the timesheet object inherits the analytic entry object.
562
.. i18n: The information is therefore not encoded into the database as two separate events, which avoids
563
.. i18n: many synchronization problems.
564
.. i18n: They are stored in two different tables, however, because a service is an analytical entry, but an
565
.. i18n: analytical entry isn't necessarily a service.
567
.. note:: Timesheets and analytical data
568
569
The implementation of timesheets in Open ERP relating to analytic entries is managed by an
569
570
inheritance mechanism:
570
571
the timesheet object inherits the analytic entry object.
572
.. i18n: The implementation of timesheets in Open ERP relating to analytic entries is managed by an
573
.. i18n: inheritance mechanism:
574
.. i18n: the timesheet object inherits the analytic entry object.
576
The information is therefore not encoded into the database as two separate events, which avoids
577
many synchronization problems.
578
They are stored in two different tables, however, because a service is an analytical entry, but an
579
analytical entry isn't necessarily a service.
581
.. i18n: The information is therefore not encoded into the database as two separate events, which avoids
582
.. i18n: many synchronization problems.
583
.. i18n: They are stored in two different tables, however, because a service is an analytical entry, but an
584
.. i18n: analytical entry isn't necessarily a service.
586
573
The information is therefore not encoded into the database as two separate events, which avoids
587
574
many synchronization problems.
588
575
They are stored in two different tables, however, because a service is an analytical entry, but an
597
584
the analytic accounts.
599
586
.. i18n: .. index::
600
.. i18n: single: benefits
587
.. i18n: single: benefits
602
589
.. i18n: An analytic account should be reflected in the general accounts, but there's no direct counterpart
603
590
.. i18n: of these analytic accounts in the general accounts. Instead, if the hourly costs of the employees
604
591
.. i18n: are correctly accounted for, the month's timesheet entries should be balanced by the salary +
619
606
because it depends on:
621
608
.. i18n: * the extra hours that they've worked,
623
* holidays and sickness,
625
610
.. i18n: * holidays and sickness,
627
* salary variations and all the linked costs, such as social insurance charges.
629
612
.. i18n: * salary variations and all the linked costs, such as social insurance charges.
614
* the extra hours that they've worked,
616
* holidays and sickness,
631
618
* salary variations and all the linked costs, such as social insurance charges.
633
620
.. i18n: The reports that enable you to relate general accounts to analytic accounts are valuable tools for
649
636
Because you've got a system with integrated timesheets you can then:
651
638
.. i18n: * track the profitability of projects in the analytic accounts,
653
* look at the history of timesheet entries by project and by employee,
655
640
.. i18n: * look at the history of timesheet entries by project and by employee,
657
* regularly adjust hourly costs by comparing your rates with reality,
659
642
.. i18n: * regularly adjust hourly costs by comparing your rates with reality,
644
* track the profitability of projects in the analytic accounts,
646
* look at the history of timesheet entries by project and by employee,
661
648
* regularly adjust hourly costs by comparing your rates with reality,
663
650
.. i18n: .. important:: Project Cost Control
652
.. i18n: Controlling the costs and the profitability of projects precisely is very important.
654
.. i18n: It enables you to make good estimates and to track budgets allocated to different services and
655
.. i18n: their projects, such as sales and, R&D costs.
656
.. i18n: You can also refine your arguments on the basis of clear facts rather than guesses if you have
657
.. i18n: to renegotiate a contract with a customer following a project slippage.
659
.. important:: Project Cost Control
665
661
Controlling the costs and the profitability of projects precisely is very important.
667
.. i18n: Controlling the costs and the profitability of projects precisely is very important.
669
It enables you to make good estimates and to track budgets allocated to different services and
670
their projects, such as sales and, R&D costs.
671
You can also refine your arguments on the basis of clear facts rather than guesses if you have
672
to renegotiate a contract with a customer following a project slippage.
674
.. i18n: It enables you to make good estimates and to track budgets allocated to different services and
675
.. i18n: their projects, such as sales and, R&D costs.
676
.. i18n: You can also refine your arguments on the basis of clear facts rather than guesses if you have
677
.. i18n: to renegotiate a contract with a customer following a project slippage.
679
663
It enables you to make good estimates and to track budgets allocated to different services and
680
664
their projects, such as sales and, R&D costs.
681
665
You can also refine your arguments on the basis of clear facts rather than guesses if you have
738
722
:mod:`hr_timesheet_sheet`.
740
724
.. i18n: .. figure:: images/timesheet_flow.png
742
.. i18n: :align: center
744
*Process of approving a timesheet*
746
.. i18n: *Process of approving a timesheet*
726
.. i18n: :align: center
728
.. i18n: *Process of approving a timesheet*
730
.. figure:: images/timesheet_flow.png
748
734
*Process of approving a timesheet*
764
750
--> My Timesheets --> My Current Timesheet`.
766
752
.. i18n: .. figure:: images/service_timesheet_sheet_form.png
768
.. i18n: :align: center
770
*Form for entering timesheet data*
772
.. i18n: *Form for entering timesheet data*
754
.. i18n: :align: center
756
.. i18n: *Form for entering timesheet data*
758
.. figure:: images/service_timesheet_sheet_form.png
774
762
*Form for entering timesheet data*
800
788
second tab to detect the days or the entries that haven't been correctly coded in.
802
790
.. i18n: .. figure:: images/timesheet_sheet_hours.png
804
.. i18n: :align: center
806
*Detail of hours worked by day for an employee*
808
.. i18n: *Detail of hours worked by day for an employee*
792
.. i18n: :align: center
794
.. i18n: *Detail of hours worked by day for an employee*
796
.. figure:: images/timesheet_sheet_hours.png
810
800
*Detail of hours worked by day for an employee*
838
828
Departments --> Departments`.
840
830
.. i18n: .. tip:: Timesheet approval
832
.. i18n: At first sight, the approval of timesheets by a department manager can seem a bureaucratic
834
.. i18n: This operation is crucial for effective management, however.
835
.. i18n: We have too frequently seen companies in the situation where managers are so overworked that they
836
.. i18n: don't know what their employees are doing.
838
.. i18n: So this approval process supplies the manager with an outline of each employee's work at least once
840
.. i18n: And this is carried out for the hours worked on all the different projects.
842
.. tip:: Timesheet approval
842
844
At first sight, the approval of timesheets by a department manager can seem a bureaucratic
845
847
We have too frequently seen companies in the situation where managers are so overworked that they
846
848
don't know what their employees are doing.
848
.. i18n: At first sight, the approval of timesheets by a department manager can seem a bureaucratic
850
.. i18n: This operation is crucial for effective management, however.
851
.. i18n: We have too frequently seen companies in the situation where managers are so overworked that they
852
.. i18n: don't know what their employees are doing.
854
So this approval process supplies the manager with an outline of each employee's work at least once
856
And this is carried out for the hours worked on all the different projects.
858
.. i18n: So this approval process supplies the manager with an outline of each employee's work at least once
860
.. i18n: And this is carried out for the hours worked on all the different projects.
862
850
So this approval process supplies the manager with an outline of each employee's work at least once
864
852
And this is carried out for the hours worked on all the different projects.
added
removed
i18n/vi/source/book/4/4_11_HR/4_11_HR_timesheet.rst
