At a glance
Operating system
Windows 10 (1909+) or 11
64-bit x64 only. ARM and 32-bit not supported.
RAM
4 GB minimum
8 GB recommended if you'll dispatch hundreds of transcripts in parallel.
Disk
2 GB for install
Plan another 5-10 GB for transcript cache and generated PDFs at firm scale.
Internet
Broadband
IRS transcript pulls are bandwidth-sensitive. Tethering works; dial-up doesn't.
Screen
1440×900 or better
TRH uses every pixel. 1920×1080 is ideal; dual-monitor pros will use the second for transcript viewing.
Installer permissions
User account OK
No admin rights required. Squirrel installs to your user profile.
IRS credentials (optional but expected)
TRH runs without IRS credentials — you can still use the resolution calculators, form library, notice lookup, and client manager. To actually pull transcripts you'll need one of:
- IRS A2A (Application-to-Application) — recommended. High-throughput, bulk-friendly. Requires an approved CAF number, e-Services account with TDS authorization, and a registered public/private key pair.
- IRS ISP (Interactive Session Protocol) — fallback. One client at a time, browser-based sign-in each session. Still supported for firms without A2A approval; can be re-enabled from Tools & System → IRS Authentication at any time.
New to A2A? The IRS publishes an A2A onboarding guide and your e-Services Admin can request TDS access. TRH's first-launch checklist walks you through registering your key with the IRS once you're approved.
Network requirements
TRH makes outbound HTTPS connections to a small, known set of endpoints. If your firm uses restrictive egress filtering, allow the following:
| Purpose | Host | Port |
|---|---|---|
| IRS Transcript Delivery System (A2A / ISP) | la.www4.irs.gov | 443 |
| IRS e-Services API endpoints | api.irs.gov | 443 |
| TRH license validation | *.execute-api.us-east-1.amazonaws.com | 443 |
| TRH auto-updater | dpneilscoxfdh.cloudfront.net | 443 |
| TRH marketing site (first-install downloads) | taxhub-usa.com | 443 |
No inbound ports are required. TRH never listens for connections.
What gets stored where
| Data | Location | Encrypted at rest? |
|---|---|---|
| Client records, cases, POA details | %APPDATA%\Transcript Services\data\ | Yes (AEAD) |
| Raw transcript archives | <your chosen transcripts folder> | No (Windows-profile ACL) |
| Generated PDFs / reports | <your chosen reports folder> | No |
| License key + machine ID | %APPDATA%\Transcript Services\data\ | Plaintext (Windows-profile ACL) |
| IRS A2A private keys | Wherever you pointed TRH; or encrypted vault | You choose |
Nothing leaves your machine except: (1) IRS API calls you explicitly dispatch, (2) license validation calls, (3) update manifest checks. We do not telemetry-ship client data.
Not currently supported
- macOS, Linux — Windows only
- ARM Windows devices (e.g., Copilot+ PCs on Snapdragon) — x64 only in this release
- Citrix / Terminal Services / thin-client deployments — designed for per-user desktop installs
- Shared network drives for the app data folder — keep it on local disk
Something missing?
If a requirement on this page is a blocker for your firm, tell us at support@taxhub-usa.com. We prioritize feature work by what customers actually need.