IRS IRIS Testing and Sandbox Guide

What Is the IRIS Testing Sandbox?

The IRS testing environment is formally called the IRIS Assurance Testing System (ATS). It is a non-production environment that allows transmitters to validate XML submissions, test authentication workflows, and confirm end-to-end transmission before filing real information returns.

The official test package is IRS Publication 5719. The IRS says each processing year’s A2A ATS environment generally opens in November and announces the exact opening date through QuickAlerts. Publication 5719 describes ATS as available throughout the year after it opens, subject to scheduled maintenance.

ATS applies to the A2A channel, not to Taxpayer Portal filing. Software Developers must pass the applicable software tests. Issuers and Transmitters using approved software must complete a one-time communication test by sending a transmission and retrieving an Accepted acknowledgment. After the required test is reviewed, the IRS moves the applicable software package or TCC production indicator from test to production.

This is a significant departure from FIRE, where the testing process was simpler — upload a test file to the FIRE test system, receive a pass/fail response, and move on. IRIS ATS testing is more rigorous because the A2A API is more complex and the XML format has stricter validation requirements.

How to Access the IRIS Sandbox

Prerequisites

Before you can access ATS, you need:

1. An IRS e-Services account with completed ID.me identity verification. See our IRIS registration guide for step-by-step instructions.
2. An approved IRIS A2A TCC. Publication 5719 requires the TCC application to be complete and signed before participating in ATS.
3. An API Client ID. All IRIS A2A users must obtain one before submitting to ATS.
4. The current IRIS A2A technical package. Use the current Publication 5718, Publication 5719, schemas, business rules, WSDL files, and ATS examples for the processing year you are testing.

Sandbox Endpoints

The ATS environment has its own set of SOAP endpoints, distinct from production. Do not confuse them — submitting to ATS endpoints does not create real IRS filings, and submitting to production endpoints during testing will create real filings that you would need to correct. The IRS provides the ATS endpoint URLs through the e-Services portal. They typically follow a different subdomain pattern than production endpoints.

ATS uses the OAuth/JWT A2A authentication flow documented in Publication 5718. Your API Client ID must be authorized for TEST access, and your transmission must use the appropriate TCC and IRIS user identity. TEST and PROD access are granted separately.

What You Can Test

XML Schema Validation

ATS validates your XML submissions against the same XSD schemas used in production. This catches structural errors — missing elements, incorrect data types, namespace mismatches, and element ordering issues — before you submit to the live system. If you are converting FIRE flat files to IRIS XML, schema validation in ATS is essential for verifying that your conversion logic produces conformant output.

Schema Compliance Across Form Types

Each 1099 form type has its own schema requirements. ATS allows you to test submissions for every form type your TCC covers. If you file 1099-NEC, 1099-MISC, 1099-INT, and 1099-DIV, test all four — do not assume that passing validation for one form type means the others will also pass. Field requirements, amount relationships, and optional elements differ across form types.

Transmission Workflow

ATS tests the complete transmission lifecycle:

1. Authentication: Verify your credentials are accepted and tokens are returned correctly.
2. Submission: Upload your XML and confirm the SOAP response indicates successful receipt.
3. Status check: Poll the status endpoint to confirm your submission is processing.
4. Acknowledgment retrieval: Download the acknowledgment response, which confirms acceptance or lists any validation errors.

Testing Limitations

While ATS mirrors the production environment closely, there are important differences to be aware of:

• No live issuer or recipient taxpayer data: Publication 5719 requires synthetic ATS TINs in the prescribed zero-prefixed format and says live taxpayer data will be rejected.
• No stress or load testing: ATS is for schema, business-rule, software, and communication testing. The IRS expressly says it does not support performance testing.
• Processing time differences: ATS response times do not represent expected production response times.
• No downstream processing: IRS downstream systems do not process ATS submissions.

Best Practices for IRIS Testing

Keep Performance Testing Outside ATS

Use ATS for the scenarios and communication tests prescribed by the IRS. Test high-volume throughput, queue behavior, and retry logic in your own non-IRS environment; Publication 5719 explicitly says ATS does not support stress or load testing. Organizations planning high-volume bulk filing should still test their internal pipeline at representative volume without directing that load at IRS ATS.

Test Corrections and Amendments

Filing original returns is only half the workflow. You also need to test corrections — filing amended returns to fix errors in previously accepted submissions. The correction process in IRIS differs from FIRE’s correction workflow, and ATS is the place to learn it before you have a real correction deadline bearing down on you.

Test Edge Cases

Push the boundaries of your data:

• Submissions with the maximum number of payee records
• Forms with every optional field populated
• Forms with only required fields (minimum data)
• Foreign addresses and non-standard characters
• Large dollar amounts near the field maximum
• Multiple form types in a single transmission batch

Automate Your Test Suite

If you are building a custom IRIS A2A integration, automate local schema and business-rule checks and keep a small, controlled ATS regression suite for the IRS-required communication paths. Do not turn ATS into a continuous load-testing target.

BoomTax and IRIS Testing

If you use BoomTax as your filing provider, you do not need to interact with ATS at all. BoomTax maintains its own IRIS integration, manages all testing internally, and ensures that every submission complies with the current IRS schemas before it reaches production. When the IRS publishes schema updates, BoomTax updates its systems and re-tests — you are insulated from the process entirely.

This is particularly valuable for organizations transitioning from FIRE. Rather than learning the IRIS A2A protocol, building a testing pipeline, passing ATS certification, and maintaining it going forward, you can upload your existing FIRE-format files to BoomTax and let BoomTax handle everything downstream.

Frequently Asked Questions

Next Steps

• IRIS A2A API integration guide
• IRIS XML format guide
• IRIS error codes and troubleshooting
• How to get an IRIS TCC
• How to file corrections through IRIS
• Skip ATS — let BoomTax handle IRIS filing