The retirement of FIRE will create a predictable wave of vendor claims.

IRIS ready.

IRIS supported.

IRIS compliant.

IRIS enabled.

Those phrases may all be true.

They may also mean very different things.

One provider may supply software but leave transmission to the payer.

Another may transmit but offer limited correction support.

Another may handle the filing connection while accepting whatever data the payer sends.

Another may support the full process from provider-data cleanup through acknowledgment and correction.

For healthcare payers, choosing an IRIS filing partner should not begin with a logo on a compatibility page.

It should begin with a clear understanding of what the organization needs before, during, and after transmission.

Start by Defining the Problem

A payer may think it needs an IRIS connection.

Its actual needs may include:

• An IRIS TCC strategy
• A2A software
• Communication testing
• Provider-data cleanup
• TIN and legal-name validation
• W-9 collection
• Address correction
• File creation
• Transmission
• Status monitoring
• Error translation
• Corrections
• Replacements
• Recipient-copy support
• Filing evidence
• Audit documentation

A vendor that solves only one of those needs may still be useful.

The mistake is assuming it solves all of them.

Before evaluating partners, the payer should separate its requirements into:

Data preparation

Is the provider information accurate and complete?

Filing infrastructure

Can the returns be transmitted through IRIS?

Filing operations

Who monitors, corrects, documents, and reports the result?

A strong selection process evaluates all three.

Ask Who Actually Transmits the File

The IRS distinguishes among Issuers, Transmitters, and Software Developers.

A software company may provide the application while the payer remains the Issuer responsible for transmission.

A third-party Transmitter may send information directly to the IRS on behalf of multiple organizations.

A Software Developer may create the product but not perform the filing.

Those roles affect TCC requirements, communication testing, support responsibilities, and who can speak with the IRS about the transmission.

Ask the prospective partner:

• Are you the Software Developer, Transmitter, or both?
• Will our organization transmit?
• Which TCC will be used?
• Does our organization need its own TCC?
• Who completes communication testing?
• Who contacts the IRS Help Desk?
• Who receives the acknowledgment?

The answer should be specific.

“We support IRIS” is not a role.

Ask Which IRIS Capabilities Are Supported

The IRS warns that third-party software or transmitters may not support every capability, including corrections and replacements. Filers are responsible for confirming that the service meets their business needs.

Ask whether the partner supports:

• Original returns
• Corrections
• Replacements
• Prior-year returns
• Automatic extensions
• Combined Federal/State Filing
• Every required form type
• Accepted with Errors workflows
• Partially Accepted transmissions
• Recipient-copy processes
• Filing-history exports

A partner that can submit an original 1099 but cannot reliably support a later correction may leave the payer stranded at the moment support matters most.

Ask How Data Is Validated

A technically valid IRIS transmission can still contain poor provider information.

Ask whether the partner validates:

• TIN format
• TIN and legal-name combinations
• Provider addresses
• Required fields
• Duplicate records
• Payment totals
• Form type
• Schema requirements
• Business rules
• Source-system consistency
• W-9 information

Then ask what happens when an issue is found.

Does the partner return a spreadsheet?

Does it provide a portal?

Does it contact providers?

Does it validate returned W-9s?

Does it correct the source data?

Does it merely reject the row and hand the problem back?

The quality of the exception process often matters more than the quality of the sales demonstration.

Ask How Acknowledgments Are Handled

The payer should receive more than a confirmation email.

The IRS advises filers using third-party transmitters to obtain:

• Copies of electronic records submitted
• Receipt IDs
• Final acknowledgments
• Transmission statuses
• Detailed error information

These records are critical for future corrections, especially if the original transmitter becomes unavailable.

Ask the partner:

• How quickly will we receive the Receipt ID?
• Can we see Processing status?
• How are errors communicated?
• Can we download the final acknowledgment?
• Do we receive record-level identifiers?
• How long is filing history retained?
• Can we export it?
• What happens if our contract ends?

The payer should never be dependent on a vendor’s private database to prove that its returns were filed.

Ask How Errors Are Translated

IRIS errors may include technical references, schema details, form-specific rules, and record identifiers.

A useful partner should convert that information into operational language.

Instead of handing the payer an error code and wishing it luck, the provider should be able to explain:

• Which provider is affected
• Which field caused the issue
• What the issue means
• What source information is needed
• Whether the record needs correction or replacement
• What the payer must do
• What the partner will do
• When the filing can be resubmitted

This is especially important for organizations where finance, provider data, claims, and information technology have separate responsibilities.

Error translation is the bridge between the IRS system and the person who can actually fix the record.

Ask About Testing

For A2A, ask:

