Because payroll and project costing are separate systems with separate deadlines. People log time for billing and then complete a second return for payroll, and the two disagree.
Finance reconciles them at month end, which is a day of work producing a number that is approximately right and impossible to defend line by line.
Time logs once against the task it was spent on. Approval makes it billable value in Books and cost against the project in Loop at the person's rate.
Where pay depends on hours — overtime, shift premia, unpaid leave — the same approved hours feed the pay run in Nest, which posts its result to the ledger.
It will not expose salaries. Project cost uses a cost rate; individual pay stays in Nest under payroll permissions, and Loop never sees it.
It also does not approve time. Submission and approval stay separate, because approval is what makes an hour billable.
Project cost and payroll agree by construction rather than by reconciliation.
The month-end close shortens, and the cost of a team on a project is a figure with the specific timesheet lines behind it.
Yes, by role, where showing individual rates would expose pay.
Yes, through the pay run, and it reduces available capacity.
Finance and whoever you permit; project owners usually see cost, not rates.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.