Drilldown logs
Route: /org/resource/bills?tab=drilldown · Permission: View Resource Billings
1. What the drilldown is
Every time log that went into the bill, listed individually and groupable five ways. It is the audit trail: the answer to "why is this bill this amount" is always on this tab.
| Drilldown | Summary | Adjustments | |
|---|---|---|---|
| Granularity | One row per time log | One row per bill | One row per correction |
| Changes anything | No | No | Yes |
| Groupable | Five ways | — | — |
2. What each row traces back to
Every grouping is a different question about the same rows.
3. Using the drilldown — step by step
Step 1 · Choose a grouping
| Group by | Answers |
|---|---|
None | The raw list |
| Resource | Who did the work, and what each person costs |
| Category | Which kind of work consumed the budget |
| Budget Head | How it maps onto finance's categories |
| Task | Which specific pieces of work were expensive |
Step 2 · Read a group header
Each header carries its own subtotals — the count of logs, hours and amount — so you can compare groups without expanding them.
Groups are sorted alphabetically by their label and can be collapsed.
Step 3 · Read the rows
Each row is one time log with its hours and its computed amount.
Resource tells you where the money went; Task tells you what it bought. Between them they explain almost every "why is this bill so large" question without opening a single task.
4. Field reference
Where each grouping's value comes from
| Grouping | Source |
|---|---|
| Resource | The user who logged the time |
| Category | The task's category |
| Budget Head | The budget category, from Organization Settings |
| Task | The task the time was logged against |
How an amount is calculated
Hours × the applicable rate, from the project's billing settings. The drilldown shows the result, not the rate arithmetic.
Rates come from project billing configuration. If a resource or role has no rate, its logs still appear with their hours and add nothing to the total — which reads as a discount rather than as missing configuration.
Group by Resource and look for a row with hours and a zero amount.
What is not here
| Missing | Why |
|---|---|
| Non-billable time | Excluded at generation, by the task's billable flag |
| Logs outside the period | Not in this bill |
| Logs already billed elsewhere | A log can be on one bill only |
| Adjustments | They are corrections to the bill, not logs — see Adjustments |
The drilldown sums the logs. The bill total is the logs plus adjustments. A gap between them is exactly the adjustments applied, and the Adjustments History tab reconciles it.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| View Resource Billings | Access Denied |
| Billable categories | No logs to show |
| Project billing rates | Hours with no amounts |
| Budget categories | The Budget Head grouping is empty |
6. Downstream
The drilldown is read-only. It is the evidence behind the statement PDF and the input to any conversation about correcting a bill.
7. Don't confuse this with…
| Thing | Where | Why it is different |
|---|---|---|
| Drilldown (this page) | The bill | The logs on one bill |
| Time Logs tab | A task | The logs on one task, billable or not |
| Timesheet Analytics | Analytics | Hours across the team, unbilled |
| Reconciliation view | Billing analytics | Billed against logged, across bills |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| A log is missing | Its task is not billable, or it is outside the period, or it is on another bill |
| Hours but no amount | No rate is configured for that resource |
| Budget Head grouping is empty | Tasks are not mapped to budget categories |
| The total does not match the bill | Adjustments are not counted here |
| Groups in an unexpected order | They sort alphabetically by label |
Related
- Adjustments — the difference between this total and the bill total
- Time logs — where each row was created