With the transition from Time Log to Timesheet, project billing workflows seem to have been deleted.
1: Since Timesheets, as opposed to Timesheet Detail, are the doc to be called during invoicing, the problem arises in leaving the responisibility of timesheets to be consistent in project field on the employee. If there were to be a mistake, it’s not something that can be caught, or filtered down, without opening each timesheet.
It would be far too easy for a timesheet to be linked with an invoice, whilst including irrelevant entries. The container is not only removing ease of access, but there is no way for entries to be reattributed to other timesheets without re-entry.
The format of time logs was simply filtering down to project, which inherently didn’t require manual searching.
- Submission. It’s also assumed that it is the employees responsibility to submit the entire sheet at certain times/timelines before anything can be processed with it. While the standard is a “weekly” timesheet, it’s far less malleable from the admistrative side of things, chasing down confirmation that it’s complete, or even accurate, before it’s submitted.
Time logs, being a daily activity, was usually not an issue, barring a day of a late entry. (Usually not a week worth of billable time, or by the time an invoice gets generated, that it would be an issue)
When using the beta at beta.erpnext.com, it looks like not only employee, but billing/costing amount is selectable. It seems pretty far fetched that this would be put in the hands of employees, so I’m assuming permissions can restrict unauthorized information being entered.
Very case specific, but as a company that provides labor for the most part, transparency is given pre-emptively, as opposed to by-request. This means that we require our time logs to include notes on the tasks handled in that day. This gets transferred to the Time Log Batch, and is handed to customers alongside the invoice.
While it’s possible to use one timesheet per time entry under the new system, printing them from list-view results in page breaks for every entry.
- Calendar view completely unavailable. List views can only describe so much from a first glance. The naming series set up, is very loose and vague unfortunately. It needs some great memory to be able to attribute any detail to the numbers provided.
I propose that the timesheet_detail doctype become editable and viewable alone, and that they can be grouped by administrative users under “timesheets”.
This was created for users to share experience opinions as requested.