The Documents That Trickle In: A Portal That Collects Everything
Most client chasing isn't about one missing form — it's about documents arriving one at a time. Here's how a structured portal collects a full request in a single pass.
Ask any practice manager where the tax season backlog really comes from, and they won't point to the lodgment queue. They'll point to the inbox. Half-finished PBC lists. A signed engagement letter with no supporting documents behind it. A client who sends three receipts today, promises the rest "next week", and disappears until you chase again. The work isn't stuck because your team is slow. It's stuck because the information arrives in fragments.
This is the quiet tax on every accounting practice: not one big chase, but a hundred small ones. And no amount of good client accounting software fixes it if the collection method is still email.
Why documents trickle instead of arrive
Email is a terrible container for a request that has parts. When you send a client a list of six items over email, you've created six opportunities for a partial response. They reply with what's on their desk, mean to send the rest, and forget. There's no shared view of what's outstanding — only your memory versus theirs.
So the cycle begins: you chase, they send a bit more, you chase again. Each round adds a day or two of lag, and multiplied across a client list, that lag becomes your whole turnaround problem. The job can't start until the last document lands, and the last document is always the one nobody's tracking.
The fix isn't a better-worded reminder. It's changing the container. A structured request has to behave like a checklist that both sides can see, where the client knows exactly what's left and you know exactly what's arrived — without opening an inbox to work it out.
What a request should actually do
A proper collection request in your account practice management software should carry a few things email never can:
- A visible list of every item, so the client sees six requests, not one vague ask. Each one is a discrete thing to tick off.
- Per-item status, so both you and the client can tell what's received, what's outstanding, and what's been reviewed and accepted.
- Upload in place, so documents attach to the request itself, not scattered across replies you have to reassemble.
- Automatic follow-up on the gaps only, so reminders name the specific items still missing rather than re-sending the whole list.
The difference is that the request answers its own "where are we up to?" question. When a client logs into the Finye client portal, they don't see a wall of email history — they see the two things they still owe you, highlighted, with a place to drop them. That framing changes behaviour. People finish a short list; they abandon a long paragraph.
Collect the whole list in one pass
The single biggest lever on document lag is designing the request so it can be satisfied in one sitting. That means front-loading the complete list at the start of a job rather than discovering what you need halfway through.
For a tax return, that's every source document, prior-year adjustments, and any specific queries you already know you'll have — packaged into one request the moment the engagement is signed. For a BAS, it's the bank data, the payroll figures, and the odd receipt that never makes it to the ledger. The point is to stop the drip: if the client can see everything you need in one place, they can gather it in one effort instead of ten interruptions.
This is where accounting client management software earns its keep over a generic file-sharing folder. A folder tells you a file exists. It doesn't tell you the request is incomplete, whose turn it is to act, or that the deadline is four days out. A structured portal ties the documents to the job, the deadline, and the client record — so an outstanding item is a live status, not a note in someone's head.
Templated request lists for repeatable work
If you do the same type of job hundreds of times a year, the request list shouldn't be rebuilt by hand each time. The set of documents for an individual return, a company return, or a quarterly BAS barely changes between clients. Save the list once as part of the job template, and every new instance of that job launches with the full request already attached.
That does two things. It removes the risk of a staff member forgetting an item — the same omission that causes a second chase two weeks later. And it means the request goes out complete and consistent, so clients across your book get the same clear ask every time. Standardising the collection is the same discipline as standardising the work itself.
Let the follow-up run without you
The reason chasing eats so much of your team's week is that it's manual and it's judgement-heavy. Someone has to remember who's outstanding, decide it's been long enough, find the original request, and word a polite nudge. Do that fifty times a fortnight and you've spent a real slice of chargeable time on admin that produces nothing.
When the request lives in the portal, the follow-up can be automatic and precise. Reminders fire on a schedule you set, reference only the items still missing, and stop the moment the client uploads. Your team doesn't decide when to chase or what to say — they just see the request tick over from outstanding to complete. The chase stops being a task and becomes a background process.
The payoff: jobs that start on time
Reducing document lag isn't really about tidiness. It's about turnaround. Every job in your practice has a start line, and that start line is "we have everything we need." The faster a request goes from sent to satisfied, the sooner the work begins and the more predictable your capacity becomes across a busy period.
Move collection out of the inbox and into a structured request, front-load the whole list, template it for your repeatable jobs, and let the follow-up run itself. Do that and the trickle stops. Documents arrive as a set, jobs start when they're meant to, and the hundred small chases that used to fill your week simply stop happening.
That's what good client accounting looks like from the inside — not more chasing done faster, but a system where the request does the collecting for you.