The PBC List That Chases Itself: Document Requests Done Right
A practical system for AML/KYC onboarding and PBC requests that stops the endless follow-up emails and keeps your client accounting work moving.
Every accountant knows the drift. You send a client your "provided by client" (PBC) list in mid-July, expecting the trust deed, the bank statements and the last set of financials back within the week. By August you've sent three reminders. By September the job is still sitting in your board marked "waiting on client", and half your WIP is tied up in files you can't start.
The same drag shows up at the very start of a relationship, during AML/KYC onboarding. Verifying identity and beneficial ownership feels like admin, so it gets treated as admin — a loose email or two, a scan attached somewhere, and no clear record of what's outstanding. Then a review or an audit lands and you're reconstructing who signed off on what.
Document collection is one of the least glamorous parts of running a firm, and one of the most expensive when it's done badly. Here's how to build a system that chases itself.
Treat onboarding verification as a job, not a favour
AML/KYC and PBC collection are usually run as afterthoughts to the "real" work. That's backwards. Both are structured, repeatable processes with a defined list of items and a clear finish line — which makes them ideal candidates for a template.
For AML/KYC onboarding, your minimum standard should cover:
- Identity verification for the individuals you're engaging — full name, date of birth, residential address, and the document you relied on to confirm it.
- Entity structure — the ABN or ACN, entity type, and how it connects to the people you're dealing with.
- Beneficial ownership — who ultimately controls the entity, especially for trusts and companies with layered structures.
- The purpose of the engagement and an assessment of risk appropriate to your firm's obligations.
The point isn't to turn every onboarding into a compliance exercise. It's to make sure the same steps happen every time, without relying on anyone remembering them. Good account practice management software lets you build this as a standard job with a fixed checklist, so a new client can't slip through with half the file missing.
Write the PBC list once, reuse it forever
The PBC list for a company tax job doesn't change much year to year. Neither does the list for an SMSF audit, a BAS, or an individual return with a rental property. Yet most firms rewrite these from scratch or copy last year's email and hope they didn't miss anything.
Build a reusable request list for each service you offer and attach it to the matching job template. When the job kicks off, the list is already there — item by item, with a clear description of what "acceptable" looks like. "Bank statements" becomes "Business account statements for the full financial year, PDF preferred, all pages." That specificity is what stops the back-and-forth where a client sends one month and calls it done.
The other benefit of a standing list: you can see, at a glance, which items are outstanding across every open job. That's far more useful than digging through email threads to work out who owes you what.
Make the client the one doing the work
The single biggest time-sink in document collection is the accountant acting as the courier. You email a request. The client replies with three attachments and a question. You reply. They send two more. You file them manually. Multiply that across a client base and it's a full-time job nobody was hired to do.
A client portal flips this. Instead of a request buried in an inbox, the client sees a clean list of exactly what's needed, uploads directly against each item, and watches the list shrink as they go. Files land where they belong instead of scattered across email. And critically, the client can see what's still outstanding without you having to tell them.
This is where client accounting software earns its keep — not by doing the accounting, but by removing the friction around getting the inputs you need to do it. In Finye, PBC and onboarding requests run through the same portal your clients already use for engagement letters and invoices, so there's one place they log into rather than another tool to learn.
Automate the follow-up so you don't have to
Reminders are the part everyone hates and everyone forgets. The fix is to stop treating them as a manual task. Once a request list is live, outstanding items should trigger their own reminders on a schedule you set — a nudge at day three, another at day seven, escalating politely.
Automated follow-up does two things. It gets documents in faster, because clients respond to prompts. And it protects the relationship, because the reminders are consistent and even-tempered rather than the slightly exasperated email you fire off when you finally notice a job has stalled for a month.
Pair this with visibility on your board. A job that's genuinely blocked on client information should look different from one you can actually progress. When you can see the whole "waiting on client" column in one view, you can decide what to escalate, what to defer, and which clients need a phone call rather than another email.
Keep the record, because you'll need it
Whatever system you use, the verification and the documents need to stay attached to the client — not to a job that gets archived, not to a staff member's inbox. When you take on staff, hand off a client, or field a query two years later, the answer to "what did we collect and when" should be one click away.
This is the difference between accounting client management software and a shared drive. The drive stores files. The system ties each document to the client, the job, the request it satisfied and the date it arrived — so your client accounting work sits on a foundation you can actually stand on.
The payoff
Get document requests and onboarding right and the flow-on effects are real: jobs start on time because the inputs arrive, WIP stops ageing while you wait on a missing statement, and your compliance obligations are met by default rather than by heroics. It's not the flashiest part of running a practice. But it's the part that quietly decides whether the rest of your workflow moves or stalls.