IRIS for accountants and payroll firms: filing 1099s for many clients

One application, the Transmitter role

"The IRS encourages transmitters who file for multiple issuers to submit one application, select the 'transmitter' role, and use the assigned TCC for all issuers. The purpose of the TCC is to identify the business acting as the transmitter of the file. As a transmitter, you may transmit files for as many companies as you need to under one TCC" (Pub 5717 2.2). The Issuer role is for a business filing only under its own EIN; it cannot be used for a client, and a firm filing its own 1099s as well as clients' needs only the Transmitter role (Pub 5718 1.3.2). The portal and A2A are separate TCC applications, so a firm that keys small clients in the portal and transmits large ones by software holds one of each.

The application is filed by a Responsible Official of the firm, needs the firm's EIN (not an SSN), a physical address, and SSN, date of birth and contact details for each RO, Contact and Authorized Delegate, and is signed by every RO with a five-digit PIN. Allow up to 45 days; the TCC starts with D. If the firm wants its clients' state copies forwarded through CF/SF, that consent is given on this application, not per client (see the CF/SF page). The TCC lifecycle guide covers the screens; a TCC unused for three years is deleted.

Users, Responsible Officials and who sees what

Everyone who will touch the portal needs their own IRS online account first: "Please advise all authorized users to set up an account BEFORE you add them to the application" (Pub 5717 2.1). Adding, removing or changing an RO or Authorized Delegate means every RO re-signs the application (Pub 5718 1.3.7), so a firm with staff turnover should keep the application's people list to the few who need to be on it and plan the re-signing.

Visibility is per user. View Submitted Forms shows "transmissions that are associated with the logged-in user" (Pub 5717 3.2), and the recipient copies a user can download are the ones from those transmissions. For a firm that means a preparer who leaves takes the easy view of their transmissions with them: keep the Receipt IDs and acknowledgments outside the portal, per client, from day one (see what to keep).

Saved issuers and the 25 limit

Issuer Management stores payer information for keyed entry and the extension screen: "You can save information for up to 25 frequently used Issuers," each under a required nickname, available from year to year (Pub 5717 3.3). Twenty-five is the number to design around. A firm with more clients than that has three choices: rotate the list each season, enter the issuer block on each form from a firm template, or move the clients above the limit to CSV upload, where the issuer block is columns in the file and the saved list is not involved. Issuer information entered on a form is not saved to the list unless it was added there first.

Volume: CSV rows, submissions, downloads

A season in the portal, client by client

Extensions and corrections per client

Extensions are per issuer TIN: "Submit a separate extension request for each issuer tax identification number" (Pub 5717 section 4). The Bulk Automatic Extension Request upload exists for exactly this, a CSV on the 8809 template with one row per client; the extensions page has the screens, the January 1 to March 31 window, and why 1099-NEC requests stay on paper. Corrections are made from the submitted form, inside its submission, and the portal copies every form in that submission into the correction transmission (Pub 5717 3.6); the corrections guide walks it. Neither can be done by a user who cannot see the original transmission, which is the second reason to keep Receipt IDs outside the portal.

What to keep for each client

Publication 5718 tells a business using a third-party transmitter what to demand from it, and a firm should hold the same set for each client, in its own files (Pub 5718 1.3.3):

• A copy of every record in each submission, with the Receipt ID of the transmission it went in.
• The acknowledgment for each transmission: the status (Accepted, Accepted with Errors, Partially Accepted, Rejected) and the error list.
• The extension acknowledgment, if one was requested, and the CF/SF states selected on each return.

The publication's reason is blunt: those items "are critical to your ability to make corrections should your Third-party Transmitter go out of business or be otherwise unavailable." For a firm, the same records are what lets a different preparer, or the client itself, pick up a correction or answer a notice. An engagement letter that says who holds the Receipt IDs and who files corrections after the engagement ends saves an argument later.

When a firm outgrows the portal

The portal has no bulk download of acknowledgments, no API, and the limits above. A firm transmitting thousands of forms, or one that wants its practice software to file and retrieve acknowledgments directly, moves to A2A: a second TCC application with the A2A transmission method, an API Client ID, and software that has passed ATS, either a vendor's or its own. The same Transmitter role applies and the same records need keeping. The A2A developer guide covers the setup end to end; a firm that buys software does the TCC, Client ID, consent and one communication test, and the vendor does the rest.

Questions people ask