The Status the Client Can See: A Portal That Answers Itself
Most client chasing runs both ways. Give clients a portal that shows where their return really stands, and half the follow-up emails never get sent.
Chasing clients is the obvious problem. The one nobody names is the reverse: clients chasing you. "Any update on my tax return?" "Did you get the docs I sent?" "When's the BAS due again?" Each one is small. Together they eat a surprising slice of your week, and every reply pulls someone off the actual work.
The instinct is to answer faster. The better move is to make the question unnecessary. If a client can see where their job sits at any hour of the day, the email never gets written. That's the real promise of a portal — not a place to dump files, but a place that answers questions before they're asked.
Why clients chase in the first place
Clients don't chase because they're impatient. They chase because they can't see anything. From their side, they handed over a shoebox of documents in July and then the process disappeared behind a wall. No confirmation the docs arrived. No signal that anything is happening. No sense of what's still outstanding.
Silence reads as inaction. So they poke. And because your reply is often a quick "still in progress, we'll be in touch", the poke achieves nothing except to interrupt your day and reset their timer to poke again next week.
Good accounting client management software closes that visibility gap. The status the client can see is the status that stops the email.
What a portal should actually show
A portal that only stores documents solves half the problem. It gives clients somewhere to upload, but nothing to look at afterwards. The version that reduces chasing shows three things clearly:
- What we're waiting on from you. An outstanding-items list the client can tick off — bank statements, a signed engagement letter, that missing dividend statement. This is the request that chases itself, because the client sees the gap without you naming it.
- Where the job is right now. Not internal jargon, but a plain-English stage: received, in preparation, in review, ready for your signature, lodged. Even a single honest status line kills most "any update?" emails.
- What needs a decision or a signature. Anything sitting on the client's side — an engagement letter to e-sign, a draft to approve, an invoice to pay — surfaced where they'll actually see it, not buried in an email thread from three weeks ago.
When those three are visible, the client's own questions answer themselves. That's the difference between a document store and a portal that reduces work.
The portal only works if it's the default
Here's where most firms undermine their own tool. They set up a portal, then keep replying to email requests, accepting documents as attachments, and sending drafts as PDFs. Now there are two channels, the portal is half-empty, and clients learn that email still works — so they keep using it.
A portal reduces chasing only when it's the single source of truth. If a client emails a document, it goes into the portal, and the reply points them there. If they ask for a status, you don't type it out — you point them to the stage they can already see. Every time you answer a question the portal could have answered, you're training the client to ask you again next time.
This is the same one-thread discipline that stops internal chasing, applied to the client side. One place. One record. One version of where things stand.
Why this ties back to your job statuses
A client-facing status is only as honest as the workflow behind it. If your internal board says "in review" but the return has actually been sitting untouched for a week, showing that status to the client just moves the lie into their view.
That's why the portal isn't really a separate feature — it's a window onto your practice management. In Finye, the work sits on boards as jobs with real statuses, PBC requests live against the client, and the client portal reflects that same underlying state. The client sees an outstanding-items list drawn from the actual document requests, and a job stage drawn from the actual workflow. You're not maintaining a second version of the truth for clients; they're looking at the one you already keep.
The knock-on effect matters. When a status is visible to the client, it stops being a place jobs quietly stall. "In review" that nobody owns is easy to ignore when only staff see it. It's far less comfortable when the client is watching. Visibility creates accountability in both directions.
What it does to your week
The saved time is obvious once you count it. Ten clients each sending two "any update?" emails a month is twenty interruptions, twenty context-switches, twenty replies that add nothing to the file. Multiply across a busy practice and the chasing tax is real money — recovery lost to admin that never touched the work.
But the quieter win is client confidence. A client who can see progress feels looked after, even when the actual answer is "we're waiting on your documents". Visibility reads as competence. Silence reads as neglect, whether or not you're actually behind.
And clients who feel across their own file are the ones who refer you. "They just make it easy" is worth more than any marketing line you could write about yourself.
Making the shift without friction
Rolling out a portal fails when it's positioned as another login the client has to remember. Frame it as convenience, not homework:
- Introduce it at onboarding, so new clients never know another way. The portal is simply how they work with you — where they upload, sign, approve and check status from day one.
- Migrate existing clients at a natural moment — the start of a return, an engagement renewal — rather than a mass "we're changing systems" email.
- Hold the line internally. When someone emails a document, route it to the portal and reply from there. The habit only sticks if your team stops offering the old channel.
None of this requires a new client accounting philosophy. It requires deciding that the status the client can see is the status you maintain — and then refusing to answer by hand what a well-kept portal already answers on its own.
Chasing runs both ways. Close the visibility gap on the client's side, and a large share of your follow-up simply stops happening.