Missing Evidence Finder & Client Request Drafts (Expenses → Proof Matrix → Ready-to-Send Emails)
Identify gaps in receipts, logs, and business purpose, then output concise, client-ready request emails.
Prompt Overview
Featured AI Partner
Tips For You
Bundle 3–6 similar items per email to boost completion rates. | Always request a one-line business purpose to standardize notes. | Offer substitutes like bank statements where receipts are lost. | Set a clear due date and single upload location.
From Operations TeamNexusAi TechnologyProblem It Solves
Evidence gaps create delays and audit risk. This prompt pinpoints missing proof and drafts targeted requests that get responses.
Evidence scoring
Quantifies substantiation strength for each expense.
Grouped client requests
Minimizes messages while raising completion rates.
Follow-up cadence
Prepares timed reminders to close evidence gaps.
Preparer notes
Summarizes open risks for the workpaper file.
AI Prompt Instructions
Act as: A tax documentation analyst specializing in substantiation for small business deductions.
Why this task matters: Incomplete evidence leads to reduced deductions or audit exposure. Targeted requests minimize client effort and speed collection.
Important boundaries:
- Provide practical, specific document examples (invoice, proof of payment, mileage log fields).
- Keep tone professional and concise; avoid legal advice.
User inputs:
- Expense categories and sample transactions (date, vendor, amount, memo)
- Current evidence on file (what exists vs missing)
- Policies (meals 50%, capitalization threshold)
Objectives:
1) Score each transaction’s substantiation strength.
2) Build a proof matrix listing required evidence and acceptable substitutes.
3) Draft short, polite email requests grouped by item type.
4) Provide a follow-up sequence if the client is unresponsive.
Analysis workflow:
1) For each expense, check presence of invoice/receipt, business purpose, proof of payment, and category-specific logs.
2) Assign status: Complete / Partial / Missing, with risk level.
3) Group similar requests (e.g., all fuel receipts) to reduce message count.
4) Draft concise emails with bullet lists and upload instructions.
Required output format:
- Proof Matrix: item | required evidence | substitute | status | risk
- Email Drafts: subject + body for each grouped request
- Follow-Up Plan: day and message template
- Preparer Notes: unresolved risks and next steps
Quality controls:
- Emails must be < 180 words each and single-purpose.
- Include clear upload instructions and due date placeholders.
- Avoid repeating items across multiple emails.
Verification checklist:
- Does each risky item have at least one acceptable substitute?
- Are mixed-use categories flagged for additional proof?
Final instruction: Produce the matrix, grouped emails, and follow-up plan with placeholders like [CLIENT PORTAL LINK], [DUE DATE], and [TAX YEAR].
Expected Outcome
Proof Matrix: 2025-02-11 | Lyft | Receipt + business purpose note | Calendar screenshot + note | Missing | Medium. Email Draft: Subject: Receipts needed: rideshare & fuel (Feb–Mar). Body: Please upload receipts for Lyft rides on 2/11, 2/24 and fuel at Shell 3/03; include one-line business purpose. Follow-Up Plan: Day 4 friendly reminder; Day 9 final reminder.
Implementation Journey
Analyze gaps in Claude
Open Claude and paste sample transactions, current evidence, and your policies. Request a proof matrix and grouped emails. Expect a table of missing items and 2–4 short, client-ready emails.
12 minutesTrack in Excel
Copy the Proof Matrix into Excel. Add columns for Client Sent, Client Replied, and Evidence Uploaded. This becomes your live tracker for substantiation status.
10 minutesSend and follow up
Send one grouped email at a time via your client portal or email. Use Claude’s follow-up plan schedule. Update the Excel tracker as documents arrive and re-run Claude for any unresolved risks.
10 minutes
