Types of PBM Audits
Desk Audits
Desk audits are the most common type. The PBM sends a letter requesting copies of documentation for a selected group of claims - typically 25 to 100 prescriptions. You have a defined response window (usually 10-14 business days) to submit copies of the requested records.
Desk audits are triggered by data patterns and are often the first step in a larger investigation. The PBM is looking at your documentation quality as much as the individual claims. A desk audit with clean results may end the matter; a desk audit with problems frequently escalates to an on-site audit.
On-Site Audits
On-site audits involve a PBM auditor physically visiting your pharmacy to review records, inventory, processes, and physical operations. These are more thorough, more disruptive, and more likely to result in significant findings. The auditor may review records beyond the initial scope if they identify concerns during the visit.
On-site audits typically include:
- Physical verification of inventory against recent dispensing records
- Review of prescription hard copies or electronic records
- Examination of signature logs
- Inspection of compounding areas and records (if applicable)
- Verification of pharmacist and technician licensing
Focused vs. Random Audits
Some audits are random - selected through statistical sampling with no particular suspicion of problems. Others are focused, triggered by specific concerns identified through claims data analysis. Focused audits are more serious because the PBM has already identified a potential issue and is looking for confirmation.
Common Audit Triggers
Understanding what triggers a PBM audit helps you avoid becoming a target. The most common triggers include:
Claims Volume Anomalies
Dispensing volumes significantly above your geographic peer average will attract attention. If your pharmacy processes 500 prescriptions per day in a market where comparable pharmacies process 200, the PBM will want to understand why. Legitimate explanations exist - high-volume locations, specialty populations, competitive pricing - but you need documentation to support them.
High-Cost Medications
Pharmacies with disproportionately high claims for expensive medications - particularly specialty drugs, compound medications, and high-cost generics - face increased audit scrutiny. If your compound claims represent an unusually high percentage of your total billing, expect attention.
DAW Code Utilization
Excessive use of DAW-1 (Dispense as Written - prescriber direction) codes, particularly for drugs with significant brand-to-generic price differentials, is a major trigger. Auditors will verify that every DAW-1 claim has a corresponding prescriber instruction on the physical prescription or in the electronic record.
Refill Patterns
Early refills, auto-refill programs that generate claims for medications patients are not actually using, and high refill volumes per prescription are all monitored. Some PBMs specifically flag pharmacies with high vacation supply or 90-day fill rates outside of mail-order programs.
Patient Complaint Data
When patients call their PBM to report that they did not receive a medication that was billed to their plan, that creates a direct audit trigger for the specific pharmacy and prescription.
Documentation Requirements
The Golden Rule
If your documentation does not support the claim as billed, the PBM will recoup. It does not matter whether you actually dispensed the medication correctly - if your records do not prove it, you lose. This is the single most important concept in PBM audit defense.
Signature Logs
Signature logs are the most frequently cited audit finding. Every prescription picked up by or delivered to a patient should have a corresponding signature with a date. Electronic signature capture through your point-of-sale system is ideal. Paper signature logs work but must be legible, dated, and match the dispensing record.
Common signature log problems:
- Missing signatures for delivered prescriptions
- Dates on signatures that do not match dispensing dates (raising questions about whether the medication was actually picked up)
- Illegible signatures that cannot be attributed to the patient or their representative
- Gaps in the signature log - missing pages or skipped entries
If you use a delivery service, implement a chain-of-custody documentation system that captures the recipient's signature, the date and time of delivery, and the prescription numbers delivered.
Prescription Hard Copies
For non-electronic prescriptions, maintain the original hard copy. For faxed prescriptions, ensure the fax copy is legible and properly filed. For phone prescriptions, document the pharmacist who took the call, the prescriber, the date, and the full prescription details.
For electronic prescriptions, ensure your system retains the complete electronic record, including the prescriber's digital signature and any annotations.
Compound Claims Documentation
Compound claims receive the most intense audit scrutiny. Every compound claim must be supported by:
- A valid prescription specifying the compound or its components
- A formulation record (master formula and individual compounding log)
- Documentation of each ingredient's NDC, lot number, expiration date, and quantity used
- Beyond-use dating based on USP standards
- Documentation of the compounding pharmacist
If you submit compound claims, your documentation must be immaculate. Compound claim recoupments are among the largest in the industry, and PBMs have dedicated teams focused on this area.
Usual and Customary Pricing
Under most PBM contracts, you must submit your usual and customary (U&C) price - the price you would charge a cash-paying customer. If your U&C price is lower than the contracted rate, the PBM pays the lower amount. But if an audit reveals that your actual cash prices differ from what you submitted as U&C, the PBM can recoup the difference on every affected claim.
Maintain a documented U&C pricing policy. If you offer discount programs, loyalty pricing, or sliding scale fees, understand how those interact with your U&C obligations under each PBM contract. This area has generated significant litigation, and the rules vary by PBM.
The Audit Response Process
When You Receive an Audit Letter
Do not panic, but do not delay. Note the response deadline immediately and work backward to create a preparation timeline. If the deadline is 14 business days away, you need to begin pulling records on day one.
Read the audit letter carefully. It will specify exactly which claims are being reviewed and what documentation is requested. Provide exactly what is requested - no more, no less. Volunteering additional information can open new areas of inquiry.
Organizing Your Response
For each claim under review, compile a complete documentation package:
- Copy of the prescription (hard copy, fax, or electronic record)
- Dispensing record from your pharmacy management system
- Signature log entry with matching date
- Any supporting documentation (compound logs, DAW justification, prior authorization records)
Make copies of everything you submit. If this is a desk audit, send your response via tracked delivery with signature confirmation. Maintain a complete copy of your submission.
Working With Your PSAO
If you are a member of a Pharmacy Services Administrative Organization (PSAO), contact them immediately upon receiving an audit notice. Many PSAOs provide audit support services, including review of your documentation before submission and assistance with appeals. Your PSAO contract may also include audit protection provisions that limit recoupment exposure.
Handling Recoupment Demands
Understanding the Preliminary Findings
After reviewing your documentation, the PBM will issue a preliminary findings report listing claims they intend to recoup. Review this report claim by claim. Common reasons for recoupment include:
- Missing or illegible signature
- Prescription hard copy not provided
- DAW code not supported by prescriber documentation
- Compound formulation record incomplete
- Dispensing quantity discrepancy
- U&C price discrepancy
The Appeals Process
Every PBM contract includes an appeals process, and you should use it. Do not accept preliminary findings without challenge. For each contested claim:
- Identify the specific deficiency cited
- Gather any additional documentation that addresses the deficiency
- Write a clear, factual appeal for each claim
- Reference the specific PBM contract provisions that support your position
- Submit within the appeal timeline (typically 30 days from preliminary findings)
Appeals succeed more often than pharmacies expect. A well-documented appeal that provides the missing documentation or clarifies the discrepancy can reverse a significant portion of preliminary recoupments.
State Audit Protection Laws
Many states have enacted pharmacy audit protection legislation that constrains PBM audit practices. Common provisions include:
- Requiring PBMs to provide a specific minimum response timeline
- Prohibiting extrapolation of audit findings to non-audited claims
- Allowing pharmacies to use prescriber records to supplement missing documentation
- Requiring preliminary findings before final recoupment
- Mandating an appeals process with defined timelines
Know your state's pharmacy audit laws. They may provide protections that the PBM's own policies do not reflect. If a PBM's audit practices violate state law, document the violation and report it to your state pharmacy board and attorney general.
Building Audit-Proof Systems
Daily Documentation Habits
Audit defense starts with daily documentation discipline, not with the audit letter:
- Verify signature capture for every prescription at point of sale
- File or scan prescription hard copies daily - do not let a backlog build
- Complete compound logs at the time of compounding, not after the fact
- Reconcile DAW codes against prescriber documentation weekly
- Run exception reports for prescriptions dispensed without signatures
Technology Solutions
Modern pharmacy management systems offer audit preparation tools. Use them:
- Automated signature log auditing that flags missing entries
- DAW code verification workflows
- Compound claim documentation templates
- U&C price consistency checking
- Audit response report generators that compile all documentation for selected claims
Mock Audits
Conduct internal mock audits quarterly. Select 25-50 random claims and attempt to compile the complete documentation package an auditor would request. Identify and fix documentation gaps before a real audit finds them.
For guidance on building a complete compliance program that includes audit readiness, see the Complete Pharmacy Compliance Checklist for 2025. For Medicare-specific audit preparation, read our guide on Medicare Part D audit preparation.
