CMS Updated the October 2026 HCPCS File Again. Check the Version Your Claims Will Use.

The October 2026 HCPCS September 23 update creates a simple question for every independent practice preparing for October 1: which version of the official file is actually in the billing system? CMS's quarterly update page now labels the October 2026 Alpha-Numeric HCPCS File as updated September 23, 2026. The page itself was last modified that morning. An earlier downloaded file may still be sitting in a vendor queue, chargemaster, clearinghouse rule set, or test environment.

The published date is evidence of a newer file, not evidence that every practice bills an affected code. CMS's page does not describe the September 23 differences in its public summary. A practice should compare the two files and its own charge inventory before claiming a specific code-level impact. Our earlier October 2026 HCPCS overview covered the September 10 correction; this check addresses the later file version.

October 2026 HCPCS September 23 Update: Identify the File in Production

Start at the CMS quarterly update page and record the official file name, download date, and the September 23 update label. Ask the EHR, practice management system, and clearinghouse which source file each one loaded, when it was loaded, and when it will become active. A vendor statement that the October codes are ready does not identify the version.

If the practice retained an earlier October download, preserve both ZIP files. Compare the contained files by name and checksum, then compare relevant code records. If the earlier file was not retained, record that limit and compare the current CMS release with the system's exported code table instead. Do not infer the size or clinical meaning of the update from the ZIP filename alone.

Test the Codes the Practice Actually Bills

Pull recent claim and charge data for the HCPCS Level II codes the practice uses. Include templates, order sets, recurring services, and any codes configured in claim edits even if no recent claim used them. Join that inventory to the current CMS file. Route missing, added, deleted, or changed records to a qualified coder for review with the official file and applicable payer rules.

Test representative October 1 and September 30 dates of service. The purpose is to catch a rule that activates a day early, stays active a day late, or differs between the claim generator and clearinghouse. A code's presence in the CMS file does not by itself establish coverage, medical necessity, documentation support, or payment. Those are separate checks.

Keep a Small Cutover Record

One accountable version record is more useful than an email saying the update was installed. It lets coding, billing, and vendor support trace a rejected claim to the source rule that produced it. VOSKPO can use a focused revenue review to map that trail and prioritize the claims with the greatest operational exposure.

• Record the CMS URL, file version label, download date, and a checksum for the file used in testing.
• Record the version and activation date reported by each vendor and internal system.
• List only the code records relevant to the practice, with a named reviewer and test outcome.
• Keep September 30 and October 1 claim examples free of patient identifiers in the shared cutover log.
• Monitor the first October rejections by code, payer, date of service, and edit reason before changing coding guidance.