PharmaDossier
Pricing & Access

NDC lookup for claims teams: reading labeler, product, and package codes before you bill

How market access and billing teams read a National Drug Code at the package level to prevent billing-unit, formulary, and rebate mismatches — with a field-by-field FDA NDC Directory workflow.

Ran Chen
Ran Chen
15 min read · Published · Source-cited

A specialty pharmacy bills an extended-release methylphenidate tablet under the 11-digit NDC printed on the bottle. The claim rejects. The NDC on the claim resolves to a 54 mg strength in the payer's crosswalk, but the vial dispensed was 36 mg — same labeler, same product code digits in the payer's master file, a different package code. The payer reads the submission as the wrong strength and denies it. The dispute is not about the drug. It is about which segment of the NDC was read.

This is the operational reality of the National Drug Code for claims teams. The NDC is a three-segment identifier — labeler, product, and package — and almost every billing, formulary, and rebate mismatch traces back to a team that read the number as one block instead of three segments. A single product can carry many package codes, each representing a different count of tablets, vial size, or bottle. Get the segment wrong and the claim denies, the AWP/ASP pricing unit misaligns, or the Medicaid rebate unit count drifts.

This article is a field-by-field NDC lookup workflow for claims, billing, reimbursement, and market-access teams. It covers how to read each segment, where to verify it in the FDA NDC Directory, how the HIPAA 11-digit billing format is built, and the 2026 final rule that will collapse today's multiple NDC formats into one. It is written for pharmacy billing staff, manufacturer reimbursement hubs, rebate and gross-to-net teams, and payer operations — the people who get the call when a claim line rejects for an NDC reason. For the aggregate directory — marketing-category mix, dosage-form concentration, and the repackagers that lead NDC volume — see the companion US drug product landscape analysis; this article stays on the package-level read a billing or rebate team performs.

What the NDC actually is: three segments, not one number

The NDC is a unique, three-segment numeric identifier for drugs in U.S. commercial distribution. FDA assigns the first segment; the labeler (manufacturer, repackager, relabeler, or private-label distributor) proposes the second and third. The three segments are:

Segment Digits today Set by Identifies
Labeler code 4 or 5 FDA The manufacturer, repackager, relabeler, or distributor
Product code 3 or 4 Labeler Specific active ingredient, strength, dosage form, formulation
Package code 1 or 2 Labeler Package sizes and types

A new product code is required when the established name, active ingredient, strength, or dosage form changes. A new package code is all that is required when only the package size or type changes — the same drug, the same strength, in a 30-count bottle versus a 100-count bottle, gets a different package code and therefore a different full NDC. That single rule is why package-level granularity matters so much downstream.

The three formats in use today

Because the labeler, product, and package segments can each vary in length, FDA currently assigns 10-digit NDCs in three configurations:

  • 5-3-2 (5-digit labeler, 3-digit product, 2-digit package)
  • 5-4-1 (5-digit labeler, 4-digit product, 1-digit package)
  • 4-4-2 (4-digit labeler, 4-digit product, 2-digit package)

In the FDA NDC Directory extract analyzed for this article (dated June 2026), 5-3-2 is the most common product-level configuration, at roughly 57% of listed products; 5-4-1 accounts for about 34%; the legacy 4-4-2 format accounts for the remaining 10%. These are the product NDC (labeler-product). The package NDC adds the package code on the end.

Package-level is where billing lives

This is the part claims teams get wrong by treating the NDC as a flat lookup. One product can — and usually does — have several package codes.

Consider metformin hydrochloride tablets from one repackager labeler (product NDC 50090-7010). That single product code resolves to five different package-level NDCs, each a distinct count of tablets in a bottle:

Package NDC Package description
50090-7010-0 60 tablets in 1 bottle
50090-7010-3 100 tablets in 1 bottle
50090-7010-4 30 tablets in 1 bottle
50090-7010-5 180 tablets in 1 bottle
50090-7010-6 90 tablets in 1 bottle

Same drug, same strength, same labeler — five billable units of inventory. A billing system that keys only on the product code (50090-7010) cannot distinguish a 30-count fill from a 180-count fill. That distinction is exactly what the package code encodes, and it is exactly what the payer, the pricing file, and the rebate calculation all key on.

