30 Claude Prompts for Tax Preparers

You are a tax preparer specializing in self-employed and small business clients. <context> I have a Schedule C client and want a checklist to walk through with them so I do not miss common deductible expenses for their type of business. </context> <inputs> - Business type: [BUSINESS TYPE] - Revenue range: [REVENUE RANGE] - Expenses client has already mentioned: [EXPENSES ALREADY MENTIONED] </inputs> <task> Produce a deduction checklist specific to this business type, grouped into categories such as cost of goods, vehicle, home office, supplies, and professional services, with a one-line note per item on what documentation supports it. </task> <constraints> Only include categories realistically relevant to the stated business type, not a generic universal list. Note where an item commonly triggers extra scrutiny, such as vehicle or meals, so the client understands why documentation matters. This checklist supports a preparer's review of the client's records and is not a guarantee that any item is deductible in this client's specific case. </constraints> <format> Return the checklist grouped under category headers, each line with a checkbox and a short documentation note in parentheses. </format>

You are a tax preparer helping a client evaluate the home office deduction. <context> A client wants to know what information I need from them to calculate a home office deduction properly. </context> <inputs> - Business use description: [BUSINESS USE DESCRIPTION] - Home square footage: [TOTAL HOME SQUARE FOOTAGE] - Office square footage: [OFFICE SQUARE FOOTAGE] - Method preference if known: [SIMPLIFIED OR ACTUAL EXPENSE METHOD] </inputs> <task> Create a worksheet the client can fill out that captures the inputs needed for both the simplified and actual expense methods, plus the eligibility questions that determine whether the space qualifies as regular and exclusive use. </task> <constraints> Include the eligibility questions before the expense inputs, since a client who does not meet regular and exclusive use should not fill out the rest. Do not calculate a final deduction amount, only collect the inputs. Note that final eligibility and method choice should be confirmed by the preparer. </constraints> <format> Return two sections: Eligibility Questions and Expense Inputs Needed, each as a fillable list with blank lines for the client's answers. </format>

You are a tax preparer reviewing a client's vehicle expense claim. <context> A client wants to claim vehicle expenses for their business and I need to walk through what makes the claim solid versus what leaves them exposed. </context> <inputs> - Vehicle use description: [VEHICLE USE DESCRIPTION] - Business miles claimed: [BUSINESS MILES CLAIMED] - Total annual miles: [TOTAL ANNUAL MILES] - Mileage log status: [LOG STATUS SUCH AS DETAILED, PARTIAL, OR NONE] </inputs> <task> Produce a review note assessing the strength of the documentation described, the gap between claimed business use percentage and what the log supports, and specific steps the client should take now to shore up the record for this year and going forward. </task> <constraints> Be direct about weak documentation without being alarmist. Do not tell the client what percentage to claim, only what the documentation currently supports and what is missing. Recommend the standard mileage rate versus actual expense comparison as a question for the preparer to run, not a decision to make here. </constraints> <format> Return three sections: Documentation Assessment, Gaps to Address, and Recommended Next Steps for the Client. </format>

You are a tax preparer who works regularly with rental property owners. <context> A client owns a rental property and I want a checklist covering the expense categories and records I need before I prepare Schedule E. </context> <inputs> - Property type: [PROPERTY TYPE SUCH AS SINGLE FAMILY, DUPLEX, SHORT-TERM RENTAL] - Rental activity level: [FULL YEAR RENTED, PARTIAL YEAR, OR PERSONAL USE MIX] - Major repairs or improvements this year: [MAJOR REPAIRS OR IMPROVEMENTS] </inputs> <task> Generate a checklist of expense categories relevant to this property type, distinguishing repairs from improvements that must be depreciated, and list the records needed to substantiate personal use days if applicable. </task> <constraints> Flag the repair versus improvement distinction clearly since it is the most common error area. If personal use mix was mentioned, include a note that the personal use days affect deductibility and should be confirmed with the preparer. Keep each item to one line. </constraints> <format> Return the checklist under headers: Operating Expenses, Repairs (Deduct Now), Improvements (Depreciate), and Personal Use Records Needed if applicable. </format>

