The Missing Signature You Only Notice at Lodgment
The client info you're waiting on rarely arrives because you asked. Here's how a portal that tracks its own requests ends the chase for good.
Every practice has a version of the same conversation. It's the third week of the job, the return is 80% done, and someone asks the question that stops everything: "Did we ever get the private health statement back from the Nguyens?" Nobody's sure. You search your inbox. You find the request you sent — and the follow-up you sent nine days later — but no reply. The work sits idle, not because you couldn't finish it, but because a single document never came back and nobody was tracking whether it had.
This is the quiet tax on almost every accounting firm: the work isn't waiting on your skill, it's waiting on information. And the systems most firms use to gather that information — email, a phone call, a note-to-self — have no memory. They send a request into the void and forget about it. The chasing that follows isn't a discipline problem. It's a design problem.
Email is a great way to send a request and a terrible way to track one
When you ask a client for documents by email, you create an obligation that lives entirely in your head. The email itself doesn't know whether the client replied. It won't remind you on day five. It won't tell you which three items of the seven you asked for are still outstanding. If the client sends back four attachments in two separate replies, you're now reconciling a checklist against a threaded conversation, by hand, hoping you didn't miss one.
Multiply that across a busy tax season and you get a firm where staff spend hours each week reconstructing the state of requests that should track themselves. This is the gap that account practice management software is supposed to close — and where a genuine client portal earns its place, rather than being a login page nobody uses.
A portal that tracks its own requests
The difference between an email and a portal request is that the portal remembers. When you raise a request through Finye's client portal, it becomes a live item with a status: sent, opened, partially completed, done. You're no longer asking "did they reply?" — you're looking at a list that answers the question for you.
That changes the daily rhythm of a job in a few concrete ways:
- The checklist is the request. Instead of listing seven documents in the body of an email, each item is tracked individually. The client can see they've uploaded five and two remain. You can see the same thing without opening a single message.
- Uploads land against the client record, not your inbox. The private health statement isn't buried in a reply from a personal Gmail address. It's attached to the job, where whoever picks up the work next can find it.
- Reminders happen without you deciding to send them. The follow-up you'd normally write from scratch on a Thursday afternoon runs on its own, so the nudge lands even when you're heads-down on something else.
- The job's real blocker is visible on the board. When work stalls, you can see it's waiting on the client — not sitting untouched because someone assumed someone else was handling it.
None of this requires the client to learn a new system or install anything. They get a link, they see a clear list of what's needed, and they upload. The portal does the accounting client management work of matching each response back to the request that prompted it.
Why clients stall — and why it's usually not their fault
It's easy to blame the slow client. But most of the time, people stall because the ask was unclear. A long email with seven documents mentioned in three paragraphs is hard to action. Someone reads it on their phone, thinks "I'll do that tonight," and it's gone.
A portal request reframes the ask as a task with a finish line. The client can see exactly what's left, tick items off as they go, and get a small sense of progress each time. That structure does more to move a job along than any number of follow-up emails, because it removes the ambiguity that caused the delay in the first place.
It also protects the relationship. Chasing feels bad on both sides — you feel like a nag, the client feels harassed. When the system handles the reminders and shows the client precisely what's outstanding, you take the friction out of the interaction. The client experiences client accounting that feels organised rather than chaotic, and you stop spending your goodwill on the mechanics of collection.
The compounding cost of a request you can't see
Consider what a single untracked request actually costs. The job sits in your work-in-progress, unbilled, for the extra days or weeks it takes to notice the gap. Staff context-switch back into a return they'd mentally closed. The lodgment date creeps closer while you wait. And at the end, when you finally chase and receive the missing item, you've spent more time managing the request than doing the work it unblocked.
Now multiply that by every open job in the practice. The individual cost is small; the aggregate is a firm that feels permanently behind, staffed by people who spend a meaningful slice of their week doing administrative reconstruction instead of client accounting work.
Good client accounting management software doesn't make clients faster. It makes the state of every request obvious, so nothing falls through the gap between "sent" and "done." The chasing you do today isn't a sign that you need to be more diligent — it's a sign the request had nowhere to live except your memory.
Close the loop before you open the job
The practices that escape the chase treat information-gathering as part of the job's design, not an afterthought. Before work begins, the outstanding items are raised as portal requests. As documents arrive, the checklist fills in on its own. When everything's in, the job moves to the next stage — and nobody had to ask "did we ever hear back?"
That's the standard worth aiming for: a firm where the missing signature surfaces the moment it's missing, not at lodgment. In Finye, the portal, the checklist and the job board are the same system, so a request you raise is a request you can always see through to done — without a single reminder written from memory.