CMS’s October DMEPOS Update Has Two Dates—and Seven Codes to Check

CMS issued its October 2026 DMEPOS fee schedule transmittal on September 29, just two days before the new date-of-service period begins. The notice names October 1 as the effective date and October 5 as the contractor implementation date. Those dates describe different parts of the change: the updated payment data are to be used for items with dates of service beginning October 1, while October 5 is the implementation date CMS assigns to the contractor instruction.

The practical question for a DME supplier is which schedule, code table, and ZIP data its billing path will apply to each claim. The notice lists specific additions and deletions, but it does not publish the October payment amounts in the transmittal itself. The CMS public fee-schedule index I checked still listed July 2026 as its newest 2026 file.

October 2026 DMEPOS Fee Schedule Update: Keep the Date and the System Change Separate

CMS says contractors must use the revised payment data for claims with dates of service beginning October 1. It separately labels October 5 as the implementation date for the contractor instruction. For claims around the cutover, ask the DME MAC or billing vendor how its system handles October 1–4 dates of service and which production schedule version it will use. Do not change a claim’s date of service to match a system-load date.

The quarterly update covers the DMEPOS fee schedule, the fourth-quarter rural ZIP code file, former competitive bidding area fee schedules, the former mail-order diabetic testing supply fee schedule, and former competitive bidding area ZIP codes. CMS says there is no update to the Parenteral and Enteral Nutrition fee schedule this quarter.

Seven HCPCS Additions Do Not Mean Seven New Fee Amounts

The transmittal lists seven HCPCS codes to add effective October 1: A4228, A6614, E0788, E2403, L1330, L1972, and L8697. A separate list names six codes receiving fee-schedule amounts: A4228, A6614, E0150, E0788, E2403, and L1972. E0150 appears on the amount list but not on the addition list, so the two lists should not be treated as interchangeable.

CMS also says L8696 is deleted from the DMEPOS fee schedule effective September 30. That statement concerns the fee-schedule file. A number that looks related to an added code is not enough to establish a one-for-one replacement or a clinical coding instruction. Have a qualified coding reviewer check the official file and applicable supplier guidance before changing code mappings.

Check the File That Will Price the Claim

Before the first October claim, compare the official update with the schedule version in the billing system and any vendor or clearinghouse tables that affect pricing. Confirm the effective date is attached to the date of service, then review the payment category, jurisdiction, and rural ZIP handling for the items the supplier actually bills. Keep the July file and the October file separately labeled so a rate question can be traced to the version used.

For an organization that orders DME but does not bill as the supplier, confirm who owns the code and fee-schedule check and how complete orders and supporting records reach that supplier. A code’s presence in a file does not by itself establish coverage, medical necessity, or payment.

A Short Cutover Checklist

This update is narrow enough to verify against a supplier’s own inventory. Start with the codes and items that are actually present in its claims, then trace those rows from CMS’s file through the system that prices and submits the claim.

• Ask the DME billing vendor or MAC which October production file and effective-date rule it will use.
• Compare the seven additions and the September 30 deletion with the codes and items the supplier handles.
• Review the separate fee-amount list; do not assume it matches the addition list.
• Test representative September 30 and October 1 dates of service, including any relevant rural ZIP or former bidding-area pricing.
• Track early payment differences by date of service, code, jurisdiction, and adjustment reason before changing a mapping.