You are a tax preparer reviewing a client's charitable contribution records. <context> A client gave me a list of donations for the year and I want to check which ones have the documentation needed to support a deduction. </context> <inputs> - List of donations with amounts and recipients: [LIST OF DONATIONS] - Documentation the client says they have: [DOCUMENTATION CLIENT HAS] - Any non-cash donations: [NON-CASH DONATIONS, IF ANY] </inputs> <task> Review the list and sort each donation into ready to claim, needs additional documentation, or likely not deductible as described, with a short reason for each. </task> <constraints> Apply the general documentation thresholds a preparer would check for, such as written acknowledgment for larger single gifts, without citing a specific dollar threshold as certain since rules can change. Flag any non-cash donation over a modest value as needing a qualified appraisal question. State clearly that final deductibility should be confirmed by the preparer against current rules. </constraints> <format> Return a table-style list with three columns: Donation, Status (Ready, Needs Documentation, Likely Not Deductible), and Reason. </format>

You are a tax preparer drafting a response to an IRS CP2000 notice. <context> A client received a CP2000 notice proposing additional tax because of an income mismatch and I need a first-draft response letter. </context> <inputs> - Notice details, income type and amount in question: [NOTICE DETAILS] - Client's explanation of the discrepancy: [CLIENT EXPLANATION] - Supporting documents available: [SUPPORTING DOCUMENTS] - Position, agree, partially agree, or disagree: [AGREE, PARTIALLY AGREE, OR DISAGREE] </inputs> <task> Draft a response letter to the IRS that states the client's position clearly, references the supporting documents by name, and requests the specific outcome the client is asking for, whether that is full acceptance of the client's figures or a corrected proposed amount. </task> <constraints> Use a formal but plain tone appropriate for IRS correspondence. Do not state a legal conclusion about what the tax code requires, describe the facts and reference the attached documents instead. This is a draft for the preparer to verify against the actual notice and current guidance before it is filed, not a final submission. </constraints> <format> Return a formatted letter with date line, notice number reference line, body paragraphs, a list of enclosures, and a signature block. </format>

You are a tax preparer drafting a first-time or reasonable cause penalty abatement request. <context> A client was assessed a late filing or late payment penalty and has a reasonable explanation I want turned into a formal abatement request. </context> <inputs> - Penalty type and tax year: [PENALTY TYPE AND TAX YEAR] - Client's reason for the delay: [CLIENT REASON] - Prior compliance history: [PRIOR COMPLIANCE HISTORY] - Requesting first-time abatement or reasonable cause: [FIRST-TIME ABATEMENT OR REASONABLE CAUSE] </inputs> <task> Draft a penalty abatement request letter that states the grounds being claimed, lays out the facts supporting reasonable cause if applicable, and cites the client's compliance history where it strengthens the request. </task> <constraints> Keep the tone factual and non-emotional, avoid over-explaining or apologizing excessively. Do not assert that the client qualifies, present the facts and let the request speak for itself. Note that the preparer should confirm current eligibility rules before this is sent. </constraints> <format> Return a formal letter with a subject line stating the request type, a facts section, and a closing paragraph stating the specific relief requested. </format>

You are a tax preparer responding to an IRS notice claiming a return was not filed. <context> A client received a notice saying a return for a prior year was never filed, but we have proof it was filed and I need a response letter. </context> <inputs> - Tax year in question: [TAX YEAR] - Filing method and date used: [FILING METHOD AND DATE] - Proof of filing available: [PROOF OF FILING SUCH AS CONFIRMATION NUMBER OR CERTIFIED MAIL RECEIPT] </inputs> <task> Draft a response stating the return was filed, citing the filing method, date, and proof reference, and requesting the IRS correct its records and confirm receipt. </task> <constraints> Keep the letter short and factual, this is a records correction request, not an argument. Reference the enclosed proof clearly by name. Note this draft assumes the proof of filing is genuine and dated correctly, which the preparer should confirm before sending. </constraints> <format> Return a short formal letter, under 250 words, with a clear subject line, the facts, the request, and enclosures listed. </format>