Across the full directory, there are roughly 252,000 package-level NDCs spread across about 136,000 product records — an average of nearly two packages per product, with many products carrying five, ten, or more. The package code is not a rounding detail. It is the field that determines quantity billed, units-of-measure math, and which pricing record applies.

Why the labeler segment drives rebate and gross-to-net work

The labeler code identifies who marketed the drug. That matters for rebate teams because the Medicaid Drug Rebate Program and most commercial rebate agreements settle against the labeler and product combination. When an authorized generic, a repackager relabel, or a new contract manufacturer changes the labeler code, the same molecule can move to a different rebate agreement, a different AMP reporting entity, and a different row in a 340B ceiling calculation. A claims analytics layer that normalizes NDCs only to ingredient name — not to labeler — will silently aggregate rebate liability across entities that should be settled separately.

This is also why repackagers dominate NDC volume. In the directory analyzed here, the largest labelers by product count are repackagers and prepackagers — Bryant Ranch Prepack, Hahnemann Laboratories, A-S Medication Solutions, REMEDYREPACK — firms that re-list existing drugs under their own labeler codes to create package sizes for specific dispensing channels. Each relist is a new labeler-product-package combination that a formulary or rebate file must map.

The HIPAA 11-digit billing format

For claims, none of the three 10-digit formats above is submitted as-is. HIPAA adopted a uniform 11-digit NDC format required whenever a covered transaction includes an NDC. That billing format is fixed at 5-4-2 (5-digit labeler, 4-digit product, 2-digit package), created by adding a leading zero to whichever segment is short.

The conversion rules are mechanical but exact, and a leading zero added to the wrong segment is a frequent cause of rejection:

Label format Segments 11-digit billing NDC
4-4-2 1234-5678-90 01234-5678-90
5-3-2 12345-678-90 12345-0678-90
5-4-1 12345-6789-0 12345-6789-00

The reconstitution problem: why 11 digits are not reversible

This is the subtler trap behind the leading-zero rule, and it is the reason every claims system ultimately has to resolve NDCs against the directory rather than parse them by rule. A zero is a valid digit in any segment, so an 11-digit billing NDC is not uniquely reversible to its native 10-digit format. The billing NDC 12345-0678-09 could be a native 5-3-2 product (12345-678-09) padded in the product segment, or a native 5-4-1 product (12345-0678-9) padded in the package segment. There is no way to tell which from the number alone. The same ambiguity bites when a payer's master file or a rebate extract strips the hyphens: without the directory record that says which segment was short, the labeler-product-package boundaries are a guess. The operational rule that follows is simple: never parse a padded NDC back into segments by assuming where the zero went. Always confirm segment boundaries against the FDA NDC Directory or the labeler's known configuration before mapping to a pricing file, a crosswalk, or a rebate unit table.

Payers reject claims that carry a 10-digit NDC, and several Medicaid and commercial billing guides state plainly that the NDC submitted must be the actual number on the container from which the drug was administered, reformatted to 11 digits with no hyphens or spaces. On the CMS-1500, the NDC goes in the shaded portion of field 24a–24g, preceded by the qualifier N4, immediately followed by the 11-digit number. On the UB-04 it goes in field 43, again with N4. In the 837 electronic transaction it travels in loop 2410: the qualifier in LIN02, the NDC in LIN03, the quantity in CTP04, and the unit of measure in CTP05.

NDC units are not HCPCS units

A second, independent source of mismatch: the NDC unit count is not the HCPCS unit count. HCPCS codes bill in units defined by the code descriptor (for example, "1 mg"), while the NDC unit count reports the quantity actually administered in the unit of measure on the package (each, mL, mg, international unit). A claim must carry both the HCPCS service units (the basis for reimbursement) and the NDC quantity plus unit-of-measure qualifier (UN for units, ML for milliliters, GR for grams, F2 for international units). Submitting the vial count as the NDC unit, or calculating NDC units from vial size instead of from the quantity administered, is a standard reason a claim denies even when the NDC itself is formatted correctly.

Field-by-field NDC lookup workflow

Use the FDA NDC Directory as the authoritative source for package and product fields. For every NDC on a claim or in a master file, walk these fields in order.

