The Portal as Your Default: Killing the Email Chase
Client chasing lives in email because that's where you invited it. Here's how a client portal changes the default and quietly ends the follow-up cycle.
Most client chasing isn't a discipline problem. It's an architecture problem. You send a request by email, the client replies with half of it, you reply asking for the rest, they forward it to their spouse, the spouse replies to the wrong thread, and three weeks later you're still short one bank statement. The follow-ups multiply because the channel invites them.
The fix isn't a better reminder cadence. It's changing where the work happens by default. When your client portal — not your inbox — becomes the place a client goes to answer you, the chase shrinks on its own.
Why email guarantees the chase
Email has three properties that make client accounting harder than it needs to be. Each one quietly generates follow-up work.
- No state. An email doesn't know whether a request is outstanding, partially answered, or done. Only you know, and only by reading the thread. So you re-read threads to figure out what's still missing — that's chasing dressed up as admin.
- No structure. A request for six documents comes back as two, with no way for the client to see the four gaps. They think they've answered you. You know they haven't. Round two begins.
- No single home. The reply lands wherever the client happens to be — a different email, an attachment named 'scan001.pdf', a photo of a receipt on their phone. Now you're collating instead of working.
None of this is the client being difficult. It's the tool doing exactly what email does. If you want to reduce chasing, you change the tool, not the client.
What a portal changes by default
A proper client portal in your accounting client management software isn't just a nicer inbox. It carries state, structure and a single home — the three things email lacks.
Requests that know their own status
When a document request lives on the portal, both you and the client see the same list with the same status. Three of six uploaded shows as three of six. The client can see the gap without you telling them. That single change removes the most common reason you send a follow-up: the client genuinely didn't know they'd left something out.
The list that chases itself
A PBC (provided-by-client) list on the portal can send its own reminders on the outstanding items only — not the whole list, not the items already received. The client gets a nudge that says 'you still owe us these two things,' with a link straight to the upload. You didn't write it, didn't time it, didn't check the thread first. In Finye, these reminders run off the request status, so a client who's completed everything simply stops hearing from you — which is exactly what a good chase should do.
One place, every time
Because everything lands in the portal, there's no collation step. The bank statement, the signed engagement letter, the answer to your question about the trust distribution — all of it sits against the client and the job it belongs to. When a staff member picks up the work, they don't reconstruct a thread. They open the job and everything is there.
Making the portal the default (not the fallback)
Buying software with a portal doesn't reduce chasing. Making it the default channel does. Most firms fail here because the portal becomes the fallback — the thing you use when email gets too messy — instead of the first channel. A few habits fix that.
Stop asking for documents in email entirely
If a client emails you asking what you need, the reply is a link to the portal request, not a list in the email body. It feels blunt for a week. Then it feels normal. The moment you answer a document question in email, you've taught the client that email works, and the chase returns.
Set the request at the start of the job, not mid-way
The tax return that stalls usually stalled because the request went out late and vaguely. When your client accounting workflow generates the PBC list as the job starts — ideally from a job template so it's the same every year — the client has the full picture up front and the reminders start doing their job immediately.
Tie the portal to the obligation, not just the email address
This is where account practice management software earns its place over a generic file-sharing tool. A portal that's connected to your compliance deadlines knows that the BAS is due, knows which documents that BAS needs, and can escalate the reminder as the deadline approaches. A standalone portal just holds files. The value is the link between the request, the job, and the obligation behind it.
What actually happens when you make the switch
Firms that move document collection onto the portal usually notice the same pattern. The volume of 'just following up on my email below' messages drops, because the follow-up is automated and targeted. The volume of half-answered requests drops, because the client can see the gaps. And the time spent reconstructing what's outstanding drops to near zero, because the status is visible at a glance instead of buried in a thread.
The knock-on effect matters more than the time saved. When collection is clean, jobs start on time. When jobs start on time, your turnaround improves and your work-in-progress doesn't age while you wait on a client. The chase wasn't just costing you the minutes spent following up — it was holding the whole job hostage.
The one rule worth keeping
If you take one thing from this: never answer a document request in the channel you're trying to escape. Every time you list what you need in an email, you've told the client that's where the work lives. Point them at the portal, let the request carry its own status, and let the reminders run themselves.
Client chasing feels like it's about persistence. It's really about defaults. Change where the client goes to answer you, and most of the follow-up you do today simply stops being necessary.