You are a tax preparer responding to a state tax agency notice. <context> A client received a notice from their state tax agency and the situation is different from a typical IRS notice, so I need a response tailored to the state's specific claim. </context> <inputs> - State and agency name: [STATE AND AGENCY NAME] - Notice type and claim: [NOTICE TYPE AND CLAIM] - Client's position: [CLIENT POSITION] - Supporting documents: [SUPPORTING DOCUMENTS] </inputs> <task> Draft a response letter addressed to the specific state agency that states the client's position, references the state notice number, and lists the enclosed documents supporting the client's case. </task> <constraints> Use the correct formal tone for a government agency letter, do not assume state procedure is identical to IRS procedure. Flag in a closing note to the preparer that state deadlines and appeal procedures vary and should be verified before sending. Keep the letter under 300 words. </constraints> <format> Return the letter with agency address block, notice reference line, body, and enclosures list. </format>

You are a tax preparer explaining an IRS notice to a worried client in plain language. <context> A client called upset about an IRS letter they do not understand and I want a clear explanation I can send them before our call. </context> <inputs> - Notice type: [NOTICE TYPE, FOR EXAMPLE CP14, CP2000, CP504] - What the notice is asking for: [WHAT THE NOTICE IS ASKING FOR] - Deadline stated on the notice: [DEADLINE ON NOTICE] </inputs> <task> Write a short, calm explanation of what this notice type generally means, what the specific deadline requires, and what the client should and should not do before we talk. </task> <constraints> Use plain, reassuring language, avoid jargon like abatement or deficiency without defining it in one clause. Do not tell the client the notice is nothing to worry about if a real deadline exists, be honest about urgency. Make clear this explanation is general and the preparer will confirm the specific next step for their case. </constraints> <format> Return a short email, under 200 words, with a plain-language subject line, a two or three sentence explanation, and a clear next step instruction. </format>

You are a tax preparer sending a year-end planning letter to clients. <context> It is late in the year and I want to send clients a letter flagging moves they should consider before December 31 based on their general situation. </context> <inputs> - Client segment: [CLIENT SEGMENT SUCH AS SELF-EMPLOYED, W-2 HIGH EARNER, RETIREE] - Relevant year-end topics to include: [TOPICS SUCH AS RETIREMENT CONTRIBUTIONS, ESTIMATED PAYMENTS, CHARITABLE GIVING] - Filing deadline note if relevant: [DEADLINE NOTE] </inputs> <task> Draft a year-end planning letter for this client segment that explains two or three relevant planning moves in plain language and invites the client to book a call before year-end if any apply to them. </task> <constraints> Write in a warm, direct tone, not a mass-market marketing tone. Do not state specific dollar thresholds or contribution limits as certain, since these change yearly and must be confirmed by the preparer before the letter goes out. Keep the letter under 400 words. </constraints> <format> Return an email with a subject line, a short opening paragraph, a bulleted list of planning topics, and a closing call to action. </format>

You are a tax preparer sending estimated tax payment reminders to clients who pay quarterly. <context> A quarterly deadline is coming up and I need a reminder letter for clients who make estimated payments. </context> <inputs> - Upcoming due date: [UPCOMING DUE DATE] - Client type: [CLIENT TYPE SUCH AS SELF-EMPLOYED OR RENTAL INCOME] - Prior quarter payment amount if known: [PRIOR QUARTER PAYMENT AMOUNT] </inputs> <task> Draft a short reminder email telling the client the due date, reminding them of their prior payment amount as a reference point, and asking them to confirm if their income has changed enough to warrant recalculating the payment. </task> <constraints> Do not state a specific payment amount as the correct one to pay this quarter, only reference the prior amount as context. Keep the tone brief and friendly, not alarmist. Note that any recalculation should go through the preparer, not be estimated by the client alone. </constraints> <format> Return a short email under 150 words with a clear subject line stating the due date. </format>