Step 1 — Resolve the full 11-digit package NDC

Start from the package NDC on the container (labeler-product-package). Confirm it is the package code, not the product code. The NDC Directory returns both a product_ndc (labeler-product, 10 digits) and, for each package under it, a package_ndc (labeler-product-package, 11 digits) plus a description field that spells out the package size in plain language ("60 TABLET in 1 BOTTLE"). The description field is the fastest way to confirm you are looking at the right package code.

Step 2 — Confirm the product-level identity

From the package NDC, drop the package segment to get the product NDC and verify the generic name, active ingredient strength, dosage form, and route against the directory record. A package code that does not match the strength on the dispensed product — as in the methylphenidate example at the top — almost always means the wrong package code was carried forward.

Step 3 — Confirm the labeler and marketing category

Read the labeler name and the marketing_category field. The marketing category tells you the regulatory basis of the product — ANDA (generic), NDA (brand), BLA (biologic), OTC monograph, or repackager relist. In the directory analyzed here, ANDA products account for roughly 37% of records, OTC monograph drugs about 26%, NDAs about 6%, and BLAs about 3%, with the remainder split among bulk ingredients, homeopathic, and "for further processing" listings. The marketing category determines whether a product is even in scope for formulary substitution, biosimilar comparison, or rebate settlement.

Step 4 — Crosswalk to the HCPCS / pricing record

Map the package NDC to the relevant pricing and coding crosswalk — the CMS ASP HCPCS-NDC crosswalk for Part B physician-administered drugs, or the PDAC NDC/HCPCS crosswalk for DMEPOS — and confirm the NDC maps to the HCPCS code being billed. This is where most NDC denials actually fire: the NDC on the claim resolves to a different HCPCS code than the one billed, or does not appear in the crosswalk at all. A separate workflow covers biosimilar HCPCS and NDC crosswalk errors in depth.

Step 5 — Confirm the listing is active for the date of service

Check the marketing_start_date and listing_expiration_date. Payers run inactive-NDC edits that reject claims for NDCs that are end-dated or not yet effective for the date of service. A newly assigned NDC can lag the crosswalk by a quarter, and a relisted package under a new labeler code can leave a window where the old NDC is inactive and the new one is not yet mapped.

Where NDC mismatches cause downstream damage

A package-segment error is rarely isolated to one claim line. It cascades:

  1. Claim denial — the NDC and HCPCS do not match in the crosswalk, or the NDC is inactive, or the strength implied by the package code contradicts the billed HCPCS descriptor.
  2. Wrong pricing unit — if the package code implies a different strength or pack size, the AWP, ASP, or NADAC unit selected from the pricing file is the wrong one, over- or under-paying the line.
  3. Rebate unit drift — Medicaid and commercial rebates settle on NDC unit counts. A package code that maps to a different pack size shifts the units counted against the rebate agreement, distorting gross-to-net in either direction.
  4. Formulary misassignment — a relist under a new labeler code can fall outside a preferred-NDC formulary list, routing a covered product to non-preferred status and triggering a prior authorization that should not apply.
  5. Audit exposure — a pattern of NDC-to-HCPCS mismatches is a standard Medicare and commercial audit trigger, and the correction must be documented against the current crosswalk, not the one in force at the original date of service.

The 2026 final rule: one format instead of three

The multi-format friction is on a fixed path to end. On March 5, 2026, FDA published the long-awaited final rule, Revising the National Drug Code Format and Drug Label Barcode Requirements (91 FR 10749), standardizing the NDC to a single 12-digit, 6-4-2 format: a 6-digit labeler code, a 4-digit product code, and a 2-digit package code. Existing 10-digit NDCs convert automatically by adding leading zeros; FDA does not treat the conversion as a new NDC assignment.

The timeline:

Date Event
March 5, 2026 Final rule published
March 7, 2033 Effective date — FDA begins assigning 12-digit NDCs; existing 10-digit NDCs auto-convert
March 2033 – March 2036 Three-year transition — 10-digit labeling tolerated; systems must handle both
After March 2036 Enforcement possible for noncompliant labeling

