AI Audit Request Coordinator: Tracking Client Document Requests

What an audit request coordinator actually does all day

In most audit offices and finance teams, the person who runs the document request list is not an auditor. They keep the list moving. The list itself has a common name in the profession: the PBC list, short for prepared by client or provided by client. Other firms call it the audit request list or the document request list. Whatever the label, the job is the same. Someone has to make sure the client's bank statements, reconciliations, contracts and board minutes arrive on time, in the right format, and in a form the audit team can use.

A typical working day is made of recurring tasks. The table below sets out the ones most business owners will recognise, using the words that usually appear in the finance and audit team's own tracker.

1. Build the request list for the engagement. Start from last year's list, remove items that no longer apply, and add items the new scope needs. Each line gets a description, a period, a format, a due date and a client owner.
2. Send the list and agree dates. Items are often sent in waves: planning items first, year-end schedules after the books close, follow-ups as fieldwork raises new points.
3. Chase outstanding items. Email, phone or message the named owner on a fixed cadence, and name the specific missing items rather than resending the whole list.
4. Log what arrived. Record the date, the sender, the file name and the version of each upload, so nobody has to ask later which copy was sent.
5. Match each file to its request. A bank statement goes against the bank line, a board minute against the governance line. Duplicates and outdated versions are flagged rather than filed.
6. Check completeness on the surface. Confirm the file is the right period, the right entity and a readable format. The coordinator checks the file is what was asked for. The audit team checks what it proves.
7. Close items that do not apply. A client with no leases should not be chased for lease schedules. Each closed item needs a one-line reason on the record.
8. Route questions from the audit team to the client. When a senior asks for a clarification or an extra schedule, the coordinator adds it to the list, assigns it and tracks it to close.
9. Keep the status tracker current. Typical statuses are not started, in progress, submitted and reviewed. Some teams separate received from approved, because the audit team's checks happen between the two.
10. Report progress. A short weekly status note tells the engagement partner or finance director what is open, what is overdue and what is blocking fieldwork.

Most of these tasks are repetitive. Some of them are quiet and easy to miss, such as noticing that the same schedule came back twice with different totals. That is why the coordinator is often the person who knows where every document is.

Which of those tasks an AI worker takes over

An AI worker can take the parts of the job that follow a clear rule. The rule might be a due date, a naming pattern, a matching key such as the account number on a bank statement, or a status change triggered by an upload. The worker reads the request list, watches the inbox or upload folder, and writes back to the tracker. It does not decide what a document proves.

The table below shows the typical tasks, the systems each one needs, and what the worker does with them. Access and setup depend on the firm's own tools and permissions, so the list describes the usual pattern rather than a fixed build.

Automated reminders are the piece most firms start with, because the logic is simple. Power Automate, a Microsoft tool that connects Outlook, SharePoint and Excel, is one common way to build a daily check of pending items with a reminder step. Microsoft's own documentation on approvals and reminders describes the same pattern for approval requests, and the same logic applies to document chasers. Other firms use dedicated audit collection platforms, which provide an upload portal and reminder settings out of the box. Those products vary, so the audit team should check each vendor's current documentation before choosing one.

The worker also needs a clear status vocabulary. If the team uses requested, received, matched, reviewed and accepted as separate stages, the worker must know which stage a file moves an item into. A file arriving is not the same as a file being accepted. Keeping those stages apart is the most important design decision in the set-up.

What stays with a person, and why

Some parts of this role cannot sit with a worker that only follows rules. The main reason is that audit evidence is judged, not just collected. The IAASB's ISA 500 standard, which sets the international rules on audit evidence, asks the auditor to design procedures that obtain sufficient appropriate evidence, and it asks the auditor to evaluate whether information produced by the entity is reliable enough to use. A worker can say a file arrived. It cannot say the file is complete or trustworthy for this purpose.

The draft revision of ISA 500 published in 2026 puts it in similar terms. Appropriateness depends on the relevance and reliability of the information, on how the audit procedure was designed, and on how the auditor applied it. Professional scepticism stays with the auditor. That is why the coordinator's role should end at the point of evidence, and the auditor's role should start there.

Several other tasks stay with a person:

