Electronic PA Reform Is Live. The Compliance Gap It Created Is Not Being Talked About.

The CMS final rule implementing electronic prior authorization requirements for Medicare Advantage plans under the Improving Seniors' Timely Access to Care Act took effect in 2026. The law was real, the regulatory timeline was enforced, and Medicare Advantage plans are now technically required to support electronic prior authorization submission and real-time decision-making on standard PA requests. By most compliance measures, the rule is in effect. The PA landscape changed.

What the compliance metrics do not capture: the rule mandated that plans support electronic PA submission. It did not mandate interoperability, standardized data formats, or workflow integration with pharmacy management systems. Plans implemented ePA through proprietary portals, non-standardized submission interfaces, and plan-specific documentation requirements that differ from one another in ways that are technically compliant and operationally burdensome. Independent pharmacies are now required to submit PA electronically — through a different portal, with different required fields, on a different timeline — for every plan in their network that has implemented a proprietary ePA system. The administrative burden did not go away. It fragmented.

The compliance gap created by fragmented ePA implementation falls hardest on independent pharmacy. Large chain operators have centralized PA submission teams, technology infrastructure built around multi-portal workflows, and negotiating leverage to push for plan-level interface integration. An independent pharmacy with one or two pharmacists managing PA across a mixed payer panel is absorbing the full complexity of plan-specific ePA systems without the operational infrastructure to manage it efficiently.

The specific risk: PA submission errors — wrong portal, missing required field, incorrect medication coding for a specific plan's ePA taxonomy — produce PA denials that look identical to clinical denials in your remittance data. If your AR reconciliation does not distinguish between clinical PA denials and administrative submission errors, you are misreading your denial pattern and missing the correctable portion of your PA failure rate. A clinical denial requires an appeal with supporting documentation. An administrative submission error requires resubmission through the correct channel. Treating them identically — which is the default outcome when denial codes are not cross-referenced against submission method — means you are appealing cases that should be resubmitted and abandoning cases that could be corrected and paid.

The secondary risk: ePA timelines are legally defined. CMS requires plans to respond to standard PA requests within 72 hours and urgent requests within 24 hours. If your tracking system does not capture the submission timestamp and flag non-responsive requests for escalation, you are not enforcing the timeline rights you are entitled to under the rule. Plans that miss the response window are required to provide a reason. Most independent pharmacies are not collecting the data needed to document a timeline violation.

Two things to build into your PA workflow now. First, segment your PA denial log by plan and by denial reason code, and add a submission method field — portal name and submission timestamp. Run that report for the last 90 days and identify which plans have the highest denial rates and whether those denials cluster around specific submission steps. You are looking for the pattern that tells you whether your PA problem is clinical or operational. Second, document every ePA submission timestamp and every plan response date. For any PA that exceeds the CMS timeline without a documented response, that is a compliance filing waiting to be made — to your state insurance commissioner or directly to CMS. You are not required to absorb a timeline violation quietly. Most independent pharmacies do not know they can escalate it.


Medicaid Unwinding Created an AR Crisis. The Damage Is Landing Now.

The Medicaid continuous enrollment protection that kept beneficiaries enrolled throughout the COVID public health emergency ended in April 2023. States began redetermining Medicaid eligibility — the unwinding — on a rolling basis through 2023 and 2024. Tens of millions of beneficiaries underwent redetermination. A significant portion lost coverage, either because they no longer qualified or because they missed the administrative steps required to maintain enrollment. The process is largely complete in most states by mid-2026, but the financial aftershocks for independent pharmacies that serve Medicaid populations are not.

The specific mechanism: during the unwinding period, beneficiaries who lost Medicaid coverage frequently did not know their coverage had lapsed at the point of dispensing. Claims were submitted under terminated Medicaid coverage, adjudicated in real time against a coverage record that had not yet updated in the state eligibility system, and paid — or held in processing limbo — before the retroactive termination triggered a recoupment demand. By mid-2026, states are issuing retroactive recoupment notices to pharmacies for claims paid under coverage that was subsequently terminated, in some cases reaching back 12 to 18 months. The AR damage is the accumulated total of paid claims that are now being clawed back.

For independent pharmacies with a significant Medicaid patient panel — particularly those serving rural, low-income, or underinsured populations where Medicaid is a primary payer — the unwinding recoupment is a cash flow event, not just an AR adjustment. The recoupment mechanism in most state Medicaid programs works the same way as PBM audit recoupment: the state offsets the disputed amount against current remittances before the pharmacy has an opportunity to appeal. You receive a reduced remittance, a recoupment notice citing specific claim dates, and a limited window to respond.

