Log hours against projects and review the company's timesheets

Both menus are the same records with different scope. The list shows Date, Project, Task, Description, Sales Order Item (filled when the task bills a sale order — that link is what the billing-type report reads) and Time Spent, with the period's total at the bottom. Behind the list sit kanban, calendar-style browsing by date filters, pivot and graph. The search offers the usual date filters and group-bys; All Timesheets plus Group by › Employee is the weekly review screen.

Each entry silently carries two derived values: its cost (hours × the employee's hourly cost, recorded negative as an expense against the project's analytics) and, on billable tasks, its revenue linkage through the sales order item. Neither is typed on the line — both flow from setup, which is why the directory and payroll topics come before this one.

An entry refuses to save without a project — by design; the project is what makes the hour mean something. For genuinely internal time, keep an explicit Internal project rather than abusing a customer's.

Somebody's hours cost nothing in the project figures — their Hourly Cost is zero on the employee's Settings tab; entries logged after it is set are priced, the old ones keep the old cost.

An employee sees no Timesheets app — their user lacks the Timesheets access right; the app is per-user, not automatic with an employee record.

The week looks empty although people worked — check the date filter first; My Timesheets opens on this week, and last week's diligence hides one filter away.