Yes, AI can summarise IRS transcripts for a tax resolution case and draft the client update, provided the transcript is redacted first and a practitioner checks every code, date and amount against the original before anything is sent. The AI translates and organises. It does not decide the resolution route or sign anything.
Where small practices lose time is the first read: three to six tax years of account transcripts, each a column of codes and dates, before the first call with the client. A good prompt can turn that into a one-page case summary in minutes. The risk is a confident misreading of a code, so the workflow below puts a named check between the draft and the client.
Which transcripts to pull, and what each shows
The IRS offers several free transcript types for individuals, and its own page lists what each contains. For a resolution case you will usually use these.
- Account transcript. Basic data such as filing status and taxable income, payments, and changes made after the original return was filed. This is the main document for balances, assessments and collection indicators. It is generally available for the current year and nine prior years through the online account, but only the current and three prior years by mail or phone.
- Wage and income transcript. Data from information returns such as W-2 and 1099 forms. It shows only what was filed with the IRS, which may not match everything issued to the taxpayer.
- Return transcript. Most line items from the return as originally filed, with no later changes. Available for the current and three prior years.
- Record of account. The return and account transcripts combined, for the current and three prior years.
- Verification of non-filing letter. States that no processed return exists as of the request date. It does not say whether a return was required.
Practitioners normally obtain these through the IRS's Transcript Delivery System, which its tax-professional page says requires a properly executed representation form (Form 2848) or tax information authorisation (Form 8821) on file; check the current routes before you build the process, because they change. Business accounts have their own transcript route. A transcript is not a copy of the return: if you need the original document, the IRS has a separate request for that.
Redact before the text goes anywhere
A transcript carries a taxpayer identification number, name, address and sometimes spouse details. None of that helps the summary. Strip it locally, then paste.
import re, sys
text = open(sys.argv[1], encoding="utf-8").read()
text = re.sub(r"\b\d{3}-?\d{2}-?\d{4}\b", "[TIN]", text) # personal numbers
text = re.sub(r"\b\d{2}-?\d{7}\b", "[EIN]", text) # business numbers
text = re.sub(r"\b\d{5}(-\d{4})?\b", "[ZIP]", text) # postcodes
for name in ["JANE EXAMPLE", "JOHN EXAMPLE"]: # names you supply per case
text = text.replace(name, "[CLIENT]")
open(sys.argv[2], "w", encoding="utf-8").write(text)Run it, then read the output once by eye to confirm nothing identifying remains: addresses in free-text lines are the usual leak. On a test file the script errs towards over-redacting. A nine-digit ZIP+4 code is caught by the first pattern, and parts of a document locator number can turn into [ZIP], which does no harm to the summary but means you check those numbers against the original. Keep the map from case code to client in your practice software, not in the AI chat. Use a business plan (ChatGPT Business or Claude Team, each $20 per user per month billed annually or $25 monthly, with two seats minimum), where content is not used for training by default. Consumer plans make you rely on a settings switch, which is the wrong foundation for client tax data. Delete the redacted text from the chat when the summary is done, and file the summary in the case record.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowReading the codes: a plain-English table
Account transcripts list transaction codes ("TC" followed by three digits). The IRS publishes their meanings in Document 6209, and the table below uses that document's Section 8A on master file transaction codes (2023 edition, the latest posted on irs.gov when checked). Treat it as a starter glossary; definitions can have conditions, so confirm against the current edition before you rely on a code in advice.
| Code | Plain-English reading | What to ask next |
|---|---|---|
| 150 | Return filed and tax assessed from it | Which date? That starts the assessment timeline. |
| 300 | Additional tax assessed by examination or appeals | Was there an audit report? Is an appeal still open? |
| 420 | Examination indicator: the return has been referred to examination or appeals | Is it open or closed, and who has the file? |
| 480 | An offer in compromise is pending for the period | Which date? Does it pause collection? |
| 520 | IRS litigation instituted, a collection hold whose reason sits in the closing code | Which reason? Bankruptcy is one possibility; the closing code says which. |
| 530 | Account currently not collectible | When was it set, and is the income position unchanged? |
| 570 | Additional liability pending or credit hold; freezes refunds and offsets | What is the pending item? |
| 582 | Lien indicator: a tax lien has been filed for the period | When was it filed, and is a release or withdrawal needed? |
| 610 / 670 | Payment with return / later payment | Do the amounts match the client's bank records? |
| 806 | Credit for tax withheld | Does it agree to the wage and income transcript? |
| 846 | Refund of overpayment issued | Was it received, or has it been offset? |
| 971 | Miscellaneous entry whose meaning depends on its action code | Read the action code and look it up; never guess. |
The last row is the one that trips up AI summaries. A model that has seen many transcripts will happily say "TC 971 means an instalment agreement is in place" when the action code on the line says something different. Your prompt must forbid interpreting any code that is not in your glossary.
A three-year case for a self-employed kitchen fitter
An illustration with made-up numbers. A practice takes on a self-employed kitchen fitter who has received IRS notices. Account transcripts exist for three years. After redaction and checking, the summary table looks like this.
| Year | Return | Tax assessed | Payments | Penalties and interest | Balance on transcript | Flags |
|---|---|---|---|---|---|---|
| 2022 | Filed, TC 150 | $18,400 | $6,000 | $1,790 | $14,190 | None |
| 2023 | Filed, TC 150 | $21,300 | $9,000 | $3,080 | $15,380 | TC 971, action code to be read |
| 2024 | No return processed | None | None | None | $0 | Wage and income shows $47,500 of 1099 income |
| Total | $29,570 |
The sums: 2022 is $18,400 less $6,000 paid, plus $1,790 penalties and interest, giving $14,190; 2023 is $21,300 less $9,000, plus $3,080, giving $15,380; together $29,570. The summary should say plainly that this is the balance as of the transcript date, not a payoff figure, because interest keeps accruing. It should also say that 2024 is not a zero-balance year: a missing return with income reported by third parties usually leads to further notices, so the first job is to prepare it.
The collection clock needs the practitioner. The IRS's own page says it generally has 10 years from the date of assessment to collect, and that events such as bankruptcy or a pending instalment agreement or offer request can suspend that period. The AI can pull the assessment date from the TC 150 line. It must not state an expiry date; the practitioner confirms it from the transcript, the notices and any suspension events.
The prompt that produces the case summary
Below is a redacted IRS account transcript for one tax year. Produce:
1. A table: transaction code, date, amount, and the plain-English meaning
ONLY if the code appears in the glossary I pasted. Otherwise write
"NOT IN GLOSSARY: practitioner to look up".
2. The year's balance as printed, and the date of the transcript.
3. Any collection indicators present (by code), listed without comment.
4. Questions for the practitioner. Do not suggest a resolution option.
Copy every amount and date exactly. If two lines look inconsistent, point
them out; do not reconcile them yourself.
GLOSSARY: [paste the table above]
TRANSCRIPT: [paste redacted text]An illustrative output for the 2023 year might read: "TC 150, 15 April 2024, $21,300: return filed, tax assessed. TC 610, $9,000, matches payments. TC 971, 3 June 2025: NOT IN GLOSSARY, practitioner to look up. Balance printed $15,380 as of the transcript date. Collection indicators: none by code. Questions: what does the TC 971 action code mean; do the payments agree to the client's records; was a notice sent after the 3 June entry?" What you check: every figure against the transcript, and the "not in glossary" flag, which is the model doing its job. What you correct: if the model wrote a meaning for the 971 line, delete it.
A mistake that looks like help
A practice tests the prompt without the glossary rule. For a specialist food importer with a corporate return year, the model reads a line with code 520 and writes "taxpayer is in bankruptcy", which the client had never mentioned. The code is a litigation or collection-hold indicator, and the closing code on the line, not the code alone, gives the reason. If that sentence had reached the client, it would have caused alarm. It showed up because the practitioner's check compared each statement in the summary with a specific line. The change to the prompt was the "ONLY if the code appears in the glossary" rule, plus a glossary entry saying "520: reason depends on closing code, practitioner to read".
The practitioner check, written as a named step
A summary is not a work product until someone accountable has checked it. Make the gate a step with a name, a person and a record.
- Tie the numbers. The reviewer opens the original transcript and ticks every amount and date in the summary table.
- Clear the flags. Each "not in glossary" line and each collection indicator is looked up and annotated.
- Cross-check sources. Compare payments with the client's bank evidence, and income with the wage and income transcript.
- Remove opinions. Anything that predicts an IRS decision or a resolution outcome is deleted.
- Sign and date. The reviewer writes initials and date on the case file. Only then does the client-facing text go out.
The review takes about 20 minutes per year of transcript in this illustration, against roughly an hour for a first manual read; your own figures will differ, so time five cases before you promise anyone a saving. For more on the review habit, see how small tax practices use AI through the busy season.
Client updates: cadence and wording
Clients in resolution cases are anxious and often avoid the post. The most useful thing you can give them is a predictable rhythm. A cadence you can adapt:
| Trigger | Update timing | Content |
|---|---|---|
| Any contact with the IRS | Within two working days | What happened, what was said, what is next |
| Active negotiation or filing | Every two weeks | Progress against the checklist, anything needed from the client |
| Waiting on a decision | Monthly | "No change" notes still go out |
| A deadline within 14 days | Weekly until met | Exactly what is needed and by when |
Have the AI draft from the checked summary, not from the raw transcript. A reviewed example, with placeholders:
Hi [first name],
A quick update on your case. We have now reviewed your IRS account records for
2022 and 2023. Together they show a balance of $29,570 as of [transcript date].
That figure grows with interest, so it is not a payoff amount.
Your 2024 return has not been filed yet. We need your invoices and bank
statements for that year by [date] so we can prepare it.
Next step: [practitioner] will call you on [date] to talk through options.
Nothing has been agreed with the IRS yet.
[your name]Note what the draft leaves out: no promise of an outcome, no "this should be fine", and no technical codes. If a client asks what a code means, the practitioner answers it. The wording follows the approach in explaining tax to clients in plain English.
Payroll-tax quarters and a pending offer
A childcare nursery with unpaid payroll tax. Business transcripts differ from the individual ones: the periods are quarterly, and the summary should list balance by quarter, not by year. Add the quarter as a column in the table, and ask for a separate list of any quarter with no payment line. Payroll tax debts are treated seriously, so keep the practitioner's check strict and do not let the draft imply any personal liability position.
A specialist food importer with an offer pending. The transcripts show a TC 480 entry. The summary needs a "dates" block listing when the offer was lodged and any later entries, because the client will ask whether collection has paused. The AI lists the dates; the practitioner answers the question from the rules and the notice letters. The tax audit support tutorial covers a similar discipline around deadlines.
Cross-checking income: a wage and income mismatch
The wage and income transcript is where many cases turn. Say the kitchen fitter's 2024 transcript lists three forms: two 1099-NEC forms from builders ($21,500 and $11,200) and one 1099-K from a card processor ($14,800). Together that is $47,500. The client's own bookkeeping shows $38,000 of 2024 sales. The AI can list the forms and the total; it cannot say why the figures differ. Possible reasons include card receipts that are also in the builders' payments (double counting between a 1099-K and bank deposits), a deposit that is a refund, or income the client forgot. Ask it to produce exactly that list of questions ("what could explain a $9,500 gap") and then have the practitioner go through each with the client. Do not file a return that ignores a reported form without a documented reason.
A prompt that works for this: "Here are three information-return lines and the client's monthly sales totals. List each form, total them, calculate the gap to the sales total, and list five questions I should ask the client about the gap. Do not conclude which figure is right." The "do not conclude" line keeps the AI inside its role.
Comparing notices with transcripts
Clients send photos of letters. A letter gives a figure and a date; the transcript tells you whether the figure is a final assessment or a proposal. Have the AI extract three things from each notice: the notice number printed on it, the response deadline, and the amount demanded. Then put them in a deadline table alongside the case.
| Notice (as printed) | Date on letter | Response due | Amount shown | Matches transcript? |
|---|---|---|---|---|
| Balance due notice, 2022 | 3 March | Per letter: 21 days | $13,640 | Yes, before later interest |
| Proposed change, 2023 | 12 May | Per letter: 30 days | $4,900 extra tax | No entry yet: await posting |
The deadline column is where AI errors are most expensive. A photographed letter turned into text can lose a digit, so read each deadline from the paper yourself and put it in your calendar. Never let a model calculate a due date from "21 days of the date of this notice"; count it by hand.
What the case folder holds when the summary is done
- The original transcripts, stored in your secure practice system and never in the chat tool.
- The redacted text used for the summary and the script that produced it.
- The reviewed summary with the reviewer's initials and date.
- The deadline table, with each date read from the paper notice.
- Copies of each client update, with the date sent.
- A short note stating the AI use: which plan, what it did, what was checked.
The last item protects you. If the case is ever questioned, you can show that the AI only drafted, and that a named practitioner verified the numbers. It also makes onboarding a new staff member easier, because the next case follows the same folder.
Handling the awkward transcripts
Years with amended returns. The account transcript shows both the original and later adjustments. Ask the model to list lines in date order and to mark each adjustment, then compare the last balance with the printed one. If they disagree, stop and read the lines by hand.
Joint filers. The transcript may relate to two people with different circumstances. Keep each person's case code separate and do not combine them in one summary unless the engagement covers both.
Very old years. Only the most recent years are available online or by mail for some transcript types. If a year you need is not available, note it in the summary as "not obtained" rather than letting the AI fill the gap with an assumption.
Time check. In this illustration, the manual first read of three transcripts takes about three hours. The redact, summarise and check route takes about an hour and a half, split between redaction (10 minutes), prompting (10), the check (about 60) and drafting the first client note (10). Those figures are assumptions; time your next three cases and use what you measure.
Costs, time and where it breaks
The software cost is a business chat plan: for a three-person practice, three seats at $20 a month billed annually is $60 a month. The larger cost is the 20-minute check, which cannot be skipped. Where it breaks: scanned transcript images (use the text version from the online account where possible), very long wage and income transcripts with dozens of forms, and years where adjustments pile up and the running balance is hard to follow. For those, build the table by hand and use the AI only to draft the explanation.
Keep one more rule on the wall: AI output is never sent to the client or the IRS on its own. If you are comparing paid tools for this work, the tax professional pilot plan shows how to test them against your own cases first.
Questions from small tax resolution practices
Which IRS transcript types should I pull first?
For a resolution case, start with the account transcript for each year (balances, assessments, payments, collection indicators) and the wage and income transcript (what was reported to the IRS). Add the return transcript if you need the filed return as submitted. The verification of non-filing letter helps when a year shows no return.
Can I upload a transcript with the social security number still on it?
Do not. Replace identifiers with a case code before the text leaves your system, and keep the key that maps the code back to the client inside your practice management software. Use a business plan whose content is not used for training by default, and follow your firm's written data-security plan.
How often should I update a client during a case?
Set a floor and tell the client what it is. One workable pattern is an update within two working days of any contact with the IRS, a fortnightly note while negotiating, and a monthly note while waiting on a decision, even if the note says nothing has changed.
Will the AI tell me which resolution option fits?
It can lay out facts from the transcripts, such as balances per year and collection flags, but choosing between an instalment agreement, an offer or other relief needs financial information and professional judgement. Keep that decision with the practitioner and record the reasoning.
Further reads
- AI Receptionist for Accounting Firms: Tax-Season Calls and Cost — Handle tax-season calls without hiring.
- How to Chase Missing Client Records With AI Before Deadlines — Chase missing client records before deadlines.
- Can AI Do My Business Taxes? What It Can Safely Prepare — What AI can and cannot safely prepare for a business.
- AI Tax Prep Software for CPAs: What to Test Before You Switch — What to test before switching tax preparation software.
- AI Tax Research Tools Compared: Citations, Cost and Checks — Research tools compared on citations and cost.
- AI Readiness Checklist for Accountants, Solicitors, Consultants — Check your practice is ready for AI before you start.
- Can AI Draft an IRS Notice Response? What to Check Before Sending — A practitioner's routine for AI-drafted IRS notice responses: triage by type and deadline, redact first, verify every code, amount and date, then sign.
- Free AI for Tax Professionals: Where the Free Tier Stops at Client Data — Which tax-practice jobs suit a free AI tier, which never should touch return information, and what a paid business plan changes and does not change.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: IRS pages on transcript types and ways to order them, the Transcript Delivery System and the time the IRS can collect tax; IRS Document 6209 Section 8A (2023 edition); OpenAI ChatGPT Business and Claude pricing pages. Checked 4 November 2026.