You are a tax preparer writing a client update about a recent tax law change. <context> A tax law change was passed that affects some of my clients and I want a plain-language letter explaining what changed and who it affects, before I confirm the technical details myself. </context> <inputs> - Summary of the law change as I understand it: [SUMMARY OF LAW CHANGE] - Client groups likely affected: [CLIENT GROUPS AFFECTED] - Effective date: [EFFECTIVE DATE] </inputs> <task> Draft a client-facing letter explaining the change in plain terms, who it is likely to affect, and inviting affected clients to schedule a review call. </task> <constraints> Write it as general information, not individualized advice. Do not state that any specific client qualifies for a specific benefit, phrase it as if this may affect you. Include a line stating the summary should be verified against the final law text and IRS guidance before the letter is sent, since draft summaries of new legislation often change before implementation. </constraints> <format> Return a letter with a subject line, a plain-language explanation section, a who this affects section, and a call to action. </format>

You are a tax preparer sending the annual document request letter at the start of filing season. <context> Filing season is starting and I want to send returning clients a document request letter tailored to their prior-year situation. </context> <inputs> - Client's prior-year income sources: [PRIOR-YEAR INCOME SOURCES] - New life events mentioned by client: [NEW LIFE EVENTS SUCH AS MARRIAGE, NEW CHILD, HOME PURCHASE] - Preferred document submission method: [SUBMISSION METHOD SUCH AS PORTAL OR EMAIL] </inputs> <task> Draft a document request letter listing the documents expected based on prior-year income sources plus any new documents likely needed due to the life events mentioned, and explain the submission method clearly. </task> <constraints> Keep the list specific to this client, not a universal checklist. Mention a deadline for submitting documents to stay on track for on-time filing, without naming the government filing deadline as certain since it can shift. Keep the letter under 300 words. </constraints> <format> Return an email with a subject line, a bulleted document list, and a clear submission instruction with the deadline. </format>

You are a tax preparer notifying a client that their return will be filed on extension. <context> A client's return will not be ready by the deadline and I need to notify them that we are filing an extension, along with what that does and does not mean for them. </context> <inputs> - Reason for the extension: [REASON FOR EXTENSION] - Estimated payment due with the extension, if applicable: [ESTIMATED PAYMENT NOTE] - New expected filing date: [NEW EXPECTED FILING DATE] </inputs> <task> Draft a letter explaining that an extension is being filed, what an extension does and does not extend, and any payment the client may still need to make by the original deadline. </task> <constraints> Be very clear that an extension to file is not an extension to pay, since this is the most common client misunderstanding. Do not state a specific dollar amount owed unless it was given as an input, otherwise describe it as an estimate the preparer will confirm. Keep the tone reassuring, not apologetic. </constraints> <format> Return a short letter with a subject line, a clear explanation paragraph, a payment note if applicable, and the new expected filing date. </format>

You are a senior tax preparer doing a final review pass before a return is filed. <context> A return is nearly complete and I want a final review checklist tailored to this client's specific forms before I sign off. </context> <inputs> - Forms and schedules included: [FORMS AND SCHEDULES INCLUDED] - Client complexity flags: [COMPLEXITY FLAGS] - Preparer's known open items: [OPEN ITEMS, IF ANY] </inputs> <task> Generate a final review checklist covering common error points for the specific forms listed, cross-checks between schedules, and a reminder to resolve each open item before filing. </task> <constraints> Tailor the checklist to the forms actually listed, do not include irrelevant checks for forms not in use. Keep each item actionable, phrased as a check to perform, not a general reminder. This checklist supports the preparer's own sign-off and does not replace it. </constraints> <format> Return a checklist grouped by form or schedule name, each line starting with an empty checkbox. </format>

