Track IRS IRIS XML schema and business rule version changes by tax year and retrieve the current package for A2A submissions
domain: irs.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an IRIS Transmitter Control Code (TCC) through IRS e-Services, which is required before schema packages can be delivered to you
Sign in to e-Services and access your Secure Object Repository (SOR) mailbox, where IRIS schema and business rules packages are delivered rather than posted as public direct-download files
Check the IRS IRIS schemas and business rules page for the current tax year's version number, its ATS (testing) start date, and its production effective date, since multiple versions can be valid at once across ATS and production
Download the matching XML schema and business rules package for the tax year and version you are transmitting against, and update your A2A submission code before the new production date takes effect
Cross-reference Publication 5718, the IRIS Electronic Filing Application to Application (A2A) Specifications, for the transmission format and business-rule structure the package implements; do not use Publication 5717, which is the Taxpayer Portal user guide
Known gotchas
Schema and business-rule packages are distributed only via the e-Services SOR mailbox to TCC holders, not as public downloads on the schemas-and-business-rules page itself
Form coverage can change between point releases of the same tax year, so check a version's release comments before assuming continuity across releases
Confusing a version's ATS start date with its production date will cause you to submit against a schema that is not yet live in production
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?