The Documents You Asked For One at a Time
Chasing clients for source documents piecemeal wastes days per return. A structured portal request that lists everything upfront closes the gap.
Most client chasing isn't one big problem. It's a hundred small ones. You email a client for their PAYG summaries. Two days later they send them, and you realise you also need the private health statement. Another email. Then the rental property figures. Then the receipt for that deduction they mentioned on the phone. By the time you have everything, three weeks have passed and you've written four emails for a return that would have taken forty minutes to prepare in one sitting.
The problem isn't the client being slow. It's that you asked for the documents the way you remembered them — one at a time, as gaps appeared — instead of asking for all of them at once, in a form the client could actually work through.
Why piecemeal chasing costs so much
Every separate request restarts the clock. The client reads the email, files it under "later", forgets, and you follow up. That cycle can take a week per item. String five items across five emails and you've turned a same-day task into a month-long back-and-forth.
It also fragments the record. When source documents arrive across a dozen email threads, someone has to hunt through an inbox to confirm what's in and what's still missing. The status of the job lives in your memory, not in your accounting client management software. Ask a colleague to pick up the return and they can't tell where it stands without reading everything you read.
And it erodes the client's confidence. From their side, a firm that emails five times for five things looks disorganised — even when the delay is caused by their own responses. A single, clear request that lays out everything needed feels professional and, crucially, gets actioned faster because the client can set aside one block of time to deal with it.
The fix: ask for everything, once, in one place
A client portal changes the shape of the request. Instead of drip-feeding items as you notice them, you send one structured list at the start of the job: every document, every question, every figure you need to complete the return. The client sees the full scope, works through it at their own pace, and uploads directly against each item.
The difference is not just tidiness. It's that the request becomes a checklist both sides can see. The client knows exactly what's outstanding. You know exactly what's arrived. Nobody has to ask "what else do you need?" because the answer is on the screen.
What a good portal request includes
- Every item spelled out. Not "send your tax documents" but a line for each: PAYG summaries, health insurance statement, dividend statements, rental property income and expenses, work-related deductions, and so on.
- Space for answers, not just uploads. Some things aren't documents — they're questions. Did you use your car for work? Did you sell any shares? Let the client respond in the same place.
- A live view of what's done. As the client uploads, items tick off. Both sides watch the list shrink.
- Reminders that fire on their own. Outstanding items nudge the client without you touching the keyboard.
Build the request from the work you already do
The best requests aren't written from scratch each time. An individual return needs the same categories of information every year; a company return needs its own set. Once you've built the list for a return type, it becomes a template you reuse for every client of that type.
This is where a portal earns its place inside your practice management software rather than sitting off to the side as a standalone file-sharing tool. When the request is tied to the actual work item — the return sitting on your board — the uploaded documents attach to the job, the outstanding items show against the job's status, and the whole thing moves through your workflow without anyone copying files between systems. In Finye, the portal request is part of the job, so the answer to "what's this return waiting on?" is visible without opening your email at all.
The chase that runs itself
Once the request is out, the follow-up should not be your job. A client who hasn't uploaded by the deadline you set gets a reminder automatically. A client who's uploaded everything triggers no reminder at all — because the system knows they're done. You stop being the person who remembers to chase, and the return moves forward whether or not you had headspace for it that week.
This matters most in tax season, when you might have two hundred returns in various states of "waiting on client" at once. Tracking that manually is impossible. But if every outstanding item lives on a job, in one view, you can see at a glance which clients are holding up which returns — and the reminders keep going out while you work on the ones that are ready.
What changes when you stop asking one at a time
Firms that move to a single structured request usually notice three things quickly:
- Returns come back faster. A client who receives one complete request tends to deal with it in one go, rather than in a slow trickle across a month of forgotten emails.
- Fewer things fall through. When the list is explicit, you don't discover a missing figure at lodgment. It was on the request from day one, and its absence was visible the whole time.
- Handovers stop hurting. Any staff member can look at the job and see what's in, what's out, and what the client's been asked. The knowledge isn't trapped in one person's inbox.
The goal of good client accounting software isn't to send more polished emails. It's to remove the need for most of them. When you ask for everything once, in a place the client can work through and you can watch fill up, the chasing largely takes care of itself — and the return that used to drag across a month gets finished the week you started it.