You are a tax preparer running a variance check between two years of a client's return. <context> I want to compare this year's draft figures against last year's filed return to catch anything that looks off before I finalize. </context> <inputs> - Prior-year key figures: [PRIOR-YEAR KEY FIGURES] - Current-year draft figures: [CURRENT-YEAR DRAFT FIGURES] - Known life or business changes this year: [KNOWN CHANGES] </inputs> <task> Compare the two sets of figures line by line, flag variances larger than a reasonable range given the known changes, and note which variances are explained by the stated changes versus unexplained and worth investigating. </task> <constraints> Do not guess at a cause for an unexplained variance, list it as unexplained and worth a client question. Present the comparison as a working note for the preparer, not a final conclusion about return accuracy. </constraints> <format> Return a table-style list with columns: Line Item, Prior Year, Current Year, Variance, Explained or Unexplained. </format>

You are a tax preparer reviewing the inputs behind a self-employment tax calculation. <context> I want to sanity-check the inputs feeding into a client's self-employment tax before I finalize the number in the software. </context> <inputs> - Net Schedule C profit: [NET SCHEDULE C PROFIT] - Deductions already applied: [DEDUCTIONS ALREADY APPLIED] - Other self-employment income sources, if any: [OTHER SELF-EMPLOYMENT INCOME] </inputs> <task> Walk through the inputs that affect self-employment tax, note anything that looks missing or double-counted, such as the deduction for half of self-employment tax or combined income from multiple Schedule C activities, and list what to verify in the software output. </task> <constraints> Do not present a final self-employment tax figure, this is a review of inputs only, since the actual calculation should be run in tax preparation software. Flag any input that looks inconsistent with the stated net profit. </constraints> <format> Return a short list titled Inputs to Verify, followed by a list titled Possible Issues Found. </format>

You are a tax preparer determining a client's multi-state filing requirements. <context> A client had income or residency touching more than one state this year and I need to work through which states likely require a return. </context> <inputs> - States involved and reason for each: [STATES INVOLVED AND REASON] - Residency status changes during the year: [RESIDENCY CHANGES] - Income sourced to each state: [INCOME SOURCED TO EACH STATE] </inputs> <task> Walk through each state involved and note the general basis for a filing requirement, resident, part-year resident, or nonresident with sourced income, and flag any state combination known for reciprocity agreements or credit for taxes paid to another state. </task> <constraints> Present each state's requirement as likely, not certain, since state rules and reciprocity agreements change and vary by exact facts. State clearly this analysis must be confirmed against current state rules by the preparer before filing decisions are finalized. </constraints> <format> Return a list with one entry per state, including Filing Basis, Residency Type, and Notes on Reciprocity or Credits. </format>

You are a tax preparer troubleshooting an e-file rejection. <context> A return was rejected during e-filing and I want a structured troubleshooting note before I resubmit. </context> <inputs> - Rejection code and message: [REJECTION CODE AND MESSAGE] - Relevant data on the return, such as name, SSN, or prior-year AGI used: [RELEVANT DATA] - Whether this is a first or repeat rejection: [FIRST OR REPEAT REJECTION] </inputs> <task> Explain in plain terms what the rejection code generally indicates, list the most common causes for that type of rejection, and suggest the specific fields to double-check before resubmitting. </task> <constraints> Base the explanation only on the general meaning of the rejection type described, not a guess at the exact cause without more information. If the code suggests a common cause like a prior-year AGI mismatch or a dependent already claimed elsewhere, name that possibility clearly. Note that the preparer should confirm the specific field data against source documents before resubmitting. </constraints> <format> Return three sections: What This Rejection Generally Means, Common Causes, and Fields to Double-Check Before Resubmitting. </format>

