An entity code in medical billing is a short X12 qualifier, such as 85, 82 or IL, that tells the payer what role a person or organization plays on an electronic claim. Code 85 means billing provider, 82 means rendering provider, and IL means subscriber. The code does not identify who that party is; the NPI, name, tax ID or member ID next to it does. You will see entity codes in two places: inside the 837 claim your software sends, and inside claim rejections that say something like “Entity’s NPI” followed by a code. This guide gives you the codes that matter on professional and institutional claims, shows how to read an entity-based rejection, and explains how to fix the most common ones.
What is an Entity Code in Medical Billing?
In X12 terms, an entity code is the Entity Identifier Code in the first element of the NM1 segment (NM101). It labels the role of the name that follows. The next element (NM102) says whether that entity is a person (1) or an organization (2). Your practice management system or clearinghouse fills these in automatically, which is why billers rarely type them. Where billers do get involved is when the data attached to a role, such as an NPI or address, is wrong and the claim is rejected.
Key Features of Entity Codes
Identification: They specify the role of an entity in a claim.
Standardization: Used across systems to ensure uniformity in data exchange.
Efficiency: Simplifies the claims process by clearly defining roles and responsibilities.
What Does “Billing Entity” Mean?
The billing entity is the person or organization that submits the claim and is paid for it. On an electronic claim it is the billing provider, entity code 85, identified by its NPI, tax ID and street address. For a group practice, that is usually the group’s organizational (Type 2) NPI and EIN. A solo clinician billing in their own name uses their individual (Type 1) NPI. The billing entity is not always the person who treated the patient. When a physician in a group sees a patient, the group is the billing entity (85) and the physician is the rendering provider (82). If payments go to a different address, that is the pay-to address (87), not a separate billing entity.
Types of Entity Codes in Medical Billing
Entity codes are classified based on the roles entities play in a medical transaction. Below are the primary types:
The table below lists the entity codes used most on 837 professional claims, with the loop where each appears. Institutional (837I) claims use most of the same codes plus 71 (attending) and 72 (operating provider).
| Code | Entity | 837P loop | What to check |
| 41 | Submitter | 1000A | Your clearinghouse or billing company ID |
| 40 | Receiver | 1000B | The clearinghouse or payer receiving the file |
| 85 | Billing provider | 2010AA | Group NPI, tax ID, street address (no PO box) |
| 87 | Pay-to address | 2010AB | Only if payments go to a different address, such as a PO box |
| IL | Subscriber (policyholder) | 2010BA | Member ID exactly as on the card; MBI for Medicare |
| PR | Payer | 2010BB | Payer name and payer ID |
| QC | Patient | 2010CA | Used only when the patient is not the subscriber |
| DN | Referring provider | 2310A | Individual NPI of the referring clinician |
| 82 | Rendering provider | 2310B | Individual NPI linked to the group with the payer |
| 77 | Service facility location | 2310C | Address where the service happened |
| DQ | Supervising provider | 2310D | Needed for some incident-to and supervised services |
| DK | Ordering provider | 2420E | Common on DME and lab claims |
Two common mix-ups: code 87 is the pay-to address, not a billing agent (the billing company shows up as the submitter, 41). And a secondary payer is not a separate code; it is reported with PR again in the other-payer loop (2330B). The full lists are maintained in the X12 external code lists.
Role of Entity Codes in Claims Processing
Entity codes serve as an integral part of claims processing by clarifying relationships and ensuring proper adjudication.
Defining Roles and Responsibilities
- Entity codes clarify who provided, received, and paid for services. This ensures accurate claim submissions.
Error Reduction
- By specifying entities’ roles, codes reduce errors caused by ambiguous or incorrect information.
Compliance and Standardization
- Entity codes align with HIPAA-mandated EDI standards, ensuring compliance in electronic claims submissions.
Coordination of Benefits (COB)
- Entity codes are crucial in COB scenarios, helping determine the order of payment among multiple insurers.
Common Challenges with Entity Codes
While entity codes simplify billing, mismanagement or lack of understanding can lead to challenges.
Incorrect Code Assignment
- The qualifier itself is rarely wrong, because software sets it. The data attached to it usually is: a rendering NPI that is not linked to the group, a billing provider address that is a PO box, a subscriber ID with a typo, or a patient entered as the subscriber. These errors are caught at the clearinghouse or payer front end and come back as rejections, not denials, so the claim never reaches adjudication until you fix it. A good claim scrubbing setup catches most of them before the claim leaves.
Coding Ambiguities
- Ambiguities in interpreting entity codes can cause confusion during claim processing.
Software Limitations
- Outdated billing software may fail to recognize or properly apply entity codes, leading to non-compliance.
Compliance Risks
- Incorrect entity code usage can lead to violations of HIPAA or payer-specific regulations.
Best Practices for Using Entity Codes in Medical Billing
To ensure accurate claims processing and minimize errors, healthcare providers should adopt the following best practices:
Invest in Staff Training
- Educate billing teams on the importance and application of entity codes.
- Regularly update training to include changes in payer policies or EDI standards.
Leverage Technology
- Use advanced billing software with integrated support for entity codes and EDI transactions.
- Automate code selection to reduce manual errors.
Implement Internal Audits
- Conduct periodic audits to verify the correct use of entity codes in submitted claims.
- Identify and rectify patterns of errors in coding.
Coordinate with Payers
- Maintain open communication with payers to stay informed about their specific entity code requirements.
Utilize Clearinghouses
- Use clearinghouses for claim submissions, as they often include built-in validation for entity codes and other claim details.
Entity Codes in Electronic Data Interchange (EDI)
In EDI, entity codes are critical for transmitting data in standardized formats, such as ANSI X12 837 claims.
Structure of EDI Transactions
- EDI transactions include segments where entity codes identify the roles of participants, such as providers, patients, and payers.
Integration with HIPAA Standards
- Entity codes align with HIPAA’s Transaction and Code Set Rule, ensuring secure and accurate data exchange.
Automation and Validation
- EDI systems automatically validate entity codes, flagging errors before claims are submitted to payers.
How to Read an Entity Code Rejection (277CA)
When a claim is reject, the 277CA acknowledgment or your clearinghouse report shows three codes together: a category code, a status code and an entity code. For example, A7:562:85 reads as: A7 = rejected for invalid information, 562 = entity’s National Provider Identifier (NPI), 85 = billing provider. In plain words, the billing NPI failed validation.
| Rejection | What it means | Usual fix |
| A7:562:85 | Billing provider NPI invalid or not on file with the payer | Check the group NPI in 2010AA and the payer’s enrollment record |
| A7:562:82 | Rendering provider NPI invalid or not linked to the group | Link the provider to the group with the payer (reassignment) |
| A7:164:IL | Subscriber’s contract or member number invalid | Re-check the member ID or MBI against the card or eligibility response |
| A8:496:85 | Submitter not approved to send claims for this billing provider | Complete the payer’s EDI or clearinghouse authorization |
Step-by-Step Fix for an Entity Rejection
- 1. Decode it: category, then status, then entity. The entity code tells you whose data to fix.
- 2. Compare the claim to the source: NPPES for NPIs, the payer enrollment record, and the latest eligibility response for member IDs.
- 3. Fix the master record, not just the claim, so the same rejection does not repeat on the next batch.
- 4. Resubmit as a new claim. A rejected claim never entered adjudication, so it is sent as an original, not as a corrected or replacement claim.
5. Track repeat rejections by entity code. A cluster of 82 rejections usually means a credentialing or enrollment gap, not a billing error.
Examples of Entity Code Usage
Example 1: A child’s physical therapy visit
- 85, Billing provider: the physical therapy clinic, with its group NPI.
- 82, Rendering provider: the therapist who treated the child, with an individual NPI.
- IL, Subscriber: the parent who holds the policy.
- QC, Patient: the child, because the patient is not the subscriber.
- PR, Payer: the parent’s insurance company.
Example 2: A patient with two plans
The primary plan appears as PR in the payer loop (2010BB). The secondary plan appears as PR again in the other-payer loop (2330B). Which plan pays first is not set by the entity code. It is set by the payer responsibility sequence in the SBR segment (P for primary, S for secondary), following coordination of benefits rules.
Frequently Asked Questions
What is an entity code in medical billing?
An entity code is a numeric or alphanumeric identifier used in medical billing to classify and identify the type of entity involved in a healthcare transaction. These codes specify roles such as the billing provider, rendering provider, patient, or payer in claims processing.
Why are entity codes important in medical billing?
Entity codes are crucial because they clarify the roles and responsibilities of all parties in a medical transaction, ensuring accurate claims submission and processing. They also help prevent errors and streamline communication between providers, payers, and patients.
What are the types of entity codes in medical billing?
The main types of entity codes include:
- Provider Codes: For billing or rendering providers.
- Patient Codes: For subscribers or dependents.
- Payer Codes: For primary or secondary insurers.
- Other Entities: Such as referring providers or billing agents.
How do entity codes relate to EDI transactions?
In Electronic Data Interchange (EDI) transactions, entity codes are used to specify the roles of different participants. This ensures standardized data exchange, aligning with HIPAA requirements for secure and accurate electronic claims processing.
What is the difference between a billing provider and a rendering provider entity code?
- Billing Provider (85): The entity submitting the claim for payment, such as a hospital or clinic.
- Rendering Provider (82): The individual healthcare professional who performed the service.
What happens if an incorrect entity code is used in a claim?
Using an incorrect entity code can lead to claim delays, denials, or underpayments. It may also create compliance issues, especially in electronic claims processing governed by HIPAA.
Can entity codes differ between payers?
While entity codes are largely standardized, some payers may have specific requirements for how these codes are used in claims submissions. Always refer to the payer’s billing guidelines for clarity.
How are entity codes used in Coordination of Benefits (COB)?
Both the primary and secondary payers are identify with the same entity code, PR, in different loops of the claim. The order of payment comes from the payer responsibility sequence code in the SBR segment (P, S or T), not from the entity code.
What tools can help ensure accurate entity code usage?
Billing software, clearinghouses, and EDI validation systems can assist in applying the correct entity codes. Staff training and regular audits also help reduce errors.
Are entity codes required for all medical claims?
They are require on electronic claims, because HIPAA mandates the X12 837 format and every name loop in it uses an entity code. Paper CMS-1500 and UB-04 forms do not show entity codes, but the same roles still apply in their labeled boxes.
What does billing entity mean in medical billing?
The billing entity is the practice, group or individual that submits the claim and receives payment. On an electronic claim it reports as the billing provider, entity code 85, with its NPI, tax ID and street address.
What does entity code 85 mean?
Entity code 85 means billing provider. It identifies the practice or organization submitting the claim for payment, reported with its NPI, tax ID and street address in loop 2010AA of the 837.
What does an “Entity’s National Provider Identifier (NPI)” rejection mean?
It means the payer could not validate the NPI for the entity named in the rejection. With entity code 85 the problem is the billing NPI; with 82 it is the rendering provider’s NPI, often because that provider is not link to the group with the payer.
What is the difference between entity codes IL and QC?
IL is the subscriber, the person who holds the insurance policy. QC is the patient, used only when the patient is someone other than the subscriber, such as a child covered on a parent’s plan.
Do entity codes decide which payer pays first?
No. Entity codes only identify roles. The payer responsibility sequence code in the SBR segment determines the payment order: primary, secondary, or tertiary, according to coordination of benefits rules.
Are entity codes used on paper CMS-1500 claims?
No. Entity codes are part of the X12 electronic transactions such as the 837, 835 and 277CA. The paper CMS-1500 uses labeled boxes instead, but the same roles, such as billing and rendering provider, still apply.
Final Thoughts
Entity codes are simple labels, but the rejections tied to them stop claims before a payer even looks at them. Learn the handful of codes on your claims (85, 82, IL, QC, PR, DN, 77), read every rejection as category, status and entity, and fix the master record so the error does not come back. Entity codes also appear on the 835, where they identify the payer and payee during payment posting.
If entity-related rejections keep slowing your cash flow, Zmed Solutions’ revenue cycle management services include claim scrubbing, clearinghouse setup and provider enrollment support. Results vary by practice.
Key Market Player
Ready to optimize your medical billing and boost your revenue? Look no further. Zmed Solutions LLC is your trusted partner in professional Medical Billing Services.
Join our growing network of healthcare providers who have already elevated their revenue with our expert services. Don't miss out on what could be your practice's most profitable decision.
Schedule a Consultation Today!
Contact Us Now, and experience the difference. Your financial success starts here!
