BCBS Payer ID and Claims Submission: What Medical Billers Need to Know

Why one Blue payer ID does not exist

The Blue Cross Blue Shield Association licenses the brand. It does not pay your claims. Independent companies do, and each one publishes its own payer ID for electronic claims.

For instance, Blue Cross Blue Shield of Texas lists 84980 in its Federal Employee Program quick reference guide. Carry that number to a Michigan claim, and you are guessing. (Plenty of billers do exactly that, because a forum post made the number look universal.)

Then add clearinghouses. The same plan may have different IDs in different clearinghouses. Ensora’s billing documentation does this, too, and it offers a good tip to keep in mind: If claims have been flowing for months, and the clearinghouse may have been quietly fixing a bad ID on its side. You won’t see the problem until you change vendors; then all the claims are denied at once.

So where should you look? Three places, in this order. The payer list inside your clearinghouse. The plan's own provider site, where the claims page or companion guide usually names its EDI payer ID. Then there's the member's card, which shows the plan and often the claims address.

One more wrinkle. A single Blue company can run several lines of business. Blue Cross Blue Shield of Michigan’s EDI page is responsible for the commercial plans, the Federal Employee Program, a Medicare Advantage PPO, Blue Care Network, and a Medicaid plan, and also processes 837, 835, 270/271, and 276/277 transactions through Availity. Before you select a payer entry, confirm which line your claim belongs to.

What the payer ID does on a claim

The payer ID gets the claim to the right front door. That is the whole job.

In a 5010 837P file, the payer ID sits in the payer name loop (2010BB), and the member's ID sits in the subscriber loop (2010BA). Two fields serve different jobs, but staff constantly mix them up. The payer ID answers one question: which company gets this file? The member ID answers a different set: which member, which home plan, and which benefits.

Paper claims work differently. The CMS-1500 has no payer ID box, only a payer name and address in the upper right corner, so a wrong mailing address does the same damage on paper that a wrong ID does electronically.

The alpha prefix does the real routing

Pull up any BlueCard. The alpha prefix is the first three characters of the member ID, and BlueCard uses it to identify the member's home plan and route claims from outside your area. The plans describe the risk in almost the same words: a wrong or missing prefix delays a claim. That is what Blue Cross Blue Shield of Montana states on its provider help page.

Three habits matter here.

Enter the ID exactly as printed, prefix included. No dropped characters, no reordered ones.

Never invent a prefix. If a card shows none, do not borrow one from another member's card, even a member of the same plan. The Blue Cross Blue Shield quick guide to ID cards says so directly, and it tells billers to follow the instructions on the back of the card instead.

Verify the prefix against the date of service. Blue Cross Blue Shield of Arizona says the prefix could change when a member switches employers or benefit plans. A claim with an invalid prefix on the service date will return with a replacement message, and an eligibility search with a stale prefix will return "inactive." That looks like a coverage issue. It's a data thing.

Honestly, most prefixes are three letters. Not all of them. Arizona's own list includes P9H, 99D, Y4M, and Z9P, so a validation rule that accepts only letters will reject good IDs.

BlueCard: file with your local plan

Look, this is the rule that saves the most rework. If you contract with a Blue plan, file every Blue member's claim with that plan, whether the member belongs to it or to a plan three states away.

The local plan prices the claim and routes it to the member's home plan, and the home plan decides what it pays. One door for you, which is the entire point of the BlueCard program.

Picture a Michigan practice that sees a patient whose card carries a prefix tied to another state's plan. A new biller looks up that plan's payer ID and sends the claim there. It bounces, or it sits. Therabill's help center calls submitting to another state's Blue plan a common mistake, and the reason is easy to see: the prefix is right there on the card, pointing somewhere else.

Special cases that break the pattern

Federal Employee Program. FEP IDs start with the letter R followed by eight digits, and the card carries no three-character prefix. Anthem's provider news describes a rule that catches people off guard: for FEP members over 64 who lack Medicare Part B, the CMS-1500 needs the rendering provider's NPI, or the claim denies with a message asking for the provider name and NPI.

Labs, DME, and specialty pharmacy: "Local plan" means something different for these providers. Labs bill the plan where the specimen was drawn, which follows the referring provider's location. Durable medical equipment and orthotics and prosthetics suppliers bill the plan where the item was shipped or where it was bought at retail. Specialty pharmacies bill the plan where the ordering physician sits. Blue Shield of California publishes all three rules, and payment follows the provider's participation status with that local plan.

Rejections, you will see, and what they mean

Two messages show up more than the rest.

The subscriber insured number does not have a valid BCBS prefix. The MacPractice help desk says prefixes are state-specific, and this message means the ID was missing a prefix or had an invalid one. The fix begins with the card, not the software.

The Payer ID is not valid for EDI claim submissions. This error is in Ensora’s claim scrub. It indicates that the ID associated with the payer entry is not what the clearinghouse expects. Ensora recommends searching the payer list with several keywords, such as “BCBS,” the state abbreviation, or the full state name, since the entry may not be the full name of the plan.

A rejection never reached adjudication. In most cases, you fix the data and send it as a new original claim, not a corrected one. Work rejections the day they land, since every day in the reject queue eats into your filing window.

Corrected claims on Blue plans

A claim the plan already accepted needs a corrected claim, not a fresh one. On electronic claims, billing frequency code 7 replaces the original, code 8 voids it, and the original payer control number has to travel with either one. Anthem documents this process for the Federal Employee Program, and in most cases the same logic carries over to other Blue plans.

Most. Not all. Blue Cross Blue Shield of Montana, for example, wants CMS-1500 corrected claims submitted electronically through its Claim Inquiry Resolution tool.

Read the plan's manual before you correct the first claim. Not after the second.

A two-minute check before every Blue submission

1. Copy the member ID from the current card, prefix included. Scan the back too.
2. Run the eligibility check with that ID and the date of service. An “inactive” result often means a prefix problem.
3. Select the local plan, your contracted plan, or, for labs, DME, and specialty pharmacy, the plan associated with the specimen, shipping address, or ordering physician.
4. Match your clearinghouse payer ID to the correct line of business: commercial, Medicare Advantage, Medicaid, or FEP.
5. Submit and receive the clearinghouse acknowledgment the same day.
6. Before anyone resubmits anything, check claim status.

That is it. Six steps, two minutes once the habit sticks.

Keeping your payer list clean

Review it every quarter, and again any time a rejection mentions the payer ID. Look for duplicate Blue entries in your practice management system (two "BCBS" lines with different IDs is a classic). Retire the ones nobody uses, and have front desk staff scan both sides of every card at every visit.

Frequently asked questions