Prices are captured when work is approved. That timing is what makes an invoice stable — but it also means work approved before a rate existed carries no price, and nothing about that is obvious from a report showing zero revenue.
This screen exists to make it obvious.
1. Why work can end up unpriced
- It was approved before billing was set up, or before a rate covered it.
- No rate layer matched its date, person, project or cost centre.
- Its rate is in a different currency from the client, so it cannot be billed to them.
- It was edited after approval, so the recorded hours no longer match the entry.
2. The four figures
| Figure | What it means | What to do |
|---|---|---|
| Approved entries | Everything that could carry a price | Nothing — this is the denominator |
| Never captured | Approved, but no price was ever recorded | Run Price what is missing |
| Billable, no rate | Captured, but no rate applied on that date | Add a rate, then re-price |
| Hours changed since capture | Edited after pricing, so the amount is stale | Re-price the period |
3. Pricing what is missing
Price what is missing fills gaps only. It never changes an amount that already exists, so it is always safe to run and safe to repeat.
4. Re-pricing a period
Re-price this range recalculates from today's rates. Use it after correcting a rate that was wrong.
Both actions are deliberately manual. A job that silently rewrote money on a schedule would be worse than one somebody chose to run.
5. What re-pricing will not touch
Work on an issued invoice keeps its original price, whatever the rates say now. The re-price reports how many entries it left alone for that reason — a silent skip would look identical to having nothing to do.
To correct an amount that has already been invoiced, void the invoice, fix the rate, re-price and raise a new one. See Invoices.