You are a tax preparer sending an appointment confirmation email to a client. <context> A client booked a tax appointment and I want a confirmation email that also tells them exactly what to bring so the meeting is not wasted. </context> <inputs> - Appointment date, time, and format: [APPOINTMENT DATE, TIME, AND FORMAT] - Client type: [CLIENT TYPE SUCH AS RETURNING OR NEW] - Documents needed for this specific client: [DOCUMENTS NEEDED] </inputs> <task> Draft a confirmation email that states the appointment details, lists the documents to bring, and gives a clear instruction for what to do if the client needs to reschedule. </task> <constraints> Keep the tone friendly and efficient, not overly formal. Put the document list in an easy to scan bulleted format near the top, not buried at the end. Keep the email under 180 words. </constraints> <format> Return an email with a subject line, a short confirmation line, a bulleted document list, and a reschedule instruction. </format>

You are a tax practice owner sending a fee estimate to a prospective client. <context> A prospective client asked what it would cost to have their return done and I want a clear email that sets the fee range and what is and is not included. </context> <inputs> - Services included in the estimate: [SERVICES INCLUDED] - Fee range: [FEE RANGE] - Common add-on that could increase the fee: [COMMON ADD-ON] </inputs> <task> Draft an email that states the fee range clearly, lists what is included, names the one common factor that could push the fee higher, and invites the client to confirm before booking. </task> <constraints> Be upfront and specific about the fee range rather than vague, clients respond better to a clear number than a soft estimate. Do not overpromise a final fixed price before the actual return complexity is known. Keep the email under 200 words. </constraints> <format> Return an email with a subject line, a fee range statement, a short included services list, and a closing call to action. </format>

You are a tax preparer thanking a client for referring new business. <context> An existing client referred a new client to me and I want a genuine thank-you note, not a generic template. </context> <inputs> - Referring client's name: [REFERRING CLIENT NAME] - Relationship or context of the referral, if known: [REFERRAL CONTEXT] - Any small thank-you gesture being offered: [THANK-YOU GESTURE, IF ANY] </inputs> <task> Draft a short, warm thank-you note that acknowledges the specific referral, expresses genuine appreciation, and mentions the thank-you gesture if one is being offered. </task> <constraints> Keep it personal and specific, avoid generic phrases that could apply to any client. Keep it under 100 words. Do not mention any details about the new client's tax situation, since that would breach confidentiality with the referring client. </constraints> <format> Return a short email or card message, no subject line needed. </format>

You are a tax preparer following up after a client missed a scheduled appointment. <context> A client did not show up for their tax appointment and I need a follow-up email that is understanding but also gets the appointment rebooked before the deadline. </context> <inputs> - Original appointment date: [ORIGINAL APPOINTMENT DATE] - Filing deadline pressure, if any: [DEADLINE PRESSURE NOTE] - Office rebooking policy, if any: [REBOOKING POLICY] </inputs> <task> Draft a follow-up email that assumes something came up rather than blaming the client, notes any deadline pressure, states the rebooking policy if one exists, and gives a clear next step to reschedule. </task> <constraints> Keep the tone understanding and non-judgmental in the first line, then get direct about urgency if a deadline is close. Keep the email under 150 words. Avoid guilt-tripping language. </constraints> <format> Return an email with a subject line, a short understanding opener, the deadline note if applicable, and a clear rebooking call to action. </format>

You are a tax preparer sending an off-season check-in to past clients. <context> It is outside of filing season and I want to send past clients a light check-in that keeps the relationship warm without pushing a hard sell. </context> <inputs> - Client segment: [CLIENT SEGMENT] - Relevant off-season topic: [OFF-SEASON TOPIC SUCH AS RECORD KEEPING, ESTIMATED PAYMENTS, LIFE CHANGES] - Any service the firm offers off-season: [OFF-SEASON SERVICE, IF ANY] </inputs> <task> Draft a short, low-pressure check-in email that shares one useful tip related to the off-season topic and invites the client to reach out if their situation has changed. </task> <constraints> Keep it genuinely useful, not promotional in tone. Do not push the off-season service hard, mention it once, briefly, near the end. Keep the email under 180 words. </constraints> <format> Return an email with a subject line, a short useful tip, and a soft closing invitation to reach out. </format>