IRIS Filing by Industry

IRIS Filing for CPAs & Accountants: One TCC, Every Client

Filing 1099s for a roomful of clients on IRIS is not the same job as filing for one business. The difference comes down to a single role on your TCC application, how each client's authorization is captured, and how the system groups one firm's many payers — get those right and one approved code carries your whole book of business through the season.

At a glance

An accounting firm files for many clients on IRIS under a single Transmitter Control Code tied to the firm's own EIN, by requesting the Transmitter role rather than the Issuer role on the application. Each client you file for is an Issuer inside your transmission, not a separate TCC, and the authorization to act for them rests on a clear engagement record plus the client's representation that a valid Form W-9 is on file for every recipient. The work that scales — or breaks — across a practice is the same handful of things repeated client by client: matching each client's legal name and EIN to IRS records, keeping each payer's returns in their own submission, and routing corrections back to the right original. If your TCC won't clear before the January 31 1099-NEC deadline, an authorized provider that already holds one can file for every client today.

In this story

Why Filing for a Book of Clients Is a Different Job

When a single business files its own 1099s, the firm is the filer, and almost every identifier on the return points back to one EIN. A practice filing for fifty clients is doing something the system treats as a fundamentally different transaction: you are a third party sending other people's returns to the IRS, and that one fact reshapes the role you request, the authorization you must hold, and the way IRIS expects your data to be organized.

The good news for firms is that you do not need a separate Transmitter Control Code for each client. The Information Returns Intake System is built so that one approved transmitter can carry many payers in a single feed, which is exactly the shape an accounting practice needs. The catch is that the privilege depends on choosing the correct role when you apply, and on being able to show, for every client, that you were authorized to file on their behalf. This guide walks the whole persona-specific path; for the underlying mechanics it leans on our deeper how-to coverage rather than repeating it, so you can read this as the firm's-eye view and follow the links when you need the step-by-step.

Two ideas do the heavy lifting throughout. The first is the distinction between an Issuer and a Transmitter, because picking the wrong one is the single most consequential mistake a firm can make on the application. The second is how IRIS groups data inside one transmission — a structure that lets your fifty clients ride together while still keeping each one's returns cleanly separated. Get comfortable with both and the rest of the season is logistics.

Official sources Pub 5717 / 5718

The web-channel walkthrough firms use for portal filing is the IRIS Taxpayer Portal User Guide (Publication 5717), and any firm filing machine-to-machine should work from the IRIS A2A Specifications (Publication 5718), which defines the transmitter-and-issuer structure described below. Both applications live inside IRS e-Services, and the TIN Matching program firms rely on is described in Publication 2108-A.

The One Choice That Defines Your Whole Setup: Transmitter, Not Issuer

On the IRIS application you select the role that describes what your firm actually does. An Issuer is a business filing returns for its own EIN — the role for a company reporting its own contractors. A Transmitter is a third party sending information returns to the IRS on behalf of others, which is precisely what an accounting practice is doing when it files for clients. Publication 5717 has the Portal applicant select Issuer or Transmitter, and Publication 5718 lets an A2A applicant request the Transmitter role alongside Software Developer and Issuer as needed. For a firm, Transmitter is the role that matters.

This is not a cosmetic preference. IRIS enforces it at the data layer: when the TCC's role is Issuer, the system requires the issuer's TIN on the return to match the transmitter's own TIN — the self-filer constraint. A firm that mistakenly applied as an Issuer and then tries to file a client's return, where the client's EIN naturally differs from the firm's, will see that submission rejected for the mismatch. Choosing Transmitter is what tells IRIS the payer on the return is allowed to be someone other than you.

IssuerTransmitter (firms)
Who it's forA business filing its own returnsA practice filing on behalf of clients
Whose EIN is the payerMust be your own EINEach client's EIN, client by client
TCCs needed for many clientsOne per filing entityOne for the whole book of business
Data-layer rulePayer TIN must equal the transmitter's TINPayer TIN is the client's, distinct from yours
Wrong choice for a firm?Yes — an Issuer-role TCC will reject any return whose payer EIN isn't yours, which is every client return you file.

Beyond the role, the application itself is the same one every transmitter completes: an e-Services account and ID.me identity verification for each named person, your firm's exact legal name and EIN, at least one Responsible Official, and the suitability review that runs before the code is issued. We cover that end to end in the full IRIS TCC application guide; the firm-specific point is simply that you complete it once, as a Transmitter, for the practice — not once per client.

How One Transmission Carries Fifty Clients