• Has the software passed IRIS ATS?
• Which tax year was tested?
• Which forms were tested?
• Are corrections tested?
• Is Combined Federal/State Filing tested?
• Who completes our communication test?
• Who provides test records?
• Who retains the Receipt ID?
• Who confirms the TCC moved to Production?
• What happens when a test fails?

The IRS requires communication testing for Transmitters and Issuers and more extensive testing for Software Developers.

Testing should be complete well before filing season.

A vendor should not be discovering its own production-readiness gaps while handling your live provider data.

Ask About Security

The partner may receive provider TINs, legal names, addresses, W-9s, payment information, recipient copies, filing files, acknowledgments, and correction records.

Ask about:

• Encryption
• Secure file transfer
• Data-storage location
• Access controls
• Employee permissions
• Security certifications
• Logging
• TIN masking
• Incident response
• Data retention
• Data deletion
• Backups
• Business continuity
• Subcontractors
• Client portal controls

Security should be demonstrated through documented controls and practices.

It should not depend on the phrase “bank-level security,” which has become the parsley garnish of technology marketing.

Ask About Support During Filing Season

Filing problems do not always arrive during a comfortable Tuesday afternoon.

Ask:

• What are support hours?
• Is support based in the United States?
• How are urgent issues escalated?
• Is there a phone tree?
• Will we reach someone who understands our account?
• What response time is committed?
• Who supports IRS Help Desk interactions?
• What happens during a system outage?
• Is after-hours support available?
• How are unresolved issues reported to leadership?

BASELoad emphasizes U.S.-based support, direct access to its team, and assistance from people familiar with the client’s process rather than an anonymous support queue.

During filing season, familiarity has operational value.

Ask Whether the Partner Understands Healthcare Provider Data

Provider tax data is not generic vendor data.

Healthcare payers deal with:

• Individual practitioners
• Group practices
• Facilities
• Professional associations
• Billing entities
• Multiple locations
• Multiple internal provider IDs
• Legacy records
• Network affiliations
• Claims-system variations
• TIN and legal-name complexity
• High provider turnover

A general-purpose filing provider may understand IRIS perfectly while understanding very little about why the payer’s provider file looks the way it does.

A partner with healthcare payer experience is more likely to recognize the difference between a simple formatting defect and a deeper provider-identity problem.

That distinction can prevent incorrect “fixes.”

Ask How the Partner Reduces Internal Work

A partner should not merely move work from one inbox to another.

Ask whether the service reduces:

• Manual provider research
• W-9 outreach
• Data entry
• Returned mail
• Spreadsheet handling
• Repeated exception review
• Year-end overtime
• Filing uncertainty
• Correction volume
• Dependence on one internal employee

BASELoad’s W-9 Corrections service includes provider outreach, portal tracking, TIN and legal-name validation, secure tax-data handling, and support designed to reduce the administrative burden on payer teams.

The right partner should improve the operating model, not simply add another portal to check.

Ask for Clear Responsibility Boundaries

Before signing, create a responsibility table covering:

• TCC application
• API Client ID
• Testing
• Data extraction
• Data cleanup
• File creation
• Approval
• Transmission
• Status retrieval
• Error resolution
• Corrections
• Replacements
• Recipient copies
• Record retention
• IRS communication
• Security incidents
• Filing completion report

Every line should show whether it belongs to the payer, partner, software provider, or another party.

Ambiguity is inexpensive during procurement.

It becomes very expensive during filing season.

Final Thoughts

Choosing an IRIS filing partner is not only a software decision.

It is a decision about data quality, filing responsibility, testing, corrections, security, evidence, support, and operational continuity.

Healthcare payers should look beyond whether the provider can connect to IRIS.

They should determine whether the partner can help the organization reach an accurate, accepted, traceable result without creating a new maze of manual work.

The strongest partner is not merely connected to the filing system.

It is connected to the reality of the payer’s data and operations.

BASELoad Can Help You Navigate the Complete IRIS Transition

BASELoad has worked with healthcare payers for more than 25 years, supporting provider-data matching, data optimization, system conversions, W-9 collection, and 1099 corrections. Its provider-tax services address TIN and legal-name mismatches, invalid addresses, incomplete W-9s, provider outreach, filing-data preparation, and the manual workload surrounding year-end reporting.

The transition to IRIS does not have to become another internal system project balanced on the shoulders of finance, claims, provider-data, and IT teams. BASELoad can help your organization prepare cleaner data, define a more reliable workflow, and approach the 2027 filing season with greater visibility and confidence.

Contact BASELoad to begin planning your FIRE to IRIS transition with a partner that already understands healthcare payer data.