Publication 5717 is the IRS guide to the IRIS Taxpayer Portal — the browser-based and CSV-upload way to e-file the 1099 series. It is the document that walks a filer through getting access, building a submission, transmitting, and reading acknowledgments. The deeper machine-to-machine (A2A) specification a developer implements lives in its sibling, Pub 5718, with required testing described in Pub 5719. Read together, these three publications are the complete IRIS rulebook, and they replace the FIRE-era Pub 1220 ahead of the December 31, 2026 FIRE sunset. If your deadline won’t wait, a provider that has already implemented all three can file today.
In this story
What Publication 5717 Actually Is
Publication 5717 is the IRS’s user guide for the Information Returns Intake System (IRIS) Taxpayer Portal — the no-software path that lets a filer key returns into a browser form or upload a CSV, then transmit them to the IRS.
It is written for the person doing the filing, not the person building a system. It explains how to request access, how a submission is structured, how to send it, and how to interpret what comes back. If you have ever searched for “publication 5717” expecting a raw XML schema, this is the first thing to internalize: 5717 is the Portal manual. The element-level, machine-readable specification that developers code against is a different document — Pub 5718, the Application-to-Application (A2A) guide. The two describe the same underlying data; they simply speak to two different audiences, one clicking through a screen and one writing code against a schema.
Read the primary documents directly: Pub 5717 (IRIS Taxpayer Portal user guide), Pub 5718 (IRIS A2A specification), and Pub 5719 (IRIS Assurance Testing System). Access and identity verification run through IRS e-Services and ID.me. Treat the published PDFs as authoritative; this article summarizes them in plain English and points back to the section that governs each claim. For the broader developer picture, see the IRIS technical guide this post sits under.
Why 5717 Matters Now: The FIRE Sunset
For decades, electronic filers lived by Publication 1220, the FIRE system’s fixed-width record layout that told you exactly which character went in which column. The IRS is retiring the FIRE system on December 31, 2026, and IRIS is its replacement. That single date is why the Pub 5717–5719 set has moved from “nice to know” to required reading: once FIRE goes dark, the procedures these publications describe are the way information returns get filed electronically.
The division of labor is straightforward once you see it. For a Portal filer, 5717 is the document that gets you from “I have access” to “I have an accepted submission.” For a developer, 5717 sets the context and 5718 carries the implementation detail. Either way, the publications — not blog posts, not vendor documentation — are the IRS’s own statement of the rules, and they are what an auditor or the IRS will point to if a filing goes wrong.
What Each Part of 5717 Covers
The publication is organized roughly the way a first-time filer experiences the system, moving from getting in the door to fixing a return after the fact. The exact section numbering changes between revisions, so the table below groups the content by purpose rather than by a page number we can’t guarantee will hold. Match each area to the question it answers, and you have a map of the whole document.
| Coverage area | The question it answers | What it actually covers |
|---|---|---|
| Getting access | How do I get into IRIS at all? | Identity verification through ID.me, an IRS account, and the IRIS application — including obtaining a Transmitter Control Code (TCC). |
| Roles & authorities | Who in my organization can do what? | Responsible Officials, authorized users, and the consent each must give before filing. |
| Building a submission | How do I enter or upload returns? | Manual key-in screens and the CSV upload templates, with the supported 1099-series forms. |
| Transmitting | How do I send it to the IRS? | The submit flow, the test (T) versus production (P) distinction, and what a successful send looks like. |
| Acknowledgments & status | Was it accepted — and if not, why? | Reading the Receipt ID, the accepted or rejected status, and the error detail that tells you what to fix. The step filers skip at their peril. |
| Corrections | How do I fix a filed return? | How the Portal handles corrected and replacement records once an original is on file. |
Notice what 5717 does not contain: it is not a line-by-line XML element dictionary. The Portal builds that XML for you behind the scenes, which is the entire point of the no-software path. The moment you need the raw element names and data types — because you are integrating directly rather than typing into a browser — you cross from 5717 into 5718.
The Fork: Portal (5717) vs A2A (5718)
The single most useful thing to understand about this publication family is the split between the two filing channels, because it decides which document you live in for the rest of the season. One channel is a website you log into; the other is a system your software talks to. They reach the same IRS, but they ask very different things of you.
| Dimension | Taxpayer Portal (Pub 5717) | A2A (Pub 5718) |
|---|---|---|
| Audience | Filers, accountants, small teams | Developers, software vendors, high-volume transmitters |
| How you file | Browser forms or CSV upload | XML transmissions sent system-to-system |
| What you build | Nothing — the IRS UI builds it | Schema-valid XML, an authenticated client, and polling logic |
| Required testing | None to start filing | ATS (Pub 5719) is mandatory before production |
| Best for | Lower volumes, occasional filing | Large batches and embedded, automated filing |
Under both channels the data the IRS ultimately validates is the same XML; the Portal just hides it from you. So if you only ever file through the Portal, 5717 is effectively your whole world, and you can stop there. If you build an integration, 5717 orients you to the system but 5718 is the spec you implement against, and Pub 5719 is the gate you have to clear before you go live.
What a Developer Actually Has to Implement
If your reason for reading 5717 is to build something, here is the honest scope. The Portal path the publication describes requires no engineering at all — it is a user interface, and the IRS maintains it. The A2A path defined in Pub 5718 is where the real implementation work lives, and it comes down to four moving parts that build on one another.
- Authentication. An A2A client authenticates to the IRS using the credentials and tokens described in the A2A guide, not a username and password typed into a browser. This is its own setup step, and getting it wrong is the first thing that blocks a transmission.
- Building the transmission. You assemble schema-valid XML: a
Transmissionwrapping one or moreSubmissionblocks, each carrying a payer and its form records, tagged with yourTCCand a test or production indicator. - Sending and polling. You submit the transmission, receive a Receipt ID, and then poll for the acknowledgment, because A2A is asynchronous — you ask the IRS for status rather than getting it back inline.
- Reading acknowledgments. You parse the accepted or rejected status and any error detail, then correct the flagged records and resubmit the rejects.
The element-level detail behind step two — exact names, data types, and required children — is exactly what the next two siblings cover, so you don’t reverse-engineer it from 5717. For the structure and validation layers, see the IRIS XML schema and validation guide; for the request and response mechanics of authenticating, submitting, and polling, see the A2A API integration walkthrough. And the full set of cross-field checks the IRS runs is catalogued in the IRIS business-rule catalog, which 5717 and 5718 both reference rather than reprint.
Don't want to implement any of it?
e1099f reads Pub 5717–5719 so your team doesn't have to — the Portal flow, the A2A spec, and the rule catalog are already built and ATS-approved.
The Testing Gate You Can't Skip (Pub 5719)
One detail catches first-time A2A builders off guard: you cannot move straight to production. The IRIS Assurance Testing System (ATS), documented in Pub 5719, is a mandatory gate for A2A transmitters. You run a set of test scenarios, prove your XML clears both the schema layer and the business-rule layer against known cases, and only then is your TCC enabled for live filing.
Portal-only filers covered by 5717 don’t face ATS, because the IRS interface is itself the tested surface. But anyone implementing against 5718 has to budget time for it, and it is the kind of step that, discovered late, turns a comfortable January into a frantic one. The practical move is to count backward from your filing deadline and start ATS early enough that a failed scenario doesn’t cost you the season.
ATS is not a same-day formality. If you are building A2A, treat the Pub 5719 testing window as part of your deadline, not an afterthought — clear the scenarios well before the forms are due, so a rejected test case is an inconvenience rather than a missed filing.
Common Rejection Reasons (and How to Avoid Them)
Whether you file through the Portal or through A2A, the IRS validates the same data, so the failures look similar from either channel. These are the ones that most often turn an “accepted” into a “rejected,” framed the way the publications describe them, with the cause first and the fix right behind it.
Cause: Filing before the IRIS application is approved, or using a Portal TCC to transmit via A2A when they are separate authorizations — and a FIRE TCC does not carry over to IRIS at all. Fix: Complete the IRIS application for the channel you intend to use and wait for approval before you file. See the full IRIS TCC application guide for the steps and the timeline.
Cause: A TIN entered with hyphens, or a dollar amount carrying a currency symbol or commas, neither of which the schema accepts. Fix: Strip the formatting — TINs are nine bare digits, and amounts are plain numbers typed exactly as the schema defines them. The Portal masks this for you; A2A does not, so your code has to normalize the values first.
Cause: A non-USPS state code, or state withholding present without the matching state block, in a Combined Federal/State Filing record. Fix: Emit the full state group together with a valid two-letter code — the rule checks them as a set, and CF/SF must be elected on the first submission of a record, not bolted on later. See how CF/SF works on IRIS.
Cause: An A2A transmitter going live without passing ATS, or sending real data with the test indicator set (or sending test data flagged as production). Fix: Clear the Pub 5719 scenarios first, and set the test or production flag deliberately on every transmission so the IRS treats your data the way you intend.
Skip the Publications Entirely: The e1099f Advantage
You can read all three publications end to end and build to them yourself, or you can hand the whole spec to software that already has. e1099f implements Pub 5717–5719 so the document stack becomes someone else’s problem — you file, rather than study.
The spec, already built
Portal flow, A2A XML, and the rule catalog from 5717–5719 are implemented and maintained as the IRS revises them.
ATS-approved
The Pub 5719 testing gate is already cleared, so you don’t run assurance scenarios just to start filing.
CF/SF handled
State elements are emitted and validated to the rules, set correctly on the first submission, with no guesswork.
Compliant IRIS filing without opening a single publication PDF.
Frequently Asked Questions
Is Publication 5717 the IRIS XML schema?
What is the difference between Pub 5717, 5718, and 5719?
Does Pub 5717 replace Publication 1220?
Do I need to read 5717 if I only file a few 1099s?
Where do I get the IRS publications?
irs.gov/pub/irs-pdf/p5717.pdf and p5718.pdf. The ATS material (5719) is distributed with the IRIS Assurance Testing package.Do I need a TCC to file through the Portal?
Is ATS testing required for Portal filing?
Does 5717 cover Combined Federal/State Filing?
How often do these publications change?
Do I have to understand any of this to file with e1099f?
Not tax advice. This is general information about IRS procedures and may change as the IRS updates IRIS; section organization and field requirements vary between publication revisions. The official IRS Publications 5717–5719 and the published IRIS schema are authoritative — verify current requirements and consult a tax professional for your situation before relying on anything here.