Understanding the shape of an IRIS transmission is what makes multi-client filing feel routine instead of daunting. Inside a single machine-to-machine transmission there is one Transmitter group — that is your firm, carrying your TCC — and then a series of submissions beneath it, with each submission representing one client's payer detail for one form type. In the schema, the transmitter is your practice and the issuer on each submission is the client whose return it is. The structure is deliberately nested so that one feed can hold many payers while keeping every payer's data in its own clearly bounded block.

A few grouping rules follow from that structure, and they are the rules that keep a busy firm out of trouble. Each submission is built around one client (the issuer) and one form type, so a client who needs both 1099-NEC and 1099-INT generates two submissions rather than one mixed batch. A transmission must not mix tax years. And a submission carries only originals, or only corrections of a single kind — never originals and corrections together. None of this requires you to think in XML if you file through software, but knowing the boundaries explains why your filing tool asks you to separate work the way it does.

The skeleton below is illustrative — the authoritative element names and ordering are defined in Publication 5718 — but it shows the nesting a firm relies on: one transmitter wrapping many issuers, each issuer being one of your clients.

Transmission TransmitterGrp <-- your firm (your TCC, your EIN) Submission (client A, 1099-NEC) IssuerDetail <-- client A as the payer RecipientDetail ... <-- client A's contractors Submission (client B, 1099-MISC) IssuerDetail <-- client B as the payer RecipientDetail ... <-- client B's vendors Submission (client A, 1099-INT) IssuerDetail <-- same client A, different form type

The practical takeaway is that a firm's mental model should be "one transmitter, many issuers," with each client appearing as an issuer as often as the form types they need. For the full anatomy of the file and how to validate it before sending, our IRIS XML format and schema guide goes element by element.

Authorization, Consent, and the W-9 That Stays With Your Client

Filing as a Transmitter means you are acting for someone else, and the IRS expects that relationship to be real and documented. The authorization that lets your firm transmit a client's returns is the engagement — the client explicitly authorizing your practice to act as their transmitter for the forms in question — and the durable evidence of it should name the client, the scope of forms, and the date, captured the same way you capture any engagement term. This is ordinary professional hygiene, but on IRIS it carries real weight because the return goes to the government under your transmission.

The most important boundary to hold clear with clients is where the Form W-9 responsibility lives. Soliciting and retaining a valid W-9 from each recipient is the payer's obligation — your client's — not the transmitter's. Your firm relies on the client's representation that a valid W-9 is on file for every recipient being filed, and that representation is part of what your engagement should capture. Keeping that line bright protects both sides: the client owns the underlying documentation, and your firm owns a clean record that you were authorized and that the client stood behind the data.

Recipient e-delivery consent is the client's call too

If your client wants to furnish recipient copies electronically rather than on paper, that requires affirmative consent from each recipient under the E-Sign Act, including a disclosure of the hardware and software needed to receive the statements and a way for the recipient to withdraw consent. Absent that recorded consent, the default delivery method is paper. For a firm, the cleanest approach is to treat e-delivery as a client-by-client decision with the consent record held against each recipient, so a single client's choice never bleeds across your book.

Where the responsibilities sit

Think of it as three layers. Your firm holds the TCC, the engagement authorization, and the transmission. Your client holds the W-9s, the accuracy of the underlying data, and the recipient relationship. The recipient holds their own consent to electronic delivery. None of these collapses into another, and the audit trail is strongest when each layer's record is kept where it belongs.

TIN Matching: The Cheapest Insurance a Firm Can Buy

Across a book of clients, the error that compounds fastest is a recipient name and TIN that do not agree with IRS records. IRIS validates the recipient's name and TIN against the IRS database during processing, and a mismatch can turn into a rejected record or, after filing, a B-notice and 24% backup withholding exposure. Because the penalty for incorrect information returns applies per return, a single bad TIN repeated across a client's vendor list can become real money in a hurry.

The defense is the IRS TIN Matching program, a separate e-Services service described in Publication 2108-A that lets an authorized payer check a name, TIN, and TIN-type combination against IRS records before filing. The enrollment fits a firm naturally: every user needs an ID.me account to reach e-Services, after which the firm's Principal — a partner, an owner of at least five percent of the firm, or a corporate officer — completes the Application to TIN Match and assigns roles such as Responsible Official and authorized agent to the staff who will run checks. Because the identity proofing overlaps with what your team already did for the TCC, enrolling in the same pass is far easier than coming back to it under deadline.

Run the checks early in the season, before you build returns, and a mismatch becomes a phone call to the client rather than a rejection in the queue. That ordering — verify, then file — is the difference between a firm that closes the season clean and one that spends February chasing corrections.

The Deadline That Governs Your Whole Practice

