CMS corrects two October EDI spreadsheet errors, with October 1 applicability and October 5 implementation
Sep 27, 2026 edition · GC-2026-0108 · Published 2026-09-27 · Version 2 · Final
The September 18 EDI transmittal replaces the August version to correct two 276/277 spreadsheet errors; systems implementation remains October 5.
What happened
CMS issued Transmittal 13967 on September 18 under CR 14429, rescinding the August 27 Transmittal 13934 to correct two typographical errors in the 276/277 Edits Spreadsheet. All other information remains the same. The October Combined Common Edits/Enhancements Module release covers Part A and Part B Medicare Administrative Contractors and the Common Electronic Data Interchange contractor. The instruction specifies October 1, 2026 effectiveness and October 5 implementation. These are distinct applicability and systems dates, rather than evidence that a provider or vendor has already deployed the update.
The instruction requires contractors and shared-system maintainers to use the attached replacement edit specifications and incorporate the updates without duplicating previously completed work. Its business requirements address test data and TA1 interchange acknowledgments, accepted, fully rejected and accepted-with-errors 999 acknowledgments, CCEM edits and the institutional and 276/277 flat-file layouts. The spreadsheet change log identifies current-version modifications within the cumulative edit record. For submitters and clearinghouses, the practical review is whether their vendors use this corrected September version and handle acknowledgments and claim-status transactions consistently with it.
Scope and timing
- Authority status
- Final
- Applicability
- Directly applicable
- Audience
- Health systems, Provider networks
- Jurisdiction
- Federal
- Affected functions
- Revenue Cycle, IT, Compliance, Finance
- Responsible owner
- Revenue Cycle
- Recorded date
- 2026-10-01
- Date type
- effective
Why it matters
A superseded specification can produce avoidable front-end rejections or inconsistent claim-status handling. Internal readiness targets should support October 1 applicability and the actual October 5 systems milestone.
Recommended action
Obtain the September 18 corrected specifications, verify the vendor version, and regression-test relevant 276/277, TA1 and 999 scenarios. Document October 1 applicability and October 5 implementation separately, with exception monitoring after release; do not infer deployment from a calendar target.
Implementation playbook
- Internal preparation target: obtain and verify the September 18 corrected 276/277 specifications; follow up if incomplete. Revenue Cycle · Due 2026-09-23
- Internal testing target: review regression results for corrected front-end and claim-status scenarios; do not infer completion. IT · Due 2026-09-27
- Confirm October 5 systems implementation and exception monitoring, keeping October 1 applicability separate. Revenue Cycle · Due 2026-10-05
Sources
- HIPAA Electronic Data Interchange Front End Updates for October 2026Official · Centers for Medicare and Medicaid Services · 2026-09-18 · Source review 2026-09-20
Complete edition and supplemental material
This finding in the complete approved report →Regulatory horizons, CIA trends and implementation trackers remain in the full report.
Read the entire Medicare & Medicaid report →