The PBC List That Never Comes Back Complete
Prepared-by-client requests and AML onboarding both stall on the same problem: scattered chasing. Here's how to make document collection a standard process, not a scramble.
Every compliance job starts the same way: you send the client a list of what you need. Bank statements, loan documents, motor vehicle logbooks, a signed engagement letter, and — for a new client — proof of identity. Then you wait. And chase. And wait again.
The prepared-by-client (PBC) list is one of the most predictable bottlenecks in a firm, yet it's almost always handled ad hoc. One partner emails a Word document. Another sends a text. Someone else keeps a running tally in their head. The result is the same across every practice: work that can't start, WIP that ages, and staff who spend more time asking for documents than doing anything with them.
Two requests, one broken process
There are really two document-gathering moments in the client lifecycle, and firms tend to treat them as separate problems when they're the same problem.
The first is AML/KYC onboarding. Before you can act for a new client, you need to verify who they are — identity documents, beneficial ownership for company and trust structures, and a record that you actually did the checks. This isn't optional busywork. Tax agents and BAS agents have obligations under the Tax Agent Services Act and the associated Code of Professional Conduct, and the AML/CTF regime is expanding to cover more accounting services. Whatever the exact scope for your firm, the expectation is the same: you can demonstrate you verified the client and kept the evidence.
The second is the ongoing PBC request — the annual scramble for source documents at the start of every tax return, financial statement, or BAS. Different documents, same mechanics: a list goes out, documents trickle in, and someone has to reconcile what's arrived against what's still outstanding.
Both fail for the same reason. The request lives in an email, the documents arrive across multiple channels, and no single place shows you what's still missing. Good client accounting software should close that gap — not by adding another inbox, but by turning document collection into a tracked, repeatable step in the job.
Why the email approach quietly costs you
When PBC and KYC requests go out as loose emails, a few things happen every single time:
- Documents scatter. One client replies to the email, another sends via a shared drive link, a third drops paper into reception. You have no consolidated view of what you've received.
- You can't tell what's outstanding. Without a checklist tied to the client, "what are we still waiting on?" becomes a manual audit every time someone asks.
- Chasing is invisible work. The junior who's spent an hour today re-requesting a super statement isn't producing anything billable. Multiply that across every job in the queue and it's a real capacity drain.
- The KYC evidence is fragile. If a licence photo sits buried in an inbox thread, you don't have a defensible record of your identity verification — you have a document you'd have to go hunting for during a review.
None of this is a discipline problem. It's a systems problem. If the only tool you've given people is email, email is what they'll use.
Make the request a job step, not a favour
The fix is to treat document collection as a standard, trackable stage of the work rather than a personal chase. That means three things need to be true.
1. The request is a checklist, not a paragraph
A PBC or KYC request should be a defined list of items, each with a status: requested, received, reviewed. When a job type always needs the same documents — and most compliance jobs do — that list should come pre-built. You shouldn't be reconstructing "what do we need for a company tax return" from memory every year. In practice management software, you set the document checklist once against the job template, and every instance of that job carries it forward.
2. The client has one place to upload
Documents that arrive through five channels can't be tracked. A client portal solves this by giving the client a single destination: they see exactly what's outstanding, upload against each item, and everything lands in one place attached to their record. No email attachments to save down, no shared-drive housekeeping. For KYC specifically, this means the identity documents you collect at onboarding are stored against the client from day one — not floating in a thread.
3. Outstanding items chase themselves
Once the request is a structured checklist with a portal behind it, the follow-up stops being a manual task. Automated reminders can nudge the client on what's still missing without a staff member drafting yet another "just following up" email. The chase happens; nobody has to remember to do it.
Where onboarding and PBC connect
Here's the part firms miss: KYC onboarding and the first PBC request are the same conversation. A new client needs to prove who they are and hand over their source documents to get the first job moving. Splitting those into two disjointed processes — an email for the ID, a separate email for the documents — doubles the friction at the exact moment you want a smooth start.
Handle them together. When a new client comes on, the onboarding flow should collect identity verification, get the engagement letter signed, and open the first document request in one coordinated sequence. The client experiences it as a single, professional intake rather than a series of scattered asks. Your accounting client management software should carry all of it — the KYC evidence, the signed engagement letter, and the job's document checklist — against one client record, so nothing is stranded in an inbox.
What good looks like
In a firm that's got this right, the pattern is boringly consistent:
- A new client is onboarded through a single flow that captures ID, gets the letter signed, and opens the first PBC list.
- Every recurring job spawns its standard document checklist automatically — no one rebuilds it.
- The client sees exactly what's outstanding in the portal and uploads against each item.
- Reminders fire on their own until the list is complete.
- Staff can answer "what are we waiting on for this client?" in one glance, not a five-minute inbox dig.
The documents still have to come from the client — no software changes that. But the difference between a firm that chases and a firm that collects is whether the request is a tracked step in the work or a favour someone has to remember to ask for. Build it into the process once, and the trickle turns into a queue you can actually see.
Finye brings AML/KYC onboarding, engagement letters, client document requests and the portal into the same system that runs your jobs — so the paperwork that starts every piece of client accounting work stops being the thing that holds it up.