For a firm, deadlines are not one date but a wave, and the steepest part of it is January 31. Form 1099-NEC is due to the IRS and to recipients on the same January 31 — there is no slack between the two, which means every client with nonemployee compensation lands on you at once. Most other 1099-series forms split the timing: recipient copies are generally due January 31, while the electronic filing deadline to the IRS is March 31. Any deadline that falls on a weekend or federal holiday shifts to the next business day.

FormRecipient copyE-file to IRS
1099-NECJanuary 31January 31
1099-MISCJanuary 31March 31
1099-INT / DIV / RJanuary 31March 31
1099-KJanuary 31March 31
1098, W-2G, 5498January 31 (5498 differs)March 31

The firm-level consequence is that 1099-NEC compresses your hardest work into the same window across every client, so the realistic planning move is to treat NEC as its own project finished ahead of the rest. For the complete, form-by-form calendar including extension options, see our 1099 filing deadlines breakdown; the persona point here is that one late client is one penalty exposure, and a firm carries that risk fifty times over.

The deadline that governs a practice isn't a client's deadline — it's the day your firm has to start, so the TCC clears and every client's NEC is built and verified before January 31 arrives all at once.— &mdash; e1099f compliance desk
Count backward from January 31

If your firm does not yet hold an IRIS TCC, remember the suitability review can run well past a month before a code is issued — Publication 5717 tells filers not to contact the Help Desk until an application has been pending more than 45 days. Begin the application in the fourth quarter and it may not clear before the NEC deadline. Count backward from January 31, line up ID.me for the whole team first, and have a fallback ready if the runway is already tight.

Corrections When You Manage Many Originals

Corrections are where multi-client filing tests a firm's bookkeeping, because every correction has to be tied back to the exact original it fixes. IRIS, following the long-standing rules in Publication 1220, recognizes two kinds. A one-step (Type 1) correction fixes a return whose identifying information was right but whose money or codes were wrong — an incorrect dollar amount, for instance. A two-step (Type 2) correction is required when the identifying information itself was wrong, such as a wrong recipient TIN, name, or form type; it voids the original record and files a fresh, correct one in its place.

A handful of rules keep corrections from going sideways across a busy practice. If a return was originally filed electronically, its correction must also be filed electronically. A correction references the original submission so the IRS can link the two, which is why your firm needs to retain each client's original Receipt ID. You cannot correct a return that was rejected — a rejected return was never accepted, so you simply fix the data and resubmit it as a new original. And a corrected recipient copy, marked "CORRECTED," has to reach the recipient just as the original did.

For a firm, the discipline that makes all of this manageable is keeping originals, Receipt IDs, and client identity organized from the start, so that when a client surfaces a fix in March you can route it to the right original without guesswork. Our guide to filing corrections on IRIS covers the Type 1 versus Type 2 decision in full detail.

Common Rejection Reasons (and How to Avoid Them)

A firm's rejections cluster around a few causes, and each one is multiplied by the number of clients it touches. These are the ones worth engineering out of your process before the season, because a reject discovered in late January is a reject you have to fix while everything else is also due.

Client's legal name or EIN doesn't match IRS records most common

Cause: The business name and EIN you entered for a client — the issuer on that submission — do not match what the IRS has on file, which trips the issuer name/TIN validation. Fix: Collect each client's legal name and EIN exactly as the IRS issued them (from their EIN assignment notice), not a DBA or trade name, and store it once at the client level so every form you build for them inherits the correct identity.

You applied as Issuer instead of Transmitter

Cause: An Issuer-role TCC enforces the self-filer rule, so any return whose payer EIN differs from your firm's — that is, every client return — is rejected for the issuer/transmitter TIN mismatch. Fix: Apply for the Transmitter role for the practice. If you already hold an Issuer-only TCC, you will need to obtain the correct authorization before you can transmit for clients.

Recipient name and TIN don't match IRS records

Cause: A recipient's name and TIN fail the IRS database check during processing — the classic source of rejects and downstream B-notices. Fix: Run the recipient through IRS TIN Matching before you file, and resolve mismatches with the client (and a fresh W-9) rather than transmitting and hoping.

Duplicate returns within a client's submission

Cause: The same recipient TIN appears more than once in a client's submission without a unique account number to distinguish the records, so the duplicate is rejected. Fix: Assign a unique recipient account number when a payer legitimately has two returns for the same TIN, and de-duplicate your import so a client's vendor isn't loaded twice by accident.

Mixed content in one submission

Cause: A submission mixes form types, tax years, or originals with corrections — combinations IRIS will not accept in a single block. Fix: Keep each submission to one client, one form type, one tax year, and one kind of work (originals, or one correction type), which is exactly how a compliant filing tool segments the batch for you.

When the Calendar Won't Wait