The pharmacy's position in a retroactive Medicaid recoupment dispute is structurally weak but not without leverage. The core question in any retroactive recoupment dispute is whether the pharmacy had reason to know coverage had lapsed at the time of dispensing. If the state eligibility verification system confirmed coverage at the point of dispensing — and your dispensing records show a real-time eligibility check — the recoupment argument weakens substantially. States cannot expect pharmacies to be the last line of enforcement on eligibility data the state's own systems failed to update accurately in real time.

The secondary problem is the patient population itself. Medicaid beneficiaries who lost coverage during the unwinding — particularly those in states with complex redetermination processes — have a high rate of re-enrollment, often after a coverage gap of 30 to 90 days. Patients who are currently presenting at your pharmacy without active Medicaid coverage, and whose prior history with your dispensing system shows continuous Medicaid coverage, are a re-enrollment opportunity that is also a bad-debt prevention strategy. Connecting them to enrollment assistance now reduces future AR risk.

Two actions before the end of Q3. First, pull your Medicaid AR aging report and identify every claim that is more than 90 days old and tied to a beneficiary whose coverage status changed between January 2023 and December 2024. That is your unwinding exposure pool. For each claim, confirm whether you have a real-time eligibility verification record at the time of dispensing. Claims with documented point-of-service eligibility confirmation are your strongest recoupment defense. Claims without that documentation are your highest-risk AR. Second, contact your state Medicaid agency's pharmacy relations office and ask specifically whether your pharmacy has any pending or anticipated retroactive recoupment notices related to the unwinding period. Some states are issuing notices in batches; knowing you are in the next batch gives you time to prepare the appeal documentation before the remittance offset hits.


PBM Audit Defense Has a New Priority. DIR Fee Clawbacks Are the Mechanism. Here’s the Pattern.

PBM audit activity in 2026 has shifted in its targeting pattern. The audits that drove the largest recoupment totals in 2023 and 2024 were primarily documentation-based: missing prescription records, incomplete patient counseling documentation, pharmacist signature gaps on controlled substance fills. Those audits generated significant findings but also generated the most successful appeals, because documentation gaps are correctable and the underlying clinical legitimacy of the claims was rarely in dispute.

The audit pattern shifting in 2026 is different. PBMs are increasingly using performance-based network tier frameworks — the structures that replaced retrospective DIR clawbacks after the CMS point-of-sale rule took effect — to generate recoupment through a different pathway. Rather than audit individual claim documentation, PBMs are auditing pharmacy compliance with performance metric reporting requirements: patient adherence outreach documentation, medication therapy management session records, quality measure data submission, and the documentation trails required to substantiate performance tier placement. If those records are incomplete or absent, the pharmacy is reclassified to a lower performance tier retroactively, and the reimbursement differential between tiers is recouped.

The DIR fee clawback, as a post-dispensing financial mechanism, was regulated. The performance-tier reclassification that achieves the same economic outcome through a different pathway is operating in a less regulated space. CMS requires plans to apply DIR at the point of sale — it does not prohibit plan-level performance programs that result in lower reimbursement for pharmacies that do not meet metric thresholds. The distinction matters because the appeal pathway for a performance-tier reclassification is different from the appeal pathway for a traditional audit finding.

A traditional audit finding is disputed through the PBM's appeal process: you submit documentation, they review, they accept or reject. The regulatory framework for that process is relatively established. A performance-tier reclassification is typically governed by the network performance program terms — which are embedded in your provider manual, not your main agreement, and which may not have an appeal process at all beyond a general dispute resolution clause.

The pharmacies absorbing the largest performance-tier recoupment losses in 2026 are those that implemented the documentation workflows required by their network agreements — the actual claim documentation — but did not separately document the performance program compliance activities that are tracked on a different timeline and submitted through different channels. The audit is finding the gap between clinical documentation and performance documentation. The two are different record sets. Most independent pharmacies are managing one of them well and the other informally.

For every Part D plan and commercial PBM in your network, identify whether your current network agreement includes a performance-based reimbursement tier. If it does, locate the performance program terms — typically in the provider manual rather than the agreement itself — and confirm what documentation you are required to maintain to substantiate your tier placement. That documentation is your audit defense on the next performance reclassification review. If you do not have it, start building it now.

Second: request your current tier placement and the underlying metric scores from every performance-based plan in your network. You are entitled to this data. Most pharmacies do not request it until they receive a recoupment notice. Receiving it proactively tells you whether a reclassification is coming before the remittance offset arrives, and gives you time to build the documentation that supports an appeal if the scores are inaccurate. The metric is only as accurate as the data the PBM has. If the data is wrong, the appeal window is now — not after the money has been taken.