I still remember the first time I got stuck in a rejection loop at a busy community pharmacy counter. The patient was waiting, the phone was ringing, and I had a claim that kept bouncing back with a message that might as well have been written in another language. If you have had that moment in training or during externship, you are not behind. Pharmacy billing is learnable if you treat it like a flowchart instead of a mystery.

This guide breaks down two topics that show up constantly in order entry and processing (aka what you deal with at the counter): third-party rejections (what they are and how to clear them) and DAW codes (what they mean and why they matter). I will keep it practical, because that is how you actually survive the counter.

A pharmacy technician entering prescription claim information on a computer workstation in a busy community pharmacy

How a claim moves

When you submit a claim to insurance, you are basically sending a structured message that answers four big questions:

  • Who is the patient, and are they eligible today?
  • What drug is being dispensed (NDC), and what quantity and days supply?
  • What the plan can verify from the claim data (prescriber, directions, past fills, safety edits, and plan rules). Diagnosis information is often not required on standard retail claims, but some payers and programs may require it in specific situations.
  • Under what conditions is it being dispensed (generic vs brand choice, prior authorizations, refill-too-soon rules, plan limits)?

If any part of that story conflicts with the plan rules, you get a rejection. Your job is to figure out which piece of the story the insurer did not accept, then correct it without creating a new problem.

DAW codes at the register

DAW stands for Dispense As Written. In practice, it tells the payer why a specific product was chosen when a generic alternative could exist.

DAW codes matter because they can change:

  • Coverage (some plans cover generic only unless an allowed DAW reason is used)
  • Patient copay (brand copays are often higher)
  • Pharmacy reimbursement (some plans pay less when a brand is chosen without an acceptable reason)

One important reality check: the DAW list is standardized, but how payers apply it can vary. Always follow payer messaging, state law, and your store policy.

DAW codes you see most

Different systems display them differently, but these are the common DAW meanings pharmacy techs are expected to recognize:

  • DAW 0: No product selection indicated (default). Substitution is permitted.
  • DAW 1: Substitution not allowed by prescriber.
  • DAW 2: Substitution allowed, but patient requested brand.
  • DAW 3: Substitution allowed, but pharmacist selected brand.
  • DAW 4: Substitution not allowed, generic not available.
  • DAW 5: Substitution allowed, but pharmacy selected brand (often shows up when the pharmacy cannot dispense the generic as written due to availability or operational reasons, depending on system and payer rules).
  • DAW 6: Override (payer-specific). Some plans use this for limited situations where brand dispensing is allowed even though substitution would normally be expected. Many payers reject it unless their rules specifically allow it.
  • DAW 7: Substitution not allowed, brand mandated by law.
  • DAW 8: Substitution allowed, but generic not available (often interpreted as a marketplace availability issue).
  • DAW 9: Other (payer-specific). Less common at the counter, and frequently rejected if used without the payer's exact instructions.

Quick way to memorize DAW 0 to 5

When I trained new staff, I used this shorthand:

  • 0 = nothing special
  • 1 = prescriber says no
  • 2 = patient says no
  • 3 = pharmacist says no
  • 4 = no generic exists
  • 5 = pharmacy selects brand (often availability related, but payer rules vary)

DAW mistakes that trigger rejections

  • Using DAW 2 when the patient did not request brand. Many payers treat it as optional brand choice and apply higher cost share or reject.
  • Using DAW 1 without support. If the prescription does not clearly indicate no substitution, the pharmacy can be audited, even if the claim pays.
  • Changing NDC and not rechecking DAW. A new NDC can change whether a brand or generic is being billed, so confirm DAW, days supply, and quantity before resubmitting.

Common rejections

Here is the mindset shift: a rejection message is rarely the true problem. It is the plan pointing at a mismatch. Your job is to identify the mismatch category.

A pharmacy technician reviewing an insurance claim rejection message on a computer screen while checking prescription details

1) Refill too soon

What it usually means: The plan believes the patient still has medication left based on the last fill date and days supply.

Fast checks:

  • Confirm the last paid claim date in your history.
  • Confirm days supply entered matches directions and quantity.
  • Ask whether there was a dose change or lost medication. That often requires an override field, pharmacist involvement, or a plan call, depending on policy.

