Start with the authority question: transcript software does not itself authorize a practitioner to access a client’s tax information. The IRS Transcript Delivery System (TDS) lets eligible practitioners request specified client transcripts, and a properly executed Form 2848 or Form 8821 must be on file before that request can succeed. Access also requires login credentials for your own account. So evaluate a tool as a workflow layer around a process you already control, not as a substitute for it.
A recommended seven-stage transcript workflow
This is a recommended framework, not an IRS requirement: a seven-stage sequence you can adapt to your practice. Each stage has a question to answer before the next one produces anything useful.
| Stage | Question to settle | Guide |
|---|---|---|
| Authority | Is this information access or representation? | Form 8821 vs. 2848: match authority to the work |
| Identity | Which identifier belongs to the task at hand? | CAF, PTIN and EFIN: different IDs, different jobs |
| Access | Are the user, the authorization and the request ready for TDS? | IRS TDS access: a readiness checklist |
| Document | Which transcript actually answers the review question? | Tax account vs. tax return transcript |
| Submission status | Where does the authorization itself stand? | Submitting Forms 2848 and 8821 |
| Review | What does the document show, and what does it not show? | IRS transcript review: findings, gaps and next checks |
| Automation | Where does a retrieved document need to land? | Tax workflow automation: from transcript to CRM |
A gap in one stage is a different problem from an error inside a single stage. A firm can buy retrieval tooling and still stall at stage one, because nobody decided whether the work needed disclosure authority or representation authority.
What the IRS actually describes
The IRS page on the Transcript Delivery System states that TDS lets eligible electronic return originators and Circular 230 practitioners request specified client transcripts, and that a properly executed Form 2848 or Form 8821 must be on file. It also lists the document types available through the system: account, wage and income, tax return, record of account, and non-filing documents.
Two implications follow for your evaluation. First, the document menu is finite, so "transcript software" cannot retrieve something outside that set for you. Second, the presence of a CAF number or a signed form is not by itself evidence that a particular authorization has been processed or that a particular request will succeed. Treat those as statuses to verify against current IRS instructions, not assumptions to build a workflow on.
Questions to ask a vendor before you buy
A useful evaluation is a list of questions whose answers tell you something checkable.
- How does the tool authenticate to IRS services? Ask for the authorized access method and who is responsible for credentials. A product that stores or asks for IRS passwords, or describes bypassing an identity step, is answering the question badly.
- Does it distinguish submitted from processed? A receipt for a form you uploaded proves delivery of a document, not that authority was granted. Ask how the product surfaces pending, processed and failed states.
- Does it record an exception path? Real practices get rejections, partial scopes and incomplete results. Ask what a staff member sees when a request does not succeed.
- What is retained, and who can see it? Client records belong in approved internal systems with access controls and a documented retention decision.
- What does the vendor not do? Boundaries stated up front are worth more than feature lists. Note that 26T1 markets authorizations, transcript and analysis tools plus custom workflow integrations, and that integration depth depends on available third-party APIs.
Put the tool decision inside your security plan
The IRS states that tax professionals must create a written information security plan, and that the plan should fit the size, scope, complexity and sensitivity of the practice. Its guidance covers assigning responsibility, risk assessment, evaluating safeguards, training, monitoring, and service-provider safeguards. See the IRS guidance on protecting client information.
The practical recommendation: evaluate transcript software as a service provider inside that plan, using the same questions you would apply to any other processor of client records. A purchase decision is not evidence that the requirement has been met.
Before you commit to a tool
- [ ] Write down the last five transcript requests the firm handled and which stage each one stalled at
- [ ] Confirm whether the underlying work needs disclosure authority or representation authority
- [ ] Ask each vendor how it authenticates and who holds credentials
- [ ] Ask how the product reports submitted versus processed authorizations
- [ ] Decide where retrieved documents will live and who can access them
- [ ] Run a first test on a redacted or synthetic file, not live client documents
- [ ] Record which answers you could not verify and need to confirm in current IRS instructions
Frequently asked questions
Does having a CAF number mean my transcript access is active?
No conclusion follows from the number alone. The number, a signed form and an authorization the IRS has processed are different states. The TDS readiness guide walks through the layers you have to confirm separately.
Can transcript software replace preparing Form 2848 or 8821?
Not as authority. Those forms establish what a client permits; software operates inside that permission. The authority comparison sets out the difference between information access and representation.
Which transcript should we ask for first in a typical review?
Start from the question, not the menu. The document selection guide maps common review questions to document types and their limitations.
How should we handle a request that comes back incomplete?
Log what was observed, what was requested and what was missing, then route it for qualified follow-up. The transcript review guide provides a note structure that keeps observed facts separate from interpretation.
Discuss your firm’s authorization, transcript and CRM workflow in a 26T1 demo.