The Work Is Finished. The Invoice Is a Decision Nobody Made
· 7 min read · Written by Faceela Research & Editorial Team
Reviewed by Ahmed Hassan Algammal — Founder and Enterprise Systems Consultant
Every firm chases its debtors. There is an aged listing, it goes to the partners, somebody has an uncomfortable conversation on a Tuesday, and the oldest lines get escalated. This is normal and it is well run.
Almost no firm chases its work in progress with anything like the same energy — and work in progress is the more expensive of the two, because a debtor is money somebody else has not paid you and work in progress is money you have not asked for.
The salaries behind it are gone. They went out on the last payroll run. The desk, the licence, the partner's review time and the manager's supervision were all bought before anybody thought about an invoice. What is sitting in that unbilled balance is not a receivable in waiting. It is expenditure the firm has already made, waiting for somebody to decide it is worth mentioning.
The chain has six links and five of them have a name
Trace it honestly, from the hour worked to the money in the account.
The work is done. The time is recorded, or reconstructed later. It becomes work in progress. Somebody decides to bill it. The invoice is raised. The money arrives.
Five of those six have an owner you could name in a meeting. The manager assigns the work. The fee earner records the time and the practice manager chases him for it. The system creates the WIP balance on its own. The billing team raises the invoice from a list finance already runs. Credit control chases the cash, weekly, in writing, with an escalation path.
The fourth link is the one that has nobody.
The shape of it
Six links, and only one of them belongs to nobody
Link 1
The work is done
A senior sits with a client's file for three days. The firm has bought those days already — they were paid for on the last payroll run, whatever happens next.
Already spent by here: Salary, review time, the desk, the software licence
Owned by: The manager who assigned it
Link 2
The time is recorded
Or it is reconstructed later, which is a different thing. Everything downstream is built on this entry and cannot be better than it.
Already spent by here: All of the above, plus whatever the recall costs in accuracy
Owned by: The fee earner, chased by the practice manager
Link 3
It becomes work in progress
Nobody does anything for this to happen. The entry lands in an unbilled balance and starts ageing, and the ageing is the only event in the chain that requires no decision at all.
Already spent by here: All of the above. It is now an asset on your own balance sheet
Owned by: The system — automatically, which is the trouble
Link 4
Somebody decides to bill it
Not raises the invoice — decides that it should be raised, at what value, now rather than after the deadline. This is the link the whole chain turns on, and it is not on a calendar, not on a list, and not in anybody's objectives.
Already spent by here: All of the above, plus every month of financing it since
Owned by: Nobody
Link 5
The invoice is raised
Mechanical, fast and well controlled in almost every firm — and it cannot begin one day earlier than link 4 allows it to.
Already spent by here: All of the above
Owned by: Billing, from a list finance already runs
Link 6
The money arrives
Chased weekly, aged into buckets, reported to the partners, escalated when it slips. The one link in the chain that has a meeting about it.
Already spent by here: All of the above
Owned by: Credit control, weekly, in writing
Which is why debtors are chased and work in progress is not
A debtor is somebody else's failure to pay. Work in progress is your own failure to ask, and the difference is that only one of them has a name against it. Both are money you have already spent.
Notice what the fourth link actually is. It is not the mechanical act of producing an invoice — that part is fast, controlled and rarely the problem. It is the prior decision that this work should be billed, at this value, now. That decision is not on a calendar. It is not on a task list. It is not in anybody's objectives, and no report raises an exception when it does not happen.
So it happens when somebody is between deadlines, which in a professional firm is never.
"I will look at it after the filing"
Everybody in this business knows the sentence.
The partner is not being evasive. Billing a client properly requires reading the file, remembering what was agreed, deciding what to do about the three days that ran over, and being ready to defend the number if the client calls. That is forty minutes of real attention, and it is competing with a deadline that has a penalty attached to it.
The deadline wins. Every time, and correctly, because the deadline is external and the billing decision is internal. Then the next deadline arrives.
This is why the problem is structural rather than a matter of discipline. Nobody is being lazy. The firm has simply arranged things so that the only unowned link in its cash chain is also the only one competing directly with statutory dates.
Ageing is the part that decides the outcome
The longer unbilled work sits, the less of it will ever be billed, and the mechanism is not mysterious.
At two weeks, the client remembers the work. He remembers asking for it, he remembers the calls, and an invoice arrives as confirmation of something he already knows happened.
At three months, the client remembers a bill. The work has been absorbed into a general sense that things were handled. He is not being difficult when he queries it — he genuinely cannot see what he is paying for, and the person who could explain it is now busy on something else.
At six months, the conversation is a negotiation, and the firm loses it before it starts, because the alternative to a discount is a fight about work already delivered to a client the firm intends to keep.
| Age of the unbilled work | What the client is being asked | What the firm usually does |
|---|---|---|
| Under a month | To pay for something he remembers requesting | Bills it in full, without a conversation |
| One to three months | To trust that the hours were what you say | Bills it, and quietly rounds down |
| Three to six months | To accept a bill for work he has stopped thinking about | Discounts it to avoid the argument |
| Over six months | To pay for a period he considers closed | Writes off part of it, and does not record why |
Nothing in that table is a policy anybody wrote. It is what happens when a decision has no owner and no clock.
Two things sit in the same balance and they are not the same thing
Here is where a real cost hides.
An unbilled balance normally contains two populations. There is work not yet billed — good work, on live engagements, that will be invoiced as soon as somebody makes the decision. And there is work that will never be billed — the job that went over on a fixed fee, the client who has made clear he will not pay for the third revision, the hours a manager put in on a matter the firm agreed to absorb.
The first is an asset. The second is an expense that has not been recognised.
A firm that carries both in one number is doing something specific: it is reporting an asset that includes a known loss, and it is doing so in the report the partners look at when they decide how much to draw. The number is not fraudulent. It is simply the answer to a question nobody asked precisely enough.
The test is a single question per line, and it takes seconds: if we invoiced this tomorrow, would the client pay it in full? A no is not a problem — jobs run over, that is delivery. A no that has never been recorded is a problem, because it means the write-off will happen eventually, at a moment nobody chose, and it will be explained as a bad month.
Which of the two it is also changes what you should do about it. Unbilled work that will be paid needs a billing decision on a date. Unbilled work that will never be paid needs a reason code and a conversation about why the job went the way it did. Treating both as "we need to bill more" achieves neither.
What to make a vendor show you
On a live system, on real engagements, not on slides.
- Show unbilled work in progress by engagement, aged, on one screen — not a total, and not a month-end report.
- Show it by partner and by manager, so the list has a human being at the top of each column.
- Mark a line as not billable, with a reason, and show that it leaves the asset immediately rather than at month end.
- Show what was written down at the moment of invoicing, separately from what was discounted when the fee was agreed.
- Raise an invoice from recorded time and show which entries were included, which were held back, and who held them.
- Show an alert that fires because a billing decision has not been made — not because an invoice is overdue.
- Reconcile the unbilled balance on that screen to the figure in the accounts.
Item 6 is the one that decides it. Every practice system can age unbilled work, and every one of them will show you a total. A system that treats the absence of a billing decision as an event — with an owner, a date and an escalation, the way an overdue debtor is treated — is doing the only thing on this list that changes the fourth link. The rest is reporting on a problem after it has already cost you.
Item 3 is the quiet one. Most systems will let you write a line off. Far fewer let you record that it was never going to be billable in the first place, which is the entry that tells you something about how the job was run.
The short version
Work in progress is not a receivable. It is money already spent on salaries, sitting in an account, waiting for a decision that belongs to nobody.
Every other link in the chain from work done to cash collected has an owner, a rhythm and an escalation path. The billing decision has none of the three, which is why it loses to every statutory deadline in the calendar and why the balance ages quietly while the debtors ledger gets a weekly meeting.
And a firm that cannot separate work not yet billed from work that will never be billed is carrying a known loss inside a reported asset. The separation costs one question per line. Not asking it costs the difference twice — once as a write-off nobody planned, and once as the lesson about the job that nobody learned.
If your timesheets are reconstructed on a Friday, start there rather than here: everything above is built on entries that have to exist first, and a timesheet filled in on Friday is a memory, not a record. What happens to the value between recorded time and cash is the realisation bridge, and what it means per client is client profitability.
What this looks like built as one system is on the professional and business services page, and the suite itself is ServX — which refuses to let time be logged against a closed project, for the same reason this article exists: a cost that arrives after the decision it should have informed is a cost nobody can act on.
