Pharmacy reject codes: meanings and next checks.

At the counter: pharmacy claims reject for recurring reasons: eligibility, formulary and coverage, quantity and days-supply limits, refill timing, prior authorization, and data mismatches. The plan returns each as an NCPDP reject code. First determine whether the code points to claim data the pharmacy can correct or to a coverage rule that needs payer or prescriber action.

The code is a signal, not a universal diagnosis or fix. In two or three characters, the processor identifies the field or rule it objected to. This reference covers selected recurring codes: what the published text says, whether the response points first to claim data or plan design, and what to check next. Every code and its official reject text below is checked against a published NCPDP reject-code list. The payer's additional message and current instructions remain authoritative.

How to read a pharmacy claim reject

Pharmacy claim adjudication is a real-time transaction. When you submit a claim, the pharmacy management system packages it in the NCPDP Telecommunication Standard (the messaging format the industry runs on) and sends it to a claims processor. The processor answers in seconds while the patient is still at the counter.

The BIN or IIN and PCN route the claim to a processor and plan or line of business; Group may further identify the employer or benefit group. Incorrect routing or member data can send the claim to the wrong benefit and produce a rejection. For the broader context, see what prescription data entry actually involves.

The processor then runs the claim against the plan's rules, including eligibility, coverage, quantity, and refill timing, and returns an adjudication response. A paid response carries pricing information; a rejected response carries one or more codes explaining the issue. Those codes come from a standard list maintained by the National Council for Prescription Drug Programs (NCPDP). The full list is licensed, but state Medicaid programs publish working subsets, and the codes below are drawn from those publications.

One convention to know before the table: a code that starts with M/I means Missing or Invalid. The plan isn't saying the value is wrong in the world. It's saying the field is blank, malformed, or doesn't match what the plan expects in that position. That distinction points you straight at the fix.

Pharmacy reject codes: 70, 75, 76, 79 and more

These twenty-four codes recur in published pharmacy claim material and cover distinct counter workflows. They are not a nationwide frequency ranking: the Louisiana Medicaid SFY 2023 denied-claims appendix is one state-program example, not evidence of uniform frequency across payers. The compact row shows the official text; expand it for a likely issue and a payer-bounded next check.

Published text is checked against the Medi-Cal Rx and Missouri state code lists. The expanded workflow notes are directional, not universal: the July 2026 Medi-Cal Rx Provider Manual and New York Medicaid's product-rejection guidance illustrate why the additional message and payer instructions control the actual resolution.

Some codes overlap without being interchangeable. MR (Product Not on Formulary) and 70 both signal coverage issues, but the payer's response message and current instructions determine the next step. A refill-too-soon condition can surface as either 79 or a DUR edit under 88, depending on the plan; the published Medi-Cal list explicitly cross-references the two.

Which pharmacy rejects point to data-entry issues?

Several codes in the table can trace back to prescription, patient, product, or claim data. The codes map to the work this way:

• 07 (Cardholder ID), 13/6E (other-payer detail), 41 (other processor), and 65/69 (not covered / terminated) point first to member or insurance information. A new card is a data-entry event, not a filing one: a transposed member ID or a stale card in the profile can be the difference between paid and rejected.
• 19 (Days Supply), 76 (Plan Limitations Exceeded), and 9G (quantity exceeds maximum) are the quantity-and-days-supply group. The submitted values may be internally inconsistent or may exceed a payer limit even when entered correctly.
• 21/54 (Product/Service ID) and 22 (DAW) are the drug field. A malformed NDC, a code for the wrong package, or a DAW that doesn't match who chose the brand all reject here.
• 25 (Prescriber ID) and 39 (Diagnosis Code) point to prescriber or clinical claim data. Verify the documented value and payer requirement rather than supplying one by inference.
• 50 (Pharmacy Number) points to the submitting pharmacy's identifier, qualifier, enrollment, or routing rather than patient data.

The instructive one is 79, refill too soon. It can look like a timing problem today but trace back to days supply on the last fill: a 30 keyed where the insulin math said 37 starts the plan's refill clock early, and the reject lands weeks later on a claim that was entered correctly. The claim that rejects is not necessarily the one with the original entry problem. Each field and its failure mode is walked through in what prescription data entry actually is. When one of these codes returns, the next move may be correcting the earlier field rather than resubmitting the same claim.

Which pharmacy rejects come from plan rules?

Codes 70, 75, 76, 9G, MR, and some instances of 79 can reflect the plan's coverage rules rather than a pharmacy error. The claim may be clean and the answer may still be no, or not yet. These rejects usually need a conversation with the patient or prescriber, not another trip through data entry.

75, prior authorization required. The plan requires authorization review before it may cover the drug. Follow the plan's process, coordinate the required information with the prescriber, and explain the current status to the patient. Approval and timing are payer-specific.

76, plan limitations exceeded. A claim can exceed a quantity, days-supply, network, or other plan limit even when the prescription is valid. Determine whether the plan permits a covered partial quantity, mail-order or network option, exception, or authorization, and whether changing the dispense requires prescriber clarification.

70 (and MR), product not covered / not on formulary. Check whether the issue applies to the drug, the submitted NDC, or the benefit. The available path may be a covered alternative, another covered package, a formulary exception, prior authorization, or no covered option under the current plan.

79, refill too soon. Verify the previous fill's date and days supply first. If they are correct, use the payer's documented process for the specific reason, which may involve an authorized override, a Submission Clarification Code, a help-desk call, or waiting until the eligible date.

First identify whether a rejection reflects incorrect claim data or a benefit rule. Correct data errors; route benefit issues through the payer, prescriber, or other process the current instructions require.