What Triggers a Part D Audit
Part D audits are not random. While CMS and Plan Sponsors do conduct routine audits as part of their oversight obligations, most pharmacy audits are triggered by specific patterns or anomalies detected through claims data analysis.
Common Audit Triggers
- High claim volume relative to peers - If your pharmacy submits significantly more Part D claims per beneficiary or per prescriber than comparable pharmacies in your area, it flags for review
- Unusual dispensing patterns - Disproportionate dispensing of certain drug categories, particularly high-cost medications, controlled substances, or specialty drugs
- High DAW (Dispense as Written) code usage - Excessive use of DAW-1 (physician-directed brand dispensing) when generic alternatives are available, resulting in higher reimbursement
- Frequent prior authorization overrides - Patterns suggesting that prior authorization requirements are being circumvented
- Patient geographic outliers - Serving a high percentage of patients from outside your normal service area
- Prescriber concentration - An unusually high percentage of prescriptions coming from a single prescriber or small group of prescribers
- Refill patterns - Early refills, consistent maximum-quantity dispensing, or refill rates that exceed expected adherence patterns
- Complaints or tips - Beneficiary complaints, competitor tips, or whistleblower reports
Understanding these triggers is not about gaming the system - it is about recognizing what puts your pharmacy on the radar and ensuring your documentation supports the legitimate clinical and business reasons behind your dispensing patterns.
Documentation Requirements
The single most important factor in a Part D audit is documentation. If you dispensed it and billed for it, you must be able to prove it. Here is what auditors will request:
Prescription Records
- Original prescriptions (hard copies or electronic records) for every claim in the audit sample
- Prescriber information - name, address, DEA number, NPI, and signature
- Patient information - name, date of birth, address
- Drug information - name, strength, dosage form, quantity, directions for use, DAW code, and NDC
- Dates - date written, date filled, date dispensed
- Refill authorization - number of refills authorized and refill history
- Transfer records - if applicable, documentation of prescription transfers
Signature Logs
Signature logs are one of the most commonly deficient areas in Part D audits. CMS requires proof that the beneficiary (or their authorized representative) received the medication. Your signature log must include:
- Patient or representative signature (not just initials)
- Date of pickup or delivery
- Prescription number or other identifier linking the signature to the specific claim
- For delivery prescriptions - proof of delivery documentation (carrier tracking with delivery confirmation, or delivery log signed by patient/representative)
Common signature log failures:
- Missing signatures for specific claims in the audit sample
- Signatures that cannot be linked to specific prescriptions
- Illegible signatures without corresponding printed names
- Missing delivery confirmation for mailed prescriptions
- Using initials instead of full signatures
Prior Authorization Documentation
For medications requiring prior authorization under the Part D formulary:
- PA approval records from the Plan Sponsor, including effective dates and duration
- Clinical documentation supporting the PA request (diagnosis, prior therapy failures, etc.)
- Emergency/urgent fill documentation if dispensed before PA was obtained, including evidence that the pharmacy sought retroactive approval within required timeframes
DAW Code Documentation
If you billed using DAW-1 (substitution not allowed - prescriber directive), you must have documentation that the prescriber specifically directed brand dispensing. This typically means:
- A written notation on the prescription (e.g., "Brand Medically Necessary" or "DAW")
- The prescriber's signature on the DAW line (for states using two-signature-line prescription forms)
- Electronic prescription with a "Do Not Substitute" or equivalent flag
- Documentation of verbal communication with the prescriber directing brand dispensing (with date, time, and name of person who communicated)
DAW code discrepancies are among the most common findings in Part D audits because auditors verify that the DAW code billed matches the documentation on the prescription.
Coordination of Benefits (COB) Records
When a patient has other insurance in addition to Medicare Part D, proper coordination of benefits documentation is required:
- Other insurance information on file for the patient
- Evidence that other insurance was billed first (primary claim submission records)
- Explanation of Benefits (EOB) from the primary insurer
- Documentation that Part D was billed correctly as the secondary or tertiary payer
COB errors can result in overpayment findings when the audit reveals that another insurer should have been the primary payer.
Responding to an Audit Notification
When you receive an audit notification, the clock starts immediately. Here is the step-by-step response protocol:
Step 1 - Read the Notification Carefully
Identify the Plan Sponsor conducting the audit, the audit type (desk or on-site), the time period covered, the claims sample, and the response deadline. Most desk audits provide 10-30 business days to submit documentation.
Step 2 - Organize Your Response Team
Designate a point person (typically the PIC or compliance officer) to manage the audit response. If the audit involves a large sample or complex issues, consider engaging a pharmacy consultant or attorney experienced in PBM audits.
Step 3 - Pull All Documentation for the Sample Claims
Gather prescriptions, signature logs, PA documentation, and any supporting records for every claim in the audit sample. Organize them by claim number or prescription number in the order listed in the audit notification.
Step 4 - Conduct a Pre-Submission Review
Before sending documentation to the auditor, review it yourself. Identify any claims where documentation is missing or weak. For those claims, determine whether supporting documentation exists elsewhere (e.g., electronic records, delivery carrier logs, prescriber confirmation).
Step 5 - Submit Documentation with a Cover Letter
Provide a professional cover letter summarizing what is enclosed, noting any claims where documentation may require explanation. Submit everything by the deadline - late submissions may be treated as non-responses, resulting in automatic recoupment.
Step 6 - Maintain Communication Records
Document every communication with the auditor, including dates, names, what was discussed, and any agreements made. If the auditor requests additional documentation, respond promptly and document the request and your response.
Handling Preliminary Audit Findings
After reviewing your documentation, the auditor will issue preliminary findings identifying any discrepancies. Common findings include:
- Missing signature - no proof of beneficiary receipt
- DAW code discrepancy - DAW-1 billed without prescriber documentation
- Quantity discrepancy - quantity billed differs from quantity documented
- No prescription on file - unable to locate the original prescription
- PA not documented - prior authorization required but not evidenced
- Refill too soon - refill dispensed before allowable refill date
- COB discrepancy - other insurance should have been billed primary
For each finding, you have the right to respond. Provide additional documentation or explanations for any findings you believe are incorrect. This is your first opportunity to reduce the scope of any recoupment.
The Appeals Process
If you disagree with the final audit findings after your initial response, most PBM contracts include an appeals process:
Level 1 - Informal Dispute Resolution
Submit a written appeal to the Plan Sponsor with supporting documentation and a detailed explanation of why you disagree with each finding. This is typically due within 30-60 days of receiving final findings.
Level 2 - Formal Appeal
If the informal appeal is denied, a formal appeal process may be available, sometimes involving an independent review panel. Review your PBM contract for specific appeal procedures and timelines.
CMS Involvement
In rare cases where you believe the Plan Sponsor's audit process was fundamentally unfair or the findings are clearly erroneous, you can raise the issue with CMS through the Complaint Tracking Module (CTM) or by contacting the CMS Part D Audit Team directly.
When to Involve Legal Counsel
Consider engaging an attorney if:
- The recoupment amount exceeds $25,000
- The findings allege fraud rather than documentation deficiencies
- The audit appears to be a precursor to network termination
- You believe the auditor's methodology was flawed (e.g., using an inappropriate extrapolation formula)
Building an Audit-Ready Pharmacy
The best audit strategy is preparation long before the notification arrives. Here are the practices that make a pharmacy audit-ready:
Signature logs: Implement a robust signature collection process. Every pickup and delivery must have a linked signature. Audit your own signature logs monthly to identify and correct gaps.
Prescription filing: Maintain organized prescription files that can be retrieved quickly. If you use electronic records, ensure they are backed up and printable.
DAW documentation: Never bill DAW-1 without clear prescriber documentation on file. When in doubt, bill DAW-0.
PA records: File all prior authorization approvals with the corresponding prescriptions. Track PA expiration dates and renew proactively.
COB verification: Verify patient insurance information regularly. Run COB checks at point of sale and document the results.
Self-audits: Conduct internal audits of your claims data quarterly. Look at the same patterns that trigger external audits - DAW usage, high-cost drug dispensing, refill patterns, and prescriber concentration. If you find anomalies, investigate and document the legitimate reasons.
For a broader perspective on PBM audit preparation, see our guide on Understanding PBM Audits. Audit preparedness also ties directly into your FWA compliance obligations, since audit findings can trigger FWA investigations if patterns suggest intentional misconduct rather than documentation lapses.
