PACE Part D PDE Attestation and Reconciliation: The Signature Behind the Payment

PACE Part D reconciliation connects prescription drug event data, or PDE data, to an attestation that helps determine whether Medicare pays risk-sharing and reinsurance adjustments. If you work in pharmacy operations, for a pharmacy benefit manager or in PACE finance, you may know which costs changed, which errors remained and what management signed. The pharmacy transaction, the submitted field and the signed statement can tell different stories about the same drug spending.

This page follows PACE’s drug costs from the source transaction through PDE reporting, certification and payment reconciliation. The broader PACE risk-adjustment calculation follows diagnoses, frailty and monthly payment, while Part D adds its own bids, cost reporting and signed attestations. The connection matters when someone inside the organization knows the government received a different account from the one in the business’s records.

What Are the PACE PDE Zero Fields?

PACE requires zero in several PDE fields because participants have no drug cost sharing. Signed attestations certify the submitted information, including those zero fields. Other fields change with the participant’s coverage category or the drug’s service date.

CMS’s PDE layout and PACE reporting instructions, issued March 8, 2024, specify the following treatment. These distinctions connect what happened at the pharmacy to the amounts reported for Medicare payment.

TrOOP is the true out-of-pocket measure used in the drug benefit’s financing calculation. The NPP field makes the distinction especially clear: for Medicare-only PACE, it reports the difference between the participant’s zero cost sharing under the PACE benefit and what the participant would have paid under the defined standard benefit. A financing field can move even though the participant owes nothing at the pharmacy counter.

The layout also separates covered drug costs below and above the annual out-of-pocket threshold. Those costs include the ingredient cost, dispensing fee, sales tax and applicable vaccine administration or additional dispensing fee. Along with other fields, the split helps determine whether a manufacturer discount applies. Someone reviewing a pharmacy invoice and someone reviewing the PDE therefore need the same underlying costs assigned to the right part of the benefit.

How Do Pharmacy and PBM Inputs Reach the PACE PDE?

Pharmacy and PBM transactions reach Medicare through the PACE sponsor’s cost reporting and certifications. A pharmacy price concession affects the negotiated drug price, while a manufacturer’s rebate applied at the point of sale belongs in a different PDE field. CMS requires PACE to distinguish them.

The Pharmacy Price Concessions at POS field reports the maximum contingent payments or adjustments the organization could receive from a network pharmacy that would reduce what it pays for the drug. Estimated Remuneration at POS instead reports qualifying remuneration expected from a manufacturer or another non-pharmacy entity and applied to the negotiated price. That distinction gives a pharmacy contracting employee, a PBM analyst and the sponsor’s finance team different pieces of the same cost calculation.

PACE also submits separate drug bids for dual-eligible and Medicare-only enrollees. In the application for new PACE drug sponsors for contract year 2026, CMS describes the bid as the expected monthly cost of qualified prescription drug coverage on a standardized basis. Costs expected to be reimbursed through reinsurance are identified separately. The pricing component receives its own certification from a qualified actuary.

The resulting Part D payment has several parts, including direct subsidy, reinsurance, risk sharing, low-income subsidies and PACE-specific additions. The bid describes expected costs. PDE reporting and direct and indirect remuneration reporting supply the actual cost and remuneration information used in reconciliation. The evidence connecting a source record to government payment therefore extends beyond the pharmacy’s invoice to the sponsor’s submitted data and later adjustment.

CMS’s application also requires contractor agreements to identify the functions performed, reporting obligations, payment terms and access to records. It requires the sponsor to commit to ongoing monitoring of the contractor’s performance. Under those instructions, a right to watch is no promise to watch.

PACE has specific Part D waivers, and CMS can approve additional waivers to address conflicting or duplicative requirements or improve coordination of benefits. The application nevertheless expressly preserves the payment-data certifications. When we assess a concern about a contractor’s data, the organization’s actual agreement and applicable waiver belong beside the reporting instructions and the submission itself.

How Did the Redesign Change PACE Drug Reporting?

The Part D redesign changed which PACE payments count toward TrOOP and how manufacturer discounts enter the drug record. The final instructions for 2025 count supplemental benefits toward TrOOP and apply manufacturer discounts to low-income and non-low-income PACE participants. Those changes make the coverage category and service date consequential to the submitted fields.

The annual threshold for 2025 was $2,000, a financing threshold while PACE participants retained zero cost sharing. CMS also retained the dual-eligible cost-sharing addition at 2% of projected costs below the threshold. The participant’s bill and Medicare’s financing calculation answer different questions.

The final instructions for 2026 make selected-drug subsidy available to PACE and require it in bids and PDE records. Prospective subsidy amounts reconcile to actual reported subsidy costs. An insider who knows what the organization advanced at the pharmacy can help connect that amount to what the sponsor later reported.

CMS required the new layout for submissions beginning January 1, 2025, including records for older benefit years and service dates. An insider reviewing a correction needs the service date as well as the submission date to connect the reported amount to the applicable payment rule.

Who Signs PACE Part D Attestations?

For the annual attestations covering contract-year 2025 data, CMS required the CEO, CFO or COO to sign electronically in its Health Plan Management System. The August 10, 2026 instructions cover attestations for CMS payment data, plan-to-plan reconciliation payment data and the Detailed DIR Report, with a PACE exception for the last one explained below.