The rule permits the package-level NDC to be carried in a linear or nonlinear barcode (such as a 2D data matrix) that conforms to a widely recognized standard such as GS1. For products that are also subject to Drug Supply Chain Security Act (DSCSA) product-identifier requirements, a single 2D data matrix barcode can encode the 12-digit NDC alongside serial number, lot, and expiration date and satisfy both the NDC barcode rule and the DSCSA product identifier from March 7, 2033 onward. For claims teams, the practical takeaway is that the seven-year runway before the effective date is the window to widen every system field, crosswalk, and pricing table that currently assumes a 10-digit NDC — because the HIPAA 11-digit billing format itself will need to accommodate the longer codes well before 2033.

Operational checklist before you bill

  1. Capture the package NDC from the container — the actual labeler-product-package number dispensed or administered, not a cached product-level lookalike.
  2. Reformat to 11 digits, 5-4-2 — add the leading zero to the short segment; never the long one.
  3. Verify package identity in the NDC Directory — confirm the package description field matches the strength and pack size dispensed.
  4. Confirm active listingmarketing_start_date on or before, listing_expiration_date on or after, the date of service.
  5. Crosswalk to the billed HCPCS — confirm the NDC maps to the code you are billing in the current ASP or PDAC crosswalk.
  6. Carry NDC units and unit-of-measure — quantity administered in UN/ML/GR/F2, separate from HCPCS service units.
  7. For rebate and GTN work, normalize to labeler-product — do not aggregate across labeler codes or contract manufacturers that settle under separate agreements.
  8. For any system build, plan for 12 digits — fields, crosswalks, and pricing tables that assume 10 or 11 digits must be widened before the 2033 effective date.

This article is for informational purposes only and does not constitute medical advice, legal advice, billing advice, or coding guidance for any specific entity. NDC formats, crosswalks, and payer edits change frequently; always verify current data in the FDA NDC Directory and the applicable payer or CMS crosswalk before submitting claims.

Last updated: June 13, 2026.

Sources

  • FDA. "Format of the National Drug Code" (presentation, Julian Chun, FDA/OC/OUDLC/DRLB, September 28, 2023). fda.gov
  • FDA. "The National Drug Code (NDC) Rules for Assigning and Changing NDCs" (presentation, LCDR Soo Jin Park, FDA CDER/OC/OUDLC/DRLB). fda.gov
  • FDA. "National Drug Code Format." fda.gov
  • FDA. "Revising the National Drug Code Format and Drug Label Barcode Requirements; Final Regulatory Impact Analysis." Federal Register, 91 FR 10749, March 5, 2026. fda.gov
  • Federal Register. "Revising the National Drug Code Format and Drug Label Barcode Requirements," March 5, 2026. federalregister.gov
  • FDA. "Public Hearing: Future Format of the National Drug Code." fda.gov
  • FDA. "National Drug Code Directory." fda.gov
  • Faegre Drinker. "FDA Finalizes Rule Requiring 12-Digit National Drug Code (NDC)," March 2026. faegredrinker.com
  • RAPS. "FDA issues long-awaited final NDC rule," March 4, 2026. raps.org
  • Mass.gov. "Learn about National Drug Code (NDC) requirements." mass.gov
  • Premera. "National Drug Code (NDC) Billing Guidelines — Professional Claims." premera.com
  • Horizon NJ Health. "How to Submit Claims with Drug-Related (J or Q) Codes." horizonnjhealth.com
  • UnitedHealthcare. "National Drug Codes Requirement for Claims Submissions (FAQ)." uhcprovider.com
  • Community First Health Plans. "National Drug Code (NDC) Billing Guidelines." communityfirsthealthplans.com
  • Reed Tech / LexisNexis. "The Anatomy of a National Drug Code (NDC)." reedtech.com
  • NBER. "NDC to Labeler Code Product Code Crosswalk" (5-3-2 vs 5-4-1 configuration and the leading-zero reconstitution problem). nber.org
  • IMO Health. "NDC Codes 101: A Complete Guide to National Drug Codes" (SPL submission, labeler code request, 12-digit format). imohealth.com
Ran Chen
Contributing Editor
Ran Chen

Founder, PharmaDossier. Life-sciences operator covering market access, specialty pharma, biosimilars, and regulated healthcare growth.

Follow on LinkedIn →