For Audit Associates ·
What you'll accomplish
Claude Pro configured with your firm's workpaper standards produces consistently structured, GAAS-appropriate audit documentation in minutes rather than hours. This guide walks through exactly how to set that up.
What you'll need
Go to claude.ai and create an account with your personal or work email. Upgrade to Claude Pro (Settings → Plan → Upgrade to Pro → $20/month). Pro gives you longer context windows, faster responses, and access to Claude Projects, which is how you'll set up persistent workpaper context.
Why Pro matters for audit work: The free version of Claude limits conversation length. Workpaper drafting often involves pasting long testing summaries or multiple sections. Pro handles this without truncating your input.
On the Claude sidebar, click Projects → New Project. Name it something like "Audit Workpapers: [Your Firm]" or "Audit Documentation Assistant."
In the Project Instructions field, write your configuration (customize the brackets):
You are an audit workpaper documentation assistant for [Your Name], an audit associate at [Firm Name], a [Big 4 / regional / local] CPA firm.
## Firm Context
- Audit standards: GAAS (AU-C sections) for private clients; PCAOB standards for public companies
- Materiality approach: [your firm's typical materiality calculation basis, e.g., 5% of pre-tax income, 1% of total assets]
- Workpaper style: formal, past-tense, third-person where appropriate; GAAS-appropriate language
- Management letter format: Condition / Criteria / Cause / Effect / Recommendation structure
## What I Do In This Workspace
- Draft workpaper narratives from testing summaries I describe
- Draft management letter comments for control findings I describe
- Help draft PBC request lists for specific client types
- Draft client communication emails (document requests, follow-ups)
- Help with accounting standard research questions
- Draft analytical procedure documentation from variance data I provide
## Critical Rules
- NEVER ask me to provide client names, client financials, or confidential data
- When I describe testing, treat all amounts and descriptions as hypothetical unless stated otherwise
- Always write workpaper narratives in past tense
- Always flag when severity classification (deficiency / significant deficiency / material weakness) requires professional judgment that I must verify with my senior
- Never provide definitive accounting guidance, and always recommend verification with primary sources (FASB, PCAOB, firm guidance)
Open a new conversation in your Claude Project. Start with a context-setting prompt:
"I'm working on the [industry type, e.g., manufacturing client] audit. Key facts about this engagement: [describe industry, approximate size, key audit risk areas]. I'll be drafting workpaper documentation for several sections today. All amounts I describe are for illustration purposes."
This primes Claude for the engagement type without sharing confidential information.
After setting context, use the standard prompt format:
Workpaper Narrative:
Draft a workpaper narrative for the [section] audit area. Testing performed:
- Objective: [what the test was designed to do]
- Population: [description and approximate size, e.g., "45 AP transactions over $5,000"]
- Sample: [selection method and size]
- Procedures: [what you actually did, such as agreed to invoices, confirmed balances, etc.]
- Results: [pass/exceptions, what you found]
- Exception handling: [how you addressed any exceptions]
Write in past tense, GAAS-appropriate language, organized as: Objective → Procedures → Population/Sample → Results → Exceptions → Conclusion.
Management Letter Comment:
Claude will produce a draft in 15-30 seconds. Your job is to review for:
If the draft needs adjustments, use follow-up prompts: "Make the conclusion stronger," "Add a note that 2 of the 25 items tested required additional procedures," or "The tone on the management letter comment is too alarming, soften the Effect language slightly."
Save these in a document for quick access:
Save the project instructions.
Draft a management letter comment for this finding:
- What I observed (Condition): [describe what control is missing or not operating]
- What should be happening (Criteria): [the applicable standard or policy]
- Why it happened (Cause): [your assessment]
- Impact (Effect): [the risk or actual consequence]
- Classify as: [Control Deficiency / I'll confirm severity with my senior]
Use Condition / Criteria / Cause / Effect / Recommendation structure. Measured, professional language.