Loading
Because the decision about what is billable is made at month end, weeks after the work, by somebody who was not there. Half of it is defensible and the other half is a guess nobody wants to defend to the client.
A billable hour is approved time on a task marked billable, priced at the rate the contract holds and tracked through to the invoice that bills it.
The billable flag sits on the task when it is planned, not on the hour when it is invoiced. Rates come from the contract in Flow, so what reaches Books is priced the way it was sold.
A developer spends six hours on a fix caused by our own error. The hours are logged, marked non-billable with a reason, and appear as cost against margin rather than quietly disappearing.
It will not decide whether to bill for something awkward. It records the decision and who made it, so the same question is not reopened next month.
Books draws billable lines for the invoice, margin counts all hours as cost, and utilisation reporting separates the two.
Yes — role rate, person rate or a contract rate, in that order of specificity.
It stays as cost with a reason, so margin tells the truth.
Yes, and the cap warns as it is approached rather than after.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.