What Is an Entity Code in Medical Billing?

You probably landed here because a clearinghouse report rejected a claim with a short string like A7:562:85, and nobody on your team is quite sure what the “85” is pointing at. That last piece is the entity code. Once you know how to read it, a lot of claim rejections become easier to fix.

The short answer

So, what is an entity code in medical billing? It’s a short code, usually two or three characters, that tells the payer who a piece of claim information belongs to. A claim names a lot of parties: the practice billing for the service, the clinician who performed it, the patient, the policyholder, the insurance company, and the organization transmitting the file. Each one gets its own code so the payer’s system knows which name, address, and ID number goes with which role.

The official name is Entity Identifier Code. It’s part of the HIPAA X12 electronic transaction standards, and you’ll mainly see it in two places:

1. On the claim itself (the 837 file). Every party listed on the claim is labeled with an entity code.
2. On claim acknowledgment reports (the 277CA). When a payer rejects a claim, the entity code tells you which party’s information caused the problem.

Your billing software fills in the first one automatically. The second one is where your team actually has to act.

The entity codes you’ll see most often

The X12 list includes hundreds of codes, but a typical professional or institutional claim uses a small core set. Here are the ones worth knowing, with the 837 Professional loops where they appear:

Code	Who it identifies	Where it appears (837P)
41	Submitter: the organization sending the claim file	Loop 1000A
40	Receiver: the clearinghouse or payer receiving the file	Loop 1000B
85	Billing provider: the practice or organization billing for the service	Loop 2010AA
87	Pay-to provider: used when payment goes to a different address than the billing provider’s	Loop 2010AB
IL	Insured or subscriber: the person who holds the policy	Loop 2010BA
PR	Payer: the insurance company	Loop 2010BB
QC	Patient: used when the patient isn’t the subscriber	Loop 2010CA
82	Rendering provider: the clinician who performed the service	Loop 2310B
DN	Referring provider	Loop 2310A
DQ	Supervising provider	Loop 2310D
77	Service facility location: where care was provided	Loop 2310C

These assignments come from the X12 implementation guides that CMS and payer companion guides follow. Medicare contractor CGS’s guide, for example, shows CSC 562: “Entity’s National Provider Identifier (NPI)” EIC: 85 “Billing Provider” as the rejection when a billing provider’s NPI is invalid. cgsmedicare

The submitter code: who is sending the claim to the payer

People often search for the entity that is sending the claim to the payer, and the answer depends on how you submit. The submitter, code 41, is whoever transmits the electronic file. If your practice sends claims through a clearinghouse, the submitter is often the clearinghouse or your billing vendor, not the practice itself. The billing provider (85) is the party asking to be paid.

They can be the same organization, but often they aren’t. Mixing them up in your clearinghouse setup is a common reason for enrollment related rejections.

IL vs. QC: the one that trips people up

IL is the policyholder. QC is the patient. When a patient has their own coverage, they’re the subscriber, and the claim only needs the IL loop. When a child is covered under a parent’s plan, the parent is IL and the child is QC. Putting the child’s information in the subscriber loop is a classic reason for eligibility rejections, especially at the front desk where demographics are first entered.

Entity type qualifier: person or organization

Right after the entity code, the claim includes an entity type qualifier: 1 for a person and 2 for a non-person entity, such as a group practice, facility, or payer. A solo physician billing under their own NPI uses 1. A group billing under its organizational NPI uses 2. If they don’t match the NPI type, the claim can be rejected even when everything else is correct.

How to read an entity code on a rejected claim

This is where entity code meaning matters day to day. When a claim is rejected at the front end, the 277CA acknowledgment includes a status segment with up to three parts:

STC*A7:562:85

• A7 is the category code. It means the claim was rejected because some information was invalid. (A6 means information was missing.)
• 562 is the status code. It names what is wrong: here, the NPI.
• 85 is the entity code. It names whose NPI: the billing provider’s.

Put together, that rejection says: the billing provider’s NPI is invalid. Not the rendering provider’s, and not the referring provider’s. The entity code tells you exactly where to look.

CGS describes the entity code on this report as a set of unique codes used to identify an entity (e.g, organization, facility, provider, and physical location, individual). Its published examples follow the same pattern: status code 500 with entity code 77 points to a bad ZIP code for the service location, and status code 164 with entity code IL points to an invalid subscriber member ID. cgsmedicare

A practical way to work these rejections

When a rejection includes an entity code, check these in order:

1. Find the loop. Use the table above to see which part of the claim the entity code points to.
2. Compare against the source. Check the NPI, tax ID, address, or member ID against NPPES, the patient’s insurance card, or your enrollment records.
3. Check enrollment, not just data entry. For Medicare, a billing provider rejection can mean the NPI isn’t active in PECOS or isn’t enrolled with that contractor. The fix there is an enrollment update, not a corrected claim.
4. Fix it at the source. If a ZIP code is wrong in your practice management system, correcting one claim won’t stop the next fifty from being rejected the same way.
5. Resubmit as a new claim. A front-end rejection means the payer never accepted the claim for processing, so you send a corrected claim rather than an appeal. Watch timely filing limits while you do it.

That last point is worth repeating: a rejection is not a denial. Rejected claims never entered the payer’s system, so the clock keeps running until a clean claim gets through.

Why entity code errors are worth taking seriously

One entity code rejection is a five-minute fix. The cost comes from repetition. A wrong service facility ZIP code or a mismatched billing NPI in your system will reject every claim built from that record until someone corrects it. Meanwhile, cash flow slows and timely filing windows get shorter.

Practices that stay ahead of this usually do three things. They review acknowledgment reports every day instead of weekly. They track rejections by entity code to spot patterns. And they make sure provider and patient data is correct at intake, before it ever reaches a claim.

When your team needs a hand

If rejections are piling up because nobody has time to work the 277CA reports, that’s a staffing problem more than a knowledge problem. GrowEdgeX’s medical billing virtual assistant services cover claims submission and tracking, denial management, and A/R follow-up, with HIPAA-trained staff working under a signed BAA. Many entity code errors start at the front desk, so our virtual medical receptionist services can help get patient and insurance details right at intake. For broader back-office support, see our healthcare BPO services.

If clean claims and faster reimbursement are the goal, contact our team to talk through where your claims are getting stuck.