Obtain the appropriate IRIS TCC
Complete the IRIS Application for TCC and confirm the application role supports the intended A2A activity.
IRIS A2A implementation
IRIS A2A setup checklist: from authorization to production transmission
A2A is not just “create XML and send it.” A production transmitter needs IRS authorization, API credentials, keys, current schemas/business rules, testing, secure deployment and acknowledgement processing.
Step-by-step fix
Use a controlled troubleshooting sequence
Request the IRS API Client ID
Use the IRS API client ID application for IRIS A2A and follow Publication 5718 system requirements.
Configure keys and authentication securely
Generate and protect the required key material/JWKS according to current IRS specifications. Never embed private credentials in public website code or support files.
Build against the current schema/business-rule package
Pin your implementation to the tax year and release you are transmitting. Validate XML locally before sending it.
Complete ATS testing
Use Publication 5719 and current ATS materials. Keep evidence of the scenarios and acknowledgements that satisfy production requirements.
Deploy production with acknowledgement handling
Store submission identifiers, retrieve results, surface record-level errors, and produce a transmission report that staff can reconcile.
Common failure points
Problems that cause avoidable repeat filings
Using the wrong environment
Keep ATS/test and production endpoints, credentials and data separated.
Schema-valid but business-rule invalid XML
XSD validation is necessary but not sufficient. Run the IRS business rules applicable to the form and tax year.
Key/JWKS mismatch
Verify the public key registered with the IRS matches the private key used by the transmitting application.
No retry/idempotency design
A network timeout does not prove the IRS did not receive a transmission. Use identifiers and status checks before blindly resending.
No printable transmission evidence
Retain Receipt ID, UTID, submission time, record count, final status and acknowledgement errors for the filer’s records.
Quick answers
Frequently asked questions
Can the website create my A2A channel automatically?
No public website should create or hold your IRS credentials for you. The organization must complete IRS authorization and securely operate its own integration.
Is well-formed XML enough?
No. Validate XML against the correct XSD and applicable business rules, then process the IRS acknowledgement after transmission.
Where do the current A2A requirements live?
Publication 5718 is the primary IRIS A2A specification, with Publication 5719/ATS materials for testing and current schema/business-rule releases from the IRS.
Need the next step?
Use the related 1099ERICH support or free tool before creating another IRS submission.
Back to IRIS SupportBrowse Supported SoftwareOfficial sources
IRS resources used for this guide
Use the current agency source as the final authority when requirements change.
Publication 5717Taxpayer Portal CSV, status and correction workflow.E-file information returns with IRISCurrent IRS overview, portal access and help desk.IRIS Known Issues and SolutionsCurrent IRS-known Portal, A2A and ATS issues.Publication 5718A2A technical specifications.Publication 5719IRIS testing package.Get an API Client IDIRS API application guidance.
Prepare cleaner IRIS files before you upload.
1099ERICH imports Excel/CSV source data, validates supported records, prints recipient copies and creates IRIS-ready filing files on Windows.