ACA Filing Transmission: Why “We Filed” Isn’t Always the Same as “The IRS Received It”

Why "We Filed" and "The IRS Accepted It" Are Not the Same Thing

When an HR director or payroll administrator says "we filed our ACA returns," they usually mean: the forms were generated, the XML was created, the vendor marked the submission complete, or a receipt ID appeared in a dashboard somewhere. Any of those things might be true. None of them is what the IRS means by filing.

The IRS considers ACA filing complete when the transmission has been received, the file has passed schema validation, the IRS has issued an acknowledgement confirming acceptance, and any errors flagged in that acknowledgement have been corrected. That is a substantially longer and more conditional process than most employers realize — and the gap between those two definitions is exactly where silent filing failures live.

Every year, employers who believed they had filed receive IRS Letter 5699 asking why their ACA returns appear to be missing.

How ACA E-Filing Actually Works

ACA information returns are submitted electronically through the IRS Affordable Care Act Information Returns system — AIR, commonly known as AIRS. The actual e-filing process has four distinct stages:

Stage 1 — File generation: The 1094-C and 1095-C data is compiled and formatted into an IRS-compliant XML file.

Stage 2 — Transmission: The XML file is uploaded to the AIR production environment. A transmission receipt ID is generated at this point. This is where many employers mistakenly believe filing is complete. It is not.

Stage 3 — Validation: AIR runs automated checks against the file. This process takes time — sometimes hours, sometimes longer for large submissions.

Stage 4 — Acknowledgement: AIR returns an acknowledgement file containing the final status: Accepted, Accepted with Errors, or Rejected. A filing is only complete when the transmission has been Accepted and any Accepted with Errors items have been corrected and confirmed.

Where ACA Filings Quietly Fail

The File Was Never Submitted to Production

The IRS operates two separate AIR environments: the Assurance Testing System (AATS) and the Production environment. AATS is a testing environment. A file accepted in AATS is not a filed return. Every year, employers and vendors confuse AATS success with completed filing, and the Production submission never happens.

The File Reached AIR but Was Rejected

AIR performs a binary schema validation on every submission. If the file fails — for any reason — it is rejected in its entirety. A rejected file has not been filed. The IRS has no record of it.

The File Stayed in "Processing" and Nobody Followed Up

Large submissions can remain in a processing state for extended periods. IRS guidance instructs filers to contact the AIR Help Desk if a transmission remains in Processing for more than approximately 48 hours.

The File Was "Accepted with Errors" and No One Finished the Job

This is the most common and most dangerous silent failure mode. "Accepted with Errors" does not mean filing is complete. It means the IRS accepted the transmission but flagged specific records that require correction — most frequently triggered by a name and TIN mismatch.

The File Was Rejected and Never Resubmitted

When AIR rejects a filing, a practical correction window exists — generally 60 days — to submit a corrected replacement file. An employer who submits a file, receives a rejection, never notices it, and takes no action has effectively not filed for that year.

The Three Types of Silent ACA Filing Failure

Transmission Failure. The file never successfully reached the IRS Production environment. This includes AATS-only submissions and files that failed at upload before AIR could process them. From the agency's perspective, no filing occurred.

Acceptance Failure. The file was transmitted to Production but was never accepted — either outright rejected or "Accepted with Errors" where the required corrections were never made. This category most naturally leads to Letter 5699 situations.

Compliance Failure. The file was accepted. The employer has an AIR acknowledgement showing Accepted status. But the data inside the accepted filing contains errors significant enough to create downstream penalty exposure. Passing AIR schema validation is not the same as passing ACA compliance validation. This is what leads to Letter 226-J — not Letter 5699.

What Actually Proves a Successful ACA Filing

For each EIN and tax year, a defensible ACA filing record should include all of the following: the Form 1094-C as filed; all Forms 1095-C as filed; a Production Receipt ID; the AIR acknowledgement file showing final filing status; the error report from any Accepted with Errors status and confirmation corrections were made; and a reconciliation confirming that accepted 1095-C record counts match the expected employee population.

What does not prove filing: a vendor dashboard screenshot showing "Submitted"; an internal system status showing "Complete"; or a Production Receipt ID without the corresponding acknowledgement.

Why Employers Usually Discover Filing Failures Too Late

Silent ACA filing failures are almost always discovered through IRS Letter 5699; through Letter 226-J proposing an ESRP assessment; through vendor transitions that expose the gap when a new vendor requests prior-year filing records; or through M&A diligence. In every one of these scenarios, the leverage window has already narrowed.

How to Audit Whether You Really Filed

The right question is not "Did we file?" It is "Can we prove the IRS accepted what we think we filed — and does that accepted data still support our compliance position?"

For each EIN and open tax year, a basic filing audit should answer: Was this filed in Production — not AATS? Do we have the AIR acknowledgement? What was the final acknowledgement status? Were all errors corrected and confirmed? Do the accepted counts reconcile to the expected employee population?

Key Takeaways