The software structures the data. It does not go and fetch it.

This article describes a use case. We have not delivered an engagement in an accountancy practice: what follows is what we observe of the profession and its tools.

Solid tooling, on the wrong half of the problem

Production software — Pennylane, Cegid, Sage, ACD depending on the practice — is good at what it was built for. It structures, it checks, it produces, it archives. A properly equipped practice processes a stream of documents with an efficiency that bears little resemblance to that of fifteen years ago.

But all of them assume the document is already there.

It is not there. It is with the client, in an inbox, on a supplier portal, in a drawer. And the work of getting it out of there is tooled nowhere.

Chasing, the job nobody chose

Ask a team member what takes them the most time on a file. The answer is rarely the review. It is the chasing.

• Knowing, client by client, what is missing at any given moment.
• Asking for it without irritating anyone, on a channel the client actually reads.
• Starting again, because the first request went nowhere.
• Starting again once more, as a deadline approaches.

This work has three unpleasant properties. It is repetitive, it eats time, and it is socially expensive: it is the team member who carries the insistence, and it is the client relationship that absorbs the price.

A practice does not lose its margin on production. It loses it on what it does before it can produce anything.

What an agent could take on

Three things, all of them coordination, none of them a professional call.

• Collecting documents from clients and chasing the missing ones, on the channel where the client answers.
• Preparing the review file from what has arrived.
• Following filing deadlines, client by client, without anyone holding the list in their head.

What does not move: the analysis, the judgement calls, the signature, the advice, and anything that falls under professional judgement. An agent that produced an accounting or tax position would be doing exactly what it must not do.

The objection that always comes first

“Our clients will not answer an agent any better than they answer us.”

That is probably true for a given client and a given message. It is not the right scale. What would change is not persuasion, it is consistency: a reminder that would go out at the right moment, every time, for every file, including the fourth time, including in peak season — precisely when a human team stops chasing because it has something else to do.

The gain would not be being more convincing. It would be never dropping a file because the week was bad.

Why we put this in the conditional

Because we have delivered nothing to an accountancy practice, and saying otherwise would be false.

What we know how to do is established elsewhere: working inside closed practice software, on a machine the practice controls, without exfiltrating data and without ever crossing the line of professional liability. What that would give across a collection campaign remains to be built, and it starts by watching a real week, in the middle of filing season, before writing a single line.

---

Engagements we have actually delivered and use cases are distinguished explicitly in our resources.