Billing
Closing the Gap Between Time Tracking and the Invoice
Revenue leaks in the space between the work being done and the line item being billed. The leak is measurable, and most of it comes from delay.
In any business that bills for time, there is a chain from work performed to cash received, and every link loses a little. The losses are unglamorous and they compound: time not recorded, time recorded without enough detail to bill, time written off at review because the narrative was too thin to defend.
Delay is the main cause
Time entered on the day is broadly accurate. Time reconstructed on Friday afternoon from a calendar and memory is not — and it is systematically low, because forgotten work is never invented but frequently omitted. Reconstructed entries are also thin on narrative, which is what makes them vulnerable at review.
Timesheets reconstructed at the end of the week are not just late. They are quietly smaller.
Make the narrative billable at the point of entry
The reviewer's job is to decide whether the client will accept a line. Give them something to work with.
• What was done, in the client's language rather than internal shorthand.
• Why it was necessary — the request or the obligation it answers.
• The output, if there was one.
• The matter or phase it belongs to.
'Review documents — 2.0' will be written off or queried. 'Reviewed vendor's revised indemnity and marked up clause 11 for call with client — 2.0' will be paid. Same work, same time, different outcome, and the difference was recorded in fifteen seconds.
Bill on a fixed cycle
Invoicing when someone gets round to it produces long, hard-to-verify invoices that clients dispute and pay late. A fixed cycle — the same working day each month, no exceptions — shortens the memory gap on both sides and makes disputes small and specific rather than large and general.
Instrument the leak
You cannot manage what you do not separate. Track these as distinct numbers, by person and by matter:
Where the number drops between two adjacent stages tells you which problem you have. A fall from recorded to billable is a scoping or supervision issue. A fall from billable to invoiced is a review and write-off issue. A fall from invoiced to collected is a collections issue, and a different team owns it.
Set expectations before the surprise
Most write-offs at review are a manager pre-emptively removing a line they expect the client to challenge. That challenge is usually about scope, not rate. An estimate agreed at the start and a short note when the work is running over converts a write-off into an approved variation — the same conversation, held early enough to have a different answer.
The narrative example is exactly right and it's the hardest habit to instil. We now reject timesheet lines under a minimum character count, which sounds petty but moved realisation four points in a year.
Splitting recorded / billable / invoiced / collected was the thing we were missing. We had one blended realisation number and spent two years arguing about whose fault it was.