The brace shipped. The claim paid. Eighteen months later, the ADR arrived.
That is how most providers learn the difference between PDAC-approved and non-PDAC products not from a compliance guide, but from a letter demanding repayment on a claim they’d long stopped thinking about. PDAC-approved products carry a confirmed HCPCS code assignment verified by Medicare’s own coding contractor, Palmetto GBA. Non-PDAC products carry an L-code a supplier printed in a catalog. When CMS comes looking, those two things are not interchangeable and the provider who treated them as equivalent is the one writing the check.
This guide covers what PDAC approval actually confirms, the exact sequence of events when a non-PDAC claim gets flagged, and how to verify a product’s status before you order. If you’re starting from scratch on PDAC basics, begin with What Is PDAC Approval and Why It Matters before continuing here.
What PDAC Approval Actually Confirms (And What It Doesn't)
PDAC approval confirms one thing: a specific product SKU has been reviewed by Palmetto GBA and assigned the correct HCPCS or L-code for Medicare billing. The manufacturer submits the product. Palmetto GBA reviews it. If it passes, the product is listed in the DMEPOS Coding System (DMECS) with a confirmed code. That listing is what protects a provider when an auditor pulls the file.
What PDAC approval does not confirm: medical necessity, LCD compliance, prior authorization eligibility, or clinical appropriateness. Those are separate obligations. PDAC approval is purely about the product-to-code relationship — and for mandatory coding verification items, that relationship must be confirmed before a single claim goes out.
Mandatory coding verification applies to a defined list of DMEPOS items where CMS requires PDAC confirmation as a condition of reimbursement. L-coded orthotic braces — knee braces, spinal orthoses, ankle braces, wrist orthoses — fall into this category. For these items, billing without PDAC verification isn’t a judgment call. It’s a claim that will not survive a post-payment review.
Original Insight The SKU Trap
PDAC approval is product-specific, not category-specific. Two knee braces, same L-code, same price point, virtually identical packaging one has a confirmed PDAC listing in DMECS, one doesn’t. A provider ordering from a supplier catalog has no way to know the difference unless they run the exact model number through DMECS themselves. The L-code printed next to a product in a supplier’s catalog is the supplier’s representation of what that product should bill as. It is not a PDAC approval. Treating them as the same thing is the most expensive assumption in DME billing.
Before placing any order for a mandatory verification item, verify a product’s PDAC status before ordering using the DMECS tool at dmepdac.com.
The Non-PDAC Billing Sequence What Actually Happens
Most guides say “non-PDAC products carry claim denial risk” and stop there. That framing suggests the problem surfaces at submission — that Medicare kicks back the claim, you catch the error, and you move on. That is not what happens.
The damage from non-PDAC billing rarely happens at claim submission. It happens 12 to 24 months later, after the money is already in your account and the patient file has been archived.
Step 1 The Claim Pays (For Now)
Medicare’s automated claim processing doesn’t catch every non-PDAC product at submission. Certain front-end edits flag obvious mismatches, but post-payment review is where the majority of non-PDAC billing problems surface. A claim processes, pays, and sits in a paid status for months sometimes years before a review program touches it.
CMS Recovery Audit Contractors operate on a contingency fee model. They are paid a percentage of what they recover. That structure creates a direct financial incentive to look backward at paid claims, not just forward at new submissions. DME is consistently one of the highest-scrutiny categories in the RAC program.
Step 2 The ADR Letter Arrives
An Additional Documentation Request is CMS’s or a MAC’s formal demand for the complete file supporting a specific claim. For a non-PDAC product, the ADR will request: the Certificate of Medical Necessity or Detailed Written Order, delivery confirmation with beneficiary signature, proof of PDAC approval for the specific product billed, and full HCPCS code documentation.
That third item — proof of PDAC approval for the specific product is where non-PDAC billing ends. There is no document that can be produced for a product that was never submitted to Palmetto GBA.
ADRs can arrive up to three years after the date of service. The claim that paid in January 2025 can generate an ADR in late 2027. When the letter arrives, most providers assume the problem is in their clinical documentation. They pull the entire chart, organize the CMN, gather the delivery confirmation, and submit a thorough response only to receive a denial weeks later because the product itself was the issue the entire time.
Original Insight — The ADR Trap
The ADR does not tell you upfront which part of the file is deficient. Providers spend significant staff hours responding to documentation requests for a claim that was never going to survive review regardless of what they submitted.
Step 3 Denial and Post-Payment Recoupment
Not all denials are equal. A soft denial is rebillable — the provider corrects the error, resubmits, and the claim pays. Non-PDAC billing produces a hard recoupment. The product is the deficiency. There is nothing to correct and resubmit.
When CMS issues a post-payment recoupment demand, the mechanics are straightforward and unpleasant: future claim payments get offset until the recouped balance is fully recovered. The hit isn’t isolated to the flagged claim — it runs across your entire book of active claims until CMS is made whole.
Repeated non-PDAC billing escalates the exposure into different territory entirely. A pattern of billing Medicare for products that fail mandatory coding verification can trigger revocation of Medicare billing privileges, OIG referral, and False Claims Act exposure. FCA penalties currently run from $14,308 to $28,619 per false claim, plus treble damages. (Source: Department of Justice FCA annual penalty adjustments) One non-PDAC brace claim is an audit finding. A hundred of them across two years is a compliance investigation.
Step 4 The Appeal Window and What It Costs
Providers have 120 days from the denial notice to file a redetermination request the first level of the Medicare appeals process. For a legitimate non-PDAC denial, the appeal will almost certainly fail. The denial is based on the product itself. There is no clinical documentation, no signed CMN, and no corrected delivery confirmation that changes the underlying problem.
Even unsuccessful appeals generate real costs: staff hours, consultant or legal fees if the recoupment is large enough to warrant outside help, and cash flow disruption during the offset period. A single non-PDAC claim denied post-payment may involve a few hundred dollars in direct recoupment. The administrative cost of responding to it typically exceeds the claim value several times over.
The Supplier Accountability Gap Nobody Talks About
When a non-PDAC product ships under an L-code and gets flagged at audit, the recoupment demand goes to the provider’s NPI. Not the supplier’s.
The supplier sold you a product. You submitted the Medicare claim. CMS’s enforcement relationship is with the billing entity. A supplier who lists L-codes in their catalog without confirming PDAC status for each SKU is not violating a regulation they’re representing what they believe the code should be. The Medicare compliance obligation transfers entirely to whoever submits the claim. That is you.
This is the accountability gap most providers don’t fully grasp until the recoupment letter is in their hands. A supplier can list L1833 next to a knee brace, ship the product in good faith, and face zero consequence when that claim is denied. The provider who billed L1833 without verifying PDAC status absorbs everything: the recoupment, the appeal cost, the audit exposure, the billing privilege risk.
Original Insight — Supplier Liability
A supplier who cannot produce a PDAC approval letter for a specific SKU is not a documentation gap. It is a compliance risk sitting on your desk. The distinction matters because one can be fixed with a follow-up email. The other requires you to stop billing that product immediately.
A compliant supplier provides at minimum a PDAC approval letter specific to the SKU, the exact model number confirmed against the DMECS listing, and HCPCS code documentation at the order level. That paper trail is what survives an ADR.
PDAC-Approved vs Non-PDAC Supplier At a Glance
Feature |
PDAC-Approved Supplier |
Non-PDAC Supplier |
|---|---|---|
HCPCS Code Source
|
Verified by Palmetto GBA
|
Self-assigned by supplier
|
Approval Documentation
|
SKU-level letter available
|
None
|
Audit Liability
|
Shared via documentation trail
|
Transfers entirely to provider
|
Claim Denial Risk
|
Low (if billed correctly)
|
High
|
Post-Payment Recoupment
|
Rare
|
Likely if audited
|
RAC Scrutiny Level
|
Standard
|
Elevated
|
For a detailed look at what a PDAC-verified supplier relationship looks like in practice including how documentation flows from order placement through delivery confirmation our dropship program overview covers the full workflow.
How to Verify PDAC Status Before You Place an Order
Verification takes under five minutes. The DMECS tool at dmepdac.com is the authoritative source — maintained by Palmetto GBA and updated to reflect current approval status.
- Get the exact model number. Not the brand name. Not the product category. Not the L-code the supplier listed in their catalog. The specific model number for the specific SKU you are ordering. If a supplier cannot provide a model number that appears in DMECS, that is your answer.
- Run the model number in DMECS. Navigate to the Product Classification List, search by model number, and read the full results table. Confirm the product is listed and note the exact HCPCS code assigned.
- Match the DMECS code to your billing code. The code in DMECS must match the code your billing team plans to submit. A mismatch — a product listed under L1832 being billed as L1833 — is a miscoding finding waiting to happen. Take a dated screenshot of the result and keep it in the claim file. That screenshot is your documentation if an ADR arrives two years from now.
When a product doesn’t appear in DMECS at all, treat it as non-PDAC until the manufacturer provides written confirmation otherwise. Not a verbal assurance. Not an email from a sales rep. Written confirmation on letterhead, specific to the model number in question.
For a complete full DMECS walkthrough — including how to interpret results and what to do when codes don’t match — our PDAC verification guide covers every step. The L1852 knee brace billing guide includes a worked verification example showing what a confirmed DMECS result looks like for a specific SKU.
Is It Ever Acceptable to Bill a Non-PDAC Product to Medicare?
There is one narrow exception. Custom-fabricated items made directly from raw materials not prefabricated, not assembled from components, fabricated from scratch for a specific patient fall outside the mandatory PDAC verification requirement. Certain truly custom orthoses qualify. Per CMS guidance and Noridian’s published policy, manufacturers of these items are not required to appear in DMECS to support a valid claim.
This exception does not apply to prefabricated braces, standard orthoses, or any product that ships in a box from a supplier’s warehouse. If you are ordering from a catalog, mandatory coding verification applies to all L-coded items.
The practical rule: if it ships in a box, it needs PDAC verification. No exceptions.
Who This Is Built For
This is the right fit if:
- You are a licensed DME provider or actively in the process of obtaining your license
- You want to offer PDAC-approved orthopedic braces or ambulatory aids without managing inventory
- You are billing Medicare for L-coded products and need a supplier whose documentation holds up when an ADR arrives
This is not the right fit if:
- You are looking to sell DME products on Amazon or Shopify
- You do not have — and are not pursuing — a DME license
- You are looking for wholesale pricing to stock your own warehouse inventory
FAQ: PDAC Approved vs Non-PDAC
The claim may initially pay, but it is highly vulnerable to post-payment review. If flagged in an ADR or RAC audit, the claim will be denied and CMS will issue a recoupment demand money already paid to you gets offset against future claims. For L-coded items subject to mandatory coding verification, there is no corrective resubmission option. The product itself is the deficiency, and no amount of clinical documentation corrects it.
No. Mandatory coding verification applies to a specific list of DMEPOS items primarily L-coded orthotic braces and other products identified in CMS LCDs. Items outside the mandatory verification list don't require PDAC confirmation for billing, though having it reduces audit exposure regardless of category. Check the current CMS mandatory verification list or your MAC's applicable LCD for the products you bill.
Use the DMECS tool at dmepdac.com. Search by the product's exact model number in the Product Classification List. Confirm the HCPCS code in the result matches the code you plan to bill. Save a dated screenshot as part of your claim file. Do not rely on supplier catalog codes as confirmation only a DMECS listing constitutes verified approval status.
Yes. Post-payment recoupment is a standard CMS enforcement mechanism for claims that fail review including non-PDAC billing. CMS offsets future claim payments until the balance is fully recovered. ADRs can arrive up to three years after the date of service, meaning a claim paid today can generate a recoupment demand years from now.
The provider. The Medicare compliance obligation sits with whoever submits the claim. A supplier listing an L-code in their catalog without PDAC confirmation creates compliance exposure for the billing provider, not for themselves. The recoupment demand, the OIG referral risk, and the False Claims Act exposure all attach to the billing NPI not the supplier's.
PDAC approved means a product has been formally reviewed by Palmetto GBA and listed in DMECS with a confirmed HCPCS code assignment. PDAC verified is sometimes used informally to mean a provider has confirmed a product's status in DMECS before billing but provider verification does not make a non-listed product approved. The product must appear in DMECS under its specific model number.
What Happens After You Contact Ava
- We verify your DME license and NPI — one business day
- We onboard your practice to our ordering portal — two to three business days
- You place your first order — we ship direct to your patient with full documentation included
No minimum orders. One unit or one hundred — the process and documentation are identical.
No long-term contracts. Partner status is not tied to monthly volume commitments.
PDAC documentation included at SKU level with every product. Not a category-level assurance — a product-specific approval confirmation for the exact model number you ordered. If an ADR arrives, the file is already built.
Ready to Bill Medicare With Confidence?
If you are a licensed DME provider who bills L-coded braces and needs a supplier whose documentation actually holds up when an ADR arrives Ava Medical Supply was built for exactly this.
Every product in our catalog is PDAC-approved at the SKU level. Every order ships with the documentation your billing team needs: PDAC approval confirmation, HCPCS code assignment, and delivery confirmation formatted for Medicare audit review. The file is built before the claim goes out not assembled in a panic when the ADR arrives.
