Loading
A ledger records the end of something. The interesting part is the chain before it: what was delivered, what was approved, and who decided it was billable.
These three follow that chain from work to cash, and back out to the project the money came from.
Software fails at boundaries. A feature list cannot show you one; a journey has to.
Work to invoice, invoice to cash and expense to margin are the three chains where finance normally waits on somebody else. All three shorten for the same reason: the posting arrives from the document rather than an import.
Invoice to cash is the one with a human end. Chasing based on behaviour rather than a monthly list is what keeps the customer while getting the money.
Expense to margin looks small and is not. Billable expenses forgotten on travel-heavy work are often the difference between a profitable project and a break-even one.
Not because anyone was careless — because the record stopped at the edge of the tool, and somebody had to carry it across by hand.
Who runs Books →If your close is slow, read work to invoice. It removes the largest single category of chasing.
If your cash is unpredictable, read invoice to cash — the behaviour section is the part that changes outcomes.
For delivered-work billing, yes. Fixed-fee invoicing runs the chain without it; what you lose is the line-level evidence behind the amount.
About a week, usually one project followed from sold price through to a reconciled payment.
The schedule changes and the chain does not. What matters is whether the amount is derived or retyped.
Between delivery and invoice. Somebody summarises the month by hand, and finance bills from the summary rather than the work.
Yes, and it is the shortest one. Hours to run to posting, with nothing exported in the middle.
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.