The Half-Finished Return: Why Clients Stall Mid-Job
A tax return doesn't stall because the work is hard. It stalls because the client owes you one more thing — and no one told them clearly. Here's how a portal fixes that.
Look at any job that's been sitting in "In Progress" for three weeks, and you'll usually find the same thing: the work isn't waiting on you. It's waiting on the client. One missing document, one unanswered question, one signature that never came back. The return is 80% done and it can't move.
This is the quiet killer of throughput in an accounting practice. It doesn't show up as a crisis. It shows up as a slow, steady accumulation of jobs that are almost finished — and a team that keeps context-switching back to chase the last 20%.
Why work stalls at the last mile
The frustrating part is that the underlying work is often trivial. You need the interest summary, or confirmation of a private-use percentage, or a signed authority to lodge. Minutes of effort, once you have it. But getting it turns into a project of its own.
Here's the typical sequence. You email the client asking for the missing item. They read it on their phone at a traffic light, mean to reply, and forget. A week passes. You send a follow-up. They reply asking what, exactly, you needed — because the original request is now buried in their inbox. You re-explain. They send the wrong document. You clarify. Eventually it arrives.
None of that is accounting. It's coordination overhead, and it multiplies across every open job. When you're running compliance work at scale, the last mile is where your capacity quietly disappears.
The request that never lands
Email is the root of the problem, not the client. An emailed request has no state. It can't tell you whether the client has read it, actioned it, or lost it. It doesn't know it's still outstanding. It sits in a thread, competing with every other message in a busy person's inbox, and it relies entirely on both parties remembering.
Worse, email gives the client no structure. "Can you send me your rental statements and the loan interest figure?" is two requests in one paragraph. The client sends one, thinks they're done, and the job stays stuck on the other. You didn't get a partial response — you got a false finish.
Good accounting client management software replaces the open-ended email with a structured request that has status. The client can see exactly what's outstanding, tick items off as they provide them, and see when they're actually finished. And you can see the same thing from your side, without opening a thread and scrolling.
What a client portal changes about the last mile
A portal turns the missing-item problem from a chase into a checklist. Instead of an email that decays over time, the client has a front door — one login where every outstanding request for them lives in one place.
Practically, this changes three things:
- The request is itemised. Each document or answer is a discrete line item, not a paragraph. The client provides three of five and can see that two remain. Nothing gets a false finish.
- The reminders run themselves. When an item is still outstanding, the system follows up on a schedule you set. You're not the one sending the third reminder — the portal does it, politely and consistently, until the item comes in.
- The upload reaches the job. When the client provides something, it lands against the work item it belongs to, not in an inbox you have to triage. The person doing the return can see it's arrived.
In Finye, the portal is tied directly to the work item on your board. A request goes out, the client responds through their one login, and the documents attach to the job itself. The status on your board reflects reality — you can tell at a glance which jobs are genuinely blocked on you versus waiting on the client, and the automated reminders handle the waiting without anyone lifting a finger.
The status question you answer ten times a day
There's a second cost to the stalled job, and it's the flip side of chasing: clients chase you. "Any update on my return?" "Did you get what you needed?" "When's this likely to be done?" Each one is a small interruption, and each one you answer by going and checking.
A portal answers most of these before they're asked. When the client can log in and see that the job is waiting on two items from them — clearly listed, with the ball plainly in their court — the "any update?" email largely disappears. The status is visible, so it doesn't need to be requested.
This is the real shift. You're not just reducing your outbound chasing. You're reducing the inbound chasing too, because both sides are looking at the same source of truth instead of trading messages to reconstruct where things stand.
Making the last mile a design choice
If jobs routinely stall at 80% in your practice, that's not a client-discipline problem. It's a process design problem, and it's fixable. A few principles:
- Request everything in one structured place. Don't split requests across email, phone and portal. Give the client one door and one list.
- Make outstanding items visible to both sides. The client should never have to ask what's left, and you should never have to open a thread to find out.
- Automate the follow-up, not the judgement. Let the system send routine reminders. Save your attention for the client who genuinely needs a conversation.
- Attach responses to the work. A document that arrives without landing on the job it belongs to is a document you'll go looking for later.
Compliance work has a natural rhythm — the same documents, the same questions, the same last-mile gap, job after job. That repetition is exactly what makes it worth designing around. When the request, the reminders and the responses all live against the work item, the half-finished return stops being the norm. Jobs move because the system keeps them moving, and your team spends its time on the accounting, not the coordination.