Everything to this point is the firm-direct path: your own Transmitter TCC, your own authorization records, your own grouping discipline across every client. It is entirely doable, and many practices run it well. But if you are reading this in the fourth quarter without an approved TCC, the suitability review alone can outrun your January 31 deadline — and that is the moment to know there is a faster compliant route.

Filing for every client, with the clock running?

e1099f files under its own IRIS TCC and A2A connection, so your firm can onboard clients and file today — no application, no suitability wait, no keys to manage.

See how it works

Run the Whole Book From One Place: The e1099f Advantage

For firms that would rather not stand up and maintain their own transmitter infrastructure, filing through an authorized provider that already holds an IRIS TCC removes the application, the wait, and the per-client plumbing while keeping you in control of the engagement.

Every client, one login

Manage all your payers in a single workspace and file each client's returns without juggling separate codes or logins.

Validation before you send

Recipient and issuer data are checked against the IRS rules up front, so you get a Receipt ID back instead of a reject to chase across clients.

Corrections kept straight

Originals, Receipt IDs, and corrections stay linked per client, so a March fix routes to the right return without detective work.

One Transmitter relationship, CF/SF where states participate, and your whole client roster filed from a single place.

Frequently Asked Questions

Do I need a separate TCC for each client?
No. A firm files for many clients under one Transmitter Control Code tied to its own EIN, as long as it requested the Transmitter role. Each client appears as an issuer inside your transmission rather than requiring its own code.
What's the difference between the Issuer and Transmitter roles?
An Issuer files returns for its own EIN; a Transmitter sends returns to the IRS on behalf of others. Firms need Transmitter — an Issuer-role TCC enforces a self-filer rule that requires the payer TIN to equal your own, which fails on every client return.
Can I reuse my FIRE TCC to file for clients on IRIS?
No. Publication 5717 states a TCC obtained for FIRE, AIR, or A2A cannot be used in IRIS, and there is no conversion path. You must submit a new IRIS Application for TCC through e-Services, as a Transmitter for your practice.
How does IRIS know I'm authorized to file for a client?
The authorization is the engagement — your client explicitly authorizing your firm to act as their transmitter for the relevant forms. There is no per-client filing with the IRS; you hold the documented authorization, and the W-9 obligation stays with the client as the payer.
Who is responsible for the W-9 &mdash; my firm or the client?
The client. Soliciting and retaining a valid W-9 from each recipient is the payer's obligation. Your firm relies on the client's representation that valid W-9s are on file, which your engagement should capture.
Can I file different form types for the same client in one batch?
Not in one submission. Each submission is one issuer (client) and one form type, so a client needing both 1099-NEC and 1099-INT generates two submissions — though a single transmission can carry them both.
Should the whole firm enroll in TIN Matching?
It's worth it. TIN Matching is a separate e-Services program (Pub 2108-A); the firm's Principal completes the application and assigns roles to staff. Running checks before you file turns mismatches into a client call instead of a reject.
What deadline matters most for a firm?
January 31. Form 1099-NEC is due to both the IRS and recipients that day with no slack, so every client's NEC lands at once. Most other forms give recipients a January 31 copy but allow March 31 for the e-file to the IRS.
How do corrections work when I manage many clients' originals?
Each correction links to its original, so retain every client's Receipt ID. Use a one-step (Type 1) correction for wrong amounts or codes, and a two-step (Type 2) for wrong identifying data like a TIN or name, which voids and replaces the record.
Can I correct a return the IRS rejected?
No. A rejected return was never accepted, so there is nothing to correct — fix the underlying data and resubmit it as a new original. Corrections apply only to returns the IRS accepted.
Does my firm handle state filing too?
Where a recipient's state participates in Combined Federal/State Filing, the CF/SF indicator on the IRIS submission covers it; non-participating states require direct filing, and 1099-K is excluded from CF/SF. Multi-state clients are where this gets involved.
Do I have to understand any of this if I file through e1099f?
No. e1099f files under its own IRIS TCC and A2A connection and handles the transmitter structure, validation, and CF/SF routing, so your firm manages clients and data while the filing plumbing is handled for you.
DM
Dariel Montesino
Founder, e1099f · Reviewed by a licensed CPA

Dariel writes e1099f's coverage of the FIRE-to-IRIS migration for filers of every size, drawing on IRS Publications 5717–5719, 1220, and 2108-A and hands-on IRIS A2A integration work, including the multi-client transmitter structure described above.

Not tax advice. This guide is general information about IRS procedures for firms filing on behalf of clients and may change as the IRS updates IRIS. The official IRS publications linked above are authoritative; confirm current requirements there and consult a tax professional for your firm's situation.

File for every client in one place. Start free — no credit card.

One Transmitter relationship, your whole client roster, validated returns and CF/SF handled for you.

An unhandled error has occurred. Reload ×

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.