What not to do: Do not guess at days supply to force a paid claim. That is a compliance and patient safety issue.

2) Prior authorization required (PA)

What it usually means: The plan needs the prescriber to justify coverage, often because the drug is non-formulary, high-cost, or has step therapy rules.

Fast checks:

  • Verify the NDC and that you are billing the intended formulation.
  • Check if the plan covers a different strength, dosage form, or preferred product.
  • Communicate clearly to the patient: this is usually not a quick fix at the counter. The prescriber must submit the PA through the plan process, and the timeline depends on the plan.

3) Step therapy or try preferred first

What it usually means: The plan wants proof the patient tried a preferred drug first, or it wants a specific sequence (the rejection may look like a PA message, but the underlying rule is step therapy).

Fast checks:

  • Read the rejection for clue words like ST, step, or preferred.
  • Check whether the plan suggests an alternative product that would go through without paperwork.
  • If the prescriber intends this drug specifically, it usually becomes a prescriber-plan conversation (often PA, sometimes a formulary exception).

4) Non-formulary or drug not covered

What it usually means: The plan does not cover that product, or it is covered only under certain conditions.

Fast checks:

  • Confirm you did not pick a non-preferred NDC when a covered one exists.
  • If it is a brand, consider whether the plan expects generic (often tied to DAW selection).
  • See whether the plan message suggests an alternative or a step therapy requirement.

5) Invalid days supply

What it usually means: The plan has limits for that drug class or dosage form, or the entered days supply does not fit the quantity and directions.

Fast checks:

  • Recalculate days supply from the SIG. If math is your sticking point, review pharmacy math and conversions.
  • Watch for insulin, inhalers, eye drops, and topical products where day supply calculations can be tricky.
  • If the prescriber wrote for a longer supply than allowed, you may need a smaller days supply fill or a plan exception.

6) Quantity limit exceeded

What it usually means: The plan limits maximum quantity per fill or per time period.

Fast checks:

  • Confirm the package size and billed quantity are correct.
  • Check whether the plan wants split fills (for example, 15 days now, 15 days later) or a PA.
  • Consider whether the patient is supposed to be on a different strength with a smaller quantity (dose optimization rules can trigger this).

7) Max daily dose or dose optimization

What it usually means: The plan is not rejecting the drug, it is rejecting the way it is written or billed. Common examples are multiple tablets per day when the plan prefers one higher-strength tablet, or a maximum units per day rule.

Fast checks:

  • Recheck the SIG, quantity, and days supply for simple entry errors.
  • Look for an easy alternative that matches the prescriber intent (for example, 1 tablet of a higher strength instead of 2 tablets of a lower strength), then involve the pharmacist to contact the prescriber if a change is needed.

8) NDC not covered or invalid product/service ID

What it usually means: The specific NDC is not recognized by the plan, not covered, or not the preferred labeler.

Fast checks:

  • Re-select the product and confirm you did not choose an outdated or discontinued NDC.
  • If your pharmacy has multiple manufacturers, try an alternate NDC that matches what you actually have in stock.
  • Confirm whether the plan expects a brand NDC versus a generic NDC, especially for authorized generics.

9) Patient not found or not eligible

What it usually means: The insurance demographics do not match, the member ID is wrong, or coverage is inactive.

Fast checks:

  • Confirm spelling of name, date of birth, and member ID exactly as on the card.
  • Confirm the correct BIN, PCN, Group, and person code if applicable.
  • Ask if the patient recently changed plans, switched employers, or is in a coverage gap.

10) Duplicate therapy or clinical edit

What it usually means: The plan sees a potential drug duplication, interaction risk, or early refill pattern that requires review.

Fast checks:

  • Review the patient profile for recent fills in the same class.
  • Escalate to the pharmacist. These edits often require pharmacist intervention, prescriber clarification, or plan override rules.

11) Diagnosis code or documentation required

What it usually means: The plan is asking for more context than a basic claim provides. Some programs and medications require diagnosis codes or additional documentation rules.

Fast checks:

  • Do not improvise clinical details. Escalate to the pharmacist and follow your workflow for contacting the prescriber.
  • Read the rejection carefully for exactly what is being requested so you can relay it clearly.

Clearing rejections in 5 steps

