Log hours

Record the hours worked per request/project. Each logged hour feeds: the client's contract usage (if billable), the real cost (your hourly rate × cost with charges) and the profitability.

The top adds up the logged hours, billable hours, value and number of entries for the period chosen on the filter rail (this month, last month, 30 days, all or dates). The sum is done in the database over the whole period; before, the screen only looked at the 200 most recent entries.

The new time entry button opens a quick dialog on top of the list itself: choose the request (mandatory), the person, the date, the hours and the billing classification — the request and person combos have text search, just type part of the name. The description of what was done is optional but worth its weight in gold when justifying the invoice. When you post it, the table and the four indicators at the top update right away, without reloading the page.

Each entry carries a billing classification, shown as a badge in the list: BILLABLE goes into the billable hours and feeds the consumption of the customer's contract; what isn't billable counts only as hours worked — it measures the team's cost and occupancy, but doesn't become an invoice. That's why the screen shows two separate numbers at the top: hours logged and billable hours. The difference between them is exactly the work the company did and didn't charge for.

On the filter rail pick "Last month" and Billing = Non-billable, and apply: KPIs and list show the same cut. Save it as a view to reopen in one click, and export to Excel or PDF from the ⋮ menu.

When the approval gate is active, logged hours go through manager approval before counting toward billing — rejected entries go back for adjustment.

The cost uses salary + regime charges (CLT/PJ) — not the "bare" salary. That's why the margin here is the true margin.

The period selector (This month, Last month, Last 30 days, All or Custom, with From/To) narrows both the entries table and the four indicators at the top at the same time — hours logged, billable hours, amount and quantity. In other words: the card's number is always the sum of what is listed below, never of another set. The Clear button resets the filters to the default. If a total looks strange, first check which period is selected.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

New entry opens the dialog: ticket, employee, date, hours, hourly rate, billing, type and description. If there is an hours approval authority, the entry stays pending and only counts in margin and billing once approved; if it exceeds the contract's hour bank, it generates an excess to bill. The row opens the read-only record — to correct, open the ticket.

The amount card and the entry's "Hourly rate" field follow your profile's "View Amounts" governance: whoever doesn't have that permission sees the hours normally, but doesn't see money — neither on screen nor in the export, which comes out masked the same way. It's neither a defect nor a cache issue: it's the same rule that applies to every currency amount on the platform. If you need to see the amounts, ask the account administrator to enable "View Amounts" on your profile.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".