AI for Collections in Professional Services: Lock-Up, Billing and the Client You Want to Keep
In a firm that sells its people's time, the debtor ledger is the last place the problem starts. By the time a balance shows as overdue, the work was done, some of the time was recorded, a draft bill waited for a partner, and an invoice went out that the client's payables function may have quietly parked for a reason nobody at the firm has been told.
Collections is where that becomes visible. It is rarely where it began. Most of what a firm calls a collections problem is a billing problem wearing a collections costume, and the slowest part of turning effort into cash happens inside the firm.
Lock-up is one number with two halves
Finance watches the debtor ledger because it is the half with an external villain. Unbilled work in progress has no villain at all. It is the firm's own money in the firm's own system, ageing and becoming less collectable every week: a narrative written long ago is harder to defend, and a client who has forgotten the work is likelier to query the bill.
Treat both halves as one cycle and the AI work changes shape. An agent pointed at overdue invoices alone is working the last stretch of a long pipe. Point it at the whole pipe and the earliest interventions turn out to be the cheapest.
Work in progress nobody has looked at
Most unbillable time was decided by inattention rather than by a person. The matter drifted, the budget went, and the balance became too old to defend.
An agent can read open matters against their fee basis and raise exceptions addressed to the responsible partner: time recorded where no live engagement letter sits behind it, unbilled entries past the firm's ageing threshold, a fixed fee job over budget with deliverables outstanding, disbursements unrecovered, matters that finished and were never billed.
The list is not the value; your system already produces one and it is ignored. The value is that each exception arrives with the entries, the history and a proposed action attached, so the partner spends minutes rather than an afternoon.
The bill sitting in a partner's drafts folder
Ask where the longest delay sits and finance will say the client; look at the timestamps and much of it sits between the draft bill being produced and the partner releasing it. The reasons are human: narratives need rewriting, a write off decision has to be made and nobody enjoys making it, and there is always something chargeable to do first.
An agent cannot make a partner decide. It can make deciding cheap: prepare the bill until only judgement remains, then chase the internal owner with the discipline a credit controller applies to a client. Few people in a firm have the standing to chase a partner consistently, which is why this is worth more than it sounds.
Narratives and billing guidelines
A bill here is a document the client reads looking for reasons to pay less. Entries that say little, a whole day in one block, internal shorthand: each invites a query, and a query restarts the clock on the whole invoice.
Clients also attach billing guidelines: which grade may do what, whether travel time is chargeable, whether two of your people at the same internal discussion may both bill it. They are long, they differ by client, and nobody reads them while drafting, so entries are submitted, disallowed and lost.
An agent that has read your house style and that client's guidelines regroups time into phases the client recognises, rewrites narratives to describe the work and its purpose, and lists every entry at risk with the requirement it offends. Flagging matters more than rewriting: a thin entry raised while the fee earner remembers the day can be fixed; after the client challenges it, it is a write off.
Purchase orders, references and the invoice nobody received
The most expensive invoice is the one the client never processed. Large clients require a purchase order number, a matter reference, a cost centre, sometimes a named approver, usually a portal. Miss one and the invoice does not bounce. It parks, nobody tells you, and the first chase gets a polite answer.
This suits an agent: it is rule compliance with a checkable answer. Before submission it confirms the invoice carries the reference the client requires, the purchase order is open with enough value left, and the window has not closed. Afterwards it looks for the acknowledgement that proves receipt and treats its absence as an exception.
The portal is the blind spot. Once an invoice sits inside a client's payables system nobody at the firm can see it, so an agent should read the status there rather than at the next ageing review.
Chasing a debtor who is also a client you want more work from
This tension makes collections here its own discipline. In a consumer book the relationship ends with the debt. In a fee earner firm the debtor is a general counsel or a programme lead whose next instruction you are pursuing, and the person best placed to ask for money is the least willing to risk it.
The question is not how to automate the chase but how to make it cost as little relationship as possible. An agent can prepare a contact that is short, specific and correct: which invoices, what they cover, what the client has already acknowledged, and what is genuinely open. It can pick the right recipient, often accounts payable rather than the partner's own contact, and hold a chase while a proposal is live.
Every word that leaves the firm is approved by a person, because in a business that sells judgement the contact is itself a sample of the firm's judgement.
Telling a genuine grievance from a stall
These look identical on an aged debt report and need opposite handling, and here the difference is rarely a line item. The complaint is usually about value: the client expected a different answer, or the same answer sooner, or does not accept the seniority applied. It is often never written down, only implied in a remark to the partner.
The signatures still differ. A grievance follows a deliverable, arrives as a request for a breakdown by phase, or produces payment of everything except the contested block. A stall is flatter: no substantive objection anywhere, other suppliers apparently paid, a rolling series of procedural reasons.
An agent can read correspondence, matter file and payment behaviour together, say which reading the evidence supports, and route ambiguity to a person.
Escalation runs through the relationship partner
Most firms have a formal ladder and an informal rule that overrides it: nothing sharper reaches a client without the relationship partner knowing. Encode that as a gate, not a notification. Before any step up, the agent should show that the partner was asked and answered, that no live proposal makes this the wrong week, and that any issue the client raised was dealt with internally.
The decision to escalate stays human, and it is rarely only a credit decision. It is a decision about whether you still want the client.
Write off and provisioning
A write off here is not purely an accounting event. It comments on a partner's judgement about what a matter was worth, which is why write offs happen late and in bulk at period end.
An agent makes the decision routine rather than personal by preparing it: how the balance arose, whether the entries behind it were ever defensible, whether the client has paid everything else, whether the amount is contested or merely old. It can propose a provision consistent with the policy the firm actually applies and show where practice and policy have drifted apart. Finance and the partner decide.
How to evaluate it before you trust it
Build a labelled set from settled history: several hundred closed matters where you know the outcome, including bills reduced after a conversation, entries disallowed under guidelines, balances written off and work never billed. A clean set flatters anything.
Measure the errors that carry consequence separately from overall accuracy. The one that matters most is calling a grievance a stall, because that is the error that reaches a client.
Shadow run for a billing cycle or two alongside current practice, then read the disagreements and see who was right. Score drafts for tone and for accuracy separately, because a chase can be accurate and still wrong to send. Then watch behaviour: how long a draft bill waits for release, and how much unbilled time crosses each ageing bucket.
Where AI fails here
Context that exists only in a partner's head
The knowledge that a client is about to restructure its panel, or that the finance director is embarrassed by the delay, sits in no system. An agent chasing a client mid negotiation on a renewal can undo months of work with one correctly worded email, so unless it can see the pipeline and the live matter list it should not initiate contact.
Disputes that are really dissatisfaction with the work cannot be settled through the receivables process. Recognise one and hand it to the partner.
What a better model does not fix
Tone is a live risk. A message that reads as brisk from a utility reads as rude from a firm charging for judgement.
Fluent and wrong does the real damage: a chase citing an invoice credited last week reads perfectly well. Bind every figure in a draft to a value read at drafting time.
Inferring a stall from silence is the standing trap. The absence of a written complaint is not the absence of a grievance.
And no agent fixes time recording nobody does honestly. Entries reconstructed from memory on a Friday are thin at source, and no rewriting downstream makes thin time defensible.
Where to start
Start before the invoice, because that is where the delay is. Guideline checking and submission compliance are the strongest first projects: rule based, with a right answer you can check, touching no client, and removing losses that happen in silence. A work in progress exception queue addressed to named partners is a good second, since every decision stays with the person who owns it.
Chasing comes later, and then only as preparation for the people who own the relationships. Measure the baseline first, or you will not be able to tell whether anything improved.
Adopt AI Partners builds these agents inside your own practice management, billing and document systems rather than as another platform beside them, and stays until your finance team and your partners can run, change and switch off the thing without us.