IRIS Portal vs A2A: Plan the Access You Need

Start with the final transmission action. Will an employee enter the IRS portal and submit, will your organization run software that connects directly, or will a third party transmit on your behalf? Writing down that distinction prevents confusion between the system where you prepare data and the system that actually sends it.

A vendor portal can still represent a provider transmission arrangement. Conversely, purchasing software does not by itself mean that the vendor takes responsibility for transmission under its own access. Ask which legal entity is the transmitter and which organization must complete the IRS access and testing steps.

List normal submissions, corrections, replacement handling, and acknowledgment retrieval as separate responsibilities. Include the forms and tax years you need. A workflow that supports the first original batch may still leave later follow-up work unassigned.

The portal and A2A distinctions come from the IRS channel overview; third-party responsibilities are discussed in Publication 5718, section 1.3.3. This matrix is an access-planning aid, not a claim that every product supports the same features.

The IRS portal accepts manual entry or its CSV format. Check the current guide and onscreen instructions for the specific upload, submission, and download limits; these are separate operations. A per-operation limit is not an annual ceiling on your organization. Publication 5717, processing year 2026.

Estimate the number of uploads, review sessions, and follow-up tasks your team would perform. Consider the variation between forms and payers, not just the return count. An orderly file with consistent source data can require different preparation from a smaller export with many exceptions.

Confirm individual access for the employees who will prepare, review, submit, and retrieve results. Identify an available person for each activity. Keep the account roster and the internal filing schedule aligned so that work does not depend on a single unavailable employee.

The IRS onboarding sequence includes an A2A TCC, API Client ID, schema package, and ATS transmissions. Assign each component to a named business or technical owner and record what evidence will show it is complete. IRS A2A setup steps.

Do not substitute a portal TCC for an A2A TCC. The assigned access must match the filing method. The IRS ATS guidance also distinguishes communication testing with transmitter access from software testing with Software Developer access.

Build the operational plan beyond sending one XML file. Decide how software retrieves acknowledgments, handles an unavailable service, prevents an unintended duplicate transmission, and routes rejected data for correction. These are engineering and workflow decisions to validate against the applicable IRS specifications.

Record the target processing year and the supported tax years. Use the schema release table to verify test and production effective dates rather than assuming they begin together.

Fictional example. A regional business has 80 straightforward returns for one filing cycle. Its team can prepare a reviewed CSV and has available portal users. Another organization processes 8,000 returns for multiple client businesses and already has a software team maintaining a recurring import pipeline.

The first team evaluates portal preparation and review time. The second evaluates direct A2A integration and provider transmission against the volume of recurring operations, including error follow-up. The counts are fictional planning inputs, not IRS eligibility thresholds or a recommendation to build software at a particular volume.

Suppose the larger organization selects a provider. It still asks who converts unusual source records, how corrections are supported, how receipt information is delivered, and what happens if the provider becomes unavailable. The access plan now assigns provider integration work to the provider and customer review work to the filing team.

For your selected arrangement, fill in the exact organization role, transmission method, access administrator, technical contact, and filing-outcome reviewer. Mark requirements confirmed by the provider or current IRS source separately from assumptions that need an answer.

For a provider arrangement, request the electronic submission records and final acknowledgment information described in Publication 5718. Agree on how your organization will retain the records necessary for future corrections. A dashboard summary alone may not answer a later record-specific question.

Close planning only when someone can explain the path from prepared data to the retained IRS outcome. Then begin the relevant application or implementation steps. Revisit the plan if you change providers, add forms, or start transmitting for additional businesses.