When a rejection pops up, you want a repeatable routine. Here is the one I used when I was training new hires and we needed consistency across shifts.

  1. Read the rejection twice. First for the category (eligibility, product, timing, limits), second for the clue words (PA, refill too soon, NDC not covered, plan limit).
  2. Check the big four. Patient info, drug or NDC, quantity, days supply.
  3. Check DAW. Ask, “Are we billing brand or generic? And is the DAW reason accurate?”
  4. Decide: correct, clarify, or escalate. Correct data entry issues yourself. Clarify with the patient for insurance info. Escalate to the pharmacist or call the plan when policy or clinical edits are involved.
  5. Document what you changed. Even a quick note in the Rx comments can save the next person 15 minutes.

Overrides and codes

Sometimes you will do everything “right” and still hit a wall because the plan is asking for an override field that is not obvious from the plain-English rejection.

Depending on your system and payer, that might look like:

  • Submission clarification codes (SCC) for specific situations like dose changes or vacation supplies
  • Other payer-specific fields that a pharmacist or lead tech handles (especially on clinical edits)

If you are thinking, “I do not see where to enter that,” you are not crazy. This is one of those moments where the clean move is to loop in the pharmacist and follow store workflow instead of clicking random options.

DAW scenarios

Scenario 1: Patient wants brand

If the prescription allows substitution but the patient insists on brand, that is typically DAW 2. The plan may still reject or apply a higher copay. Your role is to be accurate, then set expectations: a brand request can cost more and may not be covered.

Scenario 2: Prescriber says no substitution

If the prescriber truly indicates no substitution, that is typically DAW 1. Be careful: the wording matters, and each pharmacy has its own policy about what counts as prescriber direction. When in doubt, loop in the pharmacist.

Scenario 3: Generic is out of stock

This is where you may see DAW 5 in some workflows, but payer behavior varies. Some will still refuse to pay for brand if a generic exists, even if your shelf is empty. Often the real fix is finding an available generic NDC through another supplier, doing a partial fill if policy allows, or transferring to a location that has stock.

Exam vs job

For certification-style questions, you are usually being tested on recognition and proper selection:

  • Knowing what DAW stands for and what common DAW codes mean
  • Understanding what common rejection types imply
  • Spotting which field is likely wrong (days supply, quantity, NDC, eligibility)

For real-world work, you are building speed and judgment:

  • Following a consistent troubleshooting order so you do not miss something obvious
  • Knowing when to escalate to the pharmacist
  • Communicating clearly with patients without overpromising outcomes

If you are building an overall study plan, start with the bigger test domains in our pharmacy tech exam guide, then layer in the workflows like this one.

Mini practice set

1) A claim rejects refill too soon. What should you verify first?

Best first move: Check last fill date and the days supply on the last paid claim, then confirm the current claim days supply matches the SIG and quantity.

2) The patient requests brand even though a generic exists and substitution is allowed. What DAW is commonly used?

Most common: DAW 2 (patient requested brand).

3) A claim rejects quantity limit exceeded. What is a common clean fix if the prescription allows it?

Common fix: Adjust to the plan-allowed quantity or days supply and process a smaller fill, or split fills if policy and prescription allow. If the prescriber intended the larger quantity for a reason, it may require prior authorization.

Student questions

Are DAW codes the same everywhere?

The code set is standardized in pharmacy billing, but how your software displays options, defaults, and wording can differ. Also, payer rules can be strict about which DAW values they accept in specific scenarios. The meaning behind the most common codes stays consistent enough that you should recognize them anywhere.

Can I switch DAW to make a claim pay?

You should only use a DAW code that matches reality. If the patient requested brand, use that. If the prescriber prohibited substitution, use that. Picking a DAW code just to force payment is exactly how pharmacies get chargebacks and audit problems.

What should I memorize versus understand?

Memorize the core DAW meanings (especially 0 through 5). Understand the rejection categories and the troubleshooting order. That combination is what makes you fast without being sloppy.

Tie it to fundamentals

Third-party problems often look like billing problems but turn out to be SIG, math, or workflow problems. If you want to strengthen the foundation that supports accurate claims, these help:

A pharmacy technician speaking with a patient at the pharmacy counter while reviewing an insurance card and prescription information