The CMS attestation memorandum ties that signature directly to payment. Its opening explains why an insider’s concern about the attested numbers matters:

The payment attestation certifies that PDE data, Summary DIR data and other information used to determine allowable reinsurance and risk corridor costs are accurate, complete and truthful. It also acknowledges that the information will be used to obtain federal reimbursement.

For bid certification, CMS permits the CEO, CFO or an authorized delegate who reports directly to one of those officers. The annual attestation memo names the CEO, CFO or COO. Bid certification and annual payment certification can therefore carry different signatures.

CMS calls for one attestation per parent organization, covering its applicable contracts together. The system uses the parent name in effect for the data year, which can differ from its current name. For a whistleblower concern, the important connection is between the contracts covered, the data certified and the person who knew about the disputed figures.

Does Zero DIR Exempt PACE From the Attestation?

Zero Summary DIR does not exempt a PACE organization from the PDE/DIR payment attestation for contract year 2025. CMS expressly includes PACE organizations that reported zero total dollars in the Summary Report. The separate Detailed DIR attestation has an exception for those PACE organizations.

The distinction follows what each document certifies. The payment attestation covers costs used for reimbursement, while Detailed DIR data support the branded prescription drug manufacturer fee calculation. Where the Detailed DIR attestation applies, the sponsor also attests that entities generating those data on its behalf certified their accuracy. An exception attached to one report cannot explain away a missing certification on another.

What Does the Known-Error Process Reconcile?

CMS’s known-error process connects an identified PDE problem to prior notice, an explanation and continuing correction. Under the attestation memo, a sponsor aware of an error or potential error may attach an explanation when it has already notified CMS and is working to rectify the problem. The attachment describes the error, its magnitude and the expected timing of its resolution.

That gives the insider’s knowledge a specific place in the payment record. What the data team identified, what management understood, what CMS was told and what was eventually corrected can be compared against the signed attestation. We examine those connections with you, including whether the correction reached the submitted data and the resulting payment adjustment.

The payment attestation also required sponsors to certify that they had processed the applicable retroactive adjustments. CMS specifically included payments to long-term care pharmacies and beneficiaries resulting from retroactive changes in low-income subsidy status. A drug record can therefore carry a later correction relevant to the certification even though the original service belongs to the prior year.

What Does PACE Plan-to-Plan Reconciliation Show?

PACE plan-to-plan reconciliation records show payments between Part D contracts, with amounts owed and amounts paid recorded separately. The memo requires PACE sponsors with an active plan in the covered year to submit the P2P worksheet and sign its attestation. Sponsors with no P2P activity still have a worksheet and attestation obligation.

The worksheet identifies the report from which each payment originated. Comparing that report with the actual payment connects the certified figures to the organization’s financial records.

CMS requires an explanation when amounts owed and paid differ. The instructions separately address activity between contracts under the same parent when the organization does not make internal P2P payments. Where the explanation promises a future payment, CMS requires an updated worksheet and attestation after payment occurs. That later record is where a promise to correct can be compared with what the organization actually did.

Which CY2026 RxHCC Calibration Does PACE Use?

PACE’s Part D risk adjustment for calendar year 2026 blends two calibrations that both carry the 2026 RxHCC model name. The CMS implementation memorandum distinguishes a 90% component calibrated on 2018 diagnoses and 2019 expenditures from a 10% component calibrated on 2022 diagnoses and 2023 expenditures.

Monthly Membership Reports and Model Output Reports show the components and diagnosis groupings used in the calculation. These connect the diagnosis inputs to the payment result.

This matters when a questioned diagnosis and a questioned drug cost appear in the same participant’s records. The risk model follows diagnosis inputs, while PDE reconciliation follows reported drug costs and the associated certifications. We trace each to its payment effect, keeping a clinical correction, an accepted data correction, a model output and a financial adjustment in their proper places.

What Records Show a PACE Part D Payment Effect?

A PACE Part D payment inquiry connects the pharmacy or PBM transaction to the sponsor’s submitted cost, certification and reconciliation result. The transaction shows the underlying charge or concession. The PDE and DIR records show what the sponsor reported, and the bid and allowable-cost information show how those amounts entered its request for Medicare money.

The signed attestation, any error attachment and the organization’s response to the problem connect the figures to knowledge inside the business. Accepted corrections, reconciliation outputs and actual adjustment records show what happened to the money. For a health care insider, the strongest account follows the same contract and reporting period across those records. If management knowingly leaves inflated costs in the payment calculation, Medicare and the taxpayers financing it carry the overpayment.

If you are considering reporting a PACE payment concern, we work through that connection with you. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. Our work starts with the costs, the representation and the decisions you know from inside the organization.

When You Know What the Attestation Left Out

If you know a PACE drug cost, DIR submission or signed attestation concealed a discrepancy, speak with our whistleblower experts about the numbers and who knew. We work beside you to build your strongest Part D whistleblower case and bring in healthcare fraud whistleblower lawyers who understand its reporting and reconciliation. We bring the expertise to pursue what you know happened inside.