PBC List Tracking Automation for Audit Document Requests

PBC list tracking automation is a set of AI workers that take the auditor's request list, split it into individual requests, and assign each one a named owner and due date. The worker sends reminders to the people who hold the documents, watches for uploads, and matches each incoming file to the request it answers. When a file is missing, mismatched by period or entity, or unreadable, the worker flags it to the finance lead. The finance lead decides what goes to the auditor and whether the evidence is sufficient. The worker does the chasing and matching. The judgement stays with a person.
In short
- A PBC list is the auditor's list of items the client must prepare or provide, and each line needs an owner and a due date.
- The AI worker tracks, reminds and matches. The finance lead decides what is sufficient and what goes to the auditor.
- Matching depends on clear file names and periods, so unclear scans and screenshots are flagged, not guessed.
- The process map usually shows which requests depend on one person or one export, and that is where the time goes.
- Automation pays off most for recurring requests across several people, and is rarely worth building for a short, one-off list.
What this service is
An auditor sends a list of schedules, reports and documents that the client must prepare or provide. Firms call it a PBC list, which stands for prepared by client or provided by client. It is also called an audit request list or an information request list. This service turns that list into a working tracker. Each request gets its own line, an owner on the client side, a due date, a status, and a place for the file to land. An AI worker runs the chasing and the matching so that the finance team spends its time on review rather than on email.
Who it is for
The service suits any business that receives an external audit, a review or a lender-driven document request each year. A five-person firm with one bookkeeper and an outside accountant has the same problem as a group with several entities and a central finance team. The difference is the number of request lines and the number of people who hold documents. The workflow is the same.
The buyers we would expect to talk to are the finance lead or controller who answers to the auditor, and the operations head who has to pull data from sales, payroll, procurement or the bank. If the same people chase the same documents every year, the case for automation is strong. If the audit is a one-off with a short list, a shared spreadsheet and a calendar may be enough.
What is included
- An intake of the auditor's request list, with every item copied into a tracker and numbered
- A process map showing who creates each document, in which system, and how often
- A named client owner and due date for each request, agreed with the finance lead
- Reminder messages sent to document holders by email or WhatsApp, on the schedule the finance lead sets
- Automatic matching of incoming files to the request they answer, using the request number, the period and the entity in the file name and content
- A flag list for the finance lead covering missing files, files for the wrong period or entity, duplicates and unreadable scans
- A status view that shows what has been received, what is outstanding, and which chasers have gone out
- A record of every upload, reminder and status change, so the finance lead can show the history if the auditor asks
- A handover note and a short training session for the people who will use the tracker
How the engagement runs
The work runs in five stages. Each stage ends with a decision by the client, so the tracker never runs ahead of the finance lead's judgement.
- Audit. We read the current request list and the prior-year list, then note which items are recurring, which are one-off, and where the same document is requested twice.
- Process map. We map where each document lives today. This is the step that usually shows whether a request depends on one person, one spreadsheet or one system export.
- Build. We set up the tracker, the reminder rules, the matching rules and the flag list. The finance lead signs off each rule before go-live.
- Run. The AI worker runs the reminders and matching during the audit window. A person reviews the flag list each day or each week, as the finance lead chooses.
- Support. After the audit we review what was flagged, adjust the rules, and prepare the tracker for the next cycle.
Typical timelines are set out below. They describe how the work usually fits together, not a guarantee. The length depends on how many request lines there are and how many systems hold the documents.
| Stage | Typical length | What the client does |
|---|---|---|
| Audit and process map | 1 to 2 weeks | Shares the request list, names document holders, gives system access |
| Build and sign-off | 2 to 3 weeks | Approves owners, due dates, reminder wording and flag rules |
| Run during the audit | Set by the auditor's timetable | Reviews the flag list and decides what goes to the auditor |
| Support after the audit | 1 week | Reviews the flags and the rule changes for next year |
What the client provides
The service depends on material that only the client can supply. Before the build starts, the finance lead should provide the current auditor's request list, the prior-year list, and a named contact for each document holder. The client also needs to confirm which systems hold the data, such as the accounting package, the bank portal, the payroll system and shared drives, and grant the access the AI worker needs to read and file documents. The client must check that sharing employee, bank or customer records with an automated tool is allowed under its own data policy and any agreements with the auditor. Finally, the finance lead must set the rules for what counts as a complete file, because the tracker can match and flag, but it cannot decide what the auditor will accept.
What the matching can and cannot do
Matching works well when the file name, the document title or the period label contains enough signal. A bank statement for a stated month can be matched to a request for that month. A signed contract with a customer name in the header can be matched to a contract request. Matching is weaker when a scan is unclear, when one file answers two requests, or when a document is a screenshot with no date. Those cases go to the flag list. The worker does not decide that a file is good enough. It shows the finance lead what it found, why it matched, and what looks wrong.
What this service does not cover
The service does not decide what evidence is sufficient. Under audit standards, that decision sits with the auditor, and within the client's own team it sits with the finance lead. Under the PCAOB audit evidence standard, AS 1105, the auditor must evaluate whether company-produced information is sufficient and appropriate, so the tracker can supply files but it cannot make that call. The service also does not prepare the schedules themselves. If the reconciliation or the revenue analysis does not exist, the tracker will show it as outstanding. Preparing it is still an accounting task.
The AI worker can misread a document, miss a file that is named unusually, or match a file to the wrong request. The finance lead reviews the flag list for that reason. The service does not replace the auditor's portal where the firm requires one. It also does not give the auditor direct access to the client's systems. Files pass through the tracker to the client's own control.
Where the request list is short, the documents sit in one place, and one person already handles the whole process, automation may not add enough value to justify the set-up. The audit can tell you that before any build starts.
This explains the standard in general terms; it is not legal or audit advice for your case.
How AiStaffo would automate this
AiStaffo would start by loading the auditor's request list into a tracker, one line per request, with a client owner and due date agreed by the finance lead. The AI worker would then send reminders to each document holder on the schedule set, watch the shared folder and the connected systems for uploads, and match each file to its request using the number, period and entity. Files that are missing, mismatched or unreadable would appear on a flag list for the finance lead, who would decide what goes to the auditor. Book a free automation audit to measure how many request lines and document holders your own audit involves.
Questions people ask
What does PBC stand for and what is a PBC list?
Can an AI worker decide whether our audit evidence is sufficient?
How is this different from a shared spreadsheet with due dates?
Do we need a dedicated audit portal for this?
How long does setup usually take?
Is it safe to let an automated tool read our financial files?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.






























