Free IRIS developer guide
Passing IRIS A2A ATS testing
Before you can file a single return through IRIS A2A, the IRS makes you prove it works in its Assurance Testing System (ATS). Here's who has to test, exactly what to send, how to read the results and how to get moved to production, plus a plan builder for your own test.
The plan builder and TIN generator run entirely in your browser. Nothing is sent to us or stored.
Short answer
IRIS ATS (Assurance Testing System) is where software and transmitters prove their IRIS A2A transmissions work before filing for real. Software developers send five submissions of two records each (10 records), all Accepted, plus one correction record if the software supports corrections (11 in total). Transmitters using approved software pass a communication test: one transmission, one submission, two records, Accepted. Use TestCd T, made-up issuer and recipient TINs starting with 000, then call the IRIS Help Desk (866-937-4130) with your Receipt IDs to move to production.
- ATS is open all year; live taxpayer data is rejected
- New UTID for every transmission, including resends
- In ATS only, fix errors by resending as an original
- New Software ID for each tax year and form type
Last reviewed against IRS Publication 5719 (Rev. 10-2026) and the Tax Year 2026 IRIS ATS Examples.
ATS test plan builder
ATS test TIN generator Issuer and recipient TINs in ATS must start with 000.
Don't use these in the transmitter group: that must carry your real name and EIN from the TCC application.
Who has to test, and which test
| Your role | Test | What passing gets you |
|---|---|---|
| Issuer or Transmitter using approved third-party software | Communication test: 1 transmission, 1 submission, 2 records | Your TCC moves from Test (T) to Production (P) |
| Software Developer (commercial, online or in-house) | Software test: 5 submissions × 2 records, plus CF/SF and correction tests if you support them | Your Software Package and Software ID move to Production. The developer TCC itself always stays in Test. |
| Software Developer and Transmitter | Software test only; no separate communication test | As above |
A sole proprietor or single-member LLC filing under an SSN applies as a Transmitter, not an Issuer.
The process, start to finish
- Get an IRIS A2A TCC. Complete and sign the IRIS Application for TCC with the A2A method and the right roles. The application must be complete and signed before you can use ATS. Open the IRIS Application for TCC
- Get an API Client ID. Apply for an API Client ID (irs.gov/iris → Get an API Client ID) and register your public keys. Every A2A user needs one before sending anything to ATS. IRS: Get an API Client ID
- Get the schemas and business rules. Software Developers (and government agencies) download them from the Secure Object Repository. Build your XML from the current tax year's package. Open the Secure Object Repository
- Build your test files. TestCd "T", a new UTID per transmission, your real transmitter name and EIN, a verifiable Software ID, and made-up issuer and recipient TINs starting with 000. Tax Year 2026 IRIS ATS Examples
- Send them to the ATS endpoint. POST to the ATS intake endpoint, keep each Receipt ID, then request the status and acknowledgment. Endpoints: Publication 5718
- Resend until everything is Accepted. Fix every error and resend as a new original transmission (in ATS only) until each submission shows Accepted.
- Call the Help Desk for review. Give the IRIS Help Desk your Accepted Receipt IDs and details. Transmitters move to Production; software packages and Software IDs move to Production.
The TCC, API Client ID, endpoints and XML structure are covered in the IRIS A2A developer guide, and the TCC application in the IRIS TCC guide.
Rules for every test transmission
- TestCd "T" in the manifest. Any other value rejects.
- The right TCC: Software Developers use their Software Developer TCC; Transmitters doing the communication test use their Transmitter TCC. The TransmitterControlCd must match the TCC inside the UTID.
- Your real identity in the transmitter group: the name and EIN exactly as on your TCC application, never a 000 TIN.
- Fake issuers and recipients: TINs starting with three zeros (000-11-1111, 00-0111111). Live taxpayer data is rejected; ATS isn't a secure environment.
- A verifiable Software ID, in either Test or Production status.
- A new UTID every time, including when you resend after a rejection.
- Realistic content: at least one non-zero payment amount per form, and a unique account number if two forms share a recipient TIN. The IRS's yearly ATS examples list suggested fields for each form.
The software developer test in detail
- Five submissions with two records each (10 records). One transmission with all five is reviewed fastest; five separate original transmissions are also accepted.
- Form mix: at least one submission for each form type you support, repeating forms to reach five. If you support more than five, choose five.
- CF/SF: if your application says your software supports CF/SF, include a CF/SF record for a participating state in one of the five submissions.
- Corrections: if it supports corrections, send a separate correction transmission (TransmissionTypeCd "C") with one corrected record that references an Accepted record's UniqueRecordId. That makes 11 records in total.
- Exactly the required count. Send more or fewer records and you'll be asked to retest.
Reading your ATS results
| Status | What to do in ATS |
|---|---|
| Processing | Check back later. If it's still processing after seven days, call the Help Desk. |
| Accepted | Call the Help Desk for your ATS review. |
| Accepted with Errors | Fix the errors and resend as a new original before asking for review. |
| Partially Accepted | Fix the errors and resend as a new original before asking for review. |
| Rejected | Fix the errors and resend as a new original before asking for review. |
| Not Found | Check the Receipt ID or UTID and request the acknowledgment again. |
Resending as an original is an ATS-only rule. In production, Accepted with Errors means a correction, and Rejected means a replacement. Use the IRIS errors guide to decode business rule IDs.
Getting moved to production
- Call the IRIS Help Desk at 866-937-4130 (7:30 a.m. to 7 p.m. Eastern, Monday to Friday; +1-470-769-5100 from abroad). You'll get a case number to quote in every follow-up.
- Software Developers provide every Accepted Receipt ID (they're case sensitive), the CF/SF Submission ID if applicable, the Software Developer TCC, the Software ID, your company and position, phone and email.
- Transmitters provide the communication test's Receipt ID.
- The IRS only contacts you if something's wrong. The status change (TCC to P, or Software ID to Production) is your notice that you passed.
After you pass
- Keep testing in ATS with your own test data whenever you like; it's open all year (check the IRIS status page for maintenance).
- Get a new Software ID for each tax year and form type and update your software packages on the TCC application every year.
- Retesting isn't required for schema updates within a tax year, but the IRS strongly recommends it whenever your software changes.
- Don't use ATS for load testing, and don't judge production speed by it: response times differ.
- Leaving FIRE? Its last submissions are on November 19, 2026, so get through ATS well before the January filing season.
Questions at any hour: the e-Services chatbot covers ATS, TCCs and IRIS filing, with live chat on weekdays from 7:30 a.m. to 7:30 p.m. Eastern.
Sources
Questions
IRIS ATS questions
What is IRIS ATS?
The IRIS Assurance Testing System: the IRS's test environment for IRIS A2A. It checks your XML against the schemas and business rules, returns Receipt IDs and acknowledgments like production, and doesn't pass anything on to IRS processing. It's open all year.
What does an IRIS A2A software developer need to submit to pass ATS?
One transmission with five submissions of two records each (10 records), all Accepted. Use at least one submission per form type you support, repeating forms to reach five, or pick five if you support more. Add a CF/SF record if your software supports CF/SF, and a separate correction transmission with one corrected record if it supports corrections.
What is the IRIS communication test?
The test every Transmitter and Issuer must pass before filing in production: one transmission with one submission of two records that comes back Accepted. Then you call the Help Desk with the Receipt ID to have your TCC moved from Test to Production. Software Developers who are also Transmitters don't need it.
What TINs do I use in IRIS ATS?
Made-up issuer and recipient TINs that start with three zeros, such as 000-11-1111 or 00-0111111. Never use real taxpayer data: ATS isn't a secure environment and real TINs are rejected. The transmitter group, however, must use your real name and EIN from the TCC application.
My ATS transmission came back Accepted with Errors. Do I file a correction?
Not in ATS. Fix the errors and resend as a new original transmission until you get Accepted. Corrections and replacements are only used that way in production.
Do I have to retest every year?
Software Developers need a new Software ID for each tax year and form type, updated on the TCC application. The IRS doesn't require a retest for schema updates within a tax year, but strongly recommends using ATS whenever your software changes.
Do I need to pass ATS if I file through an e-file provider?
No. ATS is only for people sending A2A transmissions themselves. If an authorized e-file provider files for you, you don't need your own TCC, API Client ID or ATS testing.
Skip the testing entirely
EFileForMe is an authorized e-file provider. Create a free account, enter or import your forms, and we file them with the IRS. No TCC of your own, no API keys, no ATS.