Organize responses to my auditor's PBC request list
Turns an auditor's prepared-by-client list into a tracked plan with owners, due dates, and notes on what each request really needs.
The prompt
Help me organize and respond to my external auditor's PBC (prepared by client) request list.
The PBC list: [PASTE requests]
Audit timeline: [fieldwork dates, deadline for PBC items]
Our team and who owns what: [NAMES/ROLES]
Systems where the evidence lives: [e.g. "NetSuite, Bill.com, Gusto, shared drive"]
Issues from last year's audit: [e.g. "late cut-off support", "management letter point on access controls"]
For each request:
1. Restate in plain words what the auditor is actually trying to test (e.g. completeness of liabilities, revenue cut-off, existence of cash).
2. List the specific documents or reports that satisfy it, and the system report name if obvious.
3. Flag requests that are ambiguous - draft a one-line clarifying question to the auditor.
4. Flag items that are likely to raise follow-up questions, and what to prepare in advance (e.g. reconciliation tie-outs, explanations of large manual entries).
Return:
1. A tracker table: # | Request | What they're testing | Evidence to provide | Owner | Due | Status | Clarifying question.
2. The 5 requests most likely to delay the audit, and how to get ahead of them.
3. A short email to my team assigning items with dates in bold.
Don't suggest altering, backdating, or recreating documents - if support doesn't exist, mark it [NO SUPPORT - DISCUSS WITH AUDITOR].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Finance & Accounting prompts
What to fill in
- PASTE requests
- fieldwork dates, deadline for PBC items
- NAMES/ROLES
- e.g. "NetSuite, Bill.com, Gusto, shared drive"
- NO SUPPORT - DISCUSS WITH AUDITOR
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Plan a forensic review of a small business's financial recordsA structured plan to review several years of records for errors or misconduct: scope, documents, red flags, and how to raise findings.
- Compare insurance quotes side by side before renewalExtracts the key terms from several insurance quotes into one comparison table, highlights coverage gaps, and lists questions for the broker.
- Build a month-end close checklist with owners and deadlinesCreates a day-by-day close calendar with tasks, owners, dependencies, and review steps so the books close on time every month.
- Build a business budget with driver assumptionsAn annual or project budget built from clear drivers and assumptions.