• Deciding whether a schedule ties to the general ledger, and what to do when it does not.
• Judging whether a client's explanation for a gap is believable, or whether it needs a second request.
• Handling sensitive requests, such as payroll records, personal data, legal correspondence or anything touching a dispute or a regulator.
• Speaking to a client owner who is slow, unhappy or new to the process, where tone and timing matter more than the message.
• Agreeing alternative formats or dates with the audit manager when the client genuinely cannot produce what was asked.
• Signing off that the list is complete and that the file is the right one for the period.

Relationships are the other reason. The coordinator is often the first person a client finance team trusts on the engagement. A worker can send a reminder on time, but it cannot notice that a client's controller has gone quiet because of a personal difficulty, or that a request is causing friction between departments. A person needs to see those signals and decide what to do about them.

How this role differs by business type

The role looks different depending on what the business is audited for and who it employs. The table below covers six common setups in several countries. The details of each engagement vary, so the rows describe common patterns rather than rules.

Two points cut across all of these. First, the more entities, sites or currencies a business has, the more the matching rules matter, and the more time a person should spend setting them up. Second, where the client is spread across time zones or languages, reminders need to be worded and timed for the owner's location. A fixed daily reminder at one hour is not always the right choice for a team in another country.

How the switch happens, week by week

The safest route is a staged switch in which the coordinator stays in place for the whole first engagement cycle. The aim is to show that the worker's matches and reminders are right before anyone relies on them. The steps below assume one engagement at a time. A group with several audits should pick one engagement as the pilot.

1. Week 1: map the work. The coordinator writes down each recurring task, the system it uses, the rule behind it and the person who decides when the rule does not fit. The audit manager signs off the status vocabulary.
2. Week 2: prepare the list and folders. The request list is set up in one place with item numbers, owners, due dates and statuses. The document store is organised by client, engagement and period, and access rights are confirmed by the firm's IT owner.
3. Week 3: run the worker in shadow mode. The worker drafts reminders and proposed matches, but nothing is sent or filed until the coordinator approves it. Every disagreement is logged with the reason.
4. Week 4: review the disagreements. The team looks at the log and adjusts the matching rules, reminder wording and chase schedule. Anything the worker cannot place is routed to the coordinator by default.
5. Weeks 5 to 8: let the worker act on clear cases. Reminders go out automatically for overdue items, and files that match on a clear key are filed. Anything with a duplicate, a missing period or an unclear owner waits for a person.
6. Weeks 9 to 12: move exceptions and questions to the new owner. The coordinator's role shifts to reviewing the worker's exceptions, handling client conversations that need care, and closing items with reasons. Fieldwork questions go to the audit team through the tracker.
7. After the first full cycle: shrink to review. The coordinator reviews a sample of the worker's filings and reminders each week, and keeps the final say on closed items and sensitive files. Any change to the role, hours or duties must follow the notice, consultation and severance rules that apply in the country, and should be agreed with the employee or checked with a lawyer before it takes effect.

The timing will differ from one firm to another. A firm with one engagement a year may need a longer shadow period, because it only sees one cycle of problems in twelve months. A firm running several audits in the same season may find the worker needs tuning before the first week is over.

Risks and when not to automate this role

Automation adds risks that are easy to miss. The first is a wrong match. If the worker files a bank statement against the wrong account, the error may not be noticed until the auditor opens the file. Every filing rule needs a sample check by a person, and the sample should cover the cases the rules find hardest, not only the easy ones.

The second risk is a reminder sent to the wrong person or about the wrong item. A reminder that names a sensitive document to a broad distribution list can create a data protection problem. The access list for each folder and mailbox must be checked before the worker is switched on.

The third risk is false confidence. A tracker that shows every item as matched can look finished when it is not. The status should mean what the audit team needs it to mean. A file that is received is not the same as a file that is accepted, and a worker that blurs the two will make the audit look further along than it is.

There are also cases where automation is not worth it. Do not automate the role if any of these apply:

• The engagement is small and runs once a year with a short list, so the set-up and checking time is larger than the chasing time.
• The client's documents are mostly paper, handwritten or in formats that need manual reading before anyone can tell what they are.
• The request list changes heavily every week because the scope is still being decided.
• The audit involves regulated or highly sensitive records, and the firm cannot yet show who can access each folder and where the data is stored.
• Nobody in the firm owns the tracker. A worker with no owner will drift, and nobody will notice until a deadline is missed.
• The client relationship is fragile, and the main value of the coordinator is the conversation, not the paperwork.

Results from any of this depend on the firm's own figures and the state of its files. The free audit described below measures the current workload, the number of open items and where the bottlenecks sit before any decision is made.