Introduction – What is Publication 5164-A?
IRS Publication 5164-A, along with its core counterpart Publication 5164, is the official IRS test package and operational roadmap for the electronic filing of Affordable Care Act (ACA) information returns. It provides the technical criteria, sample test scenarios, and validation rules required to communicate with the IRS Affordable Care Act Information Returns (AIR) system.
The IRS issued its comprehensive updates for this series with a revision date of July 2026, officially posted to IRS.gov on September 18, 2026. This release establishes the required test protocols for Tax Year 2026 data submitted during the 2027 filing season through the ACA Assurance Testing System (AATS). It ensures that software developers, commercial transmitters, and direct-filing employers can transmit health coverage records without digital errors.
While the publication carries technical depth, its primary goal is simple: to make sure the computer systems handling your health coverage records talk cleanly to the IRS before the real tax filing season begins.
Who Should Read This Publication
Publication 5164-A is written specifically for technical teams and organizational filers rather than individual employees. If you are responsible for building software or delivering ACA data directly to the federal government, this publication is essential reading.
- Software Developers: Programmers and software vendors building tax preparation, payroll, and benefits software that must generate and validate ACA XML transmissions.
- Commercial Transmitters: Third-party service bureaus and payroll providers that electronically transmit health insurance data to the IRS on behalf of client businesses.
- Applicable Large Employers (ALEs) Filing In-House: Large businesses that choose to transmit their own Forms 1094-C and 1095-C directly to the IRS rather than hiring an outside service.
- Health Insurance Issuers and Plan Sponsors: Insurance carriers and administrators of self-insured group health plans responsible for reporting minimum essential coverage.
Key Topics Covered
The publication serves as a comprehensive testing manual. It outlines each checkpoint an organization must pass before receiving authorization to submit live tax returns.
- The ACA Assurance Testing System (AATS): How the staging and pre-production testing environment functions.
- Test Return Composition: Rules for constructing test submissions using Extensible Markup Language (XML) formatting.
- Predefined and Criteria-Based Scenarios: Step-by-step sample data packages designed to test various employee health insurance situations.
- Transmitter Communication Testing: Requirements for verifying connectivity, authentication certificates, and digital handshake protocols.
- Error Codes and Acknowledgments: How to read receipt status messages, validate accepted submissions, and resolve rejected test files.
Detailed Breakdown of Main Concepts
To navigate Publication 5164-A smoothly, it helps to understand the key concepts and systems that form the foundation of electronic ACA filing.
AATS vs. Production AIR Environment
The IRS separates ACA filing into two distinct digital environments. The ACA Information Returns (AIR) production system processes real, legally binding returns. In contrast, the ACA Assurance Testing System (AATS) is a secure virtual sandbox where developers and transmitters test fake taxpayer records to verify formatting and transmission speed before touching the live environment.
Software Developers vs. Transmitters
The IRS enforces different testing obligations depending on your authorized role:
| Role | Primary Responsibility | AATS Testing Requirement |
|---|---|---|
| Software Developer | Creates software packages to generate ACA forms and XML files. | Must complete and pass specific IRS test scenarios annually for supported forms. |
| Transmitter / Reporting Entity | Sends data packages directly to the IRS via web services or user interfaces. | Must pass a one-time electronic communication test to verify digital connectivity. |
XML Schemas and Manifest Headers
ACA records cannot be uploaded as plain text files or standard spreadsheets. All returns must be formatted in XML, a standardized markup language that labels every piece of tax data clearly. Every transmission requires a manifest header containing Transmitter Control Code (TCC) details, followed by the actual form payload.
Practical Examples or Scenarios
Publication 5164-A outlines realistic scenarios that mimic common business arrangements. These scenarios allow filers to prove their systems can handle complex employment situations.
Scenario 1: Full-Time Employee with Continuous Offer
A software package is tested using a scenario featuring a full-time employee who received an offer of minimum value, affordable healthcare coverage from January 1 through December 31. The test verifies that Line 14 of Form 1095-C generates the correct offer code (such as Code 1A) and that Line 16 properly confirms the employee’s enrollment without triggering a schema fault.
Scenario 2: Mid-Year Hire with Dependent Coverage
Another test case examines an employee hired on June 15 who enrolled in coverage alongside a spouse and dependent children starting August 1. The software must correctly record non-covered months, populate monthly contribution amounts on Line 15, and include dependent identification details under Part III without formatting errors.
How This Publication Relates to Specific Forms
Publication 5164-A governs testing protocols for four primary ACA tax documents. Each form has a unique structure and specific business rules that must be verified in the testing suite.
- Form 1094-B (Transmittal of Health Coverage Information Returns): The cover sheet used by insurance issuers and small self-insured employers reporting coverage providers under Section 6055.
- Form 1095-B (Health Coverage): The individual statement showing which months an individual and their dependents maintained minimum essential coverage.
- Form 1094-C (Transmittal of Employer-Provided Health Insurance Offer and Coverage Information Returns): The summary transmittal filed by Applicable Large Employers (ALEs) under Section 6056 detailing full-time employee counts and aggregated group status.
- Form 1095-C (Employer-Provided Health Insurance Offer and Coverage): The statement issued by ALEs to full-time workers detailing the specifics of employer health benefit offers.
Noticeably absent from this package is Form 1095-A. That form is issued exclusively by the Health Insurance Marketplace and does not pass through employer AIR reporting pipelines.
Common Misunderstandings Clarified
Because Publication 5164-A deals with complex regulations, taxpayers and small business owners often develop misconceptions about its scope.
- Myth 1: Individual employees must fill out these forms. Employees do not complete or test these forms. Workers simply receive Form 1095-B or 1095-C in the mail or electronically for their personal records.
- Myth 2: Every employer who issues a 1095-C must read this publication. Most employers use third-party payroll or HR software vendors. The software vendor handles the AATS testing behind the scenes, meaning regular business operators rarely need to read Publication 5164-A directly.
- Myth 3: Testing in AATS is optional for software makers. Passing AATS testing is mandatory. The IRS will not issue production status or accept real filings from unverified software packages.
Why This Publication Matters for Taxpayers
Even though ordinary taxpayers never read Publication 5164-A, its strict testing protocols safeguard the integrity of the tax filing process. Electronic testing directly benefits everyday workers and filers in several ways.
First, it prevents erroneous reporting. When employer software is rigorously tested, workers receive accurate Form 1095-C records. This accuracy prevents accidental IRS discrepancies when claiming or reconciling the Premium Tax Credit on Form 8962.
Second, it speeds up processing. Clean XML data allows the IRS to verify coverage records automatically, minimizing delayed refunds, audit notices, and administrative headaches during tax season.
Frequently Asked Questions
What is the difference between Publication 5164 and Publication 5165?
Publication 5164 contains test cases, sample records, and scenario steps for the AATS environment. Publication 5165 serves as the wider technical specification manual explaining communication protocols, data security requirements, and production filing rules.
Do I need to repeat AATS testing every single year?
Software developers must complete testing annually for the tax years their software supports. Commercial transmitters and direct filers who only transmit valid data usually only need to pass a one-time communication test, unless their systems or role permissions undergo significant architectural changes.
What happens if a test return is rejected in AATS?
The AATS environment returns an XML acknowledgment file with specific error codes. Developers inspect these codes, correct their data schema or calculation rules, and resubmit the batch until all scenarios receive an accepted status.
What is the electronic filing threshold for ACA forms?
Businesses filing 10 or more information returns across common types (including W-2s, 1099s, and ACA 1095 forms) during a calendar year must file electronically. Paper filing is strictly limited to very small volume filers.
Conclusion
IRS Publication 5164-A and the updated Publication 5164 series remain cornerstones of modern tax administration. By establishing structured test scenarios and clear validation rules, the IRS ensures that millions of health insurance records move safely from employer payroll engines into federal tax databases without disruptions.
Whether you are a developer updating software code or a compliance professional reviewing filing readiness, following these guidelines guarantees reliable, compliant, and error-free ACA reporting.
