Audit PBC request tracking with AI: status, owners and aging in minutes

When to use it

Use it during interim and year-end audits, SOC or tax provision reviews, or any time an outside party sends a long request list. The work is mostly organizing and summarizing, which is low-risk and easy to check. The documents themselves, and what you say to the auditor, stay under your control.

Input data

• The auditor's request list export (from their portal or spreadsheet): request ID, description, requested date, due date, status per the auditor.
• Your internal tracker (owners, notes), if you have one.
• A listing of the shared folder: file names and dates only. You don't need to upload the documents themselves.
• Prior-year PBC list, if available (to spot recurring requests you can prepare early).

The prompt

Replace the [bracketed] items. Paste it with your files attached. It works in any capable assistant; tool-specific notes are in the steps.

Help me manage our audit PBC (provided-by-client) list for the [FY/period] [audit type].

Attached:
- Auditor request list: [file] (columns: [list])
- Our internal tracker: [file or "none"]
- Shared folder file listing (names and dates only): [file]
- Prior-year PBC list: [file or "none"]
- Team members and areas: [e.g. Cash – Priya; Revenue – Marco; Payroll – Dana]

Tasks:
1. Merge into one tracker: request ID | description | area | owner (assign by area; mark "UNASSIGNED" if unclear) | due date | auditor status | our status | likely matching file(s) from the folder listing | days overdue.
2. Flag: overdue items; items due in the next [5] business days; requests that look like duplicates of each other; requests marked "provided" by us but still "open" in the auditor portal; requests with no likely file.
3. Map to prior year: mark which requests recur from the prior year and which are new.
4. Draft a short weekly status note to our controller: totals by status, top overdue items by owner, blockers. Use plain factual language.

Do not judge whether a document fully satisfies a request. Mark the file match as "possible match – owner to confirm".

Steps

1. Export the request list from the audit portal at the same time each week.
2. Run the prompt and share the merged tracker with owners.
3. Owners confirm their file matches and upload through the auditor's portal, not through the AI tool.
4. The controller reviews the status note before anything goes to the audit team.

Control map

What the AI may do, step by step. How ratings work.

Audit trail

• The auditor's portal remains the record of what was provided and when.
• Keep weekly snapshots of your tracker. They're handy for the post-audit retrospective and next year's planning.

Failure modes

• Wrong file match based on similar file names (e.g. "Bank rec Dec" from the prior year). That's why matches are only "possible".
• Stale export. Status changed in the portal after you exported. Always state the export time in the status note.
• Owner assignment by keyword misroutes cross-functional requests. Fix them once and keep the mapping.

Data handling

• Use a company-approved AI workspace whose terms say your inputs are not used for model training. Check your plan; don't assume it.
• Strip or mask what the task doesn't need: employee names, bank account numbers, customer PII, SSNs or TINs.
• If you are a public company, treat pre-release results as material non-public information and keep them inside approved systems.