The Three Emails That Should Have Been One Portal Request
Chasing clients for documents, signatures and answers eats your week. Here's how a client portal turns scattered follow-ups into one tracked request.
Think about the last return you couldn't finish. Chances are it wasn't waiting on your judgement or your workpapers. It was waiting on a client — a missing PAYG summary, an unsigned engagement letter, a one-line answer about whether they'd sold an investment property. And chances are you chased for it more than once.
The chasing is the quiet tax on every accounting practice. It doesn't show up as a line item, but it shows up in your week: the follow-up emails, the "just circling back" messages, the mental note to ring someone on Thursday. Multiply that by a few hundred clients at BAS time or through tax season and you've built a second job out of asking people for things they already agreed to send.
Why the inbox loses every time
The default tool for chasing is email, and email is the worst possible container for it. Here's why.
- You can't see the state. Did they read it? Did they reply and it landed in spam? Did they upload the file to a thread three weeks deep? You end up scrolling to reconstruct what you're owed.
- The client can't see it either. Your request is buried under newsletters, school notices and delivery updates. It's not that they're ignoring you — it genuinely disappeared.
- The follow-up is manual. Every reminder is a decision and an action for you. Nothing nudges the client unless you personally do it.
- The documents scatter. One client sends a photo, another a PDF, another forwards an email from their bank. You're now the filing system, re-saving attachments into folders and hoping you got them all.
None of this is a discipline problem. It's a design problem. When the request lives in an unstructured channel, chasing becomes inevitable — because there's no system holding the loop open on your behalf.
What a client portal actually changes
A proper client portal — the kind built into modern accounting client management software — moves the request out of your inbox and into a shared, tracked space. The difference isn't cosmetic. It changes who does the chasing.
One request, one place
Instead of three emails (send the checklist, follow up on the checklist, send the engagement letter separately), you raise a single request tied to the client and the job. Documents to upload, a letter to e-sign, two questions to answer — all in one view the client logs into. They see exactly what's outstanding and exactly what's done.
The system does the reminding
This is the part that gives you your week back. Once a request is outstanding, the portal can prompt the client automatically — a reminder after a few days, another if it's still open — without you touching it. You set the cadence once; the follow-up runs itself. Chasing stops being a task on your list and becomes a background process.
Uploads land where the work is
When a client uploads a document through the portal, it attaches to the right client and the right work item — not to a random email thread you have to go hunting for. In Finye, that upload sits against the job on your board, so the person doing the work can see it arrived and pick the job back up. No forwarding, no re-saving, no "did you get my file?"
You can see who's holding the ball
The single most useful thing about a portal is that it makes the waiting visible. Open your board and you can tell at a glance which jobs are genuinely on you and which are parked on the client. That distinction matters — because a job stalled on a client shouldn't count against your team's capacity, and it shouldn't be a surprise when a deadline looms.
The compliance angle: portals that chase deadlines, not just documents
Document chasing is one half. The other is deadline chasing. Clients forget their obligations constantly — the BAS due date, the signature you need before you can lodge, the information you asked for a fortnight ago that's now blocking a program deadline.
Because Finye tracks obligations and due dates alongside the work, a portal request can carry that context. The client isn't just being asked for a document in a vacuum; the request is tied to a real deadline you're both accountable to. When the reminder goes out, it lands with weight — and it goes out on time, every time, without you diarising it.
This is the shift from client accounting as a series of manual prompts to client accounting where the system holds the obligations and surfaces them. You're not lodging anything through the portal — that stays in your lodgment tools — but you're never again the reason a return sat half-finished because nobody remembered to ask the client twice.
What to look for when you set this up
If you're evaluating account practice management software with a portal, or turning one on for the first time, a few things separate a portal that reduces chasing from one that just adds another login for clients to ignore.
- Automatic reminders you configure once. If you have to trigger every nudge, you haven't removed the work — you've just moved it.
- Requests tied to the job. Documents and answers should flow back to the specific work item, not into a general document store you still have to sort.
- E-signing in the same place. If the engagement letter or authority lives somewhere else, you've split the request and you'll chase for it separately.
- A clear "waiting on client" state. You need to see, across your whole practice, what's parked and why — otherwise the stalls stay invisible until they're urgent.
- Low friction for the client. The easier it is to respond, the less you'll chase. A portal that's clunkier than email will lose to email.
Chasing less is a system choice
You will never chase zero times — some clients need a phone call, and that's fine. But the volume of routine, avoidable follow-up in a practice is almost entirely a function of where the request lives. Put it in an inbox and you'll chase. Put it in a portal that tracks state, reminds automatically and files what comes back, and most of that work simply disappears.
The three emails become one request. The follow-up becomes a background process. And the return that was waiting on the client gets finished — because the system, not you, made sure the client remembered.