Pharmacy NDC Changes and Rebilling: When the Product Code Misstates the Claim

Pharmacy NDC billing fraud concerns knowingly billing a government health care program under a National Drug Code that misstates the drug dispensed. A rejected claim can expose the decision behind the billing: someone changes the product code, resubmits the claim and seeks payment. If you saw the change, the question is concrete. Did the new code describe the medicine the patient received, or did it describe a product the payer would accept?

The dispensing record, the rejected claim and the resubmission can tell different stories about the same prescription. Omnicare’s separate settlements over manual NDC changes and automated verification show why the person who understands those differences matters. We follow the product, the claim and the payment together.

What Happens After a Pharmacy Claim Is Rejected?

After a pharmacy claim is rejected, the next submission shows what the pharmacy changed in seeking payment. The original claim and the processor’s rejection response supply the comparison. It includes the product code, any override and the resubmitted fields.

New York Medicaid’s November 2025 electronic billing companion guide supplies a practical example. It distinguishes billing, reversal and rebill transactions, so the claim history shows both the original submission and later changes.

The same guide separates product identity, quantity dispensed and days’ supply. The National Drug Code answers which product the claim represents. Quantity and days’ supply answer different questions. A claim can identify the product while misreporting how much was supplied or how long it should last.

That distinction matters to an employee who remembers being told to make a rejected claim go through. We want to understand what the instruction changed, who gave it and how the resubmitted claim compared with the actual dispense. The final accepted version alone leaves out the decision that produced it.

Omnicare’s Manual NDC Changes After Rejection

Omnicare agreed to a combined federal and state settlement of $2.24 million in October 2016 over alleged manual National Drug Code changes on rejected claims from January 2006 through September 2014. The Justice Department’s announcement identifies Medicare, Medicaid and TRICARE as the programs receiving those claims.

Omnicare was a national long-term care pharmacy supplying patients in skilled nursing and other institutional facilities. The government alleged that employees made the changes to overcome prior payment rejections. The alleged conduct preceded CVS Health’s purchase of Omnicare.

In the government’s account, the pharmacy had already dispensed the drug when employees changed its product identifier to get past a rejection. We see a payment system being given a different account of the same medicine. The change was on the claim.

A former regional service area director brought the whistleblower case. That role matters because this story crosses dispensing and billing: someone inside the business could connect the medicine supplied with the claim sent for payment. The allegations concern the employees’ manual edits, rather than the automated verification system addressed in the separate settlement that followed.

Omnicare’s Automated NDC Verification Settlement

Omnicare agreed to an $8 million settlement in May 2017 of a separate False Claims Act case alleging more than two million mismatches between the product dispensed and the product billed. The allegations concerned its automated drug-matching verification system.

The settlement agreement covered alleged conduct from January 2008 through December 2014. The government alleged that manufacturer and National Drug Code mismatches impaired billing accuracy and recall traceability. Government health programs paid the claims, and patients depended on accurate product records when a drug needed to be traced for a recall.

Here the alleged failure sat in verification itself. A reader who worked with the automated results may recognize a different problem from the employee manually editing a rejected claim. What did the system accept as a match, and how did that compare with the manufacturer and product code of the dispensed drug?

The two settlements put different decisions under examination. One concerned changing a claim after rejection. The other concerned a verification system that allegedly allowed the billed and dispensed products to diverge. We examine the manual decision or the automated control alongside the particular claims and their payments.

What Records Connect the NDC to the Payment?

The connection runs from the prescription and the product dispensed to the submitted claim, its processing history and the final remittance. The prescriber supplies the order, the pharmacy dispenses and bills, and the processor responds to the claim. We connect those records with the employee’s account of what changed and who directed it.

Purchase invoices and inventory movements show what came into the pharmacy and what moved out. Dispensing and pickup or delivery records connect that stock to the prescription. New York’s pharmacy policy separates claim submission from proof that the prescription was furnished. The product comparison reaches back to the medicine itself.

The original claim, rejection and rebill show what the pharmacy represented at each stage. The remittance shows reimbursement and later adjustments or recoupments. For Medicare Part D, the Centers for Medicare & Medicaid Services’ data guide describes Prescription Drug Event data as summary extracts of claims using standard fields. A product-code edit, a payment adjustment and a corrected federal report each leave a different record of the same prescription.

The Medicare drug plan answers for the claims even when another company processes them. That makes the plan and its processor part of the payment story alongside the pharmacy. An employee in healthcare billing may see the correction without seeing the original dispensing decision. We bring those parts together.

How Does an NDC Change Affect the Amount Paid?

The payment effect comes from the product billed, the payer’s reimbursement terms, the money paid and any later correction. We follow the changed product code through to the payment.

The agency’s July 2013 guidance on adjustments after the point of sale distinguishes a wrong National Drug Code or financial amount from a duplicate claim or a drug never dispensed. Those differences carry through to the corrections: changing product and payment fields leaves a different history from recovering a payment and deleting the federal reporting record.

These distinctions make the insider’s knowledge more useful. The question is how the inaccurate product identifier affected payment under that payer’s rules, and what the company did afterward. A corrected product field, a returned payment and a corrected federal report each tell us something different. We trace all of them before putting a dollar figure on the conduct.

Product Identity, Days’ Supply and Prescription Validity

A National Drug Code identifies the claimed product. Days’ supply affects the account of how long the medicine should last. Prescription validity concerns the authority to dispense it.

In its insulin-pen complaint against CVS, the government alleged that dispensing software calculated refill dates using inaccurate days-of-supply data. It alleged repeated premature refills and management awareness of pharmacy benefit manager audit findings and chargebacks. CVS’s December 2025 settlement included factual admissions. The comparison there concerned the quantity supplied, prescribed use and next refill date.

A separate Omnicare prescription-validity case exposed another software problem. A whistleblower started the case, and the government joined it. Its complaint quoted a compliance officer describing what the system allowed:

The government alleged that prescriptions kept rolling forward after they expired or exhausted their authorized refills. That separate case later produced a jury verdict against Omnicare over invalid prescriptions and government claims.

The compliance officer’s words make the internal problem visible: the system could create another prescription number without the documentation or pharmacist intervention described in the email. For a product-code case, the comparable question is what the product verification actually checked. The software’s acceptance is part of the evidence we examine.

When You Saw the Claim Change

A pharmacy employee may know which rejected claims were edited, what the verification system accepted or who instructed staff to resubmit. A billing or audit employee may know how those changes appeared in the remittance or later corrections. We connect that firsthand knowledge to the prescription, the product and the payment.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.

The Drug and the Claim Should Tell the Same Story

If you saw a product code changed to get a rejected claim paid, speak with our whistleblower experts about the change and who directed it. We bring the dispensing, billing and payment history together to build your strongest pharmacy whistleblower case, with pharmacy fraud whistleblower lawyers who understand NDC disputes. We stay beside you as the case develops, with